 Hello everyone, welcome to the Jenkins Google Summer of Code meeting. There are probably too many acronyms in the role, but we have recently created a special interest group for JSoc. This is the first official meeting of this group. So as usual in special interest groups in Jenkins, we have a page describing code communication channels. So if you want to know anything about this group, just go to this page. Generally it's about Google Summer of Code and other related activities like Google Coding. So yeah, even if JSoc has finished during this year, we will keep regular meetings so that we synchronize before the next year and address other tasks. And there is a mailing list and chat and guitar. So chat and guitar is where you can ask any questions you have. And we usually post links, et cetera here. For example, here's a particular link to this meeting if you want to attend. So today we have three main topics. We will have an update from Tracy about Jenkins participation in Outreach. Then Jeff, Martin and me will summarize the JSoc Mentor Summit, which we had this weekend. And then we will talk about JSoc 2019 plans. So these are three main topics. And yeah, I think we can just start from the first item, Outreach. Hello, hi. Yeah, just a second change focus. So yeah, you can present if you want. Great, I will do. Hi everybody. Yes, I'm really happy to announce Jenkins as an organization has been accepted to the upcoming Outreachy winter internships. And so just for those who might not be familiar with Outreachy, it's a very similar program to JSoc with a couple of key differences when it's designed to specifically target folks from marginalized groups in tech. So yeah, so it's opening up with the idea of trying to make open source much more inclusive. And secondly, the projects do have to provide sponsorship themselves. It's not tied to one organization like Google. So everybody sort of has to do the bit for funding. So in that spirit, I'm really pleased to say that the Jenkins Governing Board has approved funding for one internship. And we may be lucky as well to take advantage of surplus funds for a second one. So you can see the dates up there in terms of when things happen in terms right now we're just getting the projects launched. And it will be a three month internship from December 4th to March 4th. So we've got two projects we've submitted before the deadline. So one of them with Matt Sicker. So thanks to Matt, who's agreed to be the primary mentor on this is all about adding audit logging to Jenkins. So we've got details of that project then we specifically ask for different experience levels in the skills we're looking for. Okay, go see where that link's not working. And the other project because Outreachy can work on any contribution, not just code. The other project we've put in is improving Jenkins website and documentation. And this will be focused a lot on pipeline and trying to provide people more information about pipeline. So over the next couple of weeks, we expect to be in the application phase of Outreachy, which means people who are interested in applying for the projects will be doing pull requests, asking questions, and we'll be fielding people to the Gitter channel we set up. So we're really trying to model off the great work already done on GSOC. Yeah, that's it. We hope to get some people to apply and be able to find some interns we can work with. Justin, do we still accept other project ideas if somebody wants to join? The official deadline has passed. So I don't know how strict they are on it so possibly but officially the date for getting them in. So we had wanted to put in a couple of others but we were struggling to scope them. So we've just sort of said let's learn this time, have to win. Hopefully we can get at least one intern and then we'll improve for future. That's great. So thanks for driving this effort Tracy. Yeah, and again we'll be learning a lot from what everybody's been doing on GSOC so we'll definitely be trying to tap into the experience here. If somebody has any questions, are there any communication channels we can use for reaching? I have a couple just questions Tracy. Yes. I'd like to know is this expected to be full time for the participants like the JSOC? Yes, I think one of the eligibility requirements as well is they have to have seven weeks consecutive where they can work on the projects and this fixed number of hours. It's not limited to students so anybody can and I know people who have done outreach when they've been transitioning let's say from architecture or something else trying to get into tech. So I think it works really well for that but it's definitely full time paid with commitments and three evaluations along the way. And what is the time commitment for the participants? So I know the seven week jumps to mind. Am I still sharing? So you are supposed to be 40 hours a week full time and so it's full time internship. Do you have a Gitter chat for outreach under Jenkins? Like a special interest group Gitter chat? Yes, we haven't set it up as a SIG but there is the outreach Gitter which... I put the link to the chat. Oh, I stopped screen sharing. Oh yeah, if you could share that. And also we'll stick something in the minutes for this meeting. Yeah, I put it there. So yeah, the result-reaching channel is Jenkins.org. So if you have any questions you can just join the discussion here and ask questions. And yeah, just to really welcome anyone who can help answer questions. And there's a particular focus on just modeling for folks suffering from imposter syndrome. So modeling, figuring out answers, admitting when we don't know things and things like that. So I think, yeah, it should be quite nice to do. That's perfectly fine. Going forward, we find these two separate channels because JSOC and outreach are quite related. So there may be a separate channel is still preferable taking the timelines. Yeah, I'm denied about it. I thought this might make it feel slightly more focused, welcoming, but happy to consider merging or making it a more general kind of channel. Yeah, so maybe what we could do, so we could actually... Regarding channels, it may be not a problem. It definitely makes sense to get an outreach mentioned somewhere on the website. A good idea. Yes, so it could be the sub-project like Google Summer of Code. Yeah, we could somehow think about merging these activities because yeah, we have Google Summer of Code, we have coding, we have outreach. Having them all under one umbrella would be nice. Yeah, at least on website-wise. Because for the most of participants, it doesn't matter which program they take because all programs have different rules and eligibility requirements, but it's still a kind of programs for students. Yeah, that definitely sounds good. Okay, so you might need to think about it. Yeah, the action items here just to come up with the proposal how to do that. Something like that. Does it look good, Tracea? Sorry, I understand. Yeah, I just added an action item for that. Okay, yeah, that would be great. I'm just trying to find... Where in the document is that? So it's linked from the JSoc site meeting. Is it the Mentor Summit notes? Just to add some context about outreach. Last weekend we were participating in the JSoc Mentor Summit and there was a session about outreach. And it was especially dedicated to JSoc Mentors asking questions about outreach. So if you go here, you can find questions about the differences between the funding, other things like CUNY. So we may provide some additional examples of... Yeah, and information about the program. So yeah, the link is also here in the meeting notes. Any other questions about the outreach? One more question from me as well. Thanks a lot, Tracea, for sharing the information. Yeah, thank you. You need help with this from JSoc. Let us know. And yeah, probably some of mentors may be interested to join the current projects. So if somebody is interested, please reach out to Tracea. I believe that having more mentors never hits there. Okay, let's move on then. So the next topic is about Google Summer of Code Mentor Summit. So yeah, we spent two pretty productive days in Mountain View talking to JSoc Mentors. There was something like 250 mentors this year. So from the Jenkins project, Martin, Jeff and me were delegated. So usually it just happens at the late stages of JSoc, depending we discuss with mentors who is interested to go and then we delegate someone. So this time we had three delegates because Martin also won a lottery. So that, yeah. And yeah, I believe it was pretty productive. So maybe you, Martin, or Jeff, would you like to start and summarize your experience? So yeah, I could chat a little bit. I don't have the notes in front of me, but I could give some kind of general impressions. So at the beginning, we did kind of lightning talks where everybody talked about their projects. And that was really interesting to me because I was just amazed at the diversity of projects. I'd been so focused on just Jenkins and there's all sorts of stuff. There's games, there's stuff in the sciences, all of the open source stuff that you know about like Python. So that was really cool. I found that pretty interesting. And then there was the topics I found most interesting were kind of like the general topics. So there was topics like about how to run your org, how many mentors should you have. So the advice there was that it's good to have at least one backup mentor. And if you have the luxury, maybe even more, because mentors can get burned out, they can disappear, they can go on vacation. Some organizations have like different types of mentors. So they may have mentors that work directly with the students and they have other mentors that are kind of floaters to fill in or mentors that just handle scheduling. So that was pretty interesting. There was a talk about how sometimes when a student's failing, it might actually be the mentors fault and so the org admins should maybe take a look at the situation and see if maybe there's a difference in communication styles or some other thing, or if maybe the mentee's not getting enough hands-on or something. So that was sort of an interesting thing. And then so kind of the final thing, since I'm the only one that joined the session, there was a very, very small session talking about trying to get some of these coding boot camps, coding schools hooked up into open source. I found that interesting because my company personally works with a couple of these coding camps that specialize in helping women find careers in tech and it's a way of letting us increase the number of women that work for the company. And we get really, really good candidates. So I thought that would be interesting. I don't know if it's something that would be interesting for Jenkins. They don't have any sort of program. It's just some sort of people wondering how they could get involved and so they talked about maybe trying to do some hackathons or something. I don't know. I'll just kind of throw it out there as food for thought. And that's about it for me. Yeah. Sorry, my bad. I messed up notes. I started making them another document. So Jeff, if you could please put a brief summary to the document. It would be really nice. You bet. Thank you. Martin and what about you? This was my second JSOC mentor summit. And to me that is the best conference I've ever attended. And when I went there in 2016, that's how I felt. Again, I repeated the experience. It's for those who don't know what the, how it's organized. It's the reverse of a conference. So instead of going there listening to prepared talks, prepared talks by prepared presenters, the attendees propose talks. There's a bunch of time slots available. In fact, everything's open. The attendees propose topics of discussion and then we just break out into the different rooms where we meet people who want to talk about the same topics as we want. And the topics I enjoyed the most were the ones about pretty much the same as Jeff. The ones about how to work with students, how to recruit mentors, how to keep mentors interested in throughout the program, how to work with students. Especially with recruiting mentors and retaining mentors, we have found that other organizations have also taken the approach of special interest groups in their organizations like Jenkins recently has. So it kind of confirms the approach that the Jenkins org has been taking. Sorry? About taking. Sorry for the next year. Sorry for interrupting. Sorry. So for example, KDE and Python also work with what they call subprojects, but to us they are special interest groups. And the way they recruit mentors is they go to each of their subproject and they talk about JSOC and they talk about the benefits that each subproject, given subproject, could the benefits that they could have by joining JSOC. And then they ask each subproject to supply at least two mentors per project proposal. And that's how they manage to have, let's say, manage to hire more mentors into the program and grow their program. So they delegate a bit of that to their subprojects. So that was the, I guess the big takeaway for me is what I just described. There's also something that I've learned is some organizations participate in both programs in the Google Code-In as well as in JSOC. So what they do there is they get their JSOC students, they strongly encourage them to become mentors for the Google Code-In participants who are younger in age. And to retain students after they finish the JSOC project, what organizations have, what have learned and shared with us is that the idea is you have to keep these students sort of interested by giving them responsibilities with regards to code or other responsibilities in the open source organization. So they could be full request reviewers. They could be, for example, JEP reviewers. In the case of Jenkins, they could join a special interest group. But the thing is we have to keep them in the loop and not just let it go. Some students will stay, some students will move on to other things. But yes, that's what I've learned, the link between JCI and JSOC and keeping students interested, ways to keep students interested after JSOC. So it's an awesome conference. I want to emphasize that. It's an awesome conference. With lots of chocolate. Oh, my goodness. The insane amount of chocolate. I don't think we ate all the chocolate. We did. Did we? Yeah, we did. Excellent work. So we'll do something like four tables of chocolate brought by mentors from all over the world. I had the chocolate crash, like you have a coffee crash on the second afternoon. Because you can only eat so much. But then it was great. Okay. So that summarizes my experience. Actually, I second what Martin said. For me, it was also one of the best community events I've ever participated. And yeah, it's really well-organized. It's full of open source contributors. And one of the main differences is that it's full of open source contributors, which are community minded because it's Google Summer of Code. So we are from the organizational perspective. It's really nice from communication perspective and conference topics. It's also really nice. During this mentor summit, I was also focusing in addition to mentor student communication topics. I focused on some tooling. So I participated in meetings about JSOC tooling, about some tooling for event management and some others. I also participated in outreach talk just to get information more about the program. Thanks. So yeah, generally it's a really, really nice opportunity to study many topics. And actually we also got some potential cross-project collaboration options because yeah, everybody uses Jenkins and pretty much the same. Almost everybody at JSOC mentor summit also uses Jenkins. So yeah, there are a lot of communications happening in the background. I am still presenting Martin. So yeah, regarding my takeaways, one of the takeaways I have in addition to what Martin and Jeff said, is that we really need to participate more in community activities and promote JSOC. So yeah, of course it's special interest groups, but it's also communications of various events, including local events. So for example, there are JSOC meetups in cities like London, where it's really reasonable to participate the same for other events we do. It's nice and pretty effective to promote JSOC there. Then one of the interesting thing for community members that most likely there will be Google season of documentation next year. It's still work in progress, but if it happens, we really should try to attend. And since there are a lot of discussions about documentation recently and also pipeline ordering specialist group, which is being discussed and developed by many of these now, I believe it's a topic for us to consider. I guess that's it with the summary. So just in case somebody is interested, we have a lot of meeting notes. So you can find the link here. So docs, whatever. So this is a document which contains a dump of all meeting notes we've created during the sessions. And actually there's some links are nested. So for example, open hardware is stored in another document because we detached this session. And if you're interested, just go through these documents and you may find much more information. Okay, I guess that's it for JSOC mentor summit. And one update which I was about doing in the beginning that we also have JSOC 2018 summary blog post finally. So it just took me almost one month to finalize it, but now it's here. So if anybody is interested, you can just take a look. And as Jeff said, there were lightning talks. So we have two lightning talks which have been created for the JSOC mentor summit. So we will try to get them posted somehow. Maybe with videos, it's something like TBD. Okay, that's it. Any questions, especially from ones who didn't participate in the mentor summit? What one has posted a question in the chat? Where is the meeting note that you are opening? I cannot file it. You cannot open it? What? Yeah. Where's the link? The meeting note that you are writing, not this link. Yeah, this one. Yeah, it's here. No, no, I mean the meeting note. This one? Yeah, this one. Yeah, they also paste it in the chat here. But just some meeting notes. If you click into the link, yeah. Oh, crap. Yeah. Sorry about that. I was sure I posted it somewhere, but I believe I paste around clean. Okay, sorry about that. And actually one of the hints which Martin did mention, if you're a Google coding mentor, you're also eligible to participate in the JSOC mentor summit. So Google coding organization also sent mentors there. So for JSOC students, it's one of opportunities to go to the mentor summit. For example, this year there was a GCI mentor who was also a JSOC student this year. So she effectively presented her one project, which is quite unusual for JSOC, but it's one of opportunities. Okay, any other questions? Maybe we can mention that we have a pre mentor summit meeting where we discuss the plans for how we're going to do JSOC 2019. Okay, I've mentioned it. Yeah, I was about mentioning it in the next part, which is JSOC to Summit 19 plan. But yeah, we can go straight to that. So JSOC to Summit 19 plans. Okay, so we don't have so much documents to share about the mentor summit and about pre-JSOC meeting, but yeah, we can just summarize it now. So as Martin said before JSOC, we met together. So it was Jeff, Martin, me, and also Lloyd who is on the call. So we were discussing what we do for JSOC 2019 and how we approach that. And yeah, generally the summary of this approach that we started earlier in terms of looking for project ideas, in terms of preparing infrastructure for JSOC 2019. And we have already started doing some bits. So what have we done already? Just a second, there is a doc somewhere. Yeah, I believe it's here. Yeah, this pre-JSOC meeting. So effectively what we discussed is redesigning of application and project idea approach, because currently we have one page on Jenkins IO with project ideas. It's pretty hard to manage and pretty hard to discuss it for students. So we want to rework it a bit. So which project is still represented on the JSOC website. But in addition to that, there is a Google doc where students can discuss project ideas, get feedback so that we use it and chat to build up proposals. So for example, this is what we had in 2018. Instead of that, we will have a table or whatever this list of projects, short abstracts and links to the detailed descriptions in Google doc. So does it make sense for everybody? It would be especially interesting to get feedback from Wuton, who is on the call, because he was a student this year. Okay, so do you want me to provide feedback for this year or what you should know for the next year? Yeah, so since you're on the user side of this page, it would be nice to get your feedback. Okay, from this page. I think it's okay for me. It works for me. So what I did is I just scroll through the page and see the project that I interest and go to the mailing list to ask questions. That's what I did. I think it should be okay. I don't have any impression or any negative feedback about this. Maybe one more improvement if we can classify it. We can route the projects into different topics. For now, we are putting it like list by list. So maybe... Yeah, so actually it was one of the feedbacks from GSoc Mentor Summit. So there was a meeting about the second feedback about GSoc. I believe it's actually somewhere here. Or maybe not. So what they were requesting is to have labeling happening on the project basis. So currently there are labels in GSoc, but they apply to the entire organization. And students have hard time looking for relevant project ideas. So what was a feedback about... Yeah, I believe that's it. GSoc feedback. So what was the feedback? Instead of that, when students look for organizations, they can look for projects using labels. And yeah, of course we could do something like that on our website as well. Yeah, actually you have the skew section which is something similar to label. Yeah, if I understand. So it's something we could do. So other items we had during the discussions that... Yeah, we really start things earlier. And yeah, there will be an EPIC in JIRA with list of tasks we need to do before December. There is already an EPIC for that, but there is still no tasks there. My apologies for that. And yeah, in addition to that, Jeff and Lloyd will join GSoc work admins. So we will include them in the loops. And yeah, you will have mobile and Wi-Fi on GSoc administration site in order to get projects involved, as we discussed, to reach out to special increased groups, et cetera. So yeah, Jeff and Lloyd welcome aboard. And yeah, thanks a lot for your help. Thank you for that. Yeah, there is still some organizational topics like GSoc budget. We have a JEP proposed by that, but it's still not approved. So we have Jenkins, JEP. There is JEP, which is, yeah, JEP 8. So we still need to get this JEP approved. So yeah, generally it's what we have discussed at the pre-mentor summit. We didn't cover so many topics and I believe we still need to continue discussion. So now it's mid-October and what we really need to start doing is to start collecting project ideas. So if everybody has any project idea, let us know. We will try to accommodate them and we will soon create a list of 2019 project ideas and I'll put all ideas you propose there and then we will start expanding them. So my plan is to create GSoc 2019 structure maybe today. So what we will have, we will have GSoc 2019 project ideas, please. And also we will have a placeholder for GSoc 2019 implications. So as you may notice, there was already an update in Google Summer of Code page. So we moved all 2018 in the archive and yeah, now this page is pretty clean and we will be creating a separate page for GSoc 2019 similar to what we have for 2018 here. If you want to propose any changes or proposed projects, just let us know. We'll put everything here. Okay, any feedback of what else should we do in short term? Oleg, I just wanted to check on a couple things. We talked about moving the project proposals to separate Google Doc documents, which means we probably need one Google Doc document that links to all those sub-documents and we would have a template to help people prepare their project ideas. I think we need a project idea template. Okay. Yeah, I forgot to mention that. So we decided that we will have a project ideas template. So what it will include? It will include a structure, something like what you already have on Jenkins IO website. And we will also add new befriended task examples right to the project ideas. So it means that everybody interested in the project will know from which small tasks to start if he wants to apply and it will be some additional information for potential participants. So yeah, it will be much more than just this small description and they will create this template, by the way, who would be interested to create it? I can create it. I also wanted to start populating the list of JIRAs in the EPIC, going over all the feedback we have received, plus the JSOC notes that we have taken and just create JIRAs. It does not mean we do all of them, but it gives us a list of things that we can do and we can do the ones that we have the time to do and the ones that are high impact. So I wanted to do that. Okay, so to create just a second, I'll find an issue right now. It's here. Jenkins 54 or 59. So it's really empty now. Unfortunately in JIRA, when you're not locked in, the EPICs are always empty, but this one is really empty now. And yeah, I believe we could start putting information there. I also have at least one action item on my side to create the JSOC work admin checklist. So currently we have only mentor and student guidelines on Jenkins IO website. In addition to that, we need an off-codming page so that we summarize how we approach JSOC, how we used to approach JSOC during last years. So it's also something I will create. Okay, are we missing any action items? Question regarding the JIRA. Oh, sure. Do we have a component name for JSOC in JIRA? No, we don't because actually there is a project for that. So it's not Jenkins. There are other projects and one of the projects is events. So what we could do, we could get permissions for all JSOC participants, to manage the events page. But now, for example, I have no permission to create a whatever sprint or dashboard which includes issues from Jenkins events. So that's why I don't use it. Okay. So I believe that events would be the best, I think, to put this information, at least an EPIC. I'm still not sure that it's really what we need, but TBD. So creating the issues in the EPIC, should I use the Jenkins project or the events project? I will start from creating Jenkins and the website. So actually Jenkins, Infra and the website. So there are three projects which we can easily manage now. And I would propose to start from these three projects. And if something is needed, probably we need to request permissions for events. Something like that. Does it work for you, Martin? Yes. Okay, so what else do we have? Work admin checklist, 2019 tasks, JSOC, skeleton is something I can create. This one I will discuss with Tracy. And do we need a summary blog post for the mentor summit? Sorry, say that again. Do we need summary blog post? Summary blog post for the mentor summit. Oh, yeah, we should. Maybe just everybody of us writes a blog post on his own. Maybe not on Jenkins IO, but maybe, for example, on some personal resources. And then we just post three of these blog posts. Which approach would you prefer? If we posted on our own sites, then assuming we all have them then it's three times as many. Two times as many posts. Talk separate blog posts, then. So I'm not very social media savvy. Is this something that's easily doable on Twitter or LinkedIn or Facebook? Or should I really use my super old WordPress blog? Well, LinkedIn is fine. If you want, you can post on Jenkins IO. Okay. Yeah, and then once we have them, we can get them reposted on Jenkins IO or just retweet it. So as we wish. Okay. And maybe we turn on how was your blog post going? Yeah, I'm writing it on my personal website. But still take time because currently I was so very busy. I write like half of it. So it's still in draft mode. Are we having the Jenkins one next week? Yes, we do. I think I will try to do it by this week. If it happens by Jenkins, we will get it. The reference and the update. Yeah, yeah. And then I have one more suggestion for our summer course for next year. I'm not sure whether it's a, I mean, we have time to do it or not. Maybe we can like spend like one or two weeks. We create a training program for students in the first one or two weeks. Whether it's a community bonding or whether it's a coding period. So that the students can get like, they don't have, I mean, we create a training program. Like, what should we expect from the students in this period? I'm not sure whether it's doable. I think we need main power. I'm not sure. Yeah. If we have something like that, it might be like provide like some job. Yeah, so the right approaches to do that. One is to do it during community bonding for accepted students. Another approach is to do it in early application period or before application period for everybody who is interested. My purpose is we create this training and we ask the students to call me to it so that they can produce some small results during this. I'm not sure whether it's, so that we can, yeah. Yeah. It is true. Well, it's definitely something we need to discuss because here there are organizations and the mentors saying that yeah, it's really something everybody should be doing. Yeah, resource-wise. Let's see whether we can manage to do that. Yeah. Maybe. Okay, I've noted this feedback in the document. And yeah, I think we need to talk about that more at the next meeting. Yeah, sure. Yeah. Okay. I guess that's it. Quick question, Oleg. Any questions? Sorry? This is Martin. I have a quick question. Okay, just do it. So I tried to create some issues in the JSOG 2019 work epic, but oh, I can use the other component. Okay. Because it's asking me for a component and. Yeah, let's start from that and then we can move the stuff to events. Okay. Yeah. Okay. Yeah, I will create an entry ticket to get all of us permissions. Yeah. I will try to do it today, at least this week. Okay. No rush. Okay. So Lloyd, any comment? Maybe not. Okay. Then we can sync up later. So I believe we have some plan for the next few weeks. So we need to decide when we meet next time. It would be two weeks period fine. So I seem in that we get all the structural things like project ideas, template, jira, et cetera by that. Does it make sense? Or should we take three or four weeks? I think I'm okay to meet in two weeks. I'm going to have some of it done. That's for sure. Yeah. So let's just try to do a short sync up meeting. And then if needed, we'll do a longer meeting later. So I'll set it and do it. Okay. Yeah. Some. And that's it. So if there is no other questions, thanks everybody for participating or for watching this meeting. As always, this meeting will be posted on YouTube. So you can watch that. And we have meeting notes posted. So I will just process it and put on Genki's website, like we do in other special interest groups, so that we don't lose this information. And yeah, see you in two weeks, guys. Bye. Okay. Okay. Thank you. Bye-bye. Bye.