Sai Kiran Maggidi

Not sure about the folder structure of the multi-arch samples I am thinking of ``` multi-arch ├── extensions/ | └── [...] ├── builders/ | └── [...] └── buildpacks/ └── hello-world/...

@angeloashmore I am interested in contributing to this feature, would you mind let me know if this feature has any high priority, as it would take sometime for me to...

I will take this issue, as I already did some changes in imgutil related to it :)

@thesuperzapper I am willing to contribute to this feature out side the GSoC, willing to know if it is fine. Thank You.

> @WYGIN what areas do you have experience in that could help us? around 9 months of experience on containerization and GoLang and more than 2 years learning curve on...

> For those watching, we are nearly ready to start committing code for Notebooks 2.0! > > We have mostly finalized the new CRDs (see the new example repo for...

@jjbustamante If this feature ships, isn't it possible for platform operators to create their own lifecycles? excited to see this feature shipping, and I think one should publish an article...

> The pack CLI during build has supported `--lifecycle-image` for custom lifecycles with existing builders before this as well. never noticed this flag, Thanks a lot for the information

@jjbustamante there was an issue with `pack buildpack package` when packaging `local` buildpacks _**without `--publish` flag**_. Please make sure the issue is resolved before merging this PR. The issue is...

@jjbustamante can you please take a look into these links: [Git](https://pkg.go.dev/github.com/moby/buildkit/client/llb#Git) , [Http](https://pkg.go.dev/github.com/moby/buildkit/client/llb#HTTP) , I think LLB can be helpful here