search

puppetlabs / forge_issues

This repository will allow public community members to file bug reports against the Puppet Forge
Creative Commons Zero v1.0 Universal
0 stars 0 forks source link

Interface for deprecations and transfers in Forge UI #23

Open buzzdeee opened 1 month ago

buzzdeee commented 1 month ago

Use Case

I just had the case, that I wanted to deprecate one of my own modules, and point to a successor on the Forge. And had to find out, there's no easy way to do so, or at least request this type of thing directly on the Forge. By accident I came here, and found, I can do it with an issue here.

In Forge UI, I can, as a module owner, delete specific module versions. It would be nice to be able to deprecate modules, and if available, point to successors, directly on the Forge.

When the owner issues the request of the module that's going to be transferred or deprecated, this might become an automated process, without review? Or someone to review, if the successor may make change, or the successor may have to accept the request?

When the new owner of the transfer, or the successor of a deprecated module issues such a request, that shall not be automated. It might be enough, if the owner of the to be transferred or deprecated module has to OK the transfer or deprecation. Alternatively, go through a review process, like these issues here?

In any case, having to come here to the GitHub issues for module transfers and deprecations, is not straight forward, nor easy to find.

binford2k commented 1 month ago

There's already an API for it as well https://forgeapi.puppet.com/#tag/Module-Operations/operation/deprecateModule