Paketo Buildpacks Working Group, 4 Aug 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Working Group: 2020-08-04

Description

* Buildpack Naming

A

B

Oh marty: did you move to marin.

B

I did nice place.

A

Your dog is awfully still josh.

B

He's a good dog trained him. Well yeah! He knows, there's a meeting so he's being quiet, wow.

A

He's been there for months.

A

How do we know that josh is not just like a taxidermist who was trying things out on this dog.

B

No, I would never do that to joey.

B

He took all of his toys out one by.

C

A

I know we were all supposed to be in the mountains, for this.

A

B

Tim, it looks like you're like in a cloud because you can't see the bottom of your.

B

A

I think ben's in some other meeting. We don't know about.

A

Oh no now he's in our meeting. Okay.

B

um uh Stephen just said: he'll be late, so someone else should kick it off, and forrest is also going to be late because his internet is.

B

C

I guess I will take that then uh outstanding rfcs to start uh anything that we are anybody know anything about what we're waiting for on the pacquiao community charter.

A

Unfortunately, forest would be the one to speak to that.

C

Okay, then dependency mappings, emily.

D

I have the command. I was trying to push it up right before this, to update to use a binding and map digest uri, um it's almost ready. Okay, uh come.

C

Back to this in five minutes.

D

There'll be a commit there.

C

So I had that issue. Someone opened the issue against it for us and I put an example in there can you include that example. In your uh sure thing update to it.

D

Already got examples in there.

C

Okay, good enough, then cool okay, uh then I guess we just wait for forrest on the other one and emily will take care of that uh build pack name, consistency.

A

uh Yeah, the team recently was doing some work on uh release notes generation like given a build package.

A

We were generating release, notes for like releases that got cut and uh uh at the same time or like in and about the same time, the ruby build pack started, probably in the proc file, build pack and when we did that we're generating release, notes that included some of the metadata coming out of the proc file build pack, and we noticed that some of the build packs are prefixed with paquetto and some of the bill packs are not.

A

And so I just wanted us to get to the same page about whether or not we're, including the prefix of paquetto as the the prefix in the name so like, for example, the proc file bill pack says paquetto profile, build pack but, for example, some of the ruby build packs like puma or just puma, build pack.

C

So um I think it's important for us to include that, especially when it comes to outputting it in log output, so that it's identifiable where people are going to go back to and as we start mixing them uh with tanzu build packs and uh other places or the google build packs and other places of the heroku build packs and other places. It is, I think, important for the paquetto build packs to advertise exactly who they are and where they come from.

A

uh I agree completely reasonable. I just wanted to bring it up as an item, so we could all be on the same page about our intentions there casual. I think that means that the the build packs that we maintain, that don't have a prefix should should add that prefix, so that it's clear.

E

Sorry I joined a little late. I missed the first part. Is this around the naming run.

A

Yes, this is like naming for build. Packs should have like a pocketo prefix on them.

E

Okay cool, so then it's like pocato run time or whatever uh build pack. Is the convention? Yes great? So we could work on getting our stuff, updated.

C

C

That appears to be it on the agenda.

C

Anybody else have anything else: nope, okay, let's call it thanks. Everybody bye, bye,.