Cloud Native Buildpacks Implementation Sync, 29 Apr 2021

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Implementation Sync: 2021-04-29

Description

Meeting notes: https://bit.ly/38pal2Z

A

We just shipped lifecycle0112 a patch release to fix uh caching for build packs on the 06 apis.

A

So please, let us know if you see any issues with that, otherwise I think we'll be continuing on the work for reversing analyze and detect.

A

I think that pr is probably going to be about ready to merge once we bring it up to date with maine, we were going to add acceptance tests for the restore, but I really will be covering that out as a separate issue, so stay tuned for more stack, packs stuff in the coming.

A

A

Anyone else want to throw in an update.

B

Sure I did a tiny bit of work on the lifecycle this week, but um or I guess last week, so I have a pr up just around asset package stuff. Doesn't I don't think it does that much, but uh there's like a table. I would appreciate someone looking over when ever you have some time. I know that there's a lot of a lot of stuff on everyone's.

C

Plate on this team.

B

A

A

I think, if we're, if we, if there are no more status updates, um the next standing item is release planning, but I think, just to sort of state again we're working on the stack packs, um the the epic, uh the stackpacks epic, which I guess we can link to um kind of details. How we'll be breaking that down- and you know maybe releasing in chunks. But I don't think we have any more concrete things to say about the next release um until we've gotten further on the at least phase one stuff.

A

um With that uh we can go into our needs discussion and.

A

Dan hi, uh I I know that you have a needs discussion issue up here. um I guess maybe I could share my screen so that we're all looking at the same thing uh which we did discuss last week and I was supposed to add the notes from that discussion to the issue. But I did not um so maybe it's worth kind of recapping what we said and get your thoughts as well.

D

A

I think I have the notes in front of me, so I think we had said that. We think that this is a good idea. We would love an rfc for it. One of the open questions is whether it should be opt in or kind of opt out.

A

We had mentioned that there is technically a workaround that build packs can do by keeping track of a time stamp that they touch certain files with you know before doing their thing, but we see that as an additional burden on bill pack, authors that could also result in long labels on the image and you know, pose a problem for reproducibility anyway.

A

um So you know, I think we see the value in what you're describing, um but it's just, I guess going through the the steps of having an rfc that the rest of the community can weigh in on.

D

Okay, yeah, that sounds reasonable, is there uh this will be my first rfc. Is there like a getting started? You know or something I can reference to for that.

A

There is a template in the rfc's repo, um which is like fork this repo and then copy this file into text, and you give it your. You know: zero zero, zero, zero dash, my name, you know my feature name um and uh and fill in as much as you can. I think you know some of this stuff is more like encourage.

A

um You know it just as much as you can and if you get stuck in any way, um I think any of us here would be happy to provide input. um Yeah.

D

Okay, yeah that the how it works section I may need some help with I'm not totally sure how that would happen under the covers, but cool yeah. I can get it started. Thank you.

E

Although we can look at the like the readme in the rfc um repository, it says like how to propose like a new rfc.

D

Okay, I'll read through that too. Thank you.

A

Do we want to say anything more about this? Just since you know we.

E

A

E

Maybe you can change it from the discussion to needs rfc sure if we're all good with this.

D

I'm not sure if it matters, but I did implement a work around similar to what you described. Kind of storing and restoring the modification.

C

A

If we're good on this one, I want to see there are others, I think we've kind of been skipping over the stack packs ones.

A

Unless there's anything that we want to call out today- and this is it possible to export a tarball, um we had a discussion last week about build kit and some questions that we we have for eric who's, giving the presentation in our office hours today at two eastern.

A

um I don't know if, there's anything more to say I haven't looked at this since last week.

A

It remains a discussion item.

A

um And with that, I think we we're actually at the end of our agenda. Does anyone have anything else that oh rfcs, I forgot rfcs?

A

um I don't think there's anything new from last week we kind of said that we wouldn't go through each one, one by one, just if someone has something that they want to bring up in this forum. You know we can focus on it, but otherwise.

A

Please go add your comments.

A

Does anyone have anything they'd like to bring up.

C

Did everyone look at the um I'm messing this up? I haven't done this yet, but I know sam said he updated the uh his rfc for um separating the layers from the config files with a bunch of proposed directory structures. I feel like uh it's the.

E

C

It probably affects this team more than anyone else, so I just want to make sure that tesla look at the options here.

E

I reviewed it once, but I feel that I need to like, since I mean after the last changes they like he changed like this completely. um I feel like it's better to review it like more deeply, um but I agree it's going to influence our team.

A

I was just just looking for.

E

Commentary yeah, he updated it after, like the two suggestions that you emily put, it.

C

Oh jeez, I'm very distracted right now, because my cat is acting very strangely and he's had a lot of health problems. I feel like. I need to jump off and make sure he's. Okay, sorry I'll see.

B

Y'all all right is there anything else. um I think yeah. Everyone should take a look at that.

D

Yeah I had one other question that I just wanted to raise. I was talking to emily about libsy and b, and she mentioned that this might be the meeting to to kind of discuss. I guess potential changes and stuff with lib cnb is that accurate.

A

I think we're at least I think this. The people in this meeting are sort of slowly backing away, like I personally haven't done, even though lip sandy falls under the implementation. Like sub team structure, um I know that I haven't worked on lip c and b. There's there's been some discussion of breaking out a separate team to manage sort of build pack. Author related concerns. um I'm not sure where that conversation landed.

B

Yeah same, like I think, sam mentioned he'd, be interested in contributing uh on that team, but I I do think consensus is that we're maybe moving away from this team.

D

B

For that project, but uh yeah this is currently the place to talk about it. So go ahead.

D

Okay, no, I that that was kind of what I was trying to understand. um Emily had said something similar, and I was just trying to understand, maybe, where that that's at or how we can help nudge things forward there. It's lipsy and b's an area where I've got a lot of interest in helping so.

A

Are you in touch with sam from bloomberg.

D

I've I've talked to him through github, occasionally, but not uh not directly, yet.

E

I feel like him like sam and emily are the people to talk to about this.

E

I mean you can also share it with this team, but I feel that they're like working on kind of splitting it from this.

D

E

If I understand the situation correctly,.

D

Okay, maybe I'll reach out on slack and see if I can get a conversation going there awesome. Thank you.

A

There was also a uh I can't remember if it was a working group or an office hours where lib cnb was discussed at length um kind of sam and emily going over. Some of the.

A

Ways that they would like to change it um try to see if I can find that I don't know that if that recording would be valuable, but certainly interesting,.

D

Okay, yeah, I can go back for that. That would be interesting to hear their thoughts on it.

A

um If there are no more items for discussion, should we call it.

E

Sounds good jesse thank you for taking the notes. Yes,.

A

Thank you, it's so nice to have notes.

A

E

See you online bye thanks.

D