 Okay, good evening, good afternoon, or good morning people around the world here. Welcome to this Google Summer of Code office hours of today, March the 30th. So welcome everybody on the meeting and listening to the recording. So we're slowly reaching, no, we're not slowing, we're very rapidly reaching the end of this phase of Google Summer of Code. So we're reaching the end of the proposal submission. So just give a quick update where we're standing. So we have a total of 3434 drafts that were submitted for review. On those 34, eight drafts had to be withdrawn or discarded because they were on the three withdrawn projects. All of word work had to be put back either in the fridge or put aside and people realigned. Apart from Chris turn. I think we as a community as a mentor community made the terrible job in reviewing and advising on all these drafts. Otherwise for for that. We're still not the end of the draft period. Now the reason for that is that we have about three times as many proposals or drafts than we had last year. And we have exactly the same amount of mentors. So we've been overwhelmed by the questions on Gitter and the very active traffic over there, the different documents to to review. So we will definitely improve that and make it better. I thank you for your patience. 16 proposals have already been submitted on the GSOC portal. Some names and drafts I recognize some are coming out of the blue. The ones coming from out from out the blue. They need to be very, very good so proposing the drafts make it available and having discussed by the community is the way to go in order to succeed. It is now time and I'm talking to the would be contributors. It is now time to submit your proposal. Don't procrastinate. Don't. You can expect some reviews I mark. I think you want to give it a push. I would I'm wanting to make a push of it since the beginning of the week but been busy with other things. Yeah, for Sunday evening. I think there there will be no reviews anymore by mentors so because the deadline is for Tuesday. Yeah, so well, the Google summer of code rules allow them to submit and then overwrite their submission with a later submission right so there's yes there's no harm and then submitting early. And if they get additional feedback and decide to react on it they can replace their submission with an improved submission. So there's no shame in that and that means submit and then you can submit and replace your PDF with another PDF that's a better one that's that's perfectly fine. Okay, but then what would be the source of truth the Google document that the share. And the Google doc is never the source of truth to us as reviewers we always use the PDF file right there's their submitted PDF is the thing that we have to use that's the rule and it's frozen. Right and it's the only one we use for grading. The deadline, remember is Tuesday, April 4 at 1800 UTC that this is midnight in Asia or India using India as a reference. It's the evening in Europe and somewhere about the morning in in the US. The work that has been done don't let it slip. Submit in as Mark reminded, you can submit and then have a last last minute change. But at least it's already submit and John Mark just for absolute precision 1800 UTC is 1130pm India standard time. The continent about the subcontinent uses a single single time zone for whole subcontinent and I like that a lot very smart of them. Very clever. Yeah. So, once the proposals are submitted and frozen. This is where the mentors will start grading in making the selection. So contributors would be contributors can then rest a little bit and think and do other things. I will keep the office hour open so I will open the channel. It will not be recorded. I'll just keep it as a social hang out if people want to chat or discuss Indian people can try to explain me the rules of cricket. I'm more than eager to learn them. We just to be together and the channel will be open. And it's not required at all to attend. The jury will come out on Thursday, May 4 at the same time so 1800 UTC 1130pm in India so about midnight. And the results will be announced or be at Orby which means in Latin to the city and the world. So it will be announced by mail by Google to the people that will will have been selected. So publish exactly at that time Jenkins block post and will update the project pages with the selected projects and there will be also announcement on social media Twitter and LinkedIn so this is the official announcement where the people selected will be. We will hold a special office hours. The Friday just after that so Friday, May 5 at 1500 UTC usual time but just shifted by one day. So where we'll meet will will congratulate the selected Google summer of code contributors will will answer questions, maybe give suggestion to the people that were not selected. There are still things interesting and important things that they can do to learn from the experience contribute to the community. There are a lot of very exciting things that can be done. We can discuss them and we will also stake out what will happen the weeks after for the selected people and the mentors so they're the scope of the office hours will be much closer closed for the for the people. People are interested to listen and see what's happening they're welcome. We're working in the open. These are the general announcement now. We have or I have some more unpleasant comments to do and there were some, some discussions and complaints earlier this week and I would like to come back on that and clarify. Some of things. The first and most annoying thing for me was there were some precise complaints about comment bullying. I co with that are people that anonymously put comments on documents that are useless or rude or even suggest very unpleasant things like saying or implying that the the proposal is useless. And should be removed. I call that bullying. Some people might see it as just a prank. I personally don't and we as organ men and as organization don't see it that way it's an inappropriate behavior. And especially now I hope I will not do hurt somebody but as it was aimed at Sonali who is a young lady. If I'm not mistaken, which makes it even worse. So it's not acceptable is disrespectful. It's not in the spirit of open source, and it's not an adult behavior will stop. There is no other comments on that this is not acceptable, especially as that we as a community follow the Jenkins code of conduct, which is really very important guiding principle. And in everything that's going with our external communication Alyssa is somewhere. The, the, the owner and can really explain very well what this Jenkins code of conduct is. And so Alyssa if you could clarify that with with us. So, as John Mark mentioned, the, the code of conduct is our guidance into the Jenkins communities cultures are our value and our philosophy. So I put a link in the chat window. And try to share my screen with you so that I can. Okay. I'm sharing my screen. So, just to make sure that there's no misrepresentation, or any misunderstanding I'm going to read or briefly read our code of conduct, just so that hopefully when you hear it. So, you know, it absorbs better. So Jenkins code of conduct as community members contributors and maintainers of this project. And in the interest of fostering an open and welcoming community. We commit to respect all people who participate in the community through reporting issues, posting feature requests. And updating documentation submitting pull requests or patches and other activities. Our pledge as we as members contributors and leaders pledge to make participation in our community a harassment free experience for everyone, regardless of age body size, visible or invisible disability. Sex characteristics, gender identity, and expression level of experience, education, socio economic status, nationality, personal appearance, race, religion, or sexual identity and orientation. We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive and healthy community. Our standards examples of behavior that contributes to a positive environment of our community include demonstrating empathy and kindness toward other people. Being respectful of different opinions, viewpoints and experiences, giving and gracefully accepting constructive feedback, accepting responsibility and apologizing to those affected by our mistakes and learning from the experience. Focusing on what is best, not just for us as individual individuals, but for the overall community. Accept the unacceptable behaviors include use of sexualized language or imagery and sexual attention or advances of any kind, showing insulting or derogatory comments and personal or political attacks. Public or private harassment, publishing others private information such as physical or email address without their explicit permission. Other conduct which include reasonably be, which could reasonably be considered inappropriate in a professional setting. So I know that this is a, probably a lot of things to digest, but just a bare, bare basic foundation is to take away from this is be kind to each other, respect each other, and help each other out. And that's how our community grows that's what our values are as a community because we want to make this a welcoming and diversified community for everybody. So hope that helps. Thank you very much, Alyssa for this, this reminder and this is part of the open source experience and what we want to teach. Now this is very serious to us. We have here in this meeting two members of the Jenkins board, Alexander and Mark wait, who look and follow what we do and might take actions. Now, practically, we cannot defend the system from defacing or or these kind of comments comments bullying, which happens quite not quite often but happens regularly. Because of the way Google form Google doc Google doc is configured. And because we want to be as open as possible. We give the opportunity to anyone to add comments. And this is something we feel is important. We, if we want to require people and only nominate a nominal peoples to be able to do comments there will go against the flow against the spirit of openness of what we do so we want and we will remind and we've been very strong here in reminding us what is the open source code of conduct or the one we use here at Jenkins. If these type of behaviors continue. We would have to use then what I call or Mark called the nuclear weapon and then force closed comments that we have to maintain who are the people who are able to do the comments and all the comments assigned and logged. I would be very, very disappointed by that because that would mean that I failed in my work as mentoring this this community or this this group of people. So I trust you with that. I have the same comments to do about review comments closing. We have seen, and we all have seen that either logged in people or anonymous people found it very funny to close comments so that they're not seen anymore by other people or by the the author. It's easy to do. It's fun. It's, it's you're just annoying people doing that. No, it has an impact. Don't do that. Only the author of the the comments or the author of the documents are allowed to close a comment behave well. It's, it's, it's like, well, I have several examples in my mind, but when you're in a community when you're together. Don't don't just grab the food in somebody's else's plate. Just behave. Mark, you wanted to add something or so you're making a sign any any one of the any one of the candidates is welcomed choose if they if they wish to disallow anonymous review, and then assign specific people to review. I believe you each have access to our email addresses so if you need to. You are welcome to assign. I'll give you mine I'm mark dot Earl dot wait at Gmail dot com. And you are welcome to assign specific reviewers that will assure you that you don't get an anonymous anonymous comments and anonymous not getting anonymous comments means you also won't have anonymous people closing review comments. This is to be the only compromise we can make with the Google Docs use model. Now the, the next topic, and then we're we're open to this, the floor for questions and discussions. There are also complaints and discussions about copying cheating and behaviors that were not not expected. Now, I have a couple of comments on that and I will let the other lead mentors. Here, we have a crowd of people so we have a lot of people that are presenting competing, I need to accept that on a limited number of project ideas you've seen the number of drafts that have been written so that means that Jolstein is being squashing and so is expected, but there is something stronger behind the whole discussion. The way we work in open source the way the spirit of what we want to do and the spirit behind Google summer of code is that we also want to encourage sharing of ideas. And so the complete process of building and growing and on these various ideas is normal, expected and could be encouraged that what is not acceptable or not. And here we're all playing with nuances gray zone so there's no rules that can be followed by a judge and know where it becomes where this sharing of idea of goodwill community working together is definitely discussable is when we see text that has been copied and where this is obvious plagiarism and this will be detected this is these are the kind of things that mentors are looking for. So, copying cheating or these these kind of things is not relevant at this phase of the process of building the proposal. And in the Gitter channel, there was also reference to rules from Google summer of code and I didn't want to get into that debate on the Gitter channel. These rule apply for the possible exclusion of selected G so contributors and that get paid. And this is that for instance, using other people's codes without attributing it or these kind of which is there it's stealing other people's work. At this stage here we were more in sharing exploring ideas. It can be seen as somebody stealing my my work my ideas and this is unfair. And this is difficult to understand and this is difficult and and it's part of the experience and these are the kind of things we wanted to share with you or make you experience this working together and making these these ideas grow. You have been used and you might be in very competitive environments where this cooperation sharing ideas make them grow and hey I worked all these these. And somebody else's use it in open source it is normal. It's the way it works. You just attribute you build or this is done in a friendly way. In other circles you have a knife between your teeth and you're going to kill the other one and and this is the rat race. My personal opinion I don't want to be part of any rat race that way but here there's another choice. I know the world is not as simple as I wished it but so this is this is important. Now it's it's gray. It's in their very mixed feelings about that I can understand especially if it comes together with very intimidating behaviors like these these commenting and there we're very strict. This is definitely a no no. And if you add this impression oh somebody else has been stealing and here this is not what we're talking about this and I use the expression before. Remember with GSOC it's not the goal. The destination that's important being selected and having my name there on the on on on the the stereo sky. It's the way it's a complete process. Look behind you all those that participated up to now and look at what you already learned. Only a few will be selected and I want also to be very very honest. We made our calculation there will be only four people selected in all all the crowd that has been participating to that. But not being selected does not mean that first you failed anything and that you didn't learn anything and that the road is now finished. Not at all. And this is something we can we can discuss in a in another phase in another phase. Just want to conclude that part so two things first trust the mentors. The mentors will evaluate the proposals and I'm just going to remind what are the criteria is that I refreshed all the mentors that and joined them to keep these in mind when you grade the proposals. So is it a clear and well defined proposal must is the applicant does he have enough skills and experience to quickly hit the ground running. Applicants has completed contributions to the project prior to submission and attended office hours. These are evidence of his commitment to the project and understanding how our community works. The applicant has demonstrated adequate communication skills with his submissions is interactions on forms or getter on PR conversations. Applicant has the right stuff to complete successfully his described GSOC project it is globally the and it's not only putting a mark. There will be also an open discussion on all the the proposal. So the last thing and I conclude my part on that and give the word to other mentors there. There will be no exclusions based on article XYZ and so on. If we have evidence or that's for some reasons someone obviously cheated because he copied parts of text. We will see it and we will just not select the proposal full stop and so on. I we're going to leave that discussion that was raised by two of you. And we'll leave it there. Now the last point I'm going to say thank you to have raised in these points and concerns. Thank you to have reached out to to the org admins to explicitly say what your concerns are. We take it seriously and we gave you the answer about that. Now who would like to add something to what I to what I said. Otherwise we move on to open or more general questions. Mark Alex or so or was I that's boring that nobody has comment. No boring just very complete. But I agree with user mark that is definitely an important topic and thanks for elaborating that that in detail. Thank you Alex leave the mic open for a couple of seconds and then I'll we can start taking questions from the audience. There was a question raised by by mom old regarding hey is for pull requests enough it's a fun topic because almost always in software development asking is number enough. We'll we'll get a completely ambiguous answer because we rarely can successfully count things in an intellectual proper intellectual effort and decide if it's good or not. We certainly do review pull requests as part of the review process the most important thing is your proposal, not your pull request it's your proposal, make a good proposal but know that we will look at your contributions in other ways as well. I we don't we have full range of things we can evaluate. We can look at your public history on GitHub we can look at pull request you've submitted we can look at comments in chat channels those things are all viable and can help us as we try to make our best decision. Again proposals the most crucial thing agree with you this was a question for my mood. I just it was. Yeah. Okay, I hope this was answered. I have a problem scrolling through all that. And I have hit my time limit, john mark I apologize I need to give control of the session to. I'm going to hand off to Alyssa so that she becomes the host. That's fine mark. Great. Thank you very much for joining mark in for your participation. Okay, I thank you by. So what else do we have as question I lost track here. I don't see any other question for the time being. Okay, here I see. Oh, you have a question for me. If you still there. Yes. Back you said that for the Android project. You want something that is on the left part of the pipeline. So what I have proposed is like basically adding few stages to the pipeline and few things like you wanted on your. Few things you have these only issues on GitHub on that repository. Building jinkers and few things like that you have mentioned on the project piece like you want to build. You want to have multiple emulators or something like that. So, so I have proposed that is this enough or do you want to like add something more that I can look into before submitting my proposal. I would like to hear about your ideas. Mine are okay but yours are way better. That's for sure. So I will tell you what kind of ideas you should have just promote them if you have some and we'll evaluate them later on. This is very, very true. Did you understand that McCool. Okay. Here I know it's a difficult exercise and and here you're not at the school assignment where the teacher said, I want you to do that. Or if you're working for a boss. Here we want to to see your creativity and how autonomous. You are so come with ideas come with and be this guy the limit. Okay. 175 hours also are part of the limit. Go ahead. I mean, you said, like, my question is you said that you want something on the left, what does that signifies like left part of the. That means less part of pipeline or something like that. You said two weeks back on this. So my question is what is that that left part. Oh, yeah, but I think I think I wanted to say that for Android mobile applications, generally, you don't want the end user to discover that something. Is not going well with that app, you know, we want to try to catch all the errors before the application goes to production. So what I think I meant when I say shift left is shift left. Yeah, shift left. So try to catch all the errors, all the code flows, all the things that could make the application a better quality application that end user won't have to face string. Issues, errors, and so on. So that's what I meant. So of course, static analysis, unit testing, of course, instrumented testing. But if you have any other ideas that could ameliorate the code, like for example, dependency checkers, linters, whatever you have experience with, go ahead and propose. The goal is to have the best quality application possible, even if it's an empty application to start with. Okay. Okay. There was. Yeah, go ahead. I hope you're having a great time. I just wanted to say thank you for clearing everything out team and I have something to discuss related with my proposal. Can I go ahead. I was thinking, like, I can maybe add our default user, because we want a quick start for the Jenkins and I think it would be great. I can maybe add our default user, because we want a quick start for the Jenkins and I think it will help them out if they have the tutorials as a default user and all the plugins are already installed and they just want to expand their hands around. So is it a good idea. Yes, I think your gut feeling is good and the quick start should have enough components pre-configured so that the person who tries it out has everything the minimal required to do. Yes. So using Jenkins configuration as code to configure as much as possible, for instance, for me is a must for this project. Yeah, I think there's different tutorials available even in the documentation like getting started with the Java meetings and even greater. So I think I can add different. So to have a good handful of plugins that that people generally used or are interested in the purpose of it is that they have enough to get a good impression of what Jenkins does so you're on exactly on the right direction. Yeah. Okay. Thank you so much. Okay. There was a question from Jack Ruthie that has already been answered by Adrian. We, we, we don't count the number of times you've been on on the office hours and so on. So it's so and we're now the phrasing is not correct. I apologize for that is these are hints that shows the engagement to the community and how the people understand and interact it with that. And we'll look at it in a holistic way. So globally so but the way Adrian answered I think so you're you're reassured, I guess. So that question for Bruno. Adrian had to go. Okay, that's good. Thank you. Last word I'm going to make a small sales page and I going to share something that's near to my heart. Some people had their proposal canceled because they were running on a project that was removed. And they, some of them had a very interesting reaction I really appreciated that they continued working on the idea the project idea and submitted pull requests. And continue thinking and interacting and we're looking in ways to contribute to the community. Don't forget that Google summer of code is a way to enter in that world of open source. But there are other ways to to explore that world. And the last comment I'd like to do, especially for young professionals or people that are still studying open source is a wonderful school to learn more than just what your teachers tell you they only teach you a very little part of the real stuff. The real stuff you'll learn it by gaining experience and exploring it with with open source. So Google summer of code is not the end of the road. And we've seen some very positive attitudes and this makes me happy to see that these people understood the message that was behind all the efforts that we were doing here. So these are my final comments so we're now slowly reaching the top of the hour we have still quarter of an hour. If there are questions comments or somebody wants to comment about football match. I don't raise that subject with Alexander. He's not following football. I have something to, I have something to ask. How much help we can expect from mentors during the GSOC period during the contribution period. So when when during the actual contribution so if you're selected. Is that a question. Yes. We a contributor that is selected. So we estimate the time spent by mentor to eight between six and 10 hours a week work together or reviewing document or interaction so it's a very high level of interaction. So it's really platinum level of coaching that you get with. Yeah, it's, it's, but you get a very high support for that. It starts in June with a bonding period. No in May with the bonding period and then during the whole summer. There's a heavy interaction between mentors. So why we have limited the number of projects we can take, because the involvement of mentors is very high during that period. Did that answer your question. So that includes like code review from code review to one to one meet. Oh yeah, both code reviews every code that you're going to submit will work as pull request in layers and will be reviewed and will be discussed. There will be one on ones. I will, I will insist that we have once a week. This office hour. So mentors and candidates or contributor together as some kind of a stand up where everybody is will explain what is his progress. What are his concerns. What are the impediments and share the progress. So that we do we building a community. And we work together so it's really a high intensity involvement of everybody and not only per project. I want to have it globally. I would have loved to have more projects. Believe me, believe me. I've been crying to have help, but on the other side, I don't want to stretch the resources we have, because I want to be sure that we have successful projects. And you see you hear that the involvement is high. Is there any way I can contact with my project mentor who is per Vento. And because he's not really presenting the office hours, and I just want to discuss some ideas with them. And if it's feasible to add in the proposal. I'm working on the quick start with them. Bruno is the lead mentor. Bruno is the lead mentor there. Yeah, I just wanted to say I'm one of the mentors potential mentors. Oh, yeah. So is it okay. Now, generally I prefer that the questions are raised through the getter channel or publicly. But now we slowly running out of time. What is the best way to reach Bruno to monitor the getter channel? Yeah. No, I'm kind of overwhelmed by the amount of community dot Jenkins.io is something I read more often than getter. And you receive a notification by mail? Yeah. Anyway, suddenly use the community dot Jenkins.io and so make it public, but you put Bruno. Oh, yes. And my handle on community is not Bruno. It's Podang as I wrote in the comments in the chat. Which is the name of a French pastry. So you know everything. That makes it easy to remember. Well, when you know what it is and when you have tasted it, so you remember it. But it was a time where Android was coming with the cookie names for their version numbers. Okay, the next version is going to be that French pastry. Right? Story, right? Yeah, you're right. Except that, yes, we didn't get Podang. What did we get by the way? It was a piece something. Here. Other questions or points to raise? Now I wish you success. I wish the mentors to ask a little courage because this will be the last preparation of his hour. So remember I'll open the channel the coming weeks just if somebody is around. And because we'll be actively working on the grading and selection process. Enjoy the break. Hope to see you around. And wishing everybody the best. Thank you. Thank you. We can close now. You have the keys. You need to turn off the lights. Thank you. Bye.