Relationship to Cloud Native Buildpacks?

[jkutner]

Does this project have any relationship to the CNCF project https://buildpacks.io/

Is this repo an implementation of CNB, or a does it provide a component that can be used with CNBs?

[rarkins]

This project was created independently and we haven't looked into whether work could be shared in either direction

[Chumper]

It seems to me that both projects have a different vision.
https://buildpacks.io/ is about projects that will be converted to docker images based upon a given contract,
while this project is more of a docker image where different tools can be installed in multiple versions during runtime.

[jkutner]

@Chumper @rarkins thanks for the info. I'd kindly request that you change or clarify the name. We're received questions about this. In addition, if you could put an explanation in the readme we would appreciate that.

[rarkins]

If you get questions in future maybe you can explain that the term buildpack predated either project by a long way?

[jkutner]

@rarkins The Cloud Native Buildpacks project is the third version of a technology that has been around for about 10 years: https://blog.heroku.com/buildpacks-go-cloud-native. "Buildpack" has been used by Heroku, Salesforce, Cloud Foundry, and Pivotal/VMware for about that long. Since 2018 it's been used by Google, Red Hat and others.

If this project is not a buildpack (in the sense that it is commonly used across the industry), we would appreciate you clarifying the name, and explaining this in the readme.

Thank you for understanding. We only want to avoid confusion for our end-users.

[jkutner]

@rarkins @viceice Have you had a chance to discuss this some more? I was reminded that the Linux Foundation has a trademark on buildpacks.io, and wanted to share this information:

https://trademarks.justia.com/905/41/buildpacks-90541508.html

[viceice]

will try to do the renaming in the next two weeks

[rarkins]

That's great to hear that the term is buildpacks.io instead of buildpack in general. Thanks for your flexibility on the matter. We had been planning to rename but you've saved us a bunch of work.

[jkutner]

Sorry, I think you misunderstood me. I'm still requesting that you change the name of this project.

[viceice]

Added #524 to track, but hasn't high priority