On Thu, Feb 17, 2011 at 3:18 PM, Andreas J. Koenig <andreas.koenig.7os6v...@franz.ak.mind.de> wrote: >>>>>> On Thu, 17 Feb 2011 14:43:44 -0500, David Golden <xda...@gmail.com> said: > > > That raises a broader question. > > Who maintains all of the non tarball content on CPAN and what is the > > process for getting it changed? > > The original idea was that we have files on cpan in the authors tree > that have a fixed name and can be overwritten by the owner. Then other > cpan content could link to these files with relative links. It did not > work out well. It seems that once somebody owns a file it becomes a > burdon to maintain it. Not really surprising. We probably need other > models for that.
Brainstorming -- what if we put all "static" CPAN content in a git repo somewhere and arranged for the CPAN "master" to refresh from the repo periodically. Then we choose a suitable admin team to review and apply patches. (PAUSE admins + others?) That would let those motivated to update things have a much clearer method of doing so. -- David
