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 Q2 2024 at:
https://wiki.xmpp.org/web/Membership_Applications_Q2_2024
The following XSF members have to reapply:
* Daniel Brötzmann
* Artur Hefczyc
* Wojciech Kapcia
* Guus der Kinderen
* Mickaël Rémond
* Arc Riley
* Paul Schaub
* Kevin Smith
* Andrzej Wójcik
* Mathieu Pasquet
Regards,
Alex
According to my records the following 19 XSF members have voted via
proxy in the current voting period:
* andrzej.wojcik (at) tigase.org
* arne-bruen (at) monocles.de
* bmalkow (at) malkowscy.net
* daniel (at) gultsch.de
* daniel (at) spacecloud.one
* emus (at) jabbers.one
* gnauck (at) conversations.im
* guus.der.kinderen (at) igniterealtime.org
* intosi (at) ik.nu
* jabberjocke (at) jabber.org
* kobit (at) tigase.org
* lbocquet (at) jabber.org
* martin (at) mdosch.de
* neox (at) a-lec.org
* nicola (at) nicfab.chat
* ralphm (at) ik.nu
* singpolyma (at) singpolyma.net
* stpeter (at) jabber.org
* winfried (at) tilanus.com
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
Dear XMPP Summit 26 participants and beyond,
beginning of this month we in Brussels and had another great XMPP
Summit! Thank you all for participation.
I have been asked to follow-up on the action items and encourage to work
on the ToDos. Here we go. I have collected all Action Items I could find
in our pad: https://pad.nixnet.services/D6jfvHjJTTqyAfHd3Z2_Cg
If you want me to create issue, I can do so.
In general, I also invite to sent or add your feedback to the pad:
https://pad.nixnet.services/D6jfvHjJTTqyAfHd3Z2_Cg#Feedback-Summit-26
If something has been fulfilled and I missed it, let me know. Sorted in
the same order we spoke about it:
_________________________________________
# Day 1
## XMPP 2.0 - overlaps with strategy
* review modernxmpp.org[http://modernxmpp.org] landing page (cal0pteryx)
* make modernxmpp.org[http://modernxmpp.org] and compliance suite
more prominent on xmpp.org[http://xmpp.org] (maybe merge modernxmpp and
xmpp.org[http://xmpp.org]) (cal0pteryx)
* write XEP to prepare 2.0 RFC - MattJ if nobody else volunteers
* everyone write a blog post about implementing stuff and/or
contribute to libraries 😉 - singpolyma
## Editor role
* automatically publish xeps from github on merge
* put shell script that checks author in github actions
* singpolyma volunteers to help automate
* potential risk of abuse (already true)
## Discord like spa
* Kevin promises to get the spec written out (for real this time)
## Strategy (marketing)
* https://superbloom.design/ (Formerly Simply Secure) have a team of
designers that obtain funding to help open source projects
* have a way to direct devs and users who land on xmpp.org to the
appropriate places; joinjabber.org, modernxmpp
* Don’t deprecate a compliance suite while keeping the newest experimental
## Audio/Video
* document how we translate jingle to sdp for different webrtc
implementations
* volunteers needed please (Larma volunteered :) )
___________________________________________________
# Day 2
## Read Sync
* Daniel Gultsch volunteers to write the XEP:
https://gultsch.de/files/xep-mds.html
## Device Management
* Matt to submit the 2FA/authorization protocol as a XEP
## IM Routing-NG
* implement it and play with it please:
https://xmpp.org/extensions/xep-0409.html
## Stories
* MattJ to write an xep
## MUC/MIX
* Daniel Gultsch to writeup what he means by using occupant ids
## Action items Summit 25 (Written from Matthew’s memory)
* Write spaces discovery XEP (~Kev?)
* Write spaces admin XEP (~Kev?)
* Try again to implement MIX, provide feedback (~MattJ)
* Update XEP-0317 Hats with Prosody’s implementation, drop the ad-hoc
stuff and focus on display/syntax only (~MattJ)
* WebPush send profile in Push 2.0, incorporate other feedback and
submit (~MattJ)
Dear all,
the XMPP Standards Foundation once again plans to apply for the Google
Summer of Code 2024!
https://opensource.googleblog.com/2023/11/google-summer-of-code-2024-celebr…
Hereby, I call everyone interested to reach out and start planning their
participation. If you are interested please review:
- Read the mentoring guide or at least watch their Youtube videos:
https://developers.google.com/open-source/gsoc/faq
- The time you can really spent as mentor:
https://developers.google.com/open-source/gsoc/timeline
- Your project runs under a OSI approved license:
https://opensource.org/licenses/
- You will require to register to Google's organization platform with an
Google account. However, you don't need a Google mail, just carefully
follow the steps.
- Communicate and reach out in your OWN community too.
- You and your students need to be available continuously through XMPP.
In the recent years I had the experience people being offline and were
not able to reach through their XMPP accounts sufficiently.
Regarding the latter, the stipend also has interest for community
bonding, also to XMPP in general. You shouldn't expect students to solve
difficult implementation unless you know them and their capabilities.
Application starts at Monday, 22nd January 2024, please have potential
ideas ready by then.
Changes to GSoC to this year for your interest:
- "Starting in 2024 we will have small (~90 hour projects), medium (~175
hr projects) and large (~350 hour) projects available to GSoC
contributors. Orgs should have medium and large projects available in
their Project Ideas lists. Small project ideas are not required for
orgs, but if the smaller size project works for your org they should be
included in your Organization’s Ideas List."
Find our wikipage for organization here:
https://wiki.xmpp.org/web/Google_Summer_of_Code_2024
To edit the page, reach out to an XSF member to enter your input or
you’ll need a wiki account, which we’ll happily provide for you. Reach
out in the XSF public chatroom:
https://xmpp.org/chat#converse/room?jid=xsf@muc.xmpp.org
I am happy to hear from a backup org admin to help me here and there or
if I cannot make it due to other appointments. Basic organization skills
should be sufficient.
Let me know if you have further questions. Please join:
Cheers,
Eddie
_________________________
GSoC Administrator at XSF
Dear all,
we have successfully signed-up at Outreachy as community:
https://www.outreachy.org/communities/cfp/xmpp-extensible-messaging-and-pre…
We are slowly getting familiar with the program which differs in several
parts from e.g. Google Summer of Code.
With the support of JMP.chat we have also a funding for one project.
This allows us to apply for Outreachy funding as well.
So, by this message I invite to sign-up with project ideas on our
Outreachy page. Please read the guidelines before you are engaging in
this and make yourself familiar with the program:
https://www.outreachy.org/mentor/#mentor
If you have questions feel free to reach out and I will try to answer
for you.
Other then that, the Google Summer of Code 2024 application is pending
and you can engage in this program, too.
Best regards,
Eddie
Hello,
I've started proxy voting via xmpp:memberbot@xmpp.org on the membership
applications listed here:
https://wiki.xmpp.org/web/Membership_Applications_Q1_2024
We will hold a member meeting on March 5th, 2024 to formally approve the
voting results.
The meeting particulars are:
Date: March 5th, 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.
Alex
I have created the membership application page for Q1 2024 at:
https://wiki.xmpp.org/web/Membership_Applications_Q1_2024
The following XSF members have to reapply:
* Ludovic Bocquet
* Jan-Carel Brand
* Dave Cridland
* Alexander Gnauck
* Daniel Gultsch
* Tim Henkes
* Ali Mattouk
* Edward Maurer
* Daniel Pocock
* Jérôme Poisson
* Jonas Schäfer
* Florian Schmaus
* Winfried Tilanus
* Matthew Wild
* Heiner Wolf
* Nicola Fabiano
* Trần H. Trung
* Arne-Bruen Vogelsang
Regards,
Alex
Hello,
As I've been catching up on the latest XMPP developments, I noticed that the editor mailing list is experiencing a significant influx of spam. You can see the extent of the issue here: https://mail.jabber.org/hyperkitty/list/editor@xmpp.org/
Not sure what can be done to clean and filter that spam more efficiently, but the list is probably not veryt useful as is.
On a different note, I wanted to share that I quite like the Hyperkitty tool. I've been using it to browse emails from the web interface, and I found it very simple (and I am writing this email from it).
I hope this helps,
Kind regard,
--
Mickaël Rémond
