Deprecate Knative Backstage plugins

[aliok]

https://github.com/knative-extensions/backstage-plugins

Let's deprecate the components here as there's no interest at all.

cc @knative/steering-committee @knative/eventing-reviewers

[aliok]

I actually don't know if the process for deprecation is written somewhere.

[dprotaso]

@aliok we have some steps here: https://github.com/knative/community/blob/main/mechanics/SUNSETTING-FEATURES.md

In general though I think it depends on the scope and GA level of the component.

[aliok]

@knative/steering-committee @knative/eventing-wg-leads

This plugin is not used and didn't take off as we were hoping.
It wasn't production ready and we are not aware of any production usage.

Let's vote on this?

[creydr]

+1

[dprotaso]

+1

[dprotaso]

I actually don't know if the process for deprecation is written somewhere

I think it's ultimately the WG lead's call but steering can chime in (eg. if they have another maintainer that wants to take over etc.)

[aliok]

WG lead said +1, so, gonna start this work.

[evankanderson]

Ask users if they are using the feature

In the same way, it is very important to get to know if any user is actually using the feature. A post should be sent to knative-users@, with essentially the same contents as the post to knative-dev@. Again, lazy consensus can be applied over a period of two weeks.

After that, I think we can update the README, close any open issues, and archive the repo

[aliok]

After that, I think we can update the README, close any open issues, and archive the repo

Yes. That's part of the "work" :)

[aliok]

The email is sent to both mailing lists: https://groups.google.com/g/knative-users/c/H7q6_DNL8II