This message was deleted.

perhaps it would help if supersedes would be required when deprecating so you need some explicit choice "this is dead"

ewoud: Corey's proposal is to add a new metadata key so that module authors can claim in a non-authoritative way that their module supersedes another.

I get that, but I'd be worried about takeovers

so at most you can signal potential replacements

and then perhaps the Forge could show those in a sidebar, eg "also see....."

sure, the messaging would have to be explicit about that

another way could be to use the source URL

This message was deleted.

See the

camptocamp-postfix

module at https://forge.puppet.com/camptocamp/postfix?src=slack&channel=voxpupuli

metadata does have that so you could possibly detect transfers

so what you could in theory do is clone the source URL, read metadata from there and take that as a replacement

ewoud: source url is tricky. In theory we could follow it back to the repo and see where it was cloned from, but what about bitbucket or svn or gitlab or..... We'd have to implement that logic for all providers

well, how many cases are there really?

ewoud: and what if you forked a repo as a starting point but then built a different module from it?

(terrible practice, but people do it)

I would prefer it if we only check the forge for a successor module

a module needs to be 1) outdated 2) without a superseded field 3) non-GH

I think you could even do a batch job on the forge and find possible replacements, then handle it manually

I'd be surprised if the count is that high

ewoud: I am working on some Relay workflows to audit our own modules (eg, make sure the right modules have the [Supported] tag, etc.) This isn't terribly different from that.

and if it is, you could email authors "you deprecated this module, we found possible replacements, want to choose one?"

ewoud: I also want to check source url for archived repos, and other kinds of housekeeping

oh yes, that also sounds useful

ewoud: and the workflows will be OSS, if people want to contribute checks

These are all good ideas. We need to put these somewhere. Dont’ want to lose the slack log.

like https://forge.puppet.com/modules/puppetlabs/xinetd isn't deprecated but https://github.com/puppetlabs/puppetlabs-xinetd is archived

and Foreman actually depends on that module (for now), I also indicated I wanted to become a maintainer on it but got literally nowhere with puppetlabs

(see https://github.com/puppetlabs/puppetlabs-xinetd/pull/122 for my frustration)

ewoud: yes, expect those to be resolved in roughly 2 weeks. lvm, rsync, xinetd should be unarchived again.