Thanks, everyone. This is the Chicote Africa Contributon Retrospective. It's the 7th of May, 2021. We're going to discuss and identify things that went well, things that went poorly, and what we can do in our next event like this to assist it to go better. Thanks to all of you for being part of it. Thank you for being active and participating in the Jenkins Project. I'm gonna go ahead and share my screen and we're going to look at that as a way to sort of guide what I propose. So here's my proposal. Let's move that out of the way. Whoops, there, okay. So what we've got on the right-hand side of your screen is the original task document that we created. And thank you to all of you that have made comments in its retrospective section. So this is, we see comments from Cynthia, from Sharon, from Oninye, from Angelique. I know we've got comments from Kristen in here and from others, so very, very grateful for those. I think what we should do today is take this left-hand document and my proposal is I'm gonna make this bigger so we can read it together. I think we'd like to review the results, the processes and the behaviors of the project to identify specific actions that will improve future projects. We're going to, in this session, work from the assumption that everyone was working with good intentions and that they really wanted good results. And we're going to identify things we can improve and do it in a way that we acknowledge when something didn't go as well as we wanted, but we're not gonna place blame, we're not going to, this is just about trying to find the next things we will do that will help us improve and be better. Therefore, I think what we ought to do is take a look at what some of the highlights were that were commented on, obstacles that were encountered and invite some of you to comment on those obstacles, what you encountered as challenges, what problems you had, et cetera. Then, after hearing a brief description of problems and challenges, we can talk about what actions we should take and I'll try to capture those actions into a plan for actions. Does that work okay for everybody? Yeah, that's fine. Okay, so here are some of the new contributor obstacles and here are some of the mentor obstacles and some of the what could we do better topics. So I think what we ought to do is, let's take a brief moment, would one or more of you be willing to share obstacles you encountered as a new contributor or topics that you think, let's be sure we address this in our retrospective. Oninye, maybe what we could do is have you go first and then we'll take, actually, no, how about we go in the order of text here? So Sharon will ask you to go first, then Esther and then if Lucy's with us, we'll have her do it then Oninye and then Cynthia and please be relatively brief. We want to hear your voice about which things do you think we should focus on in this retrospective to help us improve. So let's see, Sharon, I think you're here. Now I can't see my participants immediately. Yes, so Sharon, would you like to go ahead? Sharon, I'm afraid we're not, I'm not hearing you. If others are hearing you, I may have an audio problem. No, I can't hear her either. Okay, so Sharon, you may have an audio problem rather than lose time. How about Esther, would you be willing to go next and give us just your insights, your recommendations, things that you would like to highlight either from the text we have here or something that's come to you since then? Nothing new except the things that I already said before. So I had an issue with Jenkins to start. And apart from that, I've seen my mate of couple was standing in Jenkins's back. So... Okay, so it was understanding Jenkins as a product? Yes. Okay, good. And I think... I'll use it, yeah. Great, and that I think fits with this comment that you had made here, right? Familiarize yourself with the platform early. And that may also fit with weekly goals. So set timelines on goals. Might have, good. Okay, excellent. Thanks, Esther. Okay. Then next voice was, let's see, Lucy. Yes, Lucy, you're here with us. Lucy, would you like to highlight a key point that for you, you would say, well, this would have been a significant improvement or it would have been better if we'd done this? Hi, everyone. So... On my side about the obstacles that I had. Okay, definitely this was my first two-pencils project. Yeah, I was having also the things that I was doing to say. So the challenges that I had initially were mostly... I remember the first few weeks, I think the second, the first one, I had the mission installing Gen Kings and all those things that we're supposed to install for everything to run. It was really a challenge because I was using a bone tool. I don't know. But then I was helped and I was able to sort out that and to catch up with the rest of the people. Then another issue, this was quite a challenge to me by the way. It was the fact that the time difference, but yes, it's understandable. But then I had... It was really so bad on my side because some meetings I used to... They used to happen very late in the night, like quite late, yeah. So I was finding it very hard for me to join up because maybe then any... Just some things used to happen around there. And it was a challenge. Thank you. So there was a scheduling thing and in some summaries, I had not captured that one. So let me put that there are improved communications by identifying times that each participant can be mentored. So we had tried the approach of a combined meeting where everyone could be mentored. And that meant that there were times when you couldn't attend. Thanks, good insight. Okay, not just solely group mentoring. Excellent. Okay, thank you. Anything else that you wanted to share there, Lucy? Maybe a proposal. There was something about... Especially for the fact that most of us were... Okay, myself I had come across as a king at some point. But then I'm considering the fact that most of us were not familiar with almost anything to do with it too, yeah. So, plus the whole open source was a new thing. So maybe we would, okay, I understand that was already in place, but if it would be something like tutorials, sometimes in a while, that the mentees could follow up, then plus there would be something like a catch up just like after... At the end of the day, we maybe not really have a meeting, but to get to discuss whatever each mentee have been able to handle the whole day, during the whole day and even the challenges that they've gone through. Very good. So I think you're echoing the same observation that Esther made that a tutorial in the early stages would have been a real benefit. Did I capture that correctly? So I think it was, let's see, and where I had it here. Oh, yes, include self-paced training courses in the task document. So this one was, I think that's trying to capture what you were describing and what Esther was describing. So a sure, successful startup by assuring completion of the course. Because there are courses. Linux Foundation offers a course, Cloud Beach University offers a course, and they're both free. We could have used those and we did not. Very good. Thanks, Lucy. So next was, next was, Oninye. Yeah, good day, everyone. Hi, everyone. To add to what my fellow mentees have said. Okay, on my own end, I didn't really have much challenges, probably because I used iOS, yes, because it was much, pretty much straightforward. Yes, and I also used real. So everything was just straightforward, yes. The only challenge I had, which I pointed out on the document was the fact that the PR, some of the PRs I used, the maintainers were not nearby to review, so I would actually suggest if it's possible to maybe alert all, let these other maintainers, let them know, give them the awareness that there will be some PRs from social so people, so they will be aware, because I'm not sure they were aware that we were supposed to contribute to their plugins. Yeah, so if they will be informed before we start, or maybe when we start, or if that's not possible, if we can strictly work on plugins that are managed by cloud groups, that we have the maintainers available that could actually quickly help us to review, that would be better. Yeah, so that's the amount, thank you. Excellent, so I tried to capture that in, let's see here, it was increase pull request, review and merge pace by not selecting plugins unless the maintainers have agreed to a prompt review. So that was a mistake that we made. I used a prioritization exercise to prioritize the plugins with the most comments, but then failed to ask the maintainers, will you commit to review promptly? And even worse in your case, one team of maintainers has had ongoing challenges for us in general. We put you on the Artifactory plugin and we've struggled with it in the past. So we really did not give you the best chance for success by doing that, and yet you did wonderful work on it. Good, yes, thank you. Okay, anything else on Yinye? No, that's basically all from my answer. Okay, Cynthia, would you like to go next? Yeah, thanks. I actually feel like they've said everything. I was going to also mention about code reviews, but also I had challenges with some, the meeting that we're having on Friday evening, sometimes they were taking long, which were affecting the people that I stayed with because they had to sleep. So I'm not sure if it's possible to have them, actually this time works for me well, but I'm not sure with other matters, but yeah, it would have been better to just have it earlier so that in case it takes longer, then it would be fine. Yeah, that's what. Good, so my interpretation of that was, let's see, we had it here, which was not just group mentoring, the attempt to use group mentoring was an attempted efficiency that I suspect we could have achieved the same results by having one-on-one mentoring with one of the mentors and each individual without doing a large group meeting, good point. All right, so now, and Kristen, I think you've got experience in this area where in Google Summer of Code, the typical mentoring experience there is focused on an individual, right, on one person. And so maybe that's a model we want to consider in the future rather than trying group mentoring like we did here. Yeah, I think we originally thought that this would be something that we could do more, maybe collaboratively or maybe even just kind of have like sessions where we all kind of, it's more like a hackathon, then it ended up being like, because it's so hard to coordinate, to coordinate multiple time zones and more people, the harder it is to find a good time, with everyone, it's, you end up finding the average time, which means it's like only okay, it's only okay versus maybe the best time. So maybe it's, we could work on maybe doing more things asynchronously and then try to focus one on one. I, yeah, I think we had, we thought it was gonna be more hackathon-ish than it ended up being, so. Right, right. Your point is good about more async work. I wonder if what we ought to consider is, should we say we'll do one group meeting a week, because I think there are some things we need in a group meeting. The group meetings that started the week were helpful to set framework, to set expectations, to do process questions, but then the technical sessions should probably be individual focused with others welcome to attend. Anyone can attend, but we'll do focus on an individual. I mean, Mark, I love this session where you basically went through and you started like, you built Jenkins Core from scratch. I mean, that was kind of nice and that's a good thing to have in a group session as well too, because it's just everything all together and we could ask questions or we could look at stuff. I thought that was nice, but it was hard for me personally because of things on Monday, probably you too, because it was in the middle of my, like in the exact middle of my night. So it was a little bit harder for me to attend that meeting. But it is good to have, like I do like the idea of having it as like a, here's what we're doing, hey everyone, this is week one, week two. And then, like Lucy you were saying, it was hard for you to attend as like the hours. And I think, yeah, it's just, yeah, easier to have individual sessions later in the week. So what do you think of this idea? If we were to identify themes for meetings and say this meeting is a group training session, we're going to share, we'll do the recording, we're going to focus on things that we think everyone needs to know or have things that are instead an individual mentoring session where anyone is welcome to attend, but we're focusing on mentoring for this person. Would that, do you think that would resolve it? Would that help? I'm gonna assume, yes, Kristen. So that idea might be feasible, good. So now there was a comment on more async work and I think that's a theme that we might want further exploration on. It's something that I hadn't seen many comments on in the feedback, but was curious if there are ideas of ways we could have done this more asynchronously for better results in the end. Maybe what we need is a group training session on preferring async. Let me think about that. Okay, just noted. Okay, so now I wanted to look at some other topics, the obstacles encountered by mentors in here, mostly I'm looking for feedback from our participants from the mentees on if some of these were particularly important would have been particularly valuable to an others less so. So could each of you look at this list and for instance, give, choose one or two that you're ready to say, oh, yes, that could have helped. So here's one on early morning meetings. Well, so I'll let you do the reading and I'm going to give us just a minute or two of quiet while you read. And then I'm gonna rotate through each of you and see if there's one or two of these topics you would like to highlight. Oh, sorry, Mark. Can you hear me? Yes, go ahead, Oninye. I didn't get that, please, go ahead. So what I would like each of you as participants to look at this list of obstacles experienced as mentor and what could we do better to see if there are things in there that I might have missed of, oh, we should do that. So Oninye, one that you highlighted was interact with more people in the community. And that's one I think may need more discussion. How could we achieve that? That's the kind of thing that I'm looking for this phase of our discussion. So review these sections. Let me paste a link to the document into the chat so that you can each open it. So where is the chat window? Chat, chat, chat, here we go. Okay, so here's the document and what look at obstacles experienced as mentor and at what could we do better and give insight. So one that Oleg had noted here is promotional things that I had not captured. How do we assure that more people are aware of this, know about it and are ready and willing to help? So those are the kinds of things you're looking for. And then we're going to loop through each of you as participants and ask for your insights. Did that explanation come through Oninye? Okay, thank you. All right, hopefully you've had time to do that review. So let's go back to, and we're going to take a slightly different order this time. I'm going to go based on what I see in the list. So Cynthia, would you be willing to be our first voice then Esther, then Lucy, then Oninye? Anything that you detected, Cynthia? Oh, go ahead. It looks like Esther, Cynthia, anything you detected that you would recommend? Oh, let's take this thing, idea from the what could we do better and be sure it's in our summary. Okay, so from what we could do better, I think it's the same thing Oninye mentioned of interacting with other people, maybe having, I don't know, ice breakers. I feel like it helps a lot to just know the people that you're with. Also, as mentioned, maybe having like a theme for each meeting that we get to have, maybe say that oh, today we're going to learn this thing or maybe you're going to learn about code reviews. We're going to learn about some gift commands. I think we'll be good just having some mentoring session. Yeah, we'd like a topic. Yeah, that would be good. Yeah, I think that's it for me. Excellent, thank you. Esther, your comments. Going through the documents, I would say interaction between, I think Kristen's observation interaction between participants and mentors and participants and guidance on how to research topic and step. So I think I'm most, I think Cynthia I remember last what she said about when having the meeting to choose something to learn, something specific to learn, yeah, that would be great. Good, okay. Well, and I see here a comment that you had made, breaking tasks into weekly goals. I had not, I was uncomfortable doing that but I think it's a very good idea. And I had not captured that. Do you mind if I put that up in the top level of that, let's see, I'm not sure. Well, maybe it's use weekly goals. The worry for me when I did it was I wasn't sure how fast each of you would be able to adapt. And I thought some of the things might take several weeks to do and none of you took several weeks, none of you. So it was a complete misunderstanding on my part, but set weekly goals. Right, yeah, I said I wrote that because I figured that sometimes I spent too much time on one thing and that I was not really moving at the fast pace and moving forward, so to speak. So it just made me fall back in a way. So it was a way for me to know that, okay, at the end of the week what I should have achieved then that would be, that would be cool because there was no goal. So it was just basically just following it and then at your own time and pace and sometimes you might fall back, so. Very good, yes, okay. And so what the idea there is we have milestones and we say, hey, if you only did a part of the things to get here, you're still, we've reached this milestone, let's go to the next thing. Very good. Okay, all right, so next I believe was, let's see, so we had Cynthia and Esther, so Lucy, would you like to be the next voice? Yeah, it's okay. So on my side, many small repetition or whatever my colleagues have just said. So first I feel like there was very minimal interactions between the mentees and the mental, so something will be done about that. Then too about the, yeah, timeline for the task, I think we should, maybe we should have, there should have been goals, like, so that after one is not able to go beyond whatever the second goal, then they can be helped like a solution can be, can be found for that. Then I was also feeling like maybe the whole, whole program will have taken longer because within the first few weeks, most of us use the time to even familiarize themselves with whatever we were supposed to do. So maybe time will be taken much longer so that we get to, people get to settle and even work within the, okay. So just to be sure I've understood, so one of your observations is, should we consider instead of a one month, do it a longer period for six weeks or for eight weeks? Is that what you were saying there? Yeah, yeah. Okay, and that's one I had not captured. So I, for me the, okay, consider a longer, longer project duration for better engagement, better experience, good, okay. And I think we had captured your notes on the weekly goals and that way we have a clear, you should be here by end of week one. Good, all right. Let's see then, on Yenye, I think your next voice. Okay, yeah, so just like I mentioned, personally, I love meeting people, I love networking. So I feel, okay, on the Slack channel we're all added to, there's a general channel there, that's the CDF Slack channel. If we're actually introduced, because I feel we're just isolated in one group like that and nobody knows that this set of persons are existing here. So I feel if there was a little bit of introduction, oh, there's some guys here that are here to do this and they welcome us and maybe we introduce ourselves, it's a large community. So I feel it will give us a bit of sense of belonging and also we could meet people there, we never can tell. So that's for my own, and if there is a way you can consider trying to introduce us to the large community, yeah, that's it. And that one for me is a challenging one. So I wanted to take some notes there because the Jenkins developers, I would say they don't have a chat channel that is heavily used by Jenkins developers, a single chat channel. What they have is a mailing list and separate chat channels for sub-components and subsystems. And so it's an interesting challenge, right? So even on Gitter, we don't have a single chat channel that's dedicated to it, right? It's really, there's a configuration as code plug-in channel, there's a git plug-in channel, there's several others like that, the cloud native group chats on CDF chat. Kristen, go ahead. Yeah, and it's like, I don't know, Mark myself, like I don't even know of a Slack channel for Jenkins. Actually, it was ironic because like I know of IRC and it's like if you wanted to go really retro with everything, there is IRC for Jenkins, but again, it's not everyone is on there and it's gonna be, because it is IRC. And it's going to be more of like, there's the general Jenkins channel at least to me is sometimes more like user questions versus developing or like using Jenkins versus like Jenkins development. So it is a little bit harder to find everyone, but and so it is usually easier like Mark was saying to find like the individual Slack chat channels based on what you're, based on different pieces, but if you, or I guess if there was a general question, it would just be in the user's channel and someone would be able to jump in and help, but yeah, it's, I think I don't, you know, different open source projects operate in different ways and this is just kind of how Jenkins operates. So I wondered, should we have, should we have introduced the team, the project to the developer mailing list at the start? And that way we at least could have had assured that each of the participants was invited to and participate in the developer mailing list. The challenge is the developer mailing list has a relatively high expectation of deeply technical content being placed there. And my worry initially why we didn't use the developer mailing list is because first-time developers like you were for the, for much of this project would likely find that developer mailing list uncomfortable or, oh, hey, we wanna have a conversation separately outside the list like we did in Slack. So yeah, I'm not. That's true. That's a good point. Sometimes it can be very technical on that list or it's talk, yeah. But it might, it might be, maybe do like in just a general introduction thread. And just as, because even like the Google Summer of Code has its own list, which is what's difficult there, but you could just do a, hey, this is like almost like a notification that this is happening. Or just another way to get the information out to people who could potentially be reviewing. And then maybe in that thing call out some of the first pieces that we were gonna work on. And so that way there was at least a little bit of a heads up, but you're right. It is kind of, I'm not, maybe that was, it's just like good to do an introduction, but it might not have been as helpful for getting, like getting started in development. Does that make sense, Mark? I think so, yeah. So announce would feel really good. And that would have at least introduced on Yenye to, and Cynthia and Esther and Lucy and Sharon to the Jenkins community and to the developer community specifically. So that's very good. All right. Sharon, sorry that we haven't heard from you. Could you try unmuting? And let's see if we'd love to hear from you if your audio is working. Okay. Hi everyone. Sorry, I had some technical issues at the start, but I'd like to say that the entire experience was good. I appreciate what you did for us, like helping us through the process. For me, I think I'll just say like the rest. I spent a lot of time at the beginning of the tasks, not knowing that it was much easier that I could have moved forward. So if we could have the goals, it would have been much helpful. And then for my case, the way I had that technical issue, I'm not sure if in case someone has something like that, is it possible to assign something like working on docs that doesn't have to work with the technical things? Ah, so your suggestion there is, should we consider being able to redefine the project or reassign if there was some unexpected barrier for one of the participants? Yeah. Good insight. Okay. So that one is that sort of a wildcard thought. Let me see, how would we say it? So it would be something like improve startup shut down by identify technical issues for participants, assign a mentor to assist with resolving the issue. Or if the issue can't be resolved, redefine the project for that contributor, that participant. Does that capture what you were saying, Sharon? Yeah, yeah. Okay. Good, all right, interesting, thank you. Okay, all right. Anyone else have insights or things that we may have missed on this? I wanted to, before we conclude our session, go through the proposed actions and then let's see if we missed something in the proposed actions where you say, no, this is something, oh, we should have done it. And we'll then add those as well. Okay, good. Then what I put as improvement, so I've tried to frame these improvement actions as a goal and an action. So I think the goal is to improve communications and one technique is in the task list require a chat posting from every participant and every mentor at the start of the project. It may seem sort of minor, but it was really quite awkward that one of you, actually one mentor and one participant didn't get into the chat channel until several weeks late because we just didn't do this. So sorry and thank you for your patience with that mistake. Then to use, to take Cynthia's suggestions, introductions at the start of meetings, ice breakers to assure we know each other. So, and now this is one I had inserted here, have each participant briefly share results in a meeting. That's synchronous, not asynchronous. And I wonder if, would that have helped or should I just delete this? I feel that's okay. Because it's a look, it will sound like a stand up. Yeah, it's okay for me. Okay, all right. So yeah, that is sort of a mini stand up, right? It is a stand up status. Yeah, good way of describing it. Thank you, okay. And then identify times when individual participants can be mentored. I think we've heard that from several people. That's a good way to avoid having a problem with multiple people not being able, or one or more people not being able to attend a group session. I don't know what to do on the more async work here. I'm prone right now to just remove that and think about it separately because I think it's a more general topic. Okay, then increase communication between participants and mentors by identifying themes for meetings. So group training or individual mentoring. Okay, and we've got ice breakers there. Oh, right, so that's, oh, good. Okay, so actually we've already got this here. Okay, in all meetings, okay. And include topics of interest. So should we identify common topics to consider for group training? So for instance, get operations using get effectively. I think Oleg had done a good session on that or compiling Jenkins. That was one that I think I did. Jenkins core and a Jenkins plugin. With that, I think that would be helpful there. The next proposal was decrease participant startup time by including self-paced training courses in the task document. So my thought was you shouldn't need to start the self-paced training until the project begins because the project was intended to be specific time but this could have been one of your first things. Instead of us just telling you, oh, do this little tutorial, we could say take this self-paced training course accepting that you may only get through part of it. Then the next piece was increase pull request review and merge pace by only selecting plugins that we have maintainers who have agreed to promptly review and ask the, each submitter to at reference all, I shouldn't say reviewers, all mentors in each PR. That was one where Esther had submitted some pull requests and I was the only one and I dropped the ball. I failed to do what I should have done. And if we mentioned all mentors, there's a better chance someone else will be able to help. Okay, then recruit plugin maintainers, announce. Oh, go ahead, yes. Okay, so if there is a label, it can be add into the pull request, specifically for, to identify our pull request. That would help also to add labels to our PR. Yeah, I thought that pull request submitters didn't have permission to add a label in general. So I like the idea. I think it would be good to have, and maybe that's an even better idea on Yenya is create a GitHub report that shows all participant pull requests to all Jenkins repos with that. Because I don't think I don't, at least Kristen, can you help me there? I think that labeling of a GitHub pull request requires that I have right permission to the repository. Let's see if I grab one, for instance, a the workspace clean, no, let's see, which, oh, build steps plugin. So let's get the build steps plugin. I don't have pipeline build steps. So if I look here, I don't think that I can actually apply a label to a pull request. So, yeah, see, I don't have edit permission to do that. And I don't think even the original submitter can create a label, but would a GitHub report meet the same need? Sure, I mean, I think also that would have been helpful too, is that if you made a pull request to like post it into the, so I know maybe it turns to spam, but to like post it into the Slack channel. I think that was actually like Oninye, like Cynthia, you guys started doing that later and that was incredibly helpful. Because I was like, oh, okay, now I can see that there's a pull request and or it's helped me at least, at least for me it was like super helpful when that was happening, because it allowed me to be able to see, oh, there's something new right now, I can go make sure I don't miss it. Because in GitHub, you can, especially if we weren't tagged explicitly, so thank you to everyone who did like tag me, because what I can do is you can go to GitHub and then you can see specific pull requests that you've been asked to review. But for me, at least like it gets mixed in with things that I'm reviewing for work or other pieces that, you know, other open source projects. And I'm not sometimes as good about checking that, but if it was like an email, or like, you know, where I'm added and I can see it to an email or in the GitHub, or the, sorry, the Slack channel, it was very easy for me to go, oh, okay, I really, I need to make sure I can review this. I noticed like, pretty much like Angelique, Meg, Mark, you were all really, all really good about, yeah, as soon as something went in that channel, people were responding very quickly. And sometimes even when I went and was like, oh, I just saw this and I clicked, it was already reviewed, which was very helpful. So I really appreciated when y'all did that and it might have maybe helped a little bit earlier too in the project for, we can make that suggestion early, like please let us know where you are. And that way we can help you as quickly as possible. Well, and that fits with this sort of heightening improving our communication by better using the Slack channel. Good, very good, thank you. Excellent, okay. So then next goal was increase community engagement by recruiting plug-in maintainers. So that's something before we ever start the project, announce it and yeah, announce it. Then this one, project startup. So the initial project startup was kind of bumpy, one because we started on a day when we didn't generally meet together. I think we started officially on a Saturday or and so first meeting was several days later and that feels like a really healthy thing and weekly goals. Now, how would you as participants have dealt with if I had done a bad job of defining the weekly goals and said, I think the first three tasks should be completed in a week. Would that have been destructive to your feeling of accomplishment? Would that have been demotivating? I worry sometimes when I set goals that I'm just guessing. If I had done this, but done it very badly, would that have been much worse than not having goals? Yeah, I think it's kind of like a 50, 50 thing because on the other hand, if you set goals then you might kind of rush participants and then might end up not really gaining anything because all they just want to do is finish their goals and they're not really getting a feel of the platform but then on the other hand, it could help them be focused. So I don't know. I wonder, Esther, maybe what you've inspired here is goals, goals should include, what if we said goals should include communication goals and interaction goals, not just code accomplishment goals. Because one of the things that Oleg reminded me of when we started was that the bigger picture goal of this project was not to improve Jenkins Pipeline Help. The bigger picture of this goal was to have add five new people who were more comfortable contributing to open source projects. So maybe if we stated the goals in bigger terms, they would be more likely to be achieved and we acknowledge, yes, we're using this technique, build a Jenkins plugin as a way to help prepare each of you to contribute in some open source community in the future, whether Jenkins or elsewhere. That's perfect. Sorry, go ahead, Oninye, say that again. Say that's cool, that's perfect. Okay, great, all right. So remember the project goals, the Shikode Africa goals, not just the Jenkins project goals, right?  Good, okay. Consider a longer project duration. So this one I'm leaving here, but I have to acknowledge that I think we chose exactly the right duration for this one because we avoided a collision with Google Summer of Code. If Google Summer of Code starts for me in I think less than a week now, it may be, no, it's 10 days. And that will take me away so I wouldn't have been able to mentor. So if this project had been declared to be two months, I would have had to say no and the project wouldn't have happened. So this one I'm leaving, but it's a compromise with need to not lose mentors because we lengthened the project. Good, okay. And last point was identify technical issues and assign a mentor. All right, any others, we've got only five minutes left. Any others before we call this retrospective done and we'll take those as planned actions? No, I don't think I have any comments. Oh, and I didn't even touch on the practices to retain. Maybe we could do that in the last few minutes. Just so, mentoring sessions, weekly session for the whole group, individual session, if we said individual session each week between a participant and a mentor, is that, would that do you think have been better than our attempt at two weekly group sessions? Yeah. Okay. So maybe that's not even a retain. That's a- I have a question. Yes, please. Was the proposed standup meeting among the mentees alone or with the mentors? I was assuming it was with the mentors. Good question. What would you recommend as a group? So I thought that this was share in each group meeting, but you're right that if you did it just as mentees, you could do it probably at much broader range of times than we could, because of my distance from you in time zone and Kristen's distance from you in time zone. That's gonna be okay too. Okay, so I mean we could, I wasn't sure if the mentees had convenient access to a way to get together. And so I, but it's a good question. Should we have a mentees standup every day or every two days? Yeah, that would be nice too. So I'm not sure if each of you were actually able to work on the project every day, because I wasn't sure that, I assumed that you were maybe putting 10 hours a week or 15 hours a week in and some days you wouldn't work on it at all. But I'm open to that. Should we discuss at the start of the project, how frequently you do, persistence or do you stand up? Sure, and it can even probably be helpful, especially if you're y'all are talking post something on the Slack channel. Very into trying to almost over communicate because I think I've put in a lot of things. Sometimes it was hard to, it felt like it was hard to track where everyone was. And so yeah, meet up, you can all talk to each other and actually that would probably be really great. Cause then if you have any questions, it might be faster to ask someone else who's working on something rather than wait until one of us is available or just if it's over the weekend, just post. But yes, just yeah, I can't emphasize enough. I know it's sometimes it could be intimidating or anything, but it's like if you, we're all here to, if you have a question, just ask or if you're blocked by something or confused, we're here to help. So yeah, the results that's asked, we didn't give you posted or just kind of this is what I'm working on today.  I wasn't planning on working today, but maybe check in tomorrow. And then that way everyone kind of know where everyone is and maybe kind of even enables a little bit more. So again, so we're also not fighting for, you know, middle of the night, trying to have a meeting together for either middle of y'all's night or like our night is just, it maybe helps a little bit more for, it doesn't hurt to over, over share, especially if you're in our channel here cause we all want to help each other. Good, very good. Okay. Excellent. We have reached our time. Thank you to all of you. Thank you, Kristen. Thank you, Cynthia and Esther and Lucy and Oninia and Sharon. It's been a privilege and a pleasure. Thank you, thank you. Any concluding comments before I end the meeting? No, I have none. Thank you more and everyone. I'm good on my side too, thanks. All right. Thanks very much. I look forward to seeing you in the future. Thank you everyone. A copy of the recording and a summary will be included in a blog or a link, no, link to the recording won't be included in the blog post. I'm preparing a blog post that will summarize the retrospective and what we learned, highlight some of your results, et cetera. I'll probably mention each of you in the blog post poll requests so that you can then review it and give comments. I hope to get that blog post done today or tomorrow. I would love to have your review before start of my day Monday because I'll probably set my goal to post the blog post to jankens.io Monday. Is that the 10th? Monday? Monday, May 10th. So I'll let you know that the blog post is out there and would love to have your feedback. Thank you, everyone. Thank you, Mark. Thank you. Thank you. Thank you. Thank you, everyone. Bye. Bye.


How to know if the narcissist is cheating on you. This test will help you to identify if the narcissist is cheating on you. It will help you to identify if the narcissist is in a committed relationship with you and only you or if they're seeking validation from other sources of supply. This test will tell you everything you need to know about the narcissist. It will tell you if it's time for you to get rid of them. Everything you need to know about the narcissist is hidden in their phone. Their phone will tell you everything you need to know about them. Think about when you last looked at the narcissist phone. When did you last see what they were doing on there to test whether or not the narcissist is cheating on you? You just have to look at their phone. They can hide behind their false image. They're very good at deceiving people. But you don't really know what they're doing. If they're always hiding their phone from you that's a good sign that they may be cheating on you. But it's not enough proof. It's not enough to confirm your suspicions about them. So you need to check their phone. You need to see who they're talking to. But you don't want to do this doing an argument. The best time to do this is when you're having a good time. When you're both calm and relaxed. Because that's when you're really going to be able to identify whether or not they're hiding something from you. Ask them to exchange phones with you for an hour. And then pay attention to their reaction. Because that will tell you all you need to know. Especially if they walk away from you. Because that means they're trying to delete messages or block phone numbers. So try to keep them engaged. Don't let them walk away. But if they do walk away from you. That means that they do have something to hide.  As though you're invading their privacy.  They will say that you don't trust them. They will try to make you feel like you're doing something wrong. Because they know that they're doing something wrong. But if they do that. That's a good thing for you. Because then you're not going to waste any more of your time and energy on them. You can invest your time somewhere else. If you ask the narcissist to exchange phones. And they get angry or upset. That should tell you all you need to know. Some narcissist may even break up with you. If you ask them to do that. Because the validation they get from their other sources of supply. Means more to them than you do. But when you give them this test. No matter how they respond it will be in your favor. Because even if you find out that they are cheating on you. It will set you free. You will know what you need to do next. If you find out that the narcissist is cheating on you. You should not invest any more of your time with them. Because that shows that they do not respect you. That shows that they do not value your relationship. If the narcissist has nothing to hide from you. They will give you their phone. The phone isn't that important. It's their reaction that should tell you what you need to know. If they try to make you feel like you're doing something wrong. If they tell you that you don't trust them. Which is why this test is very important. Because it will tell you. If you should waste any more of your time and energy with them. When you give narcissists this test. Most of them will fail. But it's good to do this test. Because then you can be sure. It will tell you whether or not the narcissist is loyal and committed to you. Thank you for watching. I hope this video resonated with you. Please like. Comment. Share and subscribe. If you would like to donate. My paypal link is in the video description. Couching inquiries. You can email me at Couching.com to buy me a good UK. Thank you for watching and I'll talk to you soon.


How many people here like to work for free? How many people like to get paid for the work that you do? Yeah, that's not even half, that's surprising. Well, actually, we're all already working for free.  Now, if you were here back in 2011 at the World Economic Forum, or even read their report, you would have likely heard of this issue, which they said was the digital economy and the new asset is the personal data. And the problem was identified back then that you have these contributors and you have the people that want the data and who sits in the middle but the companies. And they create products and services that have become less and less of value to capture our data and then they sell those in other products to their true customers. And so when I heard about this and when Snowden came out with his revelations, I was quite disturbed and so I did an artistic gesture as a reaction. We are all data slaves. I don't know about you, but I've had enough of being exploited. You know who's got it made? Corporations. If companies can make money from my information, information that I generate just by being alive, then so can I. I've decided to play their game but with a little twist by bringing the whole process down to the individual by incorporating my identity. So my solution was to create a legal container that I could then try to collect and control my personal information from. And so I looked at the ways in which I emanated data all the ways and I went as far as I could to collect it. Here's just 25 data points showing the blinking red light is the heart rate and it shows everything that you can collect just from a phone and maybe a Fitbit or something like that. And so that allowed me to try and do that but also try to bring it to the market. So I cut it up into the categories that I saw we were being cut up into. But this was my provocation. This was a protest. It wasn't that this is where I think we should go. I was trying to say there's a value we're all creating and is this where we want to go? Where do we want to go? And so I started to think of alternatives because any protest needs a solution or a demand and I was thinking well if everybody had to become a personal corporation we need something more collective, a collective data broker and data unions. And eventually five years later this thinking brought me to meet other people such as Glenn Weil who wrote the book Radical Markets and Founded Radical Exchange and together we have been thinking about what these ideas would look like. And with many others we want to move beyond critiquing to actual alternatives. The ideas I'm going to present here there are two of them so one will continue with data and then I'm also going to talk about voting but there are ideas that we don't think that they're exactly those that need to be implemented but that hold a sense of the broader principles that we could implement. So we see data as what is created by us, its life. There are uniquely forming patterns of social commitments that we create through the variety of communities that we take part in and this weaves this web of social data that is vibrant and expanding and could be so much more if there was a different structure. So one part of a data dignified world is where this new type of institution so you still have a similar structure but at the top you have what we call mids mediators of individual data. And instead of these being for profit companies or they could be profit companies but they act like fiduciaries on the behalf of people where they can collectively bargain for us and sell our data that we deem is okay to sell that we agree and we decide and that money and services come back to us and it creates more of a closed loop system. Now to illustrate this further I'd like to give an example of Jane. Jane belongs to several mids. There's a music mid, a cooking mid, an energy mid and a health data mid. With the music mid she is a musician and so it's something like Spotify but she actually is a member of it. It's not a C corporation or a private company. And so she makes music, she receives some income from that and there are listeners who pay a subscription but also receive some income from their data analysis and then there are programmers that keep developing the platform. Then when she's cooking she has some bots and technology in the environment and it's kind of like having a child in the room in the kitchen with her where she's teaching it what she's doing, what ingredients are and what are the methods that we eat and cook. Now I want to move on to another idea. This is the second idea of voting. When we have large populations like we have especially in China with many different interests one person, one vote starts to break down and so we're working on this idea that comes from again Glenn Wilde who wrote a paper back in 2014 with Eric Posner and more recently we've been working with Santiago Ciri of Democracy Earth to create an interface and it's called quadratic voting and how it works is instead of having one person, one vote you get a number of credits. So say you get 100 credits and you have 10 decisions to vote on. Every vote is a quadratic cost of the credits. So if you have one vote, you spend one token.  And what's really important is that it slows you down, it slows the process down. It makes you think about what really matters because if you want to yell as much as you want around one issue you can do that but it's going to cost you and it's not going to matter as much. So it's to incentivize spreading out what you care about. And it was used recently in Colorado. The legislature, the Democratic legislature used it to vote on their spending bill which they had $40 million to spend on 120 million in requests. So they were also voting anonymously and privately and they received more nuance in what people felt and the representative said there was better signal with less noise and they were able to capture people's intensity on what mattered to them. So now again, these are just a couple of the ideas and designs and like I said earlier, it's not exactly about these designs. These are ways to start getting you to think broadly, move past the problems, move past the critiquing and going over and over again and thinking about alternatives. Some of the other ideas that we're working on relate to moving beyond private property, to diversely shared property, to a novel approach with public funding, again a quadratic way of finance and other means of increasing returns for fair, efficient and complex ways. And we aren't the only ones hungry for change. Just in a year we have 150 chapters around the world. There's a few starting in China just this week. And together they're committed to embracing markets and technology to build bold visions that reflect our diversely shared lives. And we believe that together we can be more prosperous and things can be more efficient and that we could grow our cooperative society. So I want to end this on a deep Chinese philosopher's words that capture a bit the spirit of what we believe. I don't know how to say this in Chinese, I'm sorry. Xiling Zhang is the philosopher. And so this is closed. This is open. Together they make flapping wings and these two together are leads to change. So like the Chinese culture that the interaction of the yin, the moon, the yang, the sun, the dong which is motion and jing motionless are the push and pull that create new things. And this is what we are striving for. Thank you very much.


Last summer, congresswoman Marjorie Taylor Greene hired right-wing provocateur Milo Yiannopoulos as an unpaid intern and before that she posted this photograph of the two of them on Truth Social with the caption They cancel us because they fear the truth in all caps. Now when it comes to Milo He wasn't canceled because he's some truth teller who is just telling us the hard truths that none of us can digest He was canceled including by right-wingers because he was an open advocate for legalizing pedophilia and As Brian Tyler Cohen put it Marjorie Taylor Greene who is accusing Democrats of child grooming has hired far right Milo Yiannopoulos as an intern Yiannopoulos has advocated for it legalizing sex between 13 year olds and adults because he says 13 year olds are not children and Are quote sexually mature absolutely nauseating and let's not forget that Greene also called Democrats the party of pedophiles recently in an interview with Leslie Stull on 60 minutes, but yet she hired someone who is A-okay with pedophilia. This is someone who thinks that unrepentant homosexuals like Dave Rubin should be executed While pedophile should be allowed to legally engage in intercourse with minors. This man is sick But yet she hired him the anti-groomer lady make it make sense But it's not just the hypocrisy here that makes that photo particularly funny It's the fact that Marjorie Taylor Greene decided to get in bed with someone who would one day Royally fuck her over and I guess she's never heard of the fable the scorpion and the frog but um She might want to familiarize herself with that and maybe she's doing that now because here's what happened between her and Milo Yiannopoulos as LGBTQ nation explains the Daily Beast reported that a charge on a card in the name of Isaiah wartman this is the consultant who works for green by the way was used to make a $7,020 and 16 cents payment to go daddy to buy the domain name on November 22nd 2022 the same day that Yiannopoulos orchestrated a dinner at Mar-a-Lago with Donald Trump and white supremacist Nick Fuentes a receipt for the transaction shows Yiannopoulos's cell phone number Greene's FEC filing show that wartman was reimbursed for the expense that same day the Kanye 2020 campaign reimbursed Yiannopoulos for a domain transfer in the amount of 9,955 the increased price from what Greene's campaign was billed for could be another domain name Kanye's 2020 treasurer Patrick Crescent later resigned and raised concerns about campaign finance violations by Yiannopoulos in his resignation letter Including quote an expense for a digital asset where Yiannopoulos allegedly sought reimbursements from both Kanye 2020 and the campaign of Representative Marjorie Taylor Greene according to Politico Crescent said that that transaction occurred in November of 2022 if Greene's campaign gave over $7,000 to Wests that would violate campaign finance rules since it's over the maximum donation allowed Which is $2,000 per year So there's a plethora of issues here first and foremost it seems as if Milo Yiannopoulos allegedly falsified campaign reports he took campaign funds and Didn't tell them what it was being used for on top of that if Marjorie's campaign filed these reports then they are now Potentially culpable for giving the government's incorrect information It's a huge clusterfuck that Milo Yiannopoulos unleashed on Marjorie Taylor Greene's campaign But what was it that she said about Milo? Can we put up the tweet again?  He is a notorious troll and you hired him Marjorie and now as a result You may be in legal trouble. I think it probably depends on how much she knew although. I'm not a lawyer I can't confirm that but Marjorie Taylor Greene their campaign that her office is responding rather by basically saying We had no idea Congresswoman Greene knew nothing about the gross negligence made by a vendor and is being unfairly attacked as a result a Consultant for Greene's campaign Isaiah Wortman said in a statement the campaign was told the purchase was refunded This wasn't the case now Ross story adds according to Rolling Stones Tim Dickinson Greene immediately distanced herself from Yiannopoulos to avoid blowback Since there are rules that dictate limits on how much one campaign can donate to another so basically Milo Yiannopoulos Took this money told them that it was refunded when he in fact did not refund it according to Marjorie Taylor Greene So in other words, he took the money from them spent it got the money from Kanye West about ten thousand dollars and Then didn't give it back to them So the question is did he keep the money because if that's the case then that means that he technically stole from two campaigns Marjorie Greene's campaign and Kanye West's campaign Wow, I I'm sorry, but I find this funny. I find this hilarious. It's not like donating $7,000 to another campaign is Something that we never see it happens lots of members of Congress do this they donate to their peers They fundraise and they give it to PACs though, but that's the difference Because of Citizens United you can only donate unlimited sums of money to a campaign through a super PAC But if you give it to them directly that is tantamount to a campaign finance violation And if the money wasn't refunded then that was basically a donation from Marjorie Taylor Greene to Kanye West which is illegal So I'm not necessarily sure how legally culpable her campaign is going to be held It seems like they could probably use Milo as the scapegoat because I mean he's the one responsible for all of this But I mean I hope that the stink rubs off on Marjorie Greene and she gets into trouble as well Because it just kind of proves that you shouldn't trust people like this But she did right and now she's distancing herself from Milo Yiannopoulos Which tells us that you know she was fine with his pro pedophilia comments But she draws the line at campaign finance violations because she is someone who respects the law It's just hilarious she trusted Milo and She's now learning that that was not a very smart decision very good judgment Marjorie See here's the thing these fascists have absolutely no morals And they don't care about the suffering that they inflict on others including allies and they're willing to fuck over their own friends Like that if they can benefit from it personally But Milo doesn't care because Marjorie Taylor Greene's usefulness to him is apparently done because Kanye West decided to hire him back as director of political operations because yes Kanye West is still planning to run for president in 2024 And Milo's very first order of business was fucking over more of his former friends by firing fascists Like ali alexander and nick fuentes now I've got to say that Milo is playing a very dangerous game here because a video surfaced of nick fuentes getting into a physical altercation at cpaq And I believe this happened a couple of months ago, but we're only seeing it now And let me tell you when you see this video you're going to learn that nick fuentes the booger eating nazi in question here Is not someone that you want to mess with Stop My favorite part was the kick. It reminds me of napoleon dynamite's brother And I'm just wondering like When when nick fuentes went in Like we didn't get to see his fist like was it like open hand. Was he trying to scratch his face?  I'm sorry. I'm not over it yet one more time The kick the kick is just Oh, and they were like holding each other's hands Folks, I don't know what to make of this I don't know what to even say these people are all Fucking clowns, but getting back to the story at hand. I mean, what else can you say about this? If you play with fire, you're going to get burned But the problem is that this is a lesson that marjorie taylor green is incapable of learning Considering the fact that the remaining two brain cells in her skull are working overtime as it is to keep her from forgetting To breathe and spontaneously suffocating. So I don't necessarily expect her to learn from this and grow and stop associating with terrible people Like nick fuentes and my lenopolis only to learn that that was a bad decision I expect her to continue to get in bed with the most egregious figures because she herself Is an egregious figure, but when you have no morals, don't expect loyalty from these folks.


I'm going to put it on, I'm going to put it on. I do. I have a foundation, bro. I'm going to put it on my neck and my neck. I'm going to put it on the back of my ear. It's like a spot everywhere. I'm filming this, because I'm going to put it on my neck and imagine how much it will push me in. I just want to put it on my neck. Yeah. Let's do it, folks. Come down. I did it.


Okay, can you hear me? Yeah, it's good So I'm Benoit, I'm a community liaison for the Wikimedia Foundation and I will introduce you the extension translate So Yeah, I'm going to give you it will be a short class but as on all classes you will have a short test at the end So let's start bonjour Yeah, like multiple people in our movement, I only speak I not only speak one language and Yeah, many people only speak one language and luckily we have translators that will that will you know make the bridge between Everyone so The extension translate allow people to translate pages. That's not the same thing as content translation You may have heard about content translation The extension translated for is for dynamic pages that are updated often like policies pages Pages documentation things like that So First of all Practical example for translators how to translate Yeah, the process is really easy. I Will show it to you. It will work Well, depending on the language, of course and Most of time depending on the quality of the source Because in most cases, you know, if you don't have a good source Yeah, you will not make a good translation That's the same thing if you want to build a house if you don't have good breaks Your horse your house will not be well built So to access the translation if you go to a page, you will see at the top of the page some Yeah, a banner with all the languages and A link to translate the page you will have here a list of all languages in which that page is available If your language is not there you can click on translate this page and you will have access to the translation A translation interface so that interface is really Simple you have all different messages kind of messages you can find so and translated will require Your effort outdated message that are already translated, but that need some new New effort you also have the unit and reviewed the one for Yeah, a collaborative effort and be sure that at least two people have reviewed the message for quality You can switch to any language you would have Yeah, a research system that will Allow you to find your favorite language and Then when you have chosen the language you prefer you will be able to translate so on the left you will have the source and Yeah, for instance, you have here so for the title you have a source here for a big paragraph and On the right you will put your translation. You just have to click on the elements you want to translate and you will arrive To the translation page There you will find the source again at the top and here you can input your text you can have some suggestions there Depending on the language and when done you just need to save that's basic wiki page system, so You translate you click to next and you translate all the page that way You of course are not alone. You are helped by the tool Each message will have a documentation here at the top for instance, and you can have some suggestions for instance here, I'm trying to translate in Spanish and I have some suggestions based here on the upper term which is a System that provides translations So that's a way to be helped. You can have also messages there that are similar Because you know, you often translate the same title you often translate the same thing So those elements are here really to help you and When you translate you may see some extensions via it's a extension extension variables Sorry, so those variables are created by translate the extension and They help you to translate so here you have an example of A small paragraph to translate you are here you have a source you have to work there and inside of that That paragraph you can see some strange things starting with the dollar sign So to highlight it to highlight them a bit You will see two different things first the You have the variable in blue and also some wiki text markup So for people who are used to translate the page to to work on the wikis wiki text is not a blocker If you are not used to it, yeah, that's not that complicated to to use Especially in translation when people pay attention to when they are creating pages. So in our case we have here a Sentencing italic and here we have a link with translation variable We will we'll go back after in them more practical Way, yeah, we'll explore that later Okay, so who can work on translations like on every on all the wiki we have roles and Everyone with the authorization of doing something can do something different So we have three roles that are editors translation admins and translators All the three of us have different wolf workflows The first one is for editors Basically, you want to change a page and you want that page to be translated. So first you edit the page you add the content I will explain it to you later and Your changes when you will save the page will not be immediately available for translation But translation admin have to review the edit in order to say, yeah, that's good That's done to avoid some vandalism for instance. You have someone, you know editing the source page and Anyone can translate that page. So you will have an elism Reproduced in good faith but other people that would be damageable. So that's why there is that system So editors can you can freely edit a page a wiki page like any wiki page But you will have to rely on someone to To validate what you want to do those people are translation admins and their goal is to check the quality of the page So they will look at the diff look how things have been done Potentially they can make some small changes based on experience or based on best practices that are shared across the wikis Then they click in order to mark mark the page for translations and all edit are live Anyone can now translate the new the page that has been updated and the third role is basically translators There is a page to translate. Okay. That's easy. You translate it like I have just shown to you before and thank you Okay Let's go deeper How to edit the page? Yeah, like I've said, it's a wiki. So You did the page you make some changes actually you have to use wiki texts when you edit the page Because the visual editor is not really yet to welcome Translations and transit tax Yes, because translation Require extra market. We are going to add some new elements inside of the translations We have seen that a bit in our previous example, but let's go deeper Yeah, here is a typical page Marked for translations. Don't be afraid. That's not big deal I will show you the different examples. So let's focus on it. Okay. First you will see the translation units So you can notice them on the on the previous page here. Look you have Small numbers that looks that start with T and they are no HTML comments so Those translation units will be used in order to match the source of the page and the translation all the translations The principle is the follow the following when you open the page You will have, you know the source of the translation like we've seen before you put your text and Here at the top you have the link where that Transition units stored and here you have translation unit number two which matches The translation units in the source Okay, going deeper on how You know translation namespace works and things like that. It's not the goal of that Of that presentation, but if you have any question, you can go on wiki or ask me if you have more questions Very important Translation units are created by software. So don't change them. Don't remove them unless if you perfectly know what you are doing For instance, if you had a new paragraph between Translation unit four and translation unit five, you don't need to rename Translation unit five to have translation six and so on Otherwise, you will basically break quite all translations So, yeah, that's a golden rule for that rule and you will have no surprise in the source Translation units have a particular case. It's for titles Look, yeah, you have the t3 is after the title W equal means title in wiki mark in wiki markup. They are always after for personal reasons That's the only particular case you will see concerning translation units Number two, you have the variables. So we have already seen the variable before in the in the translation interface So here you have in blue a variable So what is the goal of a variable? first you open a variable and then you close it and The goal of those variables is to find Sorry to find Yeah, to have blocks of text that will be stored are as you know small containers So in that translation unit name 18, you will find the number here. You will see that here the variable name talk is there So for people who are familiar with wiki text here starting with the two brackets is supposed to be a link And that link is there is going to a toll page using this allow people allow translators not to worry about the page they want to target The toll page will be the same on all translations translators. That's just need to use that dollar talk element And the link will be built The goal is to avoid mistakes. For instance, if someone I don't know why decided to Translate talk colon wiki of French translation in the language The link will not work in order to find Pages that have a particular language. We are going to add the special column my language inside of a link and of course inside of a translation variable That way It will redirect automatically people to their language if their which is available for translation so Yeah, usually only with his friend. She's as a setup for my my interface. That's my my main language and Visual editor is not the same ease. Yeah in French visual editor is not the same thing as Yeah, if I translate visually there, it will not be Translates in same same way So if I create a link here, for instance without that special my language special page Then people will not go to the transit translated page if I'm using English for my interface visual editor will go to visual editor page if I'm using under the language Due to the use of special column my language. I will go to My full back page. Yeah, French So that way people can go to the to a page they can understand Okay A third element an important one is are the transit tags Transit tags allow you to know where to start the transition and when to end it So when you have a text for instance here, you have a text with 25 translation units The software will know that Transition marking the other transition system must be set up starting there and finishing there in between everything you will put will be Will be an element. It will be a separate element for translation. So if you have 24 paragraphs Every paragraph will become a transition unit with an independent Identifier so if I put translate at the beginning transit slash transit at the end Then in between every paragraph will become if I have 25 paragraph. I will have 25 Translation units So that was the basic concerning how to how to Understand how to edit the page We are going deeper with an example so Here I'm going to edit that quick text only have two paragraph in the title I'm going to add this event will happen in November at the end of the last block First case I'm just adding that at the end That's all what will then happen The edit is going to modify transition unit for because I've added a new sentence inside of the paragraph so when translation admin will mark the page for translation that paragraph will be marked as obsolete for readers and translators will have to update it they will have just you know to take the original text and Add the new translation for the last sentence and agree Let's take another example We have that paragraph and then we have one blank line and we add our new text What will happen in that case number two? That's easy like I've said every new paragraph will be considered as a new translation unit. So in trust translation units Four will not be updated The new thing in green will not be available for translation until it's marked for translation and When it will be marked for translation It will consider not translated so translator will have to translate the new element Here I've marked my page for a translation and the new translation translation unit has been added It's the 28th case number three well That is a bit tricky so You have your three units and you have put your element below and It will not be marked for translation because it has it has been added as a transit tag readers will only see it in English and translator will not be allowed to Update the page and they just translate the translation. So be careful when you edit a page. I've already seen that those cases people put their text after the translate Yeah, the closing The closing translates tag and Unfortunately, the page was not set up for translation. Okay variables. I was mentioning variables earlier So let's say that yeah, my toll page is not the same as before It's obsolete. So let's edit it We have a new toll page. Well, that's really easy You just need to edit what is between the beginning of the variable and the end of the variable You just replace the link and what will happen for transit for translators nothing will happen because On that transition, they will only see dollar toll So they will never see what is the target of the page In that case a transition admin will decide if the unit needs to be updated or not In the case that chance when the page will be marked for transition that change will appear on Yeah, it will be on all pages So people will just click on the page on the link and they will be redirected to the new page variables sometimes you will see some variables multiple variables in the same sentence and in that case I really advise to have unique variables on Here and have explicit variables, of course because I've already seen people having TV our pipe viable one. Yeah For translators, that's a bit Yeah, it can be problematic for translators, you know, because they did not know where that link is supposed to go Or what that variable means So, yeah, my advice to have something clear and also to have unique names for the whole page because you can have The same trans the same viable name for different power That's possible. But at some point if you merge the paragraph, you will have to redefine the levels if you split convert split translation and merge translation, which is Yeah A bit complicated that doable Yeah, you may have some bad spaces So yeah, my advice is to have unique names for a given page. And yeah, don't don't use special characters I've scratched my head during something like yeah, 10 hours, you know to understand why my page wasn't remarkable for transition Okay We only we don't only have text on On pages and sometimes we need to work on structure and you need to work on images. So let's go for those cases Well actually sometimes you need to update the page, but no translation are needed For instance here, I have a list of cities and if I want to add a new city into my list If that city has a pretty international name Yeah, we don't need to update it. So we are going to isolate the list of names between a closing transit tag and a new opening transit tag and if I add a new city randomly Barcelona Where? When the page will be marked for transition the page the list of cities will be automatically updated on all pages All transition at a level and it will have no impact on transitors work But sometimes the names need to be translated Indeed sometimes name need to be translated, but I'm in a case where it doesn't need to be translated For the example if that name needs to be translated I would I would have had that name, you know below the transit time so people can Yeah, of course, but yeah in that case I've randomly decided to take the name Officially spoken in the language of the country I'm good with that Yeah, if I would have added, I don't know, a city in China, I would have a Chinese tag. Yeah I'm good with that. That's a theoretical example Okay, the goal is yeah, the goal there is just to show you it's possible to make some updates without Asking more effort from transitors Transitors are all volunteers and we thank them for all the work they do that we don't need to you know Ask them for things that don't need real changes Yeah, we can also have a way to isolate templates So in that case I want to isolate the on-shore template So that transitors will not accidentally change the target of my intro that can be a bit Yeah, that can be confusing if This or the whole time it's translated. It will not work So yeah, that I will come back to that case later because it's interesting interest want to show you it's possible to isolate templates It's also possible to isolate some lists. So for instance here, I have a list of things. So I Wanted to be a list forever So I don't want for instance to have someone who will you know translate that All the bullet points because someone may want to make paragraphs because that would be better But that was not the purpose the purpose at the beginning So here we are going to create translation unit for every point that is in the bullet list. So Wi-Fi, okay? May not be translated. Okay, we can debate about that. But that's not the point Yeah, not for instance, you have more important information that will require Translation and it may be interested to interesting to isolate those those elements Okay, case of images Okay, here's the wiki syntax another to introduce to add sorry to add an image to the To page. Yeah, we can just put the image on and that's fine. Okay That's English. I translated to French. So I'm going to translate. Well everything so I'm going to add fishier Institute, France, Japan and Yeah, you can be sure of one thing That image doesn't exist on wiki made a comment. So the image will never be displayed So it's really risky. So I really advise you to avoid people sending the image Just in case so how to do that first to identify you didn't if I watched why what's to out you are sorry Just like no kidding Yeah, you have to identify what you need to be translated. So in this case, you have the whole image with a size an alignment and And the explanation of what's that image Then you only take what needs to be translated. So here it's only the caption you need to translate the caption So you have transit tags so that only What is between the orange tags Will be translated and then you'll wrap it up in order to put it inside of the page Here you have an opening translate So you put a close translate before and here you have a closing So you put a new opening in order to have all the elements translated So that's the only thing that will be translated will be the caption It can seems to be a bit tricky, but yeah when you get used to it, that's fine Okay, let's come back to To answer us though That was my previous example here I have a list of cities and somewhere in my text. I want to have a link going directly to that section Well, what happened if I translate the title? Yeah, the new title here in French will not be the same one. So we don't want to have units 26 To be a link we want to have it translated, but it will not be possible to create a link there So we are going to use the intro that will go to list And then We are going to make that that link directly to this Inside of the link when when we need it. So This element if I want to go to the list this element if I click on the on the link that will be created by that We'll go there to there that intro instead of going to that Hypothetic title that is not translated or may not be translated well Of course that list is not exhaustive. There's plenty of other examples. So you can read the documentation that has been created And is available on media. We keep new A new part a new important part after the technical part Let's discuss a bit about how to use translation for successful collaboration And there are some best practices to to to have. Yeah, the first one will be to Actually use the tool and do translations The better, you know, better, you know the tool the easier it will be for you to use it And the easier it will be for you to understand how people use it So, uh, yeah, sometimes you only speak one language it happens, of course, that's not the problem There is another way to Learn how to use the tool. I will show you later Yeah, well, that's obvious keep things short try to avoid to have massive Blocks of text So if you have a big block of text, you can have multiple Translation units instead of one big So that it would be easier for people to translate them Don't forget to use international English I see sometimes some people with a, you know, North American background or British background who make Create pages and sometimes don't manage to understand those pages just because of those differences between languages People some add some cultural references that are, you know Yeah, you know, it's like that very famous American TV show from the 70s. Yep No, I don't know it Some people use jargon, you know, that's our new project that will use the break x y z. Yep. What is it? I advise you to have a glossary somewhere so that people will not be lost Also avoid metaphors, you know Yeah, my project is that is like a new butterfly flying inside of a sun Maybe perceived. I you know, it's not that direct and people may not understand the The point you want to make Yeah, most people we are working with are have on bubble boxes English to level That's not much most people at the nindia ketun. For example, they English to English English three and below level Yeah on above actually. Yeah, so, yeah Sometimes it can be yeah Yeah, there's some tools existing that may help you to to work on that on that I mean, we have for instance the good way to know if your text will be understandable by By different people Okay. Yeah, don't forget that place Keep the titles sometimes you say you can tell yourself The titles I'm going to put here before the slash translate and after New translate tag is so that I'm going to isolate the titles I advise to keep the titles because titles are breaks. It means I can't take a break when I'm translating And I can't come back later. It would be easier to, you know, rhythm my work document It's really important That's also a way for people who only speak one language to practice that too if You are when you are on the translation page to If you type qqq in language search, you will have access to documentation That documentation can be necessary sometimes for instance, if you put a link to Wikipedia article, you can You know, tell people yeah, please add up that link to your Yeah, an article in your language That's a way to do that Uh, you have seen documentation in previous examples and so Yeah, don't forget that it's really really important to have things documented It eases a lot translation work and people can know how to make better translations Here's an example of how documentation is displayed. It's just on top of the page You would see that on yeah every time you have some documentation there Okay Final section how to create a new page Basically, that's really simple, you know how to I've explained you how to make it Happening so you can first create the page you can use v in that case Then you use wiki text to add translate tags You have the different variables you need I advise you to ask for from advice for more experienced users It can be translation admins. They can help you to set up the page best way and explain you, you know better tips than All new theory i'm showing you and yeah, and then that's done You can ask trans ask for translator for translations and Get translations done Last touch that's the cherry on the cake Don't forget to add That important element on top of the page Engages slash it will display the the bar where you can switch between languages That's so from my side So i'm going to let you work with some tests So let's go for test number one case number one Why this edit will not work? Nicholas You're not supposed to reply. Yeah, Nicholas here has created that tool. So he knows the case Okay, yeah Yeah, okay, three before the title and Same thing, okay Nicholas Yes, absolutely it will not work because of two causes you managed to find them Congratulations. The first one is indeed that one With the translation title element and here on that paragraph for translation unit four You have two variables with the same name The correct Version is that one you put the translate you have the translate Unit the transiting tag after the title and you have link one and link two Okay, those two links those two variables may have been improved, but That's a theoretical case case two How many new translation units will be created in that example, okay six and six Because i don't see the translate tags I assume there's somewhere around the example None Yeah, translate tags were missing. Okay, let's let's then assume that we have transit tags wrapping the example So how many translation unit will be created? You said six. Yeah, still six once twice And we assume that the translate extension is installed and everything yeah, yeah, of course everything is installed It's ready. It will be translated. Yeah You said three. Okay, and that's three Because you don't have any blank line between the title and the paragraph. So All that block will be considered at one translation unit that block as the second one Yeah, the correct way to make that this is better You will have one unit for the title then one for the paragraph one for the title One for the paragraph you can make a song based on that That's all. Thank you very much for attending And if you have any questions, you can go online on the wikis and you can you can also ask me right now Yeah, uh, precisely now. I was editing I was trying to translate a text A couple hours ago Can can you have uh twice the same One same text I mean twice or more than twice What the same number of a unit? No, it will be a separated element But the translation memory will identify The the fact that it's the same one and it will suggest to Give you as a suggestion the same text. So you just have to click on the suggestion and the text will automatically be Yeah, it will be used but particularly No, yeah, it will be used at least Oh, so the question is I mean the answer is that the the tool won't say no, but if the the editor The editor may change it So that you can have the same unit twice or or more times, right? Um, yeah, let's go with an example. Um here you have Uh, you have your translation you can add something and if you have somewhere else the same sentence You will have there the translation So here is with french because i'm using a different language, but here you have a percentage Saying it matches at 60 percent or 100 percent So if that if you have already used that element elsewhere in the translation And the page has already been marked for translation You will just have to click here And it will be used for you Yeah, yeah Yeah, okay. Yeah, I understand. I hope i've been clear Yeah, I hope I've been clear and reply to your question Yeah, I I understood And then uh Well, I I'd like to know the the way to to become a Translation Translation I mean okay Uh, you go to the wiki where you are active on there is inferior page where you can request to have your right changed So on uh, I don't have the precise page in mind, but uh, I can I can tell you if that's on um on media wiki It's the same request page to have, you know, all other rights same thing on meta meta, I think I'm concerning other Website using that that system. I don't know Yeah, I'm in meta right now I was just a helping an italian user who was Setting up a contest And an edition contest And I was translating into spanish But then I found out that there are a A couple of things that don't go very well Okay. Yeah, we can we can see that later One translation unit that that is a bunch of code. I mean it's like one one table, but the translation unit doesn't cover the whole table okay One translation unit, but yeah, I really like like to change it. Okay. That's an interesting case. We can see that Yeah, maybe right now if we don't have any other questions No, okay. Thank you very much