All Paketo buildpacks should be named in a consistent manner. Specifically, they should include a "Paketo" prefix before their identifier and include a "Buildpack" suffix.
Providing a buildpack name that indicates that these buildpacks are part of the Paketo organization will help users to identify the provenance of the buildpacks running on their platform more easily. There are already offerings for buildpacks in similar runtimes from other organizations. Indicating that a buildpack comes from the Paketo organization will help to clear up any ambiguity.
Taking an example of the "Node Engine" buildpack, the proper name would be
"Paketo Node Engine Buildpack". This name should appear in the buildpack.name
field within the buildpack.toml file.
The obvious alternative is to let buildpack maintainers name their buildpacks independently. This will likely lead to confusion and is not recommended.
Any buildpacks that do not follow the rules outlined above should be renamed to align with this RFC.
There are already an existing set of buildpacks within the Paketo community that conform to this naming pattern. Here is a subset of examples: