 Jai WordPress, that's how we greet each other in the WordPress community back home. So Carol gave me a nice introduction about me, so I will jump directly to my topic. So if this title is not clear enough, let me define the problem clearly. How many people here are responsible for a meetup group, like organizing local meetups, in contributor day, it could be part of local meetup or local WordCamp. So one of the big problems that I face, I believe you might be able to relate it, is that many times we get contributors who only come for first time. So do you have retention problem that people only come for first meetup, but for some reason they don't show up again? And that's the same problem we had back home. And we realized that the people who are not coming, they have their own reasons not to show up again. And one of the, it was confidence as in, they were not sure like they fit into the meetup group, because usually meetup group has a psychological partition. I won't say it's a purposefully done, it's just that the people who come often hang out together and sort of make a group. And people who come for the first time feel they don't belong there, they are not accepted, so they need a little bit hand holding. And then on the other side, people who are confident enough, they were like, okay, I'm sure I can contribute, but whether it's worth my time, whether it's my energy, whether I'm getting in return. And we, after analyzing all these problems, we tried to remove this contributor's block in a different way. So the solution, no, it's not having free pizzas or bread, that would be a tasty solution, but we wanted to do something different. And one idea we tried that in our company, when we are managing projects or onboarding a member, we usually do body programming, kind of organize a sprint. We do it a little bit more seriously and in professional manner, like we love meetups, but they run more casually. So we thought, how if we bring sprints to a translation group or a translation meetup. And with this idea, we organize a sprint, sorry for the wrong emoji, it was not a marathon. It was a software engineering sprint. And the reason for organizing that was like, I found these four things unique about a translation, in general, a sprint, that there is somebody, a senior guy, who is kind of hand holding new person as in helping them learn new things faster, say, for a new contributor, learning Glotpress can be a blocker, it's like they know the language. They can do the translation, but now they have to figure out, Glotpress, while it is easy to use software, but it still takes some time. Then most of the time we organize meetup in a really in a sense to meet. So what is the clear goal? What is we are going to achieve in the meetup? Then as I mentioned earlier, the meetup group often have groups as in old contributor, old timer, who show up again and again, and new people who feel a little bit disoriented. So we try to address all this problem by organizing a sprint, and now as we were planning to do one of our meetup in more formal way, we started preparation much before the meetup, and the part of preparation that we identified the languages we want to address. So this happened when Wordpress 4.6 around the corner, and as Carol mentioned that India has 23 official languages, and I don't think any single Indian can speak all those languages. So we picked the three languages that are popular in our region that we targeted, and for these three languages, we identified the two tasks. We will translate Wordpress core into these three languages, like the Hindi translation was already done, so that task was already marked done. Then there was a Wordpress 4.6 release video that needs a translation for subtitles. So as Hindi translation was done, we had five tasks. Now, again, as I said, we want to make it completely in a professional way. We found five people who will lead only one task, that one person should be responsible for only one task. The one of the feedback I got from the people who didn't show up again, that I contributed few strings, but it took a week for somebody to approve them, so I'm not happy about that. So we set on these five people, because all five of them were global translation editors for respective languages, so they have approval right. So not only they knew the Wordpress, but they can accept strings immediately, and we blocked their time, we got them on board much before the meetup, and we give them clear target, like you are only responsible for this task. So make sure you help your team for this task only. So then as we had RSVP, we sent this plan to the team in advance. All the meetup attendees from meetup.com received this email, where we talked about how we are going to run this meetup. So the goal was set clear. There will be five teams, leads, purpose, task. Everything was clear up front to the meetup attendees. Then can the execution day the actual meetup day? So we started with mentoring first, as in everybody was talked about. We explained the role to every person. We specifically asked all the GTEs to not translate a single string. They should only focus on helping new contributor. They are not supposed to translate a new string, because if that takes their focus away, then the new person might again feel lost and may not show up again. So then we set up a team, and then each team, the senior person helped the new people, gave an in-person walkthrough about the Glot Press interface. So they no need to go through the entire documentation, which is nice, by the way. But this kind of gave them getting started with Glot Press in ten minutes. So after this team work, we spent two hours, and we achieved this first goal for the audience. The idea is to give back first, so the people who came that day to contribute something got a polygode batch instantly, because there were GTEs who can check those strings in real time. Then we managed to finish Hindi-Marathi translation completely in the meetup, WordPress 4.6 core, as well as videos. For Gujarati language, we only managed to achieve 70%, because it was only at 60%, and somebody who worked on translations know that the earlier progress is made bit faster, because people pick the smaller strings, something like save, publish, those kind of strings, and the last 10% strings are the big one. But after the meetup, there was three-day weekend in India. Like for me, it was success. Like this meetup was success at this point only. But those people, they didn't sleep. For the next three days, especially the Gujarati team, they were like, we also want to get to 100%. Why should we be left behind? For three days and nights, they constantly worked on Slack, collaborated among themselves. Almost 90% of these people were first-time contributors. And then these people made it to the 100%. And I think WordPress 4.6 was first released with 50 languages. And the 50th language was Gujarati. And it was added to WordPress core just five days before. Like it was started translation five days before. It made to the core just two days before it's released, the complete translation. So that's the effect of organized effort. Translation sprints can bring to your meetup. Thank you.