Jenkins Google Summer of Code Office Hours, 14 May 2023

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: 2023 05 14 Building jenkins io with alternate tools

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

You're learning the magic.

B

Yeah so hi everyone today, it's my our first meeting uh for the G-Shock uh building jenkins.io with alternative tools project and we welcome our contributor hi.

C

B

Would you like to introduce yourself.

C

uh Yeah wait a minute.

B

C

Yeah hi everyone.

D

Hello So Randy tell us something about yourself. Introduction is not enough. Just to.

C

Say hi yeah yeah I should introduce myself hello, everyone. My name is vandit Singh I'm based off Delhi, India uh I'm, really interested in many Technologies and there's a lot to learn. But there's a little bit of time for everyone when you're in college, so uh I've been contributing to Jenkins since I guess, July I start I tried as tried contributing since July, but I got my first pyarmas around August I think so yeah hi. That's for me!.

B

All right so, um let's start our agenda. So let me share my screen. Let's see so I should choose. um Let me choose this one: okay, okay, I see my screen.

A

B

Okay, cool, so we're going to talk about some action items first, because we have been assigned a list of items to complete before the end of the bounding period for the project, the first contributive bio. Any questions about this one dude.

C

I was updating some documentation, I guess it was at that place.

B

Okay cool, so uh I will give it.

C

B

Yeah, but that doesn't include a photo as well. Okay, it's like um I I, think like some country.

A

B

Okay, so no issues about that way. It's okay with you yeah yeah! So next we have uh to to write a project page with details. So this is um I. Think there's a page I! Think uh if you want an example, I think you know where to go. But so, if you want an example, you can go and check out the gitlab pumpkin because they haven't already done so.

B

But for that for.

E

B

One a week, yeah I, think we've discussed some items about that before as well, because, like um hang on, let me show you my entire screen, so that's tall, it's kind of thing, yes, but anyways.

B

It's always like I think for this page here because, like uh we had some discussion about it before about that one here, because for for you can see on the right hand, side here right so on this page with abstract rationale, implementation office hours so for and also we have at the bottom here lines with guitar meetings or you'll use our project idea Chinese visa page. But uh for some reason, there's there's like um the links here.

B

If you play around with it I'm, not sure if, if it has been fixed, probably not, but the thing is uh for me, things I think it just goes back to the same page, but we don't want that for this. So we want that to be linked up to say. The document we have like here.

B

So that's one thing: uh the original g-star project idea, I, think I think we should link up to yeah the original project idea page, which we used for like form the the application Phase previously. So that's what you've seen before like for your projects, probably I'll, let me go back to this project so for this project. This is probably this one.

B

So we can see the details here.

D

B

Just we should have a link to this page, so that's uh that's what we should have for our project. So, let's see what else we have to pay attention to so I think. Let me go back to song.

B

There's like a right now, like you have remember when you, after you have done your um like file, link it up here as well, because like right now it goes to your uh GitHub page, but we wanted to be kind of like this. Oh not yet! Oh hang on yeah because, like I think we forgot to tell harsh too.

A

um This can be changed uh afterwards, I.

B

Meant this one because, like it's.

A

B

Like up to change and server GitHub page, but either one is fine so, depending on what you want so which one do you prefer so foreign.

A

Yeah um an author page on Jenkins IO is is needed as soon as blog posts are.

B

A

B

A

uh So this did the general page and there we can either point to the GitHub profile, but normally there it should point to the Jenkins profile. Yeah.

B

We can have uh for that one. We can also have a blank to the GitHub yeah.

A

Voila and maybe show also the sources of the pages, otherwise people are going to to be lost.

B

Okay: okay, good, okay,.

A

Just a tip yeah I shouldn't fill my fountain pens while talking to spill everything on my desk.

B

Right now, where are the pages bank, but we really have like um the mentors links here. So that's taken care of the only thing we need to change is contributed like here. We have to add details to it, which includes abstract rationale, implementation office hours. We.

C

B

Should stay obviously, but.

C

Chris, what will be added in that rational section.

B

C

A rational section.

D

You so I think Vandy was asking what should be added in the rationale section and I would think there. It's the that's a that's an opportunity to describe why yeah and and the motivation or the inspiration for it and.

B

D

You look at the original project idea, that's a good source or your project proposal that you submitted that we reviewed and that those for me would be the ideal things to to just copy and paste in there. Yep.

C

B

So we should, it should be kind of like uh let's say this one. It's like for the git lab plugin modernization, the version that would be the plugin we've all nice because, like we're using some outdated software called last easy, but for for it for like the because let me think because there should be a link to you, know, trees.

B

So go back here and we and I do this. If I go back to here, I think the version I was here too because like it should be somewhere like for this project, I think it's in the backline section. So it's like uh this first paragraph I think it would tell you why we have to uh up.

C

There so the product, the product version, bound line, yeah I got it.

B

Yeah you can just like paraphrase this paragraph As somebody rationale or motivation.

B

So, let's see what else we have to get to it, so you can just I think for for um too many of these. So for.

B

Go back to yeah so for I. Think uh that's one section that we've done on here, which is legs, so we can. We can remove this or you do uh because, like uh for uh by default, we already have a line section at the bottom.

B

So it's like. If you go to yeah, you will see you'll see what I mean later once you start working on that, but um I think that so you have to you have to work on voice actions in total, abstract version, no implementations and office hours.

C

I mean got it: okay,.

B

So that's the project page details so also we have to uh this year. We we're using a new feature to add to the jenkins.I website, which is the contributive blog post to it to present the project at the beginning, as well as to present yourself so write some paragraphs to explain your background. Why why you chose this project? What do you hope to get informed?

B

um Are you planning to um to do in regard to the project for the project for 4G for Jenkins, so that might be it some.

C

So uh in the blog post do I have to add some technical details as well right.

B

C

Like what what in uh in the Blogspot do I have to add some technical details like uh What, will, what will I will be doing uh in like next two weeks.

B

C

B

Good yeah, yeah yeah. It depends on what you want, but the basic idea is that you have to like Essentials so basics repeat your.

A

B

So we need to say something about project description or motivation. Is one thing so um some a short um a short file to introduce yourself.

B

And also maybe, um like you said, fans for new future, maybe maybe first two weeks, maybe uh the first few weeks.

B

uh First page.

B

D

Would it be, would it be useful to include by the time that that vandeed creates this blog post I? Think the author page will already be there and the project page with details so link to the project page that that van did may allow you to put more technical details in the project page and just link to it. But it's up to you, it's your blog post, but but the the project page details will already have some technical details in it and they may be enough already to just link to it up to you.

C

Maybe we can just add some some, maybe two or three lines about the preparation I'll be doing in technical details will have like in more depth what will I'll be doing for the first ways if that sounds right, yeah.

D

Yep I like that. That sounds very good.

A

You're you're talking to the to the community and they don't know you and.

E

A

You can also share what your feelings are starting this this adventure, but they would like to know who you are what you intend to do: what what is this project about, so just share uh that.

C

Yeah, that will it would be nice if I, add uh I, will add non-technic I'll write the blog post in like in a non-technical sense, so so that that Community, who does not know the project uh well like understand what I'll be doing. Yeah I am feeling nervous, so I'll write that.

A

But yeah, but it's it's, it's a good call for them to bear with you to help you and uh now another tip about blog post, but Mark will probably guide you also uh with that is don't make it too long. The Temptation is uh to put many details, so write your first draft and then try to condense. It.

C

Yeah I I'll get I'll yeah I'll, get it reviewed by Mark and Chris great.

B

Okay, any other things like uh maybe, and you may want to end.

E

uh Yeah so like this block, what's the starting blockers.

E

Block of like weekly or by weekly, uh no.

B

No, it's just just for for the buying period, yeah and maybe another one for for wrapping up.

A

Yeah, it's to start.

B

A

B

Of yeah, we can have a weekly one, but it depends on what um what event date wants and also like it depends on like yeah yeah. We could do that too yeah because, like for some.

E

B

They do require that yeah.

E

Yeah I mean I think so, but yesterday I don't think you need anything.

E

D

So I'm I'm a little hesitant to sign up for more frequent writing in the blog I'd, rather Focus Bandit's efforts on creating the software, but right but I no objections if vandeed is passionate about writing great but I. Think for me the time is, is more precious to spend on on doing the changes and there are a lot of changes needed in this particular project proposal. So yeah.

E

D

As a mentor, I would has I would not ex be willing to say. Oh, you must do that. It's up to you, vandit, if you choose to, but as a mentor no way would I apply the requirement that you must. What.

C

I have seen in other organizations is that g soccer is normally uh write. Three blog posts, one during Community bonding uh second after the first evaluation and third for wrapping of everything, so I think I'll go with that format that it will. It won't put much pressure on me to write weekly uh what I'll be doing like. We are already uh documenting things so uh putting the link to the document would be nice to if someone wants to dig deeper into the project details.

D

That sounds very good to me. Thank you.

B

You mean you won't have anything about the ad.

C

Nothing new from my side I, like the details currently.

B

Okay cool, so uh next thing we want to talk about is a project plan. This is kind of tricky because, like for the Jack install our website, we already have a I think we already have.

B

Because I really have a Whipple, so I should why.

B

B

This one yeah this one, so the thing is I- was thinking about like maybe or like doing something with the project here, because we already have some items here, but I'm not sure it's appropriate, even though I have to I have to invite to do that. I may need to ask first for IL project here. Maybe here so I could do that. But um the thing is I think if, if I'm going to do that, I would be the only person who is able to change the update details, but not Blended.

B

Or we could, alternatively, we could set up like uh say, private repo and uh no notified Ripple, but um a Ripple uh in our own um yeah.

B

I can't, let's say let's say so for my password twist I could probably like uh start like I, say a new one. Sorry.

B

Gonna I can do say, uh I can't say Genghis IO.

B

Two or maybe Jenny style, but I'm not gonna. Do it right now because, like um I'm just saying like I'm, just proposing an idea, I can say like.

B

So I'll make it public do like. If, if you want to do it, this way do make it public and uh I think it would be a good idea for vendett to do it. So you can, you can like, in your own, like um I, can't open the new repository with names with this one, let's say and make it public uh so, and the next thing to do is to like start building from your new Repository.

B

That would be easier for us to integrate later right.

C

Yeah then later we can like uh we can like make a branch on the main jenkins.io.

B

Master bank, because, like they're, used to even faster.

C

Yeah this would be. This would be the way I will work for, like till the midterm evaluation, and after that, if things are rolling good, we can like create a branch on the main Master Branch uh yeah yeah.

B

C

The main master, okay, that would be all right, I guess, because um I yeah.

B

Yeah, remember to invite all of us to like I, mean the Mentos team to join your Apple and to have like access right to it, so we could monitor it and make changes to it. If we see anything like um we, we like to travel changing, maybe.

E

B

Not the augments, but at least all the mentors. So it's like um MOG, uh yeming or Jeff and me.

C

Yeah yeah, we can do that.

B

Yeah so uh project plan, so then we can uh in in that case we can use a away key. So uh let me see show me back up first, okay, hope, okay, so we can use this features.

B

So we can use a that's like it's magic, Pages, usually okay, so this is um I. Think boundary is great. Other things. Oh God, there's no wonder! Okay, so we could. We could use Wickes for for setting up your project pattern.

B

Of course, project pen: uh do you have any like do? Do you have any concern about this.

C

uh I've never used them, but I think I I. We uh I'll work on that and I'll inform you how I feel it currently I, don't know. I know: I've never worked with the keys.

B

Yeah because I can show you like what I mean because, like you have to be um yeah.

C

Yeah an example would be nice.

B

Yeah I guess like we have, we do have like the git live plugin for it's like right. Now, it's open to the public, so we're using Wiki here. So the thing is, you can add things to it. The home page is like nothing is here, yet it's just welcome to get a working, but someone knows as well. You don't like some documentation in it. So it's using mark down.

C

Well contain the uh information about enter and gets me right.

B

uh Yep, that's that depends on what you do is like. This is just an example to show you what you can do with it, but the thing is for for like for for this one. So I would like you to like in case you're starting it up for settings, go to Features with strike adjectives and teams. If they can do so. That would be great.

B

So we've checked this box after we've invited us to a team yeah yeah, so we will be more private, but at first we don't have to do it, but in in case, like a few more Executives. That way, you should do that. That way too.

C

Yeah you can we can. We can start working like that. If I I just wanted to clear one thing, the wiki will be used to host the document, the documentation, the documenting I'll, be doing uh about using enter and gets.

B

C

B

uh The Reiki is for the project pattern for now or.

C

The only oh God got it.

B

Oh yeah at first: if, if we finally useful we can, we can use it for other things as well, for the documentation too, but um I think uh we should keep everything to the project pattern.

C

Yeah yeah that that sounds like them.

B

Okay, okay cool so.

A

So Mark raises.

B

Oh sorry, I didn't say: Mark here go ahead.

D

I I was just trying to trying to understand the the a piece you had described earlier so initially, your idea is that vandit will create a separate private repository for sort of Rapid experimentation uh that.

B

D

On jenkins.io right is that.

B

It's it's true uh so later on. We will push a branch from this repo to jenkins.com. That's that's the idea, but first we're going to have our own web of us. So we have. We can like set things up more easily and test things out. First right.

D

Okay, so so this is a. This is a safe space for Vandy to do rapid, rapid experimentation, rapid evaluation, and then then there comes there's comes sometime when the project team agrees. It's now ready enough to get close to jenkins.io by started. Shifting to being on the actual jenkins.io repository is that is that what you're describing.

B

um Yeah, okay,.

D

Thank you, I just needed to be sure, I understood it. So it's it's somewhat similar to what what uh Basel Crow did when he created his prototype of antora. He created a disposable prototype knowing that it was intentionally fully disposable and and when we get to to real production, it will go on to the official location. That sounds good to me.

B

B

B

We set up a new private repo.

B

For oops sorry.

B

To wrap it fermentation.

B

On finally pushing the bench, maybe I think the bench can be quite anything but master. So we can call it manually um because I really don't want to voice push into the main or Master bench, because normally that's protected.

D

And no, no, you use the word private repo, but I thought that you were okay if it was a public repo. There's no reason for vandi to new. Oh.

B

I've got it: I see: okay, yeah you're right, it's a typo, okay,.

B

D

So vandit I assume you're comfortable with that this. This methodology works for you, I saw you shaking your head. I I, like that. That's great okay,.

B

C

Because I I knew and I have written that this is my proposal about the branching part, but I was kind of nervous that it couldn't, because I have tried uh doing that or on a personal project before handwriting it there. So it was kind of uh difficult you can say to uh start a new Branch completely from a project start a new Branch with content differentiate, different from all the other branches, completely different from all the other branches, so it would be difficult to handle.

C

So this repository thing will be easy to maintain and easy to use. It will be like a playground for me, so I can work faster.

D

Great yeah that that thank you that you've you've confirmed you understood the concept I needed to ask some questions to be sure, I understood it. Thank you.

B

Okay, good, so next is to.

C

B

D

What was that? Bandit.

B

What do you say, oh I lost it.

A

I think there is a connection problem.

B

Yeah, it sounds like a Pros. You.

A

B

No indeed, and then oh I, think I think it's like it's got some connection issues.

B

um Can you guys hear me.

D

Yes, I can hear you just great yes, yes,.

C

B

Okay, good, so next stage would be to like get the community involved. The most important thing is like: how are we gonna? Stop the the whole website with the new tools for touring wise we uh for like for most parts we have discussed, but for the West. So would you like to say something about it indeed,.

B

Oh awesome: it.

A

Has a connection problem.

B

Yeah I think it's only aside if I can find them.

C

C

Hi guys I'm back uh I I, my router, he started I guess.

D

Congratulations and welcome to the internet.

C

D

On think about what we're doing here right, we have two people in China, two people in India, a person in Belgium and a person in the United States talking together in real time. Okay, occasionally there will be a bump.

C

What did I miss uh I, I, I I, didn't hear anything about that initial email part. If that has been discussed, is it discussed.

B

uh We're installing it, but you you just you, you disappeared. So the thing is like: oh, we have to talk about like which part to do which within toy and Gatsby so uh for the user, documentation and tour for the developer, documentation and so on and I think for like one two three and that's the West yeah.

B

So any suggestions.

B

So my my preference will be using Torah for everything except the blog. That's my questions.

D

So is, is that isn't that something we want vandit to explore, because we can't lose security information? We can't lose the the non-versioned components right, the the documentation will be a versioned component and the non-version components we can't regress. So vandit's challenge will be okay. How do we? How do we retain the change log and the upgrade guide and the the security pages and the Google summer of code pages.

C

Yeah uh I have I have I have seen that uh antora out of the box does not provide anything. Regarding.Yml files uh and the change logs and road maps are generated from adult yml files, so uh I would I, but Gatsby provides plugins for these things, so it I think it would be correct uh or like I. It would be a great starting point if we start uh if we use everything from Endora and the uh components like the change logs and the road map.

C

That are the only thing that and Torah does not like generates. We can generate them with using Gatsby and the block part.

B

Okay: okay, thanks for watching me now, so we have in here how the generator transox.

C

Yeah they generate dot, IML files use Gatsby, generates dot ml files. You using plugins that reads: Dr ml files and uh create an HTML site uh paste, HTML page from it, my preference would be everything would be from Endora expect the blog and the dot vml files.

B

Okay, so accept the change locks acceptable everything else, except the box too, like everyone else should be in the Torah.

D

Okay, I I love plans and I'm always surprised at how plans get reshaped as we learn more okay.

A

Old military saying.

B

um Bandit, would it be okay for you for you to write like a brief motivation for like what we've just discussed so I can relay that to the community in the email. I'll send the email, but I want you to contribute to the Box.

C

C

uh I, so it will be like a blog post for the community why we will be using uh shift into Endora and what parts will be generated from Gatsby yep yeah. Is that what.

B

C

Saying yep yeah: that's right! I can write that.

B

Okay, you can like you, can you can send it to me before next Friday, but will that be okay.

C

Yeah wait. Let me just write it somewhere. So I don't forget.

B

C

Okay, I'll send it to you, but by Friday.

B

Okay, cool or send it out after I've seen what you've written and I'll add some details to it to introduce you to the community too.

B

So uh what else do we need to do so on the agenda? We have so uh introduction.

B

Action items: okay,.

B

Determined sorry, it's like three term and.

B

Determined, okay, so any other questions you have about like what you need to do for next week,.

C

No uh I'll just sum up I'll have to create a blog post uh project, page description, all the things and the project plan would be on Wiki I'll, explore that how to use the keys uh and a blog post for the motivation I wish. Why we'll use Endora for the most part, most parts of the site and roadmaps change, logs and blogs, using Gatsby.

B

The most important thing is like to begin with the first language, so so you should have it before you can link up to it. It's a bio yeah.

C

Yeah I'll update it after this meeting.

B

Yep then blog post is no urgent, so blog post you can do anytime before the volume period ends.

C

Okay, the contribute, but the contributor blog post should be before the the blog post about the motivation where I will be using intera for the most pads right.

B

um For that, it's just to expect to the community, so you can. You should have it very sorry, uh but because I don't want to put time pressure on you, I don't want to rush you to complain, but you can complete next week if you want to so we can share it with the community. Earlier.

C

Yeah then uh I I'll I'll complete the contributor blog post by like by the by Friday and the motivation. Motivation blog can be like on Monday and or Tuesday like I. I'll can write that on the weekend.

B

Yeah and project planking can be after, but it has to be done before the only period is over. So.

C

um Project plan can be done last.

B

So the thing is.

B

Set up private accounts.

B

Okay, yes, I should have started to.

B

B

B

I can see I'll do it later. Okay,.

B

Okay, any other questions.

C

No uh I don't have any questions.

B

For you to do this week, next yeah, okay, so.

D

B

Gonna wait: okay, go ahead! Oh.

D

Vandy in terms of exams and other things that may be of importance in your personal life that we need to be aware of. If you can just be sure that that we know when those are so that we don't make heavy demands on you, that no one makes heavy demands on you at the time when you're doing school, work.

C

uh I, don't I uh my exams, maybe will start from 26 or 27, and the community bonding periods ends on 28th, so I think it won't be much of much hindrance for me, I can't I'll be able to do most of the work before that I have I have I have planned. My studies so I think I'll do three.

C

A

You so you don't need to prepare your exams.

C

I was considering that considering that uh I I'll do most of the work before my exams, okay, good.

B

So when will it be a wife exams.

C

My exams will be one week more maximum one week uh and during that I'll I'll join the meetings and I won't I won't be able to do like code work or setting up things so yeah.

B

B

So any any other thing I should we should be aware of.

C

Not that can act and not that I can now recall or I have anything planned.

B

Okay, so uh notification part right like excuse me: uh no family, vacation friend, no.

C

No, no family education.

B

Okay, cool yeah good, so it's time next time we're gonna meet us on Friday.

B

A

Next Friday.

B

Okay, cool yeah.

C

B

Friday 7 P.M.

C

B

Yeah, okay, so um anyone any any other mentors of anything they want to add. Like we're driven, you mean.

D

No thanks just sincere thanks, Vandy looking forward to this. We are going to have fun we're going to watch and then observe you're going to do a great job thanks very much for your already existing contributions and looking forward to the contributions you'll make as part of Google summer of code.

C

I mean that was nice to hear. I was I'm, so nervous, are you yes, I am but we'll fake it until we make it.

E

C

A

C

Have any questions feel free to ask her ask the questions in the channel.

B

C

A

Think I also gimming went through the same thing last year, so you can share experiences.

B

C

B

Look again next week, so thanks everyone for coming and I'll stop. Recording. Now.