Front page | perl.perl5.porters |
Postings from March 2023
On Thu, Mar 30, 2023 at 12:20 PM demerphq <demerphq@gmail.com> wrote: > FWIW, I personally stopped trying to address these tickets. Nobody else > seemed to care about them, and many of them relate to "abandonware"[1] and > I dont see the point in writing a fix that will never get released. > > I tried to get Andreas to clarify the rules about releasing fixups to > PAUSE/CPAN without having to take ownership of the distribution, but he > refused to give me a clear answer[2] so I had no choice but to assume that > you can only release something if you take ownership over it, and since I > don't wish to take ownership of a module I know nothing about I stopped > bothering with BBC tickets that are not traced back to a change I made. > > I would be a lot more enthusiastic about fixing and rolling releases for > these distributions if I knew that PAUSE would accept them. It seems a > shame actually, effectively PAUSE policy about ownership discourages people > from fixing issues like this. Who wants to spend time fixing a deprecation > in a distribution you know nothing about when the author is likely absent > and PAUSE will refuse to accept the change unless you take ownership over > the module? > The community has had some amount of success over the years in convincing some inactive authors to turn over comaint or firstcome permission bits to other willing volunteers - there is a documented process for that (send emails to the author asking to take over; send emails to modules@perl.org documenting the effort), and there have been circumstances where entirely absent/unresponsive authors have had their modules granted to other trusted community members for the purposes of patching troublesome bugs, at the discretion of the PAUSE admins. In addition, the "distroprefs" facility exists, which is a registry of patches that can be applied on top of an installation, but I think not many people know of it or make use of it, other than Slaven Rezic. I think we could probably do better with its documentation and perhaps its usability, so I want to look at this at the Toolchain Summit in Lyon at the end of April.Thread Previous | Thread Next