Jenkins Google Summer of Code Office Hours, 8 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Custom Distribution Build Service kickoff 2020 05 08

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

A

A

A

A

A

Know how can you hear me, yes, hello, I'm doing.

B

You mean next time, which we can't share this link before yes,.

A

B

Unity recording this video yeah.

A

Yeah I guess we'll record it right.

A

Do let me know when you can see my saying hi, Kristin, hey.

C

A

It going going good, really good.

A

Yep so I shared my screen.

A

So um looking, can you see it yeah.

C

A

Yep, so I just wanted to go over a couple of things since this is the kickoff meeting like what is this I've written it down in their meeting, so I'll just go over some of the items and if time permits, I could just go over the design right, yeah. So, first of all, we would like to finalize the days and times of the two meetings with the mentors per week so because Oleg said it's up to the team according to them Alec.

A

How many days do they want to meet in a V, so we could definitely yeah. We could absolutely adjust that. So what are your? What are your preferences? I mean? Do you wanna? Have it twice a week once a week, please feel free to pitch in I.

C

Sometimes we see very successfully because I know that you'll be iterating over stuff really quickly, and it just gives you a chance to ask like questions twice. So you know you have you know we can work on things and then you know you feel worth it then like an easier chance just to sync up in person. Okay, if that works, your UI I feel good twice a week is good I, don't know I, don't know whose it's a CD foundation.

B

Perico, if we don't have too much things to discuss, we can shorts at the meaty time. What is it web will be a good chance to communicate community. Okay, so frequently.

C

We don't have to happen, you know the same time twice a week, so we can, we can. You can move around, finds.

C

A

Because we do put I guess one fixed time on the I'm Nick Jenkins calendar. So would it be fine that if we select one fixed time and the other one could be moved around, is that what you're suggesting.

A

C

Sorry I was thinking like it's, you know they, they don't have to be. You know like 8:00 a.m. UTC, Monday, 8:00 a.m. UTC Thursday or something will be yeah p.m. Monday et Cie, Monday or, like you know, 3:00 p.m. UTC in a day.

A

There 3:00.

C

P.M. Thursday yeah, it isn't sorry, that's good for I was talking about, but yeah I'd, rather just have twice, or rather just have it at the same time, it's easier for us to make a commitment to show off, but you have to be at the same like physical time.

A

Okay, so um is it fine? If I float do Dylan, even you know would, for there are times that you are comfortable with, and maybe we can select the maximum.

C

A

So we'll have to add that until you decide the timings we'll add it to the Jenkins event calendar the project page and this meeting yeah. Of course we have got at this meeting notes to the page, so yeah I'll do that and I would be using this color scheme. If you guys are just copied from the last times I guess it was a multi branch, github sauce, plugin yeah. They use the kind of done working. Progress not started yet I.

A

Think I have that already, but I just put it on the side of the items so that I don't have to assign everything by myself. So I can just throw you know you can whenever you log into this document is easier for you to know. What's being done and what's in progress and what's not started you so once the meetings and I'll just put them down I'm giving you ready.

C

A

Issues document just tell me if you can't edit anything yeah but from that okay, so the next key point that I need to discuss is get introduced to key stakeholders and contributors in this area. So so like mentioned, we need to. This is an important step of.

C

A

I drew up this mailing list. I think I'm, not sure, if you're a part of this discussion, when the initial project idea came out like yeah. So this was the initial discussion that happened. I put it in a meeting like then have a look. This was the one yeah we had a huge I mean. I should call quite a huge discussion on this yeah. It's a huge thread. You don't have to read all of it but yeah. These are kind of the stakeholders that were quite interested. One was Chris.

A

He expressed a lot of interest in this. The other one was a manual Ramon and the third was I think Lee yeah. You.

C

A

Yeah, so he was Lee was another one, so they were quiet. A couple of stakeholders interested in this project idea I'm, not too sure exactly. How do you want to proceed? Do you wanna send out a general statement in the mailing list introducing the stakeholders to the so that if interested they could just join, you know you want to send out and in personalized email I'm, not too sure how it goes on. So, if you guys would guide me on that, that would be amazing.

D

Yeah, it would be great to make an announcement in the change development increased. You might have seen. This project is already included into the Jenkins roadmap.

D

Project for the Jencks community, so sending announcement to the developer, terminal histories, introductions, etc is totally reasonable and you can also think people in the development least threat, which we've had during the initial discussion on this project. All.

C

Right, that's nice thinking! It's like they're already interested in threat, so they're gonna be a following update. Sense, always good to just continue to say: hey! This was actually selected. This is working on. You can join our jitter channel if you would like, because that helps a lot to the community gives, maybe if they don't really sound of meetings, but they can provide some asynchronous.

A

So yeah, apart from that.

C

It's all good I am.

A

Yeah, the next thing we discussed I'm, not too sure this point is as relevant now during the community bonding phase, but I see last year's projects as well and they discussed it during the it was it's ruled as a project or taking the initial meetings.

A

I'm, not too sure how relevant it is now but discuss with Mendez about code reviews, and he also reissue trackers, because I'm hoping that the project, since the back end would be Britain spring good, a Java, that's up for discussion still but yeah whether we should use how element is it to discuss it? Now, you want to defer it for later.

D

A

So tell me, or so since I'm the student that would be expected to derive this but I'm comfortable with using both the github issue. Tracker I've seen a lot of discussions happening on the Jenkins mailing list as to whether the github, which there's been a lot of discussion on using just yet how about using just you know, I, don't have any strong opinions on them, but if you're using github then, since both the code and issues can be kept in the same place, I think that's a good idea. What do you guys think.

C

All of you might be able to help with this a little bit more because I last last year we worked with I worked in a project and we use the JIRA and I know it's easier to consolidate everything we're using github issues but I, don't know if that's what yeah.

D

I can share my opinion, but what a mentor some.

D

Opinions first.

D

C

Rick Rick, do you have you and you worked with like the github issues or the JIRA and I don't know I.

B

B

Yes, maybe through the years but in my opinion, github issue is, is a good choice and also we can create a project in github, so I think we way maybe and try to get happy issue. That's where we can. We don't need to switch to many system or page just the folks on github.

C

Uncle I am okay with that. If, since it is easier to track I yeah.

B

Could have a issue and github project.

D

So a second, this recommendation, github, which is a quite convenient for, is a little project. Why we used children. Jenkins heavily is because we need a changes across projects comprehends misdirecting. It hop was pretty weak about that, but now even there it makes sense and for the dated project like a distribution, build service, it's much easier to use it hot wishes, and if you want to reference something in Jenkins Judah used, you still can do that.

D

Otherwise, you just have everything visited in your own repository and the only thing you will need to keep in mind that you will need to somehow manage access to your project dashboard, but assuming that sledding and other mentors will have write access to data physically, it shouldn't be a problem.

D

For example, would be try to do misconfigurations code. We had to create the project on the organization level instead of the repository level, but for this project it shouldn't be a problem.

B

Projects this year, you, if only this project, I used github issue and github project. Maybe we cannot get a full picture of the his dog.

D

So I can provide you some examples. You know a Windows service record project. We have already agreed to move forward. Github wishes in Jenkins ax, most likely they will be using github issues as well, and it's highly unlikely that they will be using Jenkins JIRA and for other projects is basically up to project contributors and the maintainer to choose so and person expect that many projects will go for this github wishes for this year.

D

A

Yeah cool, okay, so moving on the next topic communication to all governments, what do we need, like posting new plugins trainings, take advisors since Lehrer? Isn't there so would the opinion be that it will be using github project boards for it now we're not using yeah I.

B

Have seven I feel some confused about new plugins, so you think we need to create a new Pro projects or new plugins or just a web project. I mean not a plucky.

A

It's not going to follow the normal plug-in life cycle right because it's not a plug-in and wouldn't plug into the Jenkins ecosystem. Right, yeah yep, it's going to be a it's going to be a separate project, so I don't think we would I'm not sure how to go about the hosting I've included in my proposal. Since it's a bit different mentioned that there are had childhood is to launch services using the junk in the infrastructure. I'm assuming it won't, follow the this part here.

A

So I, don't care I'm, not sure we're gonna go through this hosting plugins. Well,.

D

Generally, we go through this process anyway. Obviously we didn't apply at the same checks if the repository isn't the plug-in so how we usually approach it for new projects. You create a repository skeleton in your own repository and then once you're ready. We host it on Jenkins, so preferably to do it before the end of the community Banach phase, so that we have both admissions and others areas fixed before you start coding, but it shouldn't take long for.

D

One one question to you later: do you anticipate it to be a single repository or is a very chance? You will need multiple repositories, I'm.

A

Assuming since because this really cool and a LeBron James, it's kind of odd, the banner will be separate from the front end. Initially, I was thinking that would be two different repositories because then it's easier to pack, the JavaScript HTML ends yes or whatever it you're going to use in wonderful and then the back-end service, in the other episode that they are quite modular and separate. But if that's what that's? What the way I was thinking about it.

A

But if there are any other suggestions as to having benefits of having a single repository I'm up to change as well.

D

Don't think too many benefits on dirt, because, whatever you do, you already have custom work package, a custom work megachurch is going to be a part of the backend and most likely you will have to submit some fixes or patches to custom or package. A new project I wouldn't expect everything to be in a single repository, and it may also influence your decision about where you put the project.

C

Right I was thinking the same thing and you can always just say.

A

C

Might be easier for just trying to locate everything.

A

Okay, so you're saying that we have multiple repositories: Christine, no, no I'm, thinking.

C

Of one repository, everything is kind of packed in there, even with the multiple folding like. If you want to be able to separate you I killed, but I, don't think there needs to be a whole nother repository at.

D

Least in the beginning, because we can split it later, the restrict need, but.

D

Engineer this stuff right now: okay,.

B

Yeah plus around me it we don't have too much benefited from separate to work repository, just a keep into kept them in very paltry. We just need to create twofold folders to separate them.

B

Do two things we need to create a workflow to about how to host a regular project.

D

What I mean knowledge transfer, I.

B

Mean if someone want to host their project into you can say yoga, how do they needed to.

D

Well, it's pretty much like forcing plugins.

C

D

There are some minor differences, but you follow the same process.

D

Yeah, maybe we will need to update our documentation soon. We have just created a hosting team one week ago, and one of responsibilities of first empty more would be to improve documentation equivalent to removing this hosting plugins wiki page to JSA or and breaking it our developer, documentation pages, but in principle it's the same and more awaits were straight forward for JSOC projects because on JSOC projects already considered percepted. So it's not something we will be discussing feasibility.

C

D

A

I think we discussed the hosting new plugin since it's a project we'll be following the similar workflow we'll get that up before the coding phase starts. Apart from the idea of this numbered, so I guess we're not going to be using I guess. Last year, Oleg the entire G sub team I mean that ring so projects use the JIRA scrappin the JIRA boards. So would would it be following the same procedure this time around, so we.

D

Will create leaderboards for projects which need that and other projects are welcome to follow their approach. For example, if you use github project or if Jenkins X team, they like have a github project as well, you can just stick to that project and reference it from your documentation.

D

We will still create the jitter port for those who need that, but we won't be forcing.

C

This was I, think, ok,.

D

So, basically, what you could do create and github board, maybe 103 phrases or want to freeze.

D

C

Easier to use, if you don't want to create the board with each of these tags, so we can see everything let's have like mm-hmm, that's I guess it'd help allow you to detach its.

D

Familiar to get help get help you can use milestone for that. Okay,.

C

Maybe it'd be easier to see everything together, yeah one.

D

Way to use milestones so that there is no cross, my depository milestones, so if you want to create advanced queries, we'll be responsible to manage milestones, have multiple repositories. Alright, okay, that may help things a little better yeah. So is so much a big deal, but is.

C

It easy to move this too. Is it easy to move things? If you know we put too much work into a milestone like just optimistically? Is it easy to move a task from ferritic from one board to the next.

D

C

I think that was me singing, because it's really no you get it's very easy to get very excited about, because you're, like oh I, can do all this these things, and maybe things take longer than you originally thought, or it's like you, just let just put too much and it's just impossible to get it done easy to translate it to the next forward. Then I think I just don't have to create birth twice. That's pretty.

D

Boonton did okay.

A

Good, so should everyone vote for the community morning like epic, for the star to be done, or could we just keep out that face from the boats, I mean not to say skip? Should we include it in the github board, or is that not needed I.

C

Don't to me I think we could, let's keep you in the dark. I, don't think we'd need it, because I'd just be more focused on the code. Is that is that make sense everybody.

A

D

If you use github project github project, you can put code tusks and non code tusks, so poor tusks can even have automation. So, for example, it have wishes. They can believe to pull the requires, put requests in there to make it remote between stages and all there are other things. But if you need, you can just add a task which is not really implying code and you cannot add a task which also doesn't get officious. If you want to avoid putting tasks or create a blog post, there.

A

Yes, you wouldn't say anything: oh then we can move on to the next topic against okay,.

C

A

So trainings I mean knowledge, structures or training sessions. I think that applies if I need anything like bring, like maybe I, think last year there was one of those training sessions that just in for debugging in Java, so it will discussed in yesterday's G. So I mean it's not yesterday's. They were meeting on Wednesday that there would be common.

A

There would be common knowledge, transfer, search means like who's like creating a plug-in or some thought so I think that really is on demand. So if at all, I need something that that team could have a training session on, then I could request it. Otherwise that topic is really is really personal. I get.

D

You know this so and specifically, your project guide for creating plugins won't really how you see objects. So, for example, if you want to have a good day for custom work packager. Firstly, there should be already recording somewhere. If you want to have a fresh recording together, we can organize that.

D

Okay, it will be one out of shame, but I'm really into.

D

Well, I think because we get contributions, focus on work packager. This project was slightly abundant by any different past six months, due to some issues non related to technical ones, but yeah right now, I'm fully able to contribute the editable patches and if somebody else wants to contribute a will doesn't appreciate you doing Kokoda. If makes the bull sense, yep.

A

Maybe we could organize this just before the community bonding, maybe ends in the design document included, link yeah just second.

D

Will create a doodle because we already started to them for another knowledge transfer, so just copy it paste. For me.

D

So, do you have it next week or is.

A

D

Fine, if we do it later.

D

So taking my scribble, maybe it's better to do it next week, okay,.

D

So, let's see so I do not commit to do it next week. I I will send a little for two weeks, I'm just creating that. So you can continue the discussion.

D

In a few minutes, okay, so.

A

Training is done, take advisors, I'm, not too sure why this topic is. They have just copied it from last year's bonding to-do list.

A

The first meeting with the hive but yeah the advices I, guess that pertains to stakeholders of experts in the domain or whatever we are dealing with hosta for the multi branch by plugin plugin, forget lab I think it was because he was doing most of the reviewing and I'm that but I still in our case, we already have Rick, oh, maybe because per packet, if at all you're making patches, we have Oleg so I guess those would be. That in question obviously would be reviewing code yeah.

A

Don't because these are the main components, I'm, not too sure about the ten part you might script. My.

A

As one of the visors on maybe the front end part I'm, not too sure if we can arrange that he made a couple of comments to the proposal, but yeah I'm, not too sure of his availability. During this period, I.

D

Can't say anything specific, but definitely once you have a first prototype, you can get feedback because we have a lot of contributors with a URL to the ground by the way I put a link doodle for customer freakish apt. You can find it in the chat.

A

Yes, I think we've discussed. The last topic is the new github repository when the junk in CIO I think Rick. You put this on right, not sure. If we should interviewing the 14 I think that's already answered. It would be nice to do it before the community bonding phase. So here I'm just taking this comment out since the questions already answered.

A

Okay, cool yeah, so that's about all of the I mean that's about all of the topics that we have to comfort in the kickoff meeting. Is there okay yeah one more thing before you move on to maybe the design of the zoom link, so I guess, since Rick already has access to the CD foundation, but we might have conflict so is assuming going to be given to one of on Windows.

D

So there are some forces issues, I need to figure out by coding phase. We will have access for Rick well for Rick and Bill. If I can shade right now, because he has access to see the zoom.

B

Zoom account and also access YouTube account with you, yeah.

D

So the discussion was about Jenkins doom account because we have a second to zoom account which is specifically created for the Jenkins project, because otherwise a can risk when you use the day of account that you run into collision this another project because for Jenkins we can use jenkees calendar and your advice put your regular meeting there.

D

But we can't expect CDF to do the same. So we hit multiple issues with CDF account being clocked, and that's why my recommendation would be to switch to another zone account today. You can share access, video.

A

B

I need to send an email or something to request the treatments to.

D

Meccano for you for you, it's not inevitable, just forward it to you, yeah, so I plan to have official process for that. But since we do not have official process we'll just yeah in a very secure way by the way.

B

To add the meeting you want to take the calendar, you can send it to me.

A

Okay yeah. So apart from that yeah next steps, I guess anything. Okay, so am I missing anything that you guys want to discuss. That's necessary for a kickoff meeting. I! Guess, of course, almost everything so anything you guys say any technical things that are missing.

B

C

So I guess the thing that I was thinking about is you're, trying to determine what framework to use and threw out like a spring boot yeah.

A

C

Don't know really like do you have like preference for anything or you can.

A

C

You would okay, that's like you were trying to burn like a something new or they focus like a java-based solution, then gang, but because there's a lot of different things. Oh yeah.

A

Yeah yeah yeah yeah, that was that was them in the project was announced. Okay, so I'm. Moving on to the next section.

A

C

A

A

Cool design document, so I decided to go with it so that we all technical details are ironed out before the coding case begins and we don't run into any unexpected glitches on. Obviously, we can change certain directions. Yeah yeah, stick.

C

Yeah I was just thinking that it would be good to talk about this, because that way, you know you don't get stuck spending a lot of time during this period of time like trying to figure out how does things up and then, if we need to also like the technical mentor section, and might we can always find yeah we having like, we all, have experience of different things, but it's also like you know we didn't get to be any help or like people like the interested in perspective.

C

Oh hey, you know this was an issue 5 more than she was before, so that helps we can help find technical matters for that dude yeah.

B

C

Let's go know where I was going with that one I was like: oh, we can make Poland extra people or who might be interested depending on what makes you do it. Yeah.

D

If you need technical advisors, we have people experienced with spring. If you want to try something new, for example, quark cause has a really good framework. It could be just.

C

D

Again, we have some people who are experienced and if you want to have a mentor who's experienced, this quad cause I may be able to help it not me personally, but I I know right. People.

A

Yep, so this was one of the discussion that we had initially when the project was announced. I think Rick mentioned Bolin because he was very familiar with it, but then electoral does that it might be a bit think it's advisable to choose a certain language that then you get a lot of community feedback comments, easier to code reviews and to deploy so spring actually yeah. We can actually have a Java based solution as well, but yeah. This was the reason we were thinking of.

A

Spring Buddha was because it's just I mean it could easily integrate with the front end and it's it's almost judged Java actually just put annotations and just the ease of deployment. And now we have a lot of easy to spin up us over and you know have a container and stuff. So that's what that's the reason I wrote. The Java Springwood bye dear I'm, open to suggestions before we yeah before we we can so yeah, just just throw in a tidy.

D

A

Yes, do you want us to stick I mean, do you, you were saying that we could rather a Java based solution or Springwood.

C

I'm, just also trying to think of what would be the best way to be able to people interested be able to involve the community after the summer right because it's another thing is jafer that the project doesn't just solved, especially since it is important to Jenkins overall and will be continued on the roadmap.

C

So I just don't think I like it most like what would be the best thing to be able to encourage usage her or like continued development and I think it might be, and I don't know it's like we Java I, don't know Oh like brick like if there's an PNM, oh, it would be able to go huge, encourage feature development for this or like to be able to yeah Selena's gonna knock. It he's gonna, be well over the summer.

C

Got this awesome project in my boy, all right, like let's other people in here like interview, a good, continue, developing it or like finding you like, hey it's out of me, feature what would be the best way to continue. They encourage people.

D

Advantage of Java stick, which is not currently listed in the list that you get access to libraries and tools. We need.

C

D

For example, customer package it can be used as a library, plug-in installation, many gems to the library and I'll show where they really need for this project, but at the same time,.

D

A

A

So so I'm able to make a decision right now, as we define the design document, we're gonna move on with it or even like yeah.

C

I, don't know if we need your buying. Did you do nothing? You did we can get some good sign document. Okay, pick something later, no.

A

C

Pick something native I: don't wanna pull this up like sitting over here to like working on the find, particularly.

C

D

Think it's something.

C

We should speaking mr. Roper. It's like alright yeah. It's like I was really fun to learn something like clicks. I, don't like. Okay,.

A

Yeah, exactly okay, so yeah I think think. Or do you have anything to say on this because it so you know initial initiated for this old. You have any strong opinions on what kind of sideways pickle move on.

B

Sink our Dougie's treaty convenience luggage.

B

I'll crave this your proposal puzzle upon this. This is tech, spec.

A

So yep maybe decide yeah as and when we finalized the technical details. We could come up with maybe double its the Sailor thing. So that's like suggest, if you use Java, then really have the liberty of using some of the most developed I've reason. Now we can stick with that yeah. So, apart from that, so I not just part of the design document. Obviously so the next steps would be do we as we decide on the next meeting slots.

A

We could finalize till you in this design document to select the work that we are going to be doing over there coming I mean coming weeks filled up into the community bonding. If at all, the design document gets over early, maybe we can subtype for for the first stage, so yeah I think that that's the next step any other next step. So anything you want me to discuss before me finish it, because we can move on to the next meeting so yep anything else.

B

Both prongs answer, maybe wait. We need to settle localization I.

B

B

May we should to support multi location from the UN.

A

Language, okay, yeah, yep, cool yeah. That's all another thing that we need to consider because the initial problem is getting the UI generated as we as well EXO. Just didn't his meetings that we've had in the the doc serious we still don't exactly know is that we're gonna get all of the field, so we could create scale it in the nap. So once we actually have that we can, you know, have the localization done so I'll. Add that point, since you mentioned DUI.

D

Okay, good yeah.

A

So yeah I just added a few components, so it'll have the user interface, obviously, on the back in the really we'd have a generation of a talker which I had include in my proposal initially, but yeah we'll have that now the generation of the Apple file, the Occupy on the Walker, the desired storage of configuration.

A

This is the main user stories. Apart from that as and when the design documents gets fixed there, we could just keep refine. It is still a project readon again yep anything else to add before we wrap it up.

A

Thanks for the time sharing the dual for the next meeting slots and you guys can choose okay, all.

C

A

Everyone for the time really appreciate Oh, gentlemen.

D