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.
