develooper Front page | perl.cpan.workers | Postings from May 2015

Re: Documenting best practices and the state of ToolChain guidelinesusing CPAN and POD

Thread Previous | Thread Next
From:
philippe.bruhat
Date:
May 6, 2015 08:44
Subject:
Re: Documenting best practices and the state of ToolChain guidelinesusing CPAN and POD
Message ID:
20150506084428.GE4295@localhost.localdomain
On Wed, May 06, 2015 at 09:26:03AM +0200, Peter Rabbitson wrote:
> 
> Therefore I am urging you to think broader and go for:
> 
> Policy - short blurb what is this about
>   Policy::Org - short sub-blurb what is this about
>     Policy::Org::P5P - pumpkin maitaned
>     Policy::Org::Toolchain - joint maintainership
>   Policy::Project
>     Policy::Project::Moose
>     Policy::Project::DBIC
>   Policy::Author
>     Policy::Author::AUTARCH - explicitly reserved (and non-squatable, PAUSE
> admins take action when needed)
>     Policy::Author::RIBASUSHI
> 

Just thinking that the "Org" intermediate bit is not really needed
(and ugly). The said organizations are big/important enough that they
naturally float above the "Project" level.

So, I suggest the following simplification:

Policy
    Policy::P5P - (could be Policy::Perl, and should just link to perlpolicy)
    Policy::Toolchain
  Policy::Project
    Policy::Project::Moose
    Policy::Project::DBIC
    ...
  Policy::Author
    Policy::Author::AUTARCH
    Policy::Author::RIBASUSHI
    ...

Would documents like David's CONTRIBUTING.mkdn document that he includes in
most of his distributions fit under Policy::Author::DAGOLDEN?

-- 
 Philippe Bruhat (BooK)

 Just because you believe it does not make it so.
                                    (Moral from Groo The Wanderer #54 (Epic))

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About