On Fri, Jul 2, 2010 at 14:45, Karen Etheridge <p...@froods.org> wrote: > On Fri, Jul 02, 2010 at 11:19:02AM -0400, Chas. Owens wrote: >> Administrative Tasks: >> -------------------- > > Another one, which should have a reasonably short deadline, is identifying > the procedure for making documentation changes itself! > > Presumably this would be using a git repository, so we need to identify: > - where should perldoc participants send their ssh key to > - guidelines for branches, merging etc (who can commit to master, how > should topic branches be structured etc) > - process for requesting peer review, fact checking, verification of code > on various architectures, etc > > The document at > http://search.cpan.org/~doy/Moose-1.08/lib/Moose/Manual/Contributing.pod is > an excellent template for describing the workflow of various > participants and the use of various branches. snip
My current plan, once we get to the point that we are modifying the actual docs instead of finishing perlopquick, is to use http://github.com/Perl-5-Documentation-Team/perl as the central location for our changes. Each contributor would fork off of that repo and push changes back to it (I am using GitHub's new Organizations feature, so there eventually will be more than one person able to merge pushes back in). We would push patches off to p5p in reasonably sized chunks for committing against the current blead release (or, once we build up enough trust, they might start pulling changes from us). -- Chas. Owens wonkden.net The most important skill a programmer can have is the ability to read.
