121
edits
Difference between revisions of "Sprints"
Jump to navigation
Jump to search
m
→Past Events
Vanitasvitae (talk | contribs) m (→Past Events) |
|||
| (24 intermediate revisions by 4 users not shown) | |||
| Line 1: | Line 1: | ||
{{event}} | |||
Developer/community events, designed to gather people and work together to improve the ecosystem. | Developer/community events, designed to gather people and work together to improve the ecosystem. | ||
== Chatroom == | == Chatroom == | ||
xmpp:xmpp-sprint@chat.cluxia.eu?join | [xmpp:xmpp-sprint@chat.cluxia.eu?join xmpp-sprint@chat.cluxia.eu] | ||
== Upcoming Events == | |||
* [[Sprints/2020_March_Berlin|March 2020 Berlin Sprint]] | |||
* [[Sprints/2020_April_Toulouse|April 2020 Toulouse Sprint]] | |||
== | == Organizing an event == | ||
If you are interested in organizing an event in your region, please join the room and talk to us, we might be able to offer some advice, and advertise the event. | If you are interested in organizing an event in your region, please join the room and talk to us, we might be able to offer some advice, and advertise the event. | ||
| Line 11: | Line 17: | ||
=== General structure === | === General structure === | ||
There are no hard rules when it comes to organizing a Sprint. However over the past sprints we have established a loose structure that can act as a template to organize yours. Feel free to deviate off that if you have | There are no hard rules when it comes to organizing a Sprint. However over the past sprints we have established a loose structure that can act as a template to organize yours. Feel free to deviate off that if you have had different experiences with other community sprints or have other wise reason to do so. | ||
==== Date ==== | ==== Date ==== | ||
| Line 29: | Line 35: | ||
==== During the event / Projects ==== | ==== During the event / Projects ==== | ||
Unless you want to host a Sprint that is dedicated to one particular topic (for example MIX :-) ) you don’t have to suggest any topics to work on or prepare anything in that regard. Past sprints have all been BYOP (Bring Your Own Project). See also the | Unless you want to host a Sprint that is dedicated to one particular topic (for example MIX :-) ) you don’t have to suggest any topics to work on or prepare anything in that regard. Past sprints have all been BYOP (Bring Your Own Project). See also the [[Sprints#Participating|Participating]] section. | ||
== | == Participating == | ||
You are also welcome to join if you are looking to participate in one of the currently planned events! | You are also welcome to join if you are looking to participate in one of the currently planned events! | ||
| Line 49: | Line 55: | ||
Usually the sprint days start and end with a quick round around the table where everyone tells the others what they are planning on working on; And end with everyone telling the others what they achieved. This allows people who are working on similar topics to group together. | Usually the sprint days start and end with a quick round around the table where everyone tells the others what they are planning on working on; And end with everyone telling the others what they achieved. This allows people who are working on similar topics to group together. | ||
== | === Who else is coming? === | ||
In the weeks or days leading to the Sprint participants will enter themselves in the wiki page for that particular sprint alongside what projects they are planning on working on. So if your goal is to do inter-op testing with client X, or want to implement a certain feature in your client and know that a specific developer knows a thing or two about that, you can look in the participants section to see if they are coming. | |||
Depending on how well you know that person you want to work with, you might also be able to specifically invite someone to come as well. | |||
=== I’m not a developer === | |||
If you are not a developer you can still contribute to and participate in one of our Sprints for example by improving translations or writing documentation. Unfortunately a lot of the documentation out there - especially in regards to server set up - is mediocre at best and written by people who barley understood what they were doing. Meeting the developers in person and have them sign off on your How-To or give you general pointers on good practices can be very beneficial to the overall quality of the available documentation and can subsequently lower the barrier of entry to XMPP. | |||
Other non-developer tasks that will improve the ecosystem can include creating a curated list of public servers. | |||
In general there are plenty opportunities to participate. Be creative. Bring in your own ideas. When in doubt join our chat at [xmpp:xmpp-sprint@chat.cluxia.eu?join xmpp-sprint@chat.cluxia.eu] and ask if anyone is willing to collaborate with you on your idea. | |||
== Past Events == | == Past Events == | ||
* [[Sprints/2019_December_Leipzig|Dezember 2019 Leipzig Sprint (36C3)]] | |||
* [[Sprints/2019_September_Stockholm|September 2019 Stockholm Sprint]] | |||
* [[Sprints/2019_July_Lyon|July 2019 Lyon Sprint]] | |||
* [[Sprints/2019_June_The_Hague|June 2019 The Hague Sprint]] | |||
* [[Sprints/2019_May_Karlsruhe|May 2019 Karlsruhe GPN19]] | |||
* [[Sprints/2019_March_Berlin|March 2019 Berlin Sprint]] | * [[Sprints/2019_March_Berlin|March 2019 Berlin Sprint]] | ||
* [[Sprints/2019_January_Brussels|January 2019 Brussels Sprint]] | * [[Sprints/2019_January_Brussels|January 2019 Brussels Sprint]] | ||
* [[Sprints/2018_November_Dusseldorf|November 2018 Dusseldorf Sprint]] | * [[Sprints/2018_November_Dusseldorf|November 2018 Dusseldorf Sprint]] | ||
* [[Sprints/2018_August_Cambridge|August 2018 Cambridge Sprint]] | * [[Sprints/2018_August_Cambridge|August 2018 Cambridge Sprint]] | ||