Hi everyone,
Going through the CoC again, I notice that it has a few gaps we should
probably address.
While the current wording explicitly prohibits racist language, there are a
lot of other *-isms which are unfortunately quite present in various spaces on
the XMPP network and which sometimes roll into XSF rooms.
I do not think that we want to be perceived as, for instance, an anti-LGBTQIA+
community, so we should extend the CoC to:
a) send the clear message to the world that we won't tolerate behaviour that,
and
b) give our moderators (that includes me in some places) the necessary holding
to enforce when necessary
Concretely, I propose that we add to 2.4 Be respectful, the following items on
the list of things to avoid:
> - Use of racist, misogynistic, anti-trans, anti-gay, ableist slurs, or other
> derogatory pejoratives for oppressed identity groups against such groups.
>
> - Blatantly racist, casteist, ableist, sexist, anti-trans, or otherwise
> offensive and bigoted discourse.
In addition, before the list of things to avoid, I would like to add:
> Respect others requests for space. That includes to disengage from a
> discourse if your partner(s) indicate that they do not want to discuss a
> topic any further. It is not easy to let someone be "wrong" on the internet,
> but boundaries are there to be respected.
To section 2.5 ("Be friendly and supportive"), I would like to add after the
first paragraph:
> This includes being mindful of the abilities of others; nobody is born an
> expert in anything and we all had to learn at some point. Be supportive of
> newcomers and learners. Do not be patronizing or condescending.
I may propose a PR against XEP-0458, but before doing so I wanted to offer
this for discussion on this list.
kind regards,
Jonas
I have created the membership application page for Q3 2024 at:
https://wiki.xmpp.org/web/Membership_Applications_Q3_2024
The following XSF members have to reapply:
* Travis Burtrum
* Martin Dosch
* Severino Ferrer de la Peñita
* Timothée Jaussoin
* Konstantin Kozlov
* Bartosz Malkowski
* Tobias Markmann
* Ralph Meijer
* Edwin Mons
* Emmanuel Gil Peyrot
* Peter Saint-Andre
* Holger Weiß
* Natalie Wirth
* Marvin Wissfeld
* Trevor Krahn
Thanks,
Alex
Might be worthwhile.
<https://digital-markets-act.ec.europa.eu/dma-call-tenders-study-interoperab…>
--
Normally there is some text here, bragging about the new phone and excusing for the brevity. That is insane: if this phone was really that great, I would have sent a decent mail.
--
Normally there is some text here, bragging about the new phone and excusing for the brevity. That is insane: if this phone was really that great, I would have sent a decent mail.
Following up on the June 6 board meeting, I've created a wiki page (or
at least a stub) here:
https://wiki.xmpp.org/web/Organization_Proposal
I've also initiated a discussion on the email list for open-source
foundations, which has been quite helpful. I plan to talk in the next
few weeks with the director of an organization that moved from the U.S.
to Europe some years ago. I'll update the wiki page as I learn more, but
others should feel free to edit as well with questions and preliminary
findings.
Peter
Dear all,
today I looked at the extensions web overview which we have improved in the recent time. Special thanks to Daniel B. again.
https://xmpp.org/extensions/
I would like to enhance the filtering with tags or categories to help developers when implementing the protocol. That way a quick selection of relevant XEPs dependent on the implementation purpose could make onboarding easier. All this may be clear to you, but is not to others and interest third parties. Currently they get a numbered list, but no focus or priority nor importance.
For example, one could filter for the latest compliance suite and its relevant XEPs. Or which are important around A/V implementation. Which XEPs are part of base and advanced implementation? Which is related
And maybe you have many more better ideas to help and guide people.
Theoretically, we have the solution already: Using tags. However, only one of the XEPs has tags so far:
https://github.com/xsf/xeps/blob/master/xep-0488.xml#L25
So, if you agree and maybe also have ideas and/or suggestions I would call to update the most relevant XEPs.
If we have more tags we can also offer them as filter selections right away.
Let me know what you think.
Eddie
I've started proxy voting via xmpp:memberbot@xmpp.org on the membership
applications listed here:
https://wiki.xmpp.org/web/Membership_Applications_Q2_2024
We will hold a member meeting on June 6th, 2024 to formally approve the
voting results.
The meeting particulars are:
Date: June 6th, 2024
Time: 19:00 UTC
Location: xmpp:xsf@muc.xmpp.org
When you have problems with memberbot please contact my directly by
email or xmpp.
Thanks,
Alex
According to my records the following XSF members have voted via proxy
in the current voting period:
* flo (at) geekplace.eu
* gnauck (at) conversations.im
* guus.der.kinderen (at) igniterealtime.org
* jabber (at) larma.de
* kevin.smith (at) isode.com
* lbocquet (at) jabber.org
* linkmauve (at) linkmauve.fr
* mario (at) sabatino.pro
* martin (at) mdosch.de
* mathieui (at) mathieui.net
* nicoco (at) nicoco.fr
* nicola (at) nicfab.chat
* root (at) nicolosus.chat
* stpeter (at) jabber.org
* tim (at) mailbox.bz
If you have not yet voted, please send a message to
xmpp:memberbot@xmpp.org.
If you have problems with memberbot please contact me directly by email
or xmpp.
Thanks,
Alex
