Paketo Buildpacks Working Group, 1 Sep 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Working Group: 2020-09-01

Description

* Redesigned Website
* Node.js rearchitecture
* Versioning builder.toml

A

B

C

C

hmm Hey: hey how's, it going pretty good. How are you doing today pretty good.

C

How about you not bad it's a beautiful day.

C

And it's a short week, yeah just found that out. I.

D

C

Josh just found that out too, which is nice.

A

I knew I just forgot.

C

Somehow I missed it the first time, but I'm glad I didn't totally miss it because working from home who knows, I could have put a whole day in.

A

It's freedom friday too, just show up at retro. Where is everybody.

A

We should trick somebody and tell them that they're still work.

A

What's trick forest.

A

They canceled the they canceled the day off.

A

B

Are you in spring one all week, emily.

C

Yeah um ben and I are emceeing a breakout track starting tomorrow, so.

A

I can't believe.

C

Yeah, I don't know where the whole summer went, it seemed like it went faster than usual. Do you.

A

Believe we were in austin a year ago.

A

It was crazy what a different time.

A

Where was it supposed to be this year,.

C

That's a good question, I don't know the answer to the top. My.

B

Head, oh, it was seattle. I think.

A

What was left of seattle.

C

I haven't like attended one of these virtual conferences, yet I'm not totally sure what to expect.

A

A

A

Pre-Loaded virtual backgrounds now so nothing can stop.

A

D

Stephen coming today.

A

He's not coming today.

B

uh Is ben going to be here? If not, we could probably get started.

D

B

D

This is the non-java right.

C

I think this is the everybody, but ben can't make it today because he's doing a customer meeting.

D

Cool who wants to lead it.

D

Okay, oh sorry, tim do you want to get sure.

E

All right, um so, let's pull this out.

E

All right so um outstanding, rfcs.

E

I will share my.

E

E

Okay, so uh this first one.

E

E

E

And basically, this is aimed at um just formalizing and and surfacing uh guidelines for contributors so that we can host in the community people um there we just figured. You know it would make things easier, shortened, feedback loops if people knew exactly where and how to get started with contributing not to a huge change, and I figured it would be appropriate to add that as an rfc um there's, we I've included an issue template and a put request template um that are certainly open to review.

E

I try to encompass all the things that folks might care about from at least from or from my experience, but if anything is missing, certainly um add to that and down here I had some questions that I wasn't sure about, um namely the legal restrictions were bound by if any, uh in terms of like licenses.

E

What happens to the intellectual property of contributors when they, you know, contribute to the organization. um Do we know what I guess we want to put forward with us concerned.

D

B

D

On the ip side,.

B

Sorry go ahead.

D

I was just clarifying so what put forward in regards to what happens with their ip yeah cash of god,.

B

um On the ip side, I think forest maybe called this out in the original, like community charter or something like that. All licensing should be apache too in any of the paketo stuff, community and uh official thing, and then ip wise. I think the moment anything gets moved over the community. Rfc definitely has this now they think about it. um But ip, like just kind of belongs to cff cool.

E

uh I'll: um rework that part, then, uh speaking of the cff, uh do we need to add any new infrastructure on clas and so forth, or are we just gonna leverage, the same infrastructure that already exists and um do we need to keep them on files somewhere? Is that our responsibility um yeah? I just wasn't sure I didn't want to put anything.

B

Forward about that, I think that that's another one, that the cff is like completely uh on top of and taken care of, perhaps a separate thing that we should follow up on. Is I don't like the current cla format? I think every one of you here run into these issues and I want to switch to dca, uh so maybe that's a separate thread that we could start with the cff on that emily. Do you know much about this around?

B

I I know like the cnb project, uses dca for everything right, and I just find it's a lot more contributor, friendly.

C

Yeah, because you only need to sign off right, you don't have to sign the licensing agreement. I don't know a lot on this topic. I know that we use dco, because the cncf recommends that for all projects so we're just following the guidelines there.

E

Okay, I guess we can look into that as well, um and yet this so that I noticed that the there is a code of conduct that the pax org uses, um that the cncf endorses, supposedly by one that who exactly or how we would enforce that. If we did implement a code of conduct, um would we need to assign a specific person say the steering committee or maintainers of sub teams that roll and make it part of the governance charter or.

D

What might make sense is just that maintainers handle it per sub team like for their contributors and then beyond that steering committee for maintainers, um just like a standard like just like escalation chain, if it would ever come to that, but.

A

Yeah yeah: let's hope that we never get.

E

Sure yeah, I just wanted to go okay. That sounds reasonable to me, um so y'all can check that out if you'd like, I will continue to add to it um back to.

E

Where am I.

E

E

And is: are there any updates on this one.

D

I don't think so. I think we're just waiting on approval still or uh can you check is it? Has it been approved everyone we're waiting on? Oh.

D

Okay, that was four I was gonna know we haven't taken a look at that. Yet can you please revert the removal of the template. It appears you remove the file rather than copying it.

D

What template is he referring to here.

C

I'm assuming that it's the rfc template so instead of copying it and filling it in sounds like mark removed removed. It.

D

E

Okay, I might have also done the same thing so I'll. Try that as well.

E

C

One I put this up a while ago, uh already sort of implemented it in the java, build packs and gotten some good feedback about it. I think we're waiting for steven to review.

C

Unless did anyone else have questions about this or comments.

B

What was the motivation behind this one again? Is this like the registry, location, stuff or.

C

This is for consumers of the online versions of the paquetto build packs, who are still trying to run behind like a firewall where they can't necessarily download all of the dependencies from the build pack. So you can explicitly remap a dependency to a different uri.

C

So the way that would work in organizations is someone would like ask an operator who would then go ensure that the dependency is being installed, is approved and downloaded and then uploaded somewhere within the whitelist or within the local network. And then you can use this format to tell any build pack where to look for a given dependency.

B

Got it, and you said you said that all the java build packs uh do this right now.

C

B

Cool, maybe uh after this is approved, we could get issues set up for the other stuff. Try to adhere to this as well.

E

Yep sounds good cool. I think that's it for our series.

E

So uh the redesigned website demo.

E

So, as folks probably know, we've been working to re to freshen up the website, add some more information and you know update it and we mentioned last meeting. I think that we'd do a demo, so I think we just want to do that this week, um final cut show, did you want to, or should I.

B

uh Up to you, you wanna, you wanna, do it. I.

E

I don't have hugo stuff set up, but I can real quick.

A

E

B

E

E

So, um first off I guess so we um originally had surfaced the builder information here on the front page, but we just opted against that. So now, what we have is we simply. We changed some of the copy to.

E

I guess to be more relevant or more informative to newcomers to the site. We also made these clickable. So these take you to the docs directly and think we're still waiting on the java docs to complete a link right now. It just links to the build pack, but that's an easy fix once um looks in and um I think we we tried to be more intentional.

E

I guess we try to simplify the language and and be more intentional, so that people and to be more explicit to that folks know exactly what we're trying to say um and, uh as you can see here, there's a nice, it's a gif of what it looks like to build and run um a build pack or an app with a buildback.

E

uh There are these fancy new icons that sam help us helped us come up with.

E

And we reworked, I think this- this bottom area was get started on something else, and now this links directly to the docs, um so folks can go straight to where they need to be. uh We read, we rewrote all of these docs as well.

E

Which took a bit of doing, but there should be a lot more informative for folks trying to get started with buildbacks, um including you know, information about the environment, variables and so forth. uh Is there anything I'm missing.

E

B

This covers most of it.

E

D

E

Right so we've added a little things that should it make it more user-friendly, such as this copy clipboard um that gives nice feedback to. Let users know that they've actually copied things and we link out to relevant repos, where applicable.

E

I think we are still working. We're, there's still a bit to be done. Someone mentioned in the packet of slack the community org and that there wasn't much about it on the current iteration of the website. So I think that, along with a few other changes still need to be made.

E

um We replaced the learn page that was here on the home page. I think that's. What now is getting started.

A

Now the learn page was the faq which we just deleted.

E

Okay, there we go.

C

I'm noticing there's no drama docs under bill packs. There is that something that you guys have talked to been about in the past or something we should be contributing in the near future.

B

I talked to him just last week about it. uh He liked he seemed to like the format of all of this a lot. uh So he wanted, like, I think, separate pages for uh what's it called the java native image and also a separate page for the javadocs.

B

So I think after, like perhaps some of the spring uh spring one stuff uh calms down a little bit uh ben or some of the spring folks might help out with us, um and I think there was one other docs change ben wanted to make, which was to document like the c uh like the cnb binding or the kubernetes like service binding spec. I think the java build packs are the only ones that utilize that so ben. I think just wanted to enhance that water build packs page effectively.

B

So I think, as soon as we get that we're like these are all in a branch right now uh as soon as we get that we're probably good to just merge changes in and stuff like that. So probably, like you know two weeks, something like that.

C

Sounds good thanks.

E

Is there anything else that um folks, who aren't as familiar with this site can see offhand that jumps out that could be corrected or improves.

D

I've noticed at least like one or two like just small typos or something it's not gonna. It's gonna go through like another copy editing process or something.

D

Is it? Is it um no.

E

D

You it should okay, I didn't. I didn't know if that was the place, the place now to point out tiny details like because it's just.

B

Small things, but do you actually like file if folks notice stuff, like github issues in the uh in the website, repo, um because that would really help just with like tracking tiny changes like this.

D

Single word like singing.

B

D

Yeah, like transform, uh transform your application source code to image that can run so it probably should be images right.

D

Sorry, that's like.

C

Creating for that is a no easier than creating a pr for that right.

D

Yeah, I don't really want to create an issue for that. I'm sorry.

B

At that point, just like push up to the redesigned branch, we're all contributors to this thing. uh I push up to it every day.

A

I think I'm gonna do that. I think the point, though, that we need like to go through like a serious copy. Editing thing of this still stands like, so we should probably plan for that.

C

B

C

Nice, this is the first time I've seen it. I think it looks great.

E

Yeah, that's good! It's like cool all right.

D

um And marty now that I've seen the stacks page, I'm gonna go ahead and accept your story. That's why I want to look at it.

A

Thanks so much.

E

Next on the list is the uh node.js re-architecture update, so uh we've I think, completed the three bill packs, which book and their respective order groupings in the node.js, buildback or metabuildpark.

E

So that's uh nodestart, yarnstart and npm start which each set they said, the command the start command for the build pack based on you know the flow from the up uh two of these yarn start and npm start utilize teeny, which allows for better process management- and, I guess most or more importantly, graceful shutdown of the app in like its context or in a darker s, context.

E

Yeah. I think that's it for that.

E

uh I guess one thing to call out is that there's still a couple of things left to do with the node.js rear architecture, um but most of that I think, is subtractive in terms of removing functionality that is now duplicated across some of the buildbacks.

A

Yeah we're working on that right now, just making yarn install do less. Basically, I think.

E

And then this last one versioning builder.

A

We're transferring ownership of the builders from the core depths team to the feature range team and as part of that, we are going to start checking in a fi, a builder.toml file and uh tagging the repo for that. For that uh for that file, um so yeah we were kind of just like talking about it's not I mean that's the main, that's the main thing there.

A

You can look at the issue for like a little bit more detail, but- um and another thing we're gonna do- is we're also going to um split out each builder into its own repo, so we can version them independently, so there'll be a builder full of builder, whatever like media, but the builder small or whatever they're called um so uh yeah just be on lookout for that. um But the the final result will be the same, which is just um they'll, be in the same place in gcr and docker hub. So.

C

That's super cool. I feel like it's made development hard in the past not being able to easily recreate that without the pipeline. So I think they'll be really great both for us and for consumers who are trying to figure out how the builder came into being or play with it.

A

Cool, that's good to hear that it'll be useful so because we we kind of just thought that. But I didn't have much uh much proof that it would actually. It would actually be useful. But it's good to hear that that they will so.

E

Cool all right is there anything else anyone wanted to call out.

D

um On this, uh what do you guys think are you gonna move away from github actions from this one.

A

For the builder yeah, we're gonna use github actions for at least most of it. We still haven't decided the best way to pull um for updating components. So we decided to leave that up too. Whoever does the story, because it's interchangeable right so whatever as long as something sends a dispatch event to the git of actions to create a pull request. Whenever something gets updated, then um it can be kind of whatever so we're gonna experience.

A

So we're still not totally sure what the implementation is gonna be, but um we're kind of leaving that as an implementation detail for now, if that, if that makes sense,.

C

One thing the riff team did with their builder repo, and this is a bit indirect- I'm not sure that I'm recommending it as the way to automate this. But just so you know it's an option because they had basically a go mod in the repo that had dependencies to all the different, build packs and then sort of use that and the fact that you can integrate that with the pandabot, which will then make a pr every time.

C

One of those things has a release and then wrote some slightly hacky scripts that took what was in there and then put it in the builder tunnel.

A

Yeah, I know we talked about that for I'd like to do like a different thing kind of like that, but um seems a little bit hacky. In my opinion, I.

C

Think it's a little bit hacky too, but if you're, if you're looking for a way to do it just wanted to put that out there. Some prior art.

A

Yeah another I mean another option we have is like we do this for tandoors. We just have a concourse pipeline that just sends dispatches, that's it, so it just watches and sends this matches. So that's nothing. We do we're also thinking about implementing a cron, a cron job on github actions, that'll just like every minute or so, or something we'll try to do something to figure out. If there's, if there's new updates, but um unfortunately it's going to no matter what it's going to be a little hacky, I think so.

A

But yeah be on the lookout for that, so.

E

um If there's nothing else, I guess we can call it there.

E

All right, thank y'all for coming, see you next next time.

D

See ya, bye, bye,.