 So, hello, Biavan Toedo, Eshutash, we are on the 19th of May, 2024, this is our kickstart meeting, our first meeting for the GSOC project about how to start with Jenkins, thanks to Docker-based examples. So we will just try to get, to know each other a little better, just the first meeting and we'll see how we can plan for the next ones and the work we can do all together by the next meeting. So Eshutash, how are you feeling today and how are you feeling about this project? I'm feeling quite good and I felt a little bit behind than other participants in yesterday's meeting. Yeah, of course, but we started late, that's okay, you had your exams, Biavan To was not available, Said was on vacation, so that's perfectly normal. You don't have to stress about that, we still have plenty of time, yeah, that will be okay. So that's, I think that's it, but I do understand your feeling now, Biavan To, would you have anything to add at the beginning? Okay, thank you. So I'm sharing my screen, there is not much for this time being, it's just meeting notes. So whenever we have to take action or if there are open action items, we should put it into that document so that next meeting we know what we should have done, what we will have done and what is left to do. Both of you, do you have access to this document? I shared it via Google Docs, but I don't know if you received an email or something about that document. I got the email. Okay, so Biavan To, I don't know if you have it or not, I'll put it in the chat just in case. And if you don't have access to it, don't hesitate to ask me for the link, okay. So Ashutosh, I think you have started your PR about your bio, am I right? Yes, I have merged it, they have merged my bios on. It's already merged? Yes. Oh, cool, even didn't take the time to review it. So my bad, would you be kind of to share the link via the chat and to share your screen if you don't mind so we can see how it looks like. Yeah, no problem. I've shared a link once already. Yes, thank you. By the way, do you have an account on Jenkins.io? Yes, I do. Cool, okay, cool. So let's have a look at how it looks on Jenkins.io live. Okay, so as you haven't written anything yet, it has to be found another way. So, so I can see that. Really? Yeah, hello Said. Hey, yeah, this is the link. Cool, so this did work. Cool, thank you. So don't hesitate to write notes in the document if you still have the link. So that would make that all together. Okay, and the PR there. Nice. So if I'm not mistaken, the next work you have to do is to write to or to modify the document about the project, which is. Yes, I have already created the content I have to write in that. I just needed the office hours link for our weekly meeting. Oh, the weekly meeting for office hours. Not the G-Shock one. Go ahead. The G-Shock one. Okay, let me check. While I'm searching for that, you could maybe share your screen and show us what you have already written, if you don't mind. So let me check next week. G-Shock office hours. There we go. I'm not getting the option for screen sharing. Really? Okay, let me check. That may be my fault. Could you please retry? Okay, great. So in the chat, I put the link to the Zoom meeting for the G-Shock office hours. I'm not talking about the weekly office hours of Tuesday. I meant to say the one we will have for this project-specific meeting. Oh, okay. Bervinto said, did you, I think Bervinto, I saw your answer to the doodle. I should have seen your answer for the doodle to say, did you see the doodle about the weekly meeting that we would have? No, I don't think so. Let me check for the office hours or something else. No, not office hours. Our weekly meeting for this project, in fact. So this is also the very first one. We don't have to have the very same time slot each week. So that's why I proposed a weekly meeting. Yes, there we go. I'll put the link in the chat. Weekly meeting, weekly meeting at the same time? No, it's the, there are several time slots proposed and you should choose one that suits your agenda. No, I didn't get anything. Okay, so please click in the chat on the last link. So you can see the doodle and see how it looks like for you. Okay, I can see. So for you, Bervinto, it was on Monday or Wednesday. Morning for me, whatever for you, I guess. I'll be free anytime. Yeah, so that's it. Thanks for entering the doodle. So Monday and Wednesday. Yes, these are the two slots where Bervinto is available. Yeah, so Monday, okay, nine is good, Wednesday, yeah, Monday is good. Okay, okay, I'll see. Cool, thank you. So it looks like we'll see each other once again on Monday. I don't help, I should tell you that you will have any progress to share on Monday because it will be the weekend, but we have to start something. Maybe that will be a very fast, quick meeting where we will just exchange our feelings or whatever. So don't stress yourself too much this weekend to have something to show us on Monday. That's not mandatory. Okay, nice. Ashutosh, could you please create like you did the other day for this meeting, invitation on Google for everyone, yes, for Monday. And like you did the other time, you may be an administrator or something that I could change. Yeah, I'll make everybody. Yeah, thank you. Because that allowed me to change the Zoom meeting for today. So I can then link it to the Jenkins Zoom account. So we have on Cloud Recording and so on. So I'll do the same if you don't mind. Though we have a Zoom meeting linked to the Jenkins account. Fine with you? I'll set it up for Monday. Cool. And I'll modify the link later on. Thank you. All set. So now you have the link or you should have the link or the time slot. So could you please share with us once again your screen so we can see the document about the project? Okay, you pasted it in the chat. Yes, I also pasted it in the chat. Okay, I didn't see that. It's in raw format right now. Okay, okay. Okay, so don't hesitate to create the PR when you have time. You don't have to do it by Monday, okay? But whenever you can do it, we'll start from that later on. Now let me review the task we're supposed to have. So we're still on the bonding period. So you're not supposed to code right away. You could or you can if you want to. But we have some things to do before even coding. I know how frustrating it is to just do administrative task and not coding. We have to do it nonetheless. So regarding the communication, you created, no, you created, yes, a Slack workspace but we got rid of this one. Then we have something on the CDF Slack workspace. Yes, but it's not super convenient to me. I don't know about the others. I don't hesitate to say what you're thinking about it because we have to switch between different workspaces and sometimes I even don't see that I have a message in the CDF workspace. I have to go by myself to see if there is something which is not that convenient. So we can of course keep it. But I think that if you want quick feedback, we'd better go with, how is it called? Gitter, you know, the Gitter workspace. I have created Run and Alexer de Brandes has made it part of the Jenkins workspace. So you should be able to join it. So are you part of that? So Ashutosh, you're part of that, but for you. There is a problem with my Gitter account right now while merging Gitter and Matrix time. When they merge together now, my account, I can only open my account on my computer right now. It's not linked to my email. So I'll have to create a new one. Oh, bummer. I'll create a new one today. Okay, for reference, here is a link to the, how is it called? Channel workspace, whatever. I'm not a specialist of. Okay. So this is the one where we'll discuss all together. So let me add that in the meeting notes. Okay. Now let me check on community.genk.io. I'll tell you earlier about a post where we'll put the updates. Yeah. Yeah, there it is. No, not a blog post, sorry. Community post. So when this meeting will be finished and I'll get the recording, I'll put it on this post to say, and maybe with a summary of what we discussed together today. So anybody interested in the project could know that we are progressing. Somewhere. Okay. Next, what should we do? So Ashutosh, you know Git, of course. The communication channels is clear for everyone. So we have Slack, but not the preferred one, Gitter. And of course we can discuss by email, but it's better as it's open source open and so on. If everyone can have access to it. So it's better if we are using a public channel like the Gitter one. Gitter. If you don't mind. Yeah. Cool. What else? Yeah. Do you have a working environment with Docker and so on Ashutosh? What do you mean by that? Do you have a working computer with Docker installed with an IDE? Yes, yes. Yes, I have all the setup ready. Okay. I have worked with Docker. Great. Now, the thing is the part of the project is modifying the existing documentation by supplying some examples. But I think the first step would be to have some working examples before writing any documentation about that. So how do you plan on organizing that? I have already created one for proposal. I plan to create a similar Docker Compose files for other parts of the website. There are like three parts that I will repeat. Three other parts that needs Docker Compose files. Okay, okay. But regarding the organization, I meant what about GitHub repo, for example? Would you create an organization with all of us inside it or a personal repo where we would have access in a way or another? How do you plan on doing things so that we can all participate, review and so on? I was thinking if we can create a sub repo in Jenkins or something like that. Or should I create my personal one? That I'm very busy. Yeah, I think we should maybe start with a personal repo and then we would see if we try to attach it to the Jenkins organization. But that could prove difficult because we would have to discuss on the Jenkins mailing list and so on. Because people maybe won't accept project in such an early stage in the Jenkins organization. So I guess we should have... Okay, private is not the right thing, I guess. We should make it public. Yes, yes, I meant public. Okay, that's better. Okay, so let me put a few things. I'm talking too much. I'm sorry folks, by the way. So I will just take a few notes and if you have something to say or ask, go ahead. I'm too talkative. Sorry, go ahead. I'll write down some notes in the document. I was thinking if I should create a blog or something. I attended Google Summit day before yesterday and they emphasized to document your journey while blogging about it. So should I start blogging? Blogging is always a good idea, but does it have anything to do with Jenkins for the timing? Just to know where to put the blog post. What you would like to write about? It's like a daily reminder of how much I have completed my blog every day. So everyone in the community can see that I'm completing the whole thing. So I suggest to do something else. Create a repository in your GitHub account and create multiple directories by your dates. For example, day one, day two, day three, day four, etc. And inside day one, add your documents in addition to your code and all the things and then we can review all the things together. And after completing the project, we can measure all of them together and then migrate the repository to Jenkins.io to the main organization and writing a quick review blog post to mention the main repo. Okay, that sounds like a good idea. What do you think, Bruno? Yeah, that's a good idea. If you want to write all the days, you work on the project and write your experience, everything you do inside the project, you can create a multiple project by the days. Okay, we still have some time. Ashlosh, could you please share us your initial proposal so we can see how to plan for the coming weeks? We're not supposed to begin coding, as I said before. But if you need to make some refinements, change some things at the moment. I've posted the link on the chart. But you can share your screen also, if you don't mind. So we can all see the same thing at the same time, yeah, okay. I see what you're doing. Okay, so I see a little bit later in the document that you want to start with a simple Docker Compose file. I think we could go this way. So with just no blue ocean as you proposed in your first iteration, just... I sent something in the chat, two links about the project of working on Jenkins that consists of a complete Jenkins stack. Ashlosh can work on that or other can work on that to make it more complicated and add some features, add some new things, like the JCask and something else, because we already have all the things in that repo. And Jenkins user used this repository as a main repository to deploy Jenkins stack. In addition to Jenkins, it deploys all the components they may need in implementing the CI CD pipelines. And you can use it and change it or separate it into the multiple things that if the user need to just deploy the Jenkins, you can separate the Compose file to just deploy the Jenkins. If they want to deploy something else in addition to Jenkins, for example, Docker in Docker model to be able to build image inside the Jenkins without touching anything on the main Docker engine. You can use these repositories as a reference to find a big picture about the stack that's already some companies working on that. Okay, thank you for the link, Said. The only downside I see with that is that it's already fairly complicated. And the very first step is to have something as simple as possible. Yeah, but afterward, with as simple as possible, we work, of course, this is a very good resource to start with. Yes, thank you for your work and for proposing it. Yeah, that's for sure. But the very first step, if you don't mind, as we said during the proposal session, is to start as small as possible, as simple as possible because the existing documentation is already too complicated for the basic user who has never, ever done Docker or Jenkins or the combination of the two because you have to write the Docker file and so on. So first example, as simple as possible, then we have lots of super cool ideas in, Said's two repos, that's for sure. Yeah, maybe in a few weeks from now. Cool. Yeah, to start, you can start in the proposal or we can see a small Docker compose to bring up the Jenkins and do something. It could be the starting and it can be more simple because inside the Docker Composer can see you connect the Jenkins into Docker to do something. You can avoid using that for the main step. In the main step, for example, some users need to deploy just the Jenkins and get the experience about how Jenkins deployed into the containers. And after that, for the second step, you can see that, okay, if you want to have a Docker inside the Jenkins environment, you can use this Docker Compose. If you want to, if you need something else, use this Docker Compose and other Docker Compose that make a complicated environment and complex environment to bring up everything they want. Yep, we can go as far as time will allow. We'll see that because we have to supply some working Docker Compose files at the first step, but then we have to write the documentation and then we have to imagine something that would allow Jenkins.io to regenerate and to test the Docker Compose files every day, every week, every once in a while. So we know it's still working. In a night release, we can create a pipeline to test it in a night release. Yep, that's for sure. But this part, maybe it will be difficult because we have to discuss with the people from the infra team. So we'll see, but what I'd like, tell me, I'm not the one who decides I should touch, by the way, it's your project. Tell me if I'm too authoritative. But for me, the idea would be to have first the simplest Docker Compose file that does work, then a documentation that goes with it that explains how to use it and why it's working that way. And then the next step would be to integrate that with Jenkins.io workflows. So we have to start the discussion early with the infra teams. So we can have a setup that works for infra team and for us. And then we could work on more complex examples, maybe starting from site to repose, for example. What do you think of that, Ashutosh? Yes, I also think simpler examples for first days, better. Okay, Davion, though? We start from the simple one. And we start earlier for communicate with infra team. Cool. I hope that could work, because that's the idea I had. Let's hope it will work. I have some good contacts with people from the infra team. So it could work. I think the communication part should be kind of easy. And then the implementation will see if that's easy or not. So I'll write it down in the meeting notes. So next step would be to write documentation. Get it integrated in the Jenkins.io website. And for the second step, I guess we would have to discuss with documentation single interest group, DOC-SIG, which happens on Thursday night for me. So you don't have to go. I will go, but you're welcome to attend to DOC-SIG, but I guess we would have to discuss with the documentation SIG about where we could add our documentation. Because we don't want to break everything existing regarding DOC-SIG, but we have to insert it in a smart way. So write the meeting notes. Go ahead. I think we should discuss with DOC-SIG about where and how to add the documentation. Cool. The last step would be to discuss with the infrared team about the workflow slash process to regularly test our DOC-Compose files. Nice. So Ashutosh, what do you think about that? What documentation part? No, the small steps of the first steps, so the first three steps, are you okay with that? Starting with a very simple example, as small as possible, and then trying to write some documentation. And on my side, I will start off to discuss with people from the DOC-SIG and from the infrared team. Yes, same thing, good idea. I could put the link to end the time slot for the documentation SIG. There is one which is linked to Asia. There is the Asia documentation SIG, which is super early in the morning for me, like 4 a.m. But that's maybe something that you could attend. If you want to, you don't have to, but if you want to, Ashutosh. And there is another one on Thursday night for me, about 7 p.m. for me. It's the US and EMEA DOC office hours, DOC-SIG platform, sorry. So I'll attend this one. Don't feel like you have to, but you could, if ever you want to address the checks of the documentation for the DOC or a quick daughter, you got it for our GSOC project. And then for the infra discussion, I started by myself, but there is also a public meeting for the infra team, which happens to be on the third day, 4 p.m. my time. So about the same time we started the meeting today. So pretty late for you, Ashutosh. It's fine, I'm free for some occasions, so I can manage. Okay, but I'll put the links to those meetings in the document. If any of you want to attend, to get his voice heard, feel free to join. I'm still talking too much. Does anyone has anything to add, a comment, a question, remark? Okay, may have been crystal clear or intimidating? I don't know. Okay, so if you don't have any questions, I propose that we wrap it up. I'll clean up the notes and I'll post a video of this meeting on the Community Jenkins IO post. And we should see each other next Monday without many news to share, because we'll be on the weekend. I don't expect anything to progress. Fine for you? Fine. Monday, yes. Cool. So no regret, no question? I was wondering about the thing that Chris mentioned about communicating with everyone on all teams with emails. Oh, I didn't see, it was an email? No, he proposed that we, the contributors are not communicating enough with the community and they should engage more with communities. So he proposed something with email. I don't remember correctly. I haven't read that. The Berbjorn Tosai, did you see something like that? Or if you have a mail, I thought you could share your screen so we can see it. I'll search in my mail quickly. No, it was not on the mail. He mentioned it during the meeting. Chris proposed an idea. So yesterday? Yes, Chris proposed to communicate with everyone on the Jenkins Community with email, I think. So on the Jenkins mailing list? Yes, yes, that's, yeah, Jenkins mailing list. OK, but it's not that active, in fact, whereas the most activity is on GitHub. And then on comiketjenkins.io with Jenkins mailing links, I don't get that many emails per day, so it's not that active. But why not? I don't say it's a bad idea, not at all. It's just that I'm surprised. So communicate via this Jenkins mailing list. Why not? But about what? I don't remember correctly, but Chris mentioned something about this, so I was just wondering. My bad, I was there. I was at the meeting, but I can't remember. Anything. OK, if you ever remember what he said, what he proposed, just let us know and we'll see what we can do. But apart from that, I don't know. I'll say. Yeah, I just remember something that he said. We have to make all the contribution and communication through the public channels. But I can't remember anything about the email or mailing list. That's maybe because he told her so yesterday and GSOC office hours. Office hours. Yeah, maybe, yeah, maybe. I didn't see you there. But I was there, but I just can't remember what he said. So OK, I should ask if you ever remember or maybe ask publicly on Gitter to Chris in the Jenkins channel or Jenkins GSOC channel what he meant, maybe, you know, if he gave us an explanation. I'll check on the recording of yesterday's session. Why not? Good idea. OK. Good for me. So if you don't mind, we'll wrap it up and see each other. Go ahead. I also I also wanted to ask about that blog on Jenkins.io. Yes, I read Hush and one that's blog and should I should I create a big or small one like Hush is small and one that's like a little bigger? Well, if I remember well, the document is a living document. You know, it's a blog post, but that will evolve. So you don't have to make it big for a time being. It doesn't need to be big per se. Just put the information you have for the time being and we'll make it evolve later on. Vandit has gone farther than us for a time being. They already have done three meetings or so and he has started working on the project, really coding. It's also that's that doesn't surprise me that his blog post is bigger than yours. So no, just go ahead. Put the information you have and we'll make a review. The community will make a review, not only the members, but the rest of the community. So go ahead and we'll see if that's not enough. Jean-Marc, for example, will let us know. So that's not a problem. Go ahead, start small, but start fast and we'll see what we can do. OK, anything else? No, I don't think it's cool. So thank you, folks. I'll see you on the other side of the weekend. So just, yeah, just, please set the calendar and send the links. And I'll modify the link with a Jenkins Zoom account just when I receive the email. OK, good. Fine. So I'll modify the document and keep you posted. Good. Bye, folks. Thank you. Yes, thank you. Thank you. Bye bye.