Implement RFC 63 Project Status

[loewenstein-sap]

With the RFC 63 we decided to put some transparency on the status of repositories in the paketo-buildpacks Github organization.

This is a tracking issue to collect all work and discussions around the topic.

Buildpacks

• Java
• Node.js
• Go
• Phython
• Web Servers
• .NET Core
• PHP
• Ruby
• Rust
• Utilities

Tooling

• libpak
• libpak-tools
• packit
• jam
• github-config
• pipeline-builder

Others

• Content
• Dependencies
• Stacks
• Builders

[loewenstein-sap]

@paketo-buildpacks/steering-committee I created this issue to track progress on the implementation of the RFC 63.

For composite buildpacks, it might make sense to create individual issues on the composite buildpack repos to contact the maintainer teams and check in with them on the criteria for Tier 1 to 3.

Not sure for all the other issues, maybe we can also just start discussions here. WDYT?

Another topic we should align on is where and how to publish. I think we should put this information into the individual affected repositories and additionally create a new Markdown file in the community repo listing the different tiers and member repositories for delivering an overview. We should probably also mention this on the project documentation page and finally write a blog post once we have everything in place.

[dmikusa]

For composite buildpacks, it might make sense to create individual issues on the composite buildpack repos to contact the maintainer teams and check in with them on the criteria for Tier 1 to 3.

Could we do this here? If we add a "template" markdown snipped to the story description, teams can copy & paste into a comment and populate with the info needed. We can check off and add the tier status to the description as it's been verified.

Another topic we should align on is where and how to publish. I think we should put this information into the individual affected repositories and additionally create a new Markdown file in the community repo listing the different tiers and member repositories for delivering an overview. We should probably also mention this on the project documentation page and finally write a blog post once we have everything in place.

+1 for blog post to announce when we have this ready
+1 in the community repo, probably a new file. I think this should be the official source of record
+1 for documentation as that's where users will most likely encounter this. Maybe add a page under Concepts? It would be awesome if we could automate this, maybe a Github action that scrapes the community page & updates the docs page. I worry that this gets out of sync.

As for individual buildpack repos, what I'd love to see is a badge icon. Like you see on a lot of different repos, that would point show the tier level and link to the community repo if clicked. Not 100% sure how we'd do that. I think those usually require a link to a server, but I think that would be cool if we could make it work. It's dynamic and looks nice too.

Maybe another way to update the docs and buildpack repos would be to have a job in the community repo that runs when the tiers markdown is updated. It could parse that and push updates out to the docs & the buildpack projects. 🤔

I really think it needs to be automated or stuff get's out-of-sync.