4 ms·
On CPAN, you can be added as a co-maintainer if there is a long-standing bug with inactive maintenance, you've fixed it in a way that's eminently usable by the
by Vivtek 13y ago
On CPAN, you can be added as a co-maintainer if there is a long-standing bug with inactive maintenance, you've fixed it in a way that's eminently usable by the maintainer, and you can demonstrate long-term fruitless attempts to contact the maintainer.
In the Github context, since pull requests are obvious demonstrations of the first two criteria, it seems to me the most logical solution would be simply to move existing forks over to a new maintenance fork owned by a popular fork maintainer with an explicit governance mechanism. Then the original owner isn't interfered with, but the new forked community king can go ahead with centralized management of the overall project if the community agrees with that.
- alexchamberlain 13y agoThere's very little coordination between forks and URLs point directly at repos, so I'm not sure how this would work.
- Vivtek 13y agoI'm suggesting that there should be more coordination between forks. I'm not sure what your URL point means - that the URL is a unique identifier for the project and that there's no way to forward people to the new "authoritative fork", I suppose, which is a good point. Perhaps an explicit forward on a moribund project or something.... Hm. You're right, though. The CPAN thing works because there's a centrally managed list of unique identifiers that point to the analogue of URLs (which are stored under user's names, just like Github). Good point.