 There we go, so here we are a second meeting of the G-Soc Jenkins Docker base quick start It's our first weekly meeting. We had the kickstart meeting last week and Today we have of course, I should wash be a viento and also Jean-Marc Just listening for the time being I Hope said we'll join a few minutes from now. So of course last meeting was what? Four days ago. So not so much was done during last meeting and Now and of course, it was a weekend also. So that's also why we didn't progress that much So we had a list of action items when we saw each other Last week there were some things I had to do some things I should wash had to do and a few things got checked So we have progressed So we now have the zoom meeting invite Link to the Jenkins account. That's why we are able to record and the recording will be available then later on on the community Jenkins IO website in the post that we created especially for that The first video of the first meeting has been posted on these community posts, so I've done my shores I Was supposed to start a discussion also with the infrared team because as you know, we hope to have our Docker base quick start examples part of the Jenkins IO website and tested on a regular basis So we'll have to discuss with the infrared team so that they can help us to automate that So I started that last Friday and And We'll discuss about that later on but we will have to create a post on community genkin dot IO and tag people from the infrared team So we can discuss with the infrared team and the rest of the community about this automation process Then I should have had to create a Google calendar meeting invite which he did because we are the four of us in this meeting so that worked and And while it was supposed to give to create to modify sorry that document of You know the GSOC document linked to this project on the Jenkins IO website, which he did during the weekend Thanks, baby unto for your review by the way because it allowed it to be merged. So that's first win congrats for for that And that's there are also a few action items that we didn't have time to do So I put them with all their action items on the action items of today There we go. So Actually, how are you feeling today about the progress and the project in general? Yes, I'm feeling good. The only thing left was the blog I'm working on it right now. I think I'll complete it today. So I'll I'll post it in draft as a draft PR Since you mentioned it in notes. Yeah, the thing is I was That's not a problem at all But I was kind of frustrated because I saw that you created a pull request and say, um, I Won't have a look at this during the weekend because we didn't ask Ashutosh to work on the weekend But he did nonetheless and I wanted to review it this morning And then I discovered that the aviento you had reviewed it that Chris had pinged us and That it was already merged which is fine because of course my review would have been looks good to me So no value added on my side. So just during the weekend If the other are okay with that Maybe you could create a draft pull request instead of a pull request. So that Mentors can have a bit of time to assess and to review the PR. I know it's not 100% Fine because our meeting in on Monday pretty early for us in Europe So If ever you were making a draft PR We wouldn't maybe not be able to Review or get it merged before the meeting, but yeah, I don't know. That's just a proposal That's not a strict rule. If you don't agree with that. That's okay with me It's just because I was not able to review during the weekend. I chose I'll keep it in mind to post it as draft PR and on weekends Okay, if you can and you although don't mind fine with me. Thanks for understanding How did you find the review process Ashutosh Review process was I Worked fine for me. Everybody was nice and helped me to Help me with the PR So yeah, it was good So I have a few action items will discuss But you told me that you were already working on the blog post for the project, which is cool So that will be able to tick on before next meeting Then you created I saw that in the Github channel. You just created your own repo To host your experiment. That's right. Yes So I would like to get the link into The project page if that's not an error John Mark should tell us if it is But I think that's the least of the different things should be listed in that project page No, thank you so so like I confirmed is the way to go so you can start with a repo in whichever What's the name on Github domain or Organizational yeah organization exactly just make sure that the links are correctly published to continue and Try to use the PR method is the best way for people to review so Don't push directly to the main branch because then people don't see what's going on and you don't give them a chance to My two cents of advice on that but Well done Thank you, John Mark the thing is we have I Wouldn't say branches, but yes, we will have to write some documentation on Jenkins that I also of course You've got your own fork and you will have to use branches on your fork before making a PR Haven't checked, but of course, I guess that's what you did with your Jenkins project. Okay Because master to master that's a mess But then we have another repo which is not linked to Jenkins that I owe well your story or document compose files for documentation and It would be also fine to use branches for that even if we don't Make pull request to another repo just to keep things well separated and to have a main Branch that always does work and all other that could be called feature branch or whatever Maybe Burviento or say it will have better idea than I have but you know when you're working on a part particular Subset of what we are asking you to do maybe Create a branch and then make a PR to your own main branch So we can review and whenever this will be accepted merge Even if it's your own repo that would be better I guess to have something that always work on the main branch, but I guess that later on we'll have to make another branch on your fork of Jenkins that IO repo So your Docker Composify get integrated into the Jenkins IO website, but for the time being we're working with a standalone repository with your own Examples, but please do use branches Whenever you are starting with a new Docker compose or a new feature that you want to implement But I don't know would you have anything to add regarding branches repose and so on I Think I should just need to add us. I started fewer because sometimes I lost His PR Fine with you. I Don't understand what he said. Can you repeat it? I mean when you create a PR You need to add us the mentors as a review this Okay, okay. I'll do it. I'll remember the next time cool Why are we there it's only the beginning of the meeting Do you plan to take some vacation as you touch and be a viento or Are there a few weeks where you won't be available during the summer? I will probably be Won't be able to work for two three days while I'll be traveling that's it I'll inform you beforehand But it will mostly be two three days not more than that Okay Do as you please the Honest thing I'm asking is to get to know that before it happens No, no rush. No pressure. But whenever you know the dates, please let us know so that we don't expect anything from you during these days I Should take some vacation during July or August, but I don't know yet about the dates So I'll also let you know when I won't be available They have done anything about your time of vacation or anything I don't have any vacation But okay, I have some public quality But not not much Got it. Oh, I should maybe Share my screen because I'm entering some notes and you can see that. Oh I thought I was doing it too bad There we go Okay So what do I have in the action items so I should I'm asking you to Modify so make a new PR if you don't mind about the project page because I'd like to see The link to the community blog post, you know the blog post Which is about The videos and so on you know the meetings I think it would be interesting to have this link in the Jenkins project page Come on Yeah, there you go. The first time being there is only one video and a link to the Google doc But I'd like this link to be part of the Jenkins GSOC project page then Thank you. I would also like to get the link to the weekly zoom meeting that we having now You know on the project page. So if you can extract the URL from the Google calendar invite that would be fine so that if anyone want to join is able to join What else I haven't seen that in the other projects, but if you have it I'd like to add the link to the GSOC office hours on Thursday to link on the project page Because there's already the paragraph some line about the office hours meetings But there is no link for the time being Yeah, I think that's the same thing so I should get rid of that. Okay Then I know it's pretty early But you could start the discussion on community Jenkins.io About the mandatory steps to get automation started, you know, whenever you have a docal compose that does work for you We'd like to add it someday in the Jenkins I.O And it should be linked to an existing documentation But also and at the main point we'd like it to be tested on a regular basis Thanks to the Jenkins infra team. So we have to start the discussion with them And the rest of the community to know how we'll be able to implement that for example They did something special for another GSOC project, which is Jenkins plugin health You know, they had to add something to test regularly and so on. So that's the same kind of things So first thing would be to create a community Jenkins I.O blog post and then tagging the infra team in that post I think I have written something about that Yeah So I have started in discussing with them and they asked me to first create a post in community Jenkins I.O So the whole community knows about that and then I think we they will ask us to create a ticket an issue into their help desk, which is help desk dot I put the link in the action item You know, but first time being we should not create A ticket into the help desk. It's way too early. We don't have anything to share We don't have a docal compose that has been validated by the mentors and so on. So Not need to start that, you know, they'll basically there, but please create Whenever you have time no rush Um a discussion on community jenskins.io. Is it okay for you? Yes, it's okay Okay, cool Uh, what else do I have? Uh, the link to the Gitter channel. Yes, please add that also on the project page And Yeah And that's all I had for the action items I said I would have discussion with the docs seek to know how to modify the existing documentation, but uh first things it's on Thursday, I guess so it won't happen before this Thursday And we don't have anything to propose yet. So I just start the discussion, but There is nothing concrete that I can share with the platform seek for time being so that will just be an introductory discussion Okay for you Cool Yeah, if you want to is there anything you would like to ask to add a comment to question something Okay Thank you Um, Ashutosh What about you? Is there any concern? question I was wondering if the sec team or the infrateem records their meeting so I can get to know the people that work in their teams Yes, indeed The infrateem meeting I should start to search for the links I will write it down And docs office hours So I will let you know, of course, uh, there are some uh videos It's available on the community Jenkins IO by the way, if you make a source about infrateem You should find the videos. There is one post per week because it's on every Tuesday So if you want to see what's going on, it should be fairly easy to find that in community Jenkins IO Uh, most of the time the people we see in the infrateem meetings are Mark Wait, Mark wait um Damien DuPortal Damien DuPortal, I guess Herve Le Meur Stefan Meurl, and I'm there but just listening because I do nothing which has linked to the infrateem I just try to understand what's going on. That's why I'm part of this meeting, but I do nothing in that area And for the docs office hours most of the time, it's also mark wait is just about everywhere and kevin martins And most of the time are also there just to listen to what they have to say I don't participate that much in the documentation part of Jenkins Does that answer your question? Yes, it does. I'll try to see the videos and understand what they work on Okay, there are quite a few hours so It could take some time but on The blog post and on the post which are associated to the videos on coming to Jenkins IO You will find some summaries. So you don't have to listen and watch the whole video Just have a look at a few of them. So you'll see what it's all about and maybe try to find the post on communityjenkins.io Regarding, you know, the modifications the infrateem has done for The Jenkins health plugin, you know, because they had to make something that looks more or less that what they have to do for our project But that's not mandatory. If you don't find it, that's okay. I'll ask it about on Gitter channel If I don't find it Okay, great Um, any other question? No, uh, not right now Okay, so what's missing? I'm looking at my checklist So I think you are kind of familiar with the contributing process So, you know how to use git the workflow the communication channels or that is pretty clear for you, I guess Yes, that's cool Okay The communication channels we agreed to use Gitter Yes For the most part slack is still there But we may not be that active on slack. We do prefer to use Gitter and one of the argument against Slack was that three months from now all we wrote will just disappear because it's a free version Um comparison Gitter should stay as long as Gitter exists hopefully We saw last time that you had your own local development environment And that you were able to launch darker compose command Yes cool What has to be done is to know how you will divide your time Along the next 12 weeks So we should have maybe A quick review on your proposal if you don't mind so we know How you think you will progress during the 12 weeks after the bonding period Okay for you if you have it With you Could you please share your screen or I do it myself if you have a Problem I think Okay Thank you Okay, so automated testing this one may be delayed because it should take some time to discuss with Infra team Uh the documentation could be done in parallel, I guess So coding begins on the 29th. Oh seven days from now scary So define Extend ocular compass file. Okay extend Okay, great So it looks like we're wired for success. That would be cool. So we're not on the Coding period yet. I I know that Should be frustrating for you, but we have to do our shores first. So administrative documentation block post and so on That's the way we're supposed to you If you ever want to start Aside from that a few code A few darker compose or whatever. Of course, you are not restricted You can't do it nonetheless, but we have to do first what we're supposed to do with that time period, you know, we have to Make all the block post the documentation the Discussion channel and so on we have to do that. And then if you still have time, of course, you could start something But that's not mandatory I'm still looking at my checklist Okay, that looks Pretty good for the time being Jean-Marc, why are you there? don't jump on your mic button, but Anything you would like to to say a comment question something I forgot I needed to find a screen back where the zoom meeting is going on Sorry about that. No, it sounds good. So it it sounds you're You're exactly matching the goals of the bonding period and so All lights green go go go Thank you so much, Jean-Marc Yeah, I was afraid I would have forgotten something really important if that's not okay. That's perfect We're here together to Think and put ideas together and adapt to the situation. So Don't worry. Let's go. Thanks a lot Um, I should just in case you would start coding Which I totally understand During for your proposal, um used Blue ocean and so on and I know we already had that discussion Yeah, we don't want to use blue ocean anymore because it's not It won't see any updates or features. Uh, yeah, it's it's officially a end of life and the replacement is still in work So what we would like is to have the simplest jane kins instance possible, which is just one jane kins controller And one j kins agent working together Um, and just one very simple job if you don't mind And that's all Okay, we decided the first one should be the as simple as possible. So Yeah, uh, the thing is we want to Make the path as smooth as possible for newcomers because when I was a newcomer last year I had some trouble Figuring out why I had to create a darker file Why there was blue ocean? Why there were so many cryptic arguments and comments I just want people to make something like darker compose up and down. They've got jane kins working And I think that's the foundation of all the rest of your Project this summer. So please do something as simple as possible And even if there is no job configured for the time being that would even be fine with me, you know, because for jobs you would have to do something Kind of complicated because you have to you know, copy files from the repo From the directory, sorry put it into a github repo and so on that's not, you know It doesn't work out of the box darker with jobs for janking. So even if there is no job fine with me just a controller with uh agent Fine with you Yes, it's fine. Thank you. Thanks a lot. Thanks cool um So I'll write it down if ever as you touch wants to start instance, which is Was controlled with one agent without blue option I think there was something else I wanted to add but I forgot Okay, uh, we'll see um I know i'm getting really pushy on This third example. It's not my gsoc project. It's yours but I let you go for the rest of the project but for the very first step I really want to make it as simple as possible. So Um, don't expect me to be as pushy as I am now for the rest of the project because it's your project but for this one, I know I can be a pain in the neck but It will go away with the rest of the project. I agree with you for being the first one as simple as possible Okay And I know that could prove difficult But whenever you don't agree with me don't hesitate to let me know As I just told you it's not my project. It's yours. Okay The rest you can Uh, do you have anything to add? No, I don't have Cool, uh, any last question or comments? No, not right now Okay, if you have anything, of course, we have the Github channel. So don't hesitate. Yes, uh, I should be Notified whenever something happens on the channel. I think I configured it correctly on my side Uh, Jean-Marc before we wrap it up. Would you have anything to add? No, very good job. You're you moving ahead as I said So cool Thanks a lot for coming. It's Monday morning pretty early for him. So That's uh, very kind of yours to have come to this meeting anyhow um, so it looks like We reached the end So we should see each other one week from now or even sooner than that if we are able to attend GSOC office hours meeting on Thursday And by then whoever has a question or comment or whatever, don't hesitate to use the Github channel This video should be posted on the community blog posts Within 24 hours If you ever forgot what we said, it should be there. Okay Thanks a lot everyone have a wonderful week if possible and see you later Bye. Bye. Okay. Have a nice week. Good work. Thank you