Should this repo be sunset?

[edmorley]

The last commit to this repo was 3 years ago, and PRs aren't being reviewed (eg #39) - as such it seems this repo is unmaintained? Should it be archived to make the current status clearer?

[jjbustamante]

I think the answer is yes!
I have in my TODO list to open the conversation to archive this repository, thanks for creating this issue @edmorley

[edmorley]

Just checking in about the status of this?

If we're not yet ready to sunset the repo, could we at least merge the docs only #39?

[edmorley]

In #39 we found that CI is completely broken at the moment.

I think this is another reason we should archive this repo now. (It can always be unarchived in the future if this project is resurrected.)

[jjbustamante]

In #39 we found that CI is completely broken at the moment.

I think this is another reason we should archive this repo now. (It can always be unarchived in the future if this project is resurrected.)

@hone @jkutner do we have a process in place to archive repo under CNB?

[jjbustamante]

My thoughts about this:

• If I am not wrong, this repository is just a staging area for any change that we want to make in the Tekton Catalog
  • buildpack-phases
  • buildpack
• David and Javier were responsible in the past for keeping up to date with the API versions available in Tekton, honestly, I haven't tried to do this, as a Platform maintainer, I think, is part of my duties but I do not have the bandwidths right now.
• We should update the OWNER files mentioned above, I can do that.
• If we archive this repository, the only side effect will be we won't have a way to easily test an update to the catalog before merging it, right?

[edmorley]

This integration is currently buggy/broken btw, and people are using it not realising it's not actively maintained:
heroku/buildpacks-python#196