 Hello, everyone. Today we have a sync up of Google Summer of Code Special Interest Group in the Jenkins project. We will have a discussion about what's going on in the project, what are plans for GSOC 2019, and what we still need to do for GSOC 2018 and its follow-ups. I'll start the screen share right now. Do you see my screen? I'm not right now. And what about now? Yes. Yeah. So you're probably my laptop just hangs a bit. OK, so I present to everyone so that it also appears in YouTube. OK, so we have a meeting notes document. Everybody should have access to that. I've pasted the link in the GSOC GitHub chat, and there is also a channel for the participant link, just in case somebody wants to join. So we have three topics in our agenda. So action items and then what we discussed previously. So we have Jeff, Pierce, Tracy, Miranda, and Sokum, Christine, Oleg, and Lloyd on the call, right? So we don't have anybody else. OK, I'm terrible at making notes, so please feel free to edit it in parallel if something needed. Let's start from the action items. So the first one was to me and Tracy to come up with a proposal of how we integrate all the activities on the Genki SIO website. I believe it's still to do. At least we didn't discuss it. Yeah, progress from outside. OK, then next one, create individual summary blog post for the mentor summit. So Martin's one was posted. My one, I haven't published it yet because it was less than one week from Martin's. And what about you, Jeff? Yeah, so I created mine, but I haven't published it yet. I was waiting for the link to get the one on Jenkins I.O, which was probably done quite a while ago. So I think I can publish it now. Yeah, so you can just publish it or if you prefer to publish it on your personal blog, it's something you can do. Which do you think is better? I don't get very much traction on my personal blog, so maybe it would be better to publish it on Jenkins I.O. Well, you will make sure to repost it to you in Twitter, Facebook, and then it's generally your decision where you want to publish it. So if you prefer Jenkins I.O., it's also fine. I'll go ahead and do it on my personal blog then. OK, yes. So as you wish. Just once you publish it, send us a link in the Gitter so that we can promote it. And I'm there in the behind all my tasks. I'm trying to catch up, but it takes a while. Regarding JSOC 2019 skeleton, so actually this task is kind of done. So what we have now on the JSOC website, we have a JSOC 2019 page. There are project IDs. There is a pending pull request from me to somehow refactor it and to have metadata. So we have Jenkins I.O., so actually it's here. It fails, I'm not sure why. But yeah, once we do that, we will have a revamped project IDs page. So the page will be small. But we will have pages for each project. And there will be some metadata. So later we can create search links or whatever other features if we need. So as an example, each project is defined in a YAML file. Just not YAML ASCII.DOG, but there is YAML metadata, like skills, mentors, et cetera. And we will be all supporting new befriended issues there and maybe keywords. So it's something TBD, but it's in the project, in process. Regarding the rest, also there was a pull request from Lloyd about adding a schedule. So currently, if you take a look at the subproject, Google Summer of Code, I believe there is also a 2019 page. So there should be a 2019 schedule, right? Yeah, this one. So you start putting some information there. You will need to clarify that. But at least the skeleton is here. And we need to proceed with it. Regarding the JSOC templates, so I have some updates. Martin actually has completed that. So there are templates in Google Doc. There is an ongoing discussion between Martin, Lloyd, and all other participants in the chat about how it has to be addressed. Because the original plan was to have Google Docs. Then we have a question about removal of Google Docs. And since we don't have a JSUT or whatever, we cannot really keep them in a safe place. So we have two options on the table. One is keeping it in the wiki. And another one is just keeping it on Genki Sayo, which is the current state. So my question to participants would be about your preferences. Yeah, my preference is not mentioned in the video chat. So your preferences, I don't hear you. I said my preference is Google Doc. I mentioned at GitterChat. And then when the final authoritative proposals that we send to Google, that will be published on Genki Sayo via ASCII Docs. So they can't be changed. But for the initial document creation, revisions, and comments. It's more effective using Google Doc. Yeah, that's for sure. So for us, there was two questions. One is proposals by mentors. And keeping Google Docs is perfectly fine. Or just asking them to propose a pull request, whatever they prefer. And another question for us is about student comments. So one of the issues we had in the previous years is that when you just put project ID on Genki Sayo website, something like that, there is no clear way how to comment on that. Our suggestion was to go to the developer mailing list, but it wasn't really comfortable. And Google Doc link is one of the approaches we wanted to use. But it's not clear whether we still want to go forward with it. Unfortunately, there is no Martin on the call. So probably we should park it for now. But yeah, it's still an open question. Tracy, how do you approach it? How to reach it, by the way? Yeah, always. But then for the actual submissions, you have to use the outreach as an online place to enter the project, so all the details stay on their website in a fixed format. But I don't know of going forward. Yeah, we haven't really thought through saving those ideas for the next round yet, so we'll probably learn something of sync with what you're doing. So generally, you use mostly Gitter now. Sorry? You use Gitter for the discussions. Yes, for discussion, there's Gitter. The outreach also has its own chat thing called ZULIP, which they're trying out this year. So we'll see. And that's to help mentors across different projects to communicate. So I can let you know how that goes and not much evidence of. Well, actually, I don't know what's happening yet. It's just been set up for the first year, and the program hasn't started yet, so let's see. So it's outreach in general? Yeah. Something like that. So yeah, personally, I'm pretty fine with mainly please send a Gitter. So if we prefer to stay with such approach this year, I would be fine. So without confluence overheads, one of the things which may help us, actually, we now have special interest groups. And what I plan to do, that we will be having Sieg links, so that particular discussions can go to the special interest million please, instead of the Jenkins developer million please. It may also help a bit to detach discussions, which was one of the main issues. Because yeah, one problem that we sometimes have something like five students asking about the same project. They start different threads, and it's a pain. That's why Martin raised this question, and that's why we came up to Google Doc proposal. But yeah, I'm not sure we can discuss it more right now without Martin. So let's finish with election items. Then putting 2019 tasks, actually, we had this in-cub with Martin. And we have created an epic with some top level tasks here. These are not all the tasks we need to consider, but at least we have this epic. So yeah, I believe it's here. I'll just put a link so that we don't forget about it. Two, seven, 19 tasks. Then work admin check list, it's work in progress. I still need to submit it. But so let's make sure that I submit it by the next meeting. Because yeah, there is already some discussion that is a lot about the schedule, so that we do not duplicate the information. And I'll make sure to do that. I like to request permissions for events in JIRA, for all JIRA cork admins, it's still to do. Because yeah, we still don't have a full list of JIRA cork admins for this year. It's to be decided. I still didn't get an answer from Steven Crystal whether he's interested. Yeah, then this item is done. So, which one has published his blog post? It was retweeted. Yeah, I can try to find it. And this one is done. So effectively, we proceed with weekly meetings, at least for now, while we prepare for everything. Yeah, this meeting is one hour. But if we have less topics to discuss, we can just drop earlier. Probably not a case for today, but maybe for the next meetings. OK, GSOP 2018 leftovers. Should we discuss it now, or should we postpone it? So who is interested in this topic? From the scheduling perspective, just are we all done with shipping swag? No. So we haven't even started in general, because we're behind traveling, et cetera. I have a list of deliveries, but I haven't done it yet. So swag delivery is one of the technical depth topics, and we should do it ourselves, of course. And another one, which is left over, is JEP for JSOC budgeting. So the story behind it, that we have JEP, which would allow us to manage the budget without waiting for governance board approval for any action, like sending swag, et cetera. So there is JEP for that. And I'm still waiting for the feedback from BDFL. I pinged KK two or three weeks ago, no response so far. But I'm not sure how much is the blocker for this year. We do not expect much spendings till June, I believe. But it's still something we need to get over the fence. And we need feedback. So these are two major items we have in the list from the previous year. And as far as I can tell, we don't have anything else. Am I missing something? OK, we saw 2,000 thanking. So our current state is that there was an announcement from Google Summer of Code. So now we have official program, Summer of Code 2,019. So now we have official timeline, which has been posted and which we can refer to. So one of the interesting things that this year application deadline is February 8. So last year, they moved JSOC a bit, so everything starts a bit early. And we needed to, so for example, application deadline was something like January 15. And then the final JSOC phase was mid-August. So it was something complicated for us. And it seems they moved it back because there was such feedback at the JSOC Mentor Summit. So now we are good. And one of the reasons why we are good, that application deadline happens after FOSDOM. So it means that we will have an opportunity to discuss JSOC at FOSDOM, that is usually a hackathon. And we can get some bits like documentation, et cetera, over the fence like we used to do in previous years. But yeah, I'm not sure who is going to FOSDOM this year. I'll probably be there. Usually JINX project organizes hackathons there. And yeah, it was one of the options. But yeah, I'm not sure about this year because I'm not sure I will be able to come. Yeah, I think February 4th are likely to have a JINX community. Possibly hackathon. Anyone else going to be there? So I believe everybody else on the call is from the United States. And Sopun is from Asia, so probably no. But if you have similar events in your nearby location, if you can go there, if you can present Jenkins, if you're interested to talk about that, it's something we will definitely appreciate. So for example, there is scale in the United States. I'm not sure whether it happens on the winter this year as well, I guess. And yeah, so probably FOSDOM isn't the option for us this year. Previously, all our card means we are going to FOSDOM, so it was more convenient. Not this year. And actually, it would be good for us to apply earlier. So let's start on January 15th. My proposal would be to actually target this date as much as possible. And since we have all templates, we have samples from previous years, it shouldn't be a big deal to apply. The thing we really need right now is project ideas. Regarding project ideas, what we have now. So we have five project ideas on the website. We have pending project ideas. So three project ideas pending right now. They will be blocked because we will be working the project ideas side. So the project ideas we have right now is a multi-builds equivalent for pipeline. Then we have one idea is about the still agent slave to agent cleanup. It's something we agreed to add to this year. I'm not sure whether we still want to do it Tracy, but yeah, maybe we should post a project idea if there are mentors who may be interested. And then we have one is support of deployment environments and traceability. I'm working with a submitter. And last but not least is Andre Falco. It was something for Docker, right? Yeah, I'm just missing the page. Yeah, it's for Docker integration. So yeah, maybe it's obvious that we may have something like nine project ideas, which probably a decent starting point. But what we need to do is we need to go to special interest groups and ask for project ideas there. So for example, as a leader of Platinum Seek, I will try to get at least one project from there. So is anybody familiar with special interest groups? Yeah. OK, so then it's here. But actually, the specifics of Jenkins that not all sub-projects have six right now, sub-projects. So in addition to six, we also have a list of projects here. And actually, if we can get some project ideas from active projects, it's something which could help us a lot because we can start from project ideas. So literally, we need to get to something like 20 plus project ideas. And we need to work with the community on that. And it leads us to several action items. So we need to announce GSOC on our site. Oh, I forgot about one idea just a second. Announce GSOC on our site. So it would be a blog post plus a developer list. Announcements and go to seek meetings. And they invite people to something like that. So by the way, is anybody on the call interested to propose their own project idea? And that was hard to think of things on the spot. But we'll make sure to edit the doc. OK. Yeah. Yeah, so generally, you can just start preparing a template. So since Martin is on the call, he may be able to just paste a link to the template. And yeah, it's pretty much the same as previous year. So you can just take something here. And what we expect in addition to what we had before with project ideas is links to new befriending issues around your project. Whomever is interested in your project proposal may try to get something done before the application. The rest is exactly similar like we had in the previous year. So we still have some proposals around. So we will likely remove chain acceptance test harness from this year because we need mentors for that in order to do that. And the idea plugins will stay, your strategy will stay. And the cloud features will stay. Thanks, Martin. OK. Yeah, effectively, project ideas is the only big thing we need to do right now till the end of December. Because the rest is fine. We just make a proposal. And we have all templates, so it's not a big deal. We need to work with potential mentors. So do project ideas need to come hand in hand with mentors? Technically, yes. So if you have a project idea, it's still nice to get it somehow recorded. But what we need to do when we post project idea on the website, we need at least one mentor. So there is at least one contact person so that everybody interested can ask questions. But if you have a project idea without a mentor, then probably we should talk about posting it somehow. So for example, I have one project idea from the previous year. It's about accessibility of Jenkins Web UI. For example, colorblind mod, just to be specific. Yeah, I have project idea. Probably it's even a better fit for outreach. But even for JSOC, it's something considerable. But we really need mentors in order to pull this idea off. But if we can do that, it would be perfect. So if you have some such ideas in mind, probably if you write up a description, it would be still really helpful. Because we can have a shared pool of ideas for JSOC and outreach. Yeah, that would be good. There is not much difference in the terms of project ideas, descriptions, et cetera. And yeah, we can create a pool of such ideas so that we can extend more. So yeah, you may see that there is actually a lot more of project ideas here already created by Martin. So and yeah, this is actually a good action item. So a pool of project ideas, a shared pool of project ideas. Does it make sense? So I'm not sure whether Rick is on the call. Yes. Oh, yeah, so you can just describe your idea here. I mean, I just read. Yeah, I just see another Mr. Jenkins. So I didn't recognize you. OK, so yeah, if you want to add it, just add it to the list. And yeah, I definitely know that Owen Mechaghan is looking for maintainer for the GitLab plugin. So maybe it could be somehow aligned. So is it something you would be interested to lead? Sorry? Would you be interested to mentor this project idea? OK, I'd like to be. OK, yeah. Maybe we could also find something specific to change is localization seek. So yeah, for example, if you have project ideas, it doesn't have to be only code. So we're still interested in the code because it's Google Summer of Code. But for example, if you want to create frameworks, if you want to create engines for Chinese website, it's still something we could organize. And the same for Jenkins infrastructure, there is a lot of things we could do there. And JSOC, yeah, we can take any of the services it needed. So yeah, over the next month, we should just reach out to people and ask them as much as possible to work and to propose project ideas. And if we get to 20 to 30, it would be a great advantage for us because the account matters in this case, especially the account of really good project ideas, which we can be taken by students. OK, any questions? I have a question. Sorry I'm late. My question is, have you already talked about reaching out to the different Cs? Yes. Yeah, so I'm not sure how we split this task across Orca means, so it would be really nice to load balance it. So for example, we can create tasks for each C or for each sub project and assign it to Orca mean, or maybe to somebody who is interested to volunteer and do that. Would it be OK if we follow this approach? Yeah, I'm sure. Yes, I want to reach out to the Cs and we can load share and each pick our Cs. But there's only five Cs, right? There is five Cs and there are sub-projects which are not special interest groups. For example, Jenkins SACs, Configurations Code, the infrastructure, they have regular meetings. They have a meeting list. They have charts. So they look like six, smell like six, but they are not six. But for us, it doesn't matter. So we still can reach out to them. Oh, OK. Yeah, so whatever opportunity we have to get mentors involved is something we could try to do. And yeah, why not? Is there a list of how to reach them somewhere? OK, just. Yeah, I already screen-shared it briefly. So yeah, if you go to the Jenkins site, there are a decimized screen now. Yeah. Yeah. So for example, Jenkins SACs, if you go here, there is OK to the Slack channel, for example. So we can use these slacks. I'm not sure whether they have many lists, but yeah, there is, for example, a meeting tomorrow so somebody can just join and participate, especially if you're interested in Jenkins SACs. But yeah, probably it makes sense to start from charts and Slack before going to the meeting so that there is some discussion happening before. Pretty much the same about, for example, configuration as code. There is a Gitter chart, which is really active now. For infrastructure, there is IRC chart. You can try asking there whether it's made at least. So depending on the project, the approach may be different. OK, do you want to talk about splitting the work, splitting the reaching to SIGs now, or do you want to take it offline? As you wish. So we have some time, so we can do it now unless there is other agenda topics. I'm fine doing it now. Any other topics, Jeff, Christine, Lovitt? Someone Tracy? Not really. Is there actually a good time for us to go and talk to the SIGs and maybe so we don't all go into two different meetings and pitch it twice? So yeah, that's why we can load balance it. Yeah. So for example, SIG, let's say SIG, project mapping, that starts from SIGs. So it's CloudForm, CloudNative, then chain is localization. Yeah, JSOC, and your pipeline link. So my question to you, would we like to have a specific JSOC project for the JSOC specialist group? Probably no. I don't think we do. That'd be pretty funny, though. Yeah, it would be interesting to find something. But yeah, I also have nothing from the top of my head. And yeah, Jeff. I was going to mention I think Google is also starting a new, it's like GSOC for technical writers. Yeah, it's a. That's something in the area without my help for the GSOC activities. But I don't think we're ready to take that on right now. Well, we are going to take that on. But even Google is not ready to do it right now. So as we discussed in the previous meeting, Google's season of documentation is something under the discussion. And we have Jenkins project contributors who are specifically focused on the documentation. So I have my action item to get it organized. But generally, it's autogonal thing. So it may be happening within JSOC SIG, but it's widely to be discussed. Even last communication I've heard from Google that probably it won't be managed by Google's community team because, sorry, open source team. Because yeah, they have a bit different focus for season of documentation. So right now it's out of the scope. But yeah, I will do some follow-ups. So be sure we apply. And I have already added Jenkins project to the list of projects interested in Google's season of documentation. OK, I'm back to SIGs. So for example, we have RIC on the call. So probably RIC is the best contact to reach out to Chinese localization. I guess so. For me, it's the same for platform special interest group. Now we have pipeline operating. It's not a special interest group, Martin. Oh, sorry. Yeah, we will get to it. So who does want to talk to Cloud Native Jenkins SIG? Is that Cloud Native's same thing as Jenkins X? Yes and no. No. Have any? Yes. Right now Jenkins X is not a part of Cloud Native special interest groups. I believe it may happen. It may change soon because there were discussions at the contributor summit in the United States about them joining the project. But so far, no. So these are orthogonal things. But yeah, obviously there is a lot of communication. So yeah, I'll keep it separate for now. Yeah, I'll reach out to Jenkins X because I recently joined their Slack channel. But I need to find out when they're hanging out and so on. I think James did make show interest to Martin I don't know whether they're ready to take on mentorship or not, but I can reach out to Jenkins X. OK. So about Cloud Native Jenkins? I don't know. Sorry. I was just going to say, I can take them, but if you want to, that's OK, too. Well, as you wish. If you want to do that, just go forward. And yeah, I can also help. But yeah, if you want, I'll just leave it to you. So you drive it and I'll help if needed. Yeah, my memory is sick. I think I am technically too, but I haven't joined many of the meetings. Yeah. So yeah, maybe we can just do it as is. So generally you can start from the mailing list and from the Gitter Chat. So the Gitter Chat is here, for example. You can just join and bug people. I'm not sure how many people we have right now here. But yeah, it's still something which we may utilize, at least getting some visibility. So Pipeline AutoRank, Christian, would you be interested? I can help with that one. Or I know a couple of people on the Evergreen group. I was like, I can help out with that one, too. OK. Yeah, so if you can help with it, it would be really helpful. So for Pipeline AutoRank, I was already talking about some projects at the inaugural meeting of Pipeline AutoRank seat. So we have just a second. So we have promoted builds equivalent for Pipeline which I will submit to the results Pipeline doc, documentation generator. And they even mentioned that was something they were looking for. So I can definitely think that they're going to get behind. Yeah, right. So the main problem with this project is that they're probably not ready to commit to my project right now. But yeah, I'm not sure. I think there's already a project proposal related to documentation that Kristin and I kind of started talking about last year. Yes. Yeah, right. So yeah, if you can somehow rework, so why we didn't get much attraction with this project last year is because it wasn't much about code. So if we can adjust it so it's a coding project, then it's totally eligible for the summer of code. And actually this thing may be one of opportunities. OK, I'll kind of beef up the part about how there is code involved. It's just maybe it wasn't as apparent to be in the project proposal to anyone who might have been interested if they were worried they'd just be writing documentation because it's there. But they're right. So what else we have? Configuration as code. Actually, I wanted to talk to Vylina about it today, but she was unable to attend the daily meeting. But yeah, I could just sync up with Vylina and maybe we could get something organized there. OK, I was interested as well in this one. OK, so. But OK. So just take it. It's perfectly fine with me. OK. OK, that's it. So what else do we have? Infrastructure. I had an infrastructure idea the other day. Which one? Oh boy, it's either on the Gitter Chat or on IRC. Oh, it's the Update Center. Danielle Beck keeps telling us that the Update Center is a. OK, I'm going to quote him. He says the design is shitty. And I replied back saying, well, would you like to have help? And the first reflex, the first response we get from people when we offer help is that they don't have time to spend on someone who wants to help them. So I was trying to convince him that four hours a week, five hours a week of mentoring could solve his Update Center problems. Oh, wow. If it's a problem. I don't know. He has a leader of security team, and he has a lot of other things. So I understand that it may be difficult for him to dedicate even a few hours sometimes on the consistent basis. One of the things, ideas I can offer to you, recently, we have hosted the Giuseppe on the JNPCI organization. It's actually Embedded Update Site, which is a kind of standalone project. It's an Update Center generator. And if you don't want to mess with infrastructure due to whatever reasons, so it would be one of the options. You may want to consider if you want to do something standalone, for example. But yeah, of course, if you're interested to work on something within infrastructure, you may need to talk to Daniel about that, and maybe to Olivier, who now leads many infrastructure efforts. OK, I think I met him at the Olivier. I met him at the Hack House, right? He was there. OK. Yeah, I can approach Olivier with that. OK. If you'd be interested. Yeah, so maybe it makes sense. I'm not sure, but yeah, it's worth trying anyway. And yeah, then what else do we have? If we take a look at Jenkins IO. So subprojects, there is so remoting. Well, we did a good project this year, which we could continue. So actually, I wanted to discuss with Oton whether he wants to somehow organize the follow-up projects for that. So it's something I will do, I believe. So it's remoting, maybe together with Supoon. Let's see. Then regarding other projects, we have Bloatio. I'm not sure. And yeah, I believe that's it from the list. So I tried reaching out to Bloatio contributors multiple times. Maybe it makes sense to at least ask in the chat. But I'm not sure how effective it will be. But does anybody want to try something in this area? Don't use Blue Ocean. So it's not something that I know. But asking for reaching out to them to see if they would be interested in participating in JSOC is something I can do. But I won't have much in any ideas for them. Well, they started working on extensibility recently. So now it may be quite natural, for example, if we take code coverage plug-ins story, if Bloatio extensibility is available, then probably adding a project to have coverage integration for Bloatio and something like that. But yeah, it still needs discussion because I'm not sure what's the state and what are the plans for this sub-project. OK, yeah, maybe I'm not the best person. OK, so let's park it for a while. So I'll ask around and understand whether it makes sense to push in this area at all. So yeah, I'll just sort of assign it. And yeah, by the way, there is a big active project. So if you see a plug-in or if you know that there is some activity in a particular group, you can just go there, offer something. So just in case you have any ideas, reaching out to people directly is really nice. And if you want to do that, just put something here so that we know that you're going to reach the particular people and we can also synchronize. OK. So any other topics for today? Because yeah, we're running cover time a bit. Yeah, we spend some time on setting up the recording. But yeah. There are some guidelines in the Jarrett tasks. Do they have or are people going to be taking ownership for them, like the ones for the mentors and the students? I'm asking because for me not having been a student or a mentor, I'm not sure if I can write out the guidelines. But if others have been mentors and students, maybe it's easier for them to write out the guidelines. So if you see such tasks, I believe that the goal for this week for us is to just get the pending changes for the site and the project ideas framework ready. And then let's talk about mentor and student guidelines next week because yeah, we have something to do there definitely, but maybe we'll have more when the wife to discuss it. OK, sounds good. OK. So now thanks, Martin, for scheduling weekly meetings. So then we meet weekly and yeah, let's try to make everything scrolling. Is it too early for you, Jeff? No, not at all. I get up normally about 5 o'clock by the end. This is 6 AM my time, so it's perfect. OK. So I guess that's it. And yeah, let's sync up in one week. So thanks to everybody for the interest. And let's try to get project ideas on the table. OK. Thank you. Thank you, Oleg. Yeah, thank you. Bye. Bye. Thank you.