 Okay, I'm gonna try to speak louder. Since my first talk, you'll see me crash at some point. I'll just have to reboot then. We'll see. So make XMPP sprint again. It started with an ID that a few people in the community, in the XMPP community had because I felt and other people also felt that we weren't enough visible. That what was done in the open community wasn't enough visible. And so after discussing that with, I guess actually, hi, hi, hi, hi, hi. Yes, oh, I forgot that. I'll start here. I might know my name, Pep, on the XMPP channels, almost all of them. I work at Collabra, free software consultancy. And I'm active in the XMPP community as a developer, mostly client-side development, and server operator, and also do support in a few chat rooms for different projects. Yeah, what, why? So as I was saying, the ID started because a few people thought we weren't visible enough in the community, the public community. And there was quite a lot to improve on every, in every implementation or even protocol still. So we decided to gather together and organize. The first event was, for me at least, was in Karlsruhe in Germany at GPN. And I was there with J.C. Brandt, the author of Converse.js. And Daniel, I don't know how to pronounce his name, the author of Conversation. And we worked on Omimo at the time, the end-to-end encryption mechanism. And from there, we discussed with J.C. that he had similar kind of events in the Plough and Community, the Python Plough and Community. And so I wanted to organize similar events. So that's where it started. In, yeah, and so why? To, well, to improve the ecosystem in general, but also, it was my first event where I got to meet XMPF Fuel. So that was a good opportunity to meet more member of the community. And in general, it's quite useful to get people who know what they're talking about. So you can also implement in your client or serve implementation. And yeah, so transmission of knowledge and for me the best, what I get out of this is motivation. So it's like really focused on two, three days and I can do what I do in six months time usually. Yeah, so this talk is mostly about how for you to organize your own sprints and how to, for these events to become, so I don't have to push you to do it then. So what do you want in a sprint? You want to be able, you want to define what you're gonna do. So what are you, what is a sprint for? Choose a topic or maybe a few multiple topics, depending on the number of people you have. Yeah, so the first sprint we had in Cambridge, there was a few disparate topics, but it was quite focused still. We decided to work on in-band registration so for easier onboarding or there were also a few people working on bookmark conversion, so from bookmark has been a fun story in the XMPV community. So we decided to fix a few things, a few useful things I think. And then for whom our sprint in general are really contributor focused, so we invite anybody who would like to contribute to the ecosystem in general. So, well mostly developers, but also translators or people willing to work on documentation or UX in general, user experience and also give us feedback on the implementations. Yeah, so you're gonna have to decide dates. We generally start thinking, so I know people give the idea that they might want to do a sprint at some point somewhere and then what usually happens is that I push them a bit to start organizing and we make a poll, ask around for any interested people. And so we decide dates are usually one, two months before, not too long before and not too close to the date itself, so people can organize themselves for transportation and accommodation. It's usually organized during the weekend because, well, people might have to take holidays to get to the place and yeah, they might prefer not to do that in the middle of the week. And putting these events closer to bigger events like first time, like we had one on Wednesday. I say Wednesday because Thursday and Friday were the XMPP Summit, so it was all packed together. Might attract more people, so they just have to take holidays for that event, the big event. The venue, I feel the venue is the hardest thing to get depending on, for my case, it was actually quite easy. I just had to ask a collaborator, sponsored the venue for the first event in Cambridge, in the UK, so I could use the office. They also sponsored food, but for others who don't have the opportunity, you could ask for any association around you. I know the last print in Brussels was in some association, I don't know the name of, and the one before in Düsseldorf was in Chaosdorf, one of the CCC local branch, so Hacker Spaces. Or you could even do it at someone's place or Airbnb's or, I don't know, Squats or wherever you can find this place. It doesn't have to be, I mean, it can just be a place to hang around, it doesn't have to be official, anything. But yeah, I can help, I can ask people if ever you have an interest in organizing one, and we can help you find sponsors or anything. Accommodation, transportation is, this might be the hardest bit for people coming to your event. It's gonna be more costly. Not everybody can come and that's fine. Don't force people to come to your event if it's a bit too far. Often it might even be more expensive for people closer to you to come than people at the other end of the world because Ryanair or, so it's fine if not everybody can come. Few possible solutions for that is organizing more sprints in different places, so yeah, around the same theme maybe or not, depending on the interests. Or I wrote video conferencing of the first sprint in Cambridge. JC from Converse.js wanted to come but he couldn't and at the last minute we decided to have something video conference, so it was there and we would communicate through that whenever we had questions or stuff like that. He also did a nice presentation on the client implementation and some details. But yeah, it's now the same experience for the people participants, but it might be useful sometimes. And the activity is what we actually do. Not everybody knows the whole community, so introductions are useful. Then we have some kind of collaborative pads, so we use ether pads or whatever you fancy to document what's happening in the event or even before the event, what people want to talk about, where, when, and any useful detail, what, if you have a new recommendation, as the organizer, if you have a new recommendation for accommodations they could use or anything you can think of before, mostly agenda and what you're planning to do after during the event. So then defining the agenda, we do that generally on the first morning. When we arrive at the place, we spend about an hour talking about what we're here for and really defining what we're gonna do and who is interested in what topic. So we lay out the topics and we count the number of people interested and we form maybe small groups or maybe there are topics that are worth taking time at the beginning all together. The agenda, it's also useful, it might be useful if not everybody knows what is gonna happen in the sprint, the sprint to define the agenda beforehand so they can come and having researched a bit and not lose time doing the sprint. Then we have the fun part, the hacking and discussions. So that's a big chunk of the weekend mostly. And yeah, food and drinks is usually done on the spot. It's not a regular hours. We will go whenever we're hungry or a small group will go to a supermarket to bring back stuff and often it happens on the place, we eat on the place or at night we decide to go out and go for dinner in the restaurant somewhere. Yeah. And the last point is that's one of the most important things I think. Do a retrospective on what you've worked on, how it went and what's left, what's the progress. It helps you to know where you are. It helps the others that might not have been working with you and it helps the community in general to know what happened and how they can help you maybe. Yeah, yeah, then writing about it is also a pretty important point. Once you have all the data you've put in that pad, you can write about it. It helps, it will have promote the events and the technology in general or promote your project maybe or some projects. Thanks to sponsors if you had any or and encourage future events and encourage people organizing more events of this type. And I think that's about it. That's some links for what we've done. And so the first one was at GPM in Karlsruhe. It wasn't technically at that spot. It wasn't really called a sprint yet, but it was the idea. And then the one in Cambridge and the one in Düsseldorf and there's probably more blog article coming. The one in Brussels just was this week's solo. I guess we'll do that soon. And that's about it. Any questions? Thanks for your talk. What do you think is a good frequency for a sprint like this? How often, how far are they apart and was it like too soon or too long? It will depend. For the moment I will, for the moment I don't think doing them too often is a good idea because we don't yet have the resources to do them too often. We might be missing people or yeah, I would like, ideally I would like to have one sprint every six months close to you. Maybe more if we manage to do that but that'd be a good goal I think already. All right. The bridge is made with other protocols in order to, and made by default, the XMPP protocol in some products or so on to sponsor. Even if they aren't ready developments, do you communicate a lot with other promoters of other protocols? Not at the moment but it could be an idea. Yeah, sure.