10. February 2021
Last sunday (2021-02-07), we gathered on a public chatroom to start a new collective. In summary, we intend to be a community centered around the needs and desires of end-users and service providers of the Jabber/XMPP network. The complete notes (minutes) of our meeting can be found here.
If you would like to participate in the next meeting, please vote for the next date on our forums (offline). It will take place on the public chatroom on firstname.lastname@example.org. The agenda for the meeting is available on a pad. Anyone is invited to submit points to the agenda before the meeting, or at the start of it.
Our goals as a collective could be summarized like this:
The complete list of our objectives adopted during the meeting can be found in the meeting #1 minutes.
Our collective operates in English because that is the language we all had in common for this meeting. In order to divide tasks among contributors, and facilitate onboarding of new contributors, we split into smaller working-groups:
JoinJabber is a volunteer-run collective. Everyone who is aligned comfortable with our goals is welcome to contribute to any part of our project. If you don't know how to contribute, here's a few ideas.
If you have experience using a specific client, or maintaining a Jabber server for a community, you can make a tutorial for others to get started. You can also contribute a FAQ.
If you would like to help translate JoinJabber resources into your language, please join the chatroom of the Translations Working Group
If you can help with design, we could use:
If you are involved in UX and usability studies, you could review the services deployed by our collective and the clients we recommend, as well as the additional services setup by specific server operators, and formulate proposals to improve things.
If you are a security/pentesting expert, you could help with:
If you are a sysadmin/devops familiar with self-hosting services and Ansible (or other declarative/programmable infrastructure solutions), you may contribute to our infrastructure.
Even if you are not familiar with Ansible, you can review our configuration templates for:
Other systems administration issues you can contribute to may also be found on our infrastructure's bugtracker.