John Morrison wrote:
> [Vote 1]
> [+1] Seperate "apps" module: xml-cocoon2-apps
>
> [Vote 2]
> [+1] cvs ci for xml-cocoon2-apps goes to list xml-cocoon2-cvs
> [-1] cvs ci for xml-cocoon2-apps goes to list xml-cocoon2-apps-cvs
>
> <personal>I feel happiest if everyone working on the
> main project saw the uses their contibutions were being
> put too and I'm sure people working on apps should really
> keep upto date with the main project. This may have a knock
> on effect of somebody with just -apps karma submitting
> sufficient patches and being added to the main cvs! :)</personal>
+1 to alll you say :-)
> [Vote 3]
> [+1] People voted cvs access for documentation to have
> full karma
> [-1] Module "hack" for xml-cocoon2-docs to do:
> cvs co xml-cocoon2/xdocs
>
> <personal>If people want to only co the xdocs then
> they can, but I think it would be best to document
> how to do so than create a "hack" (sorry Ken).</personal>
No need to be sorry, it was just a RT.
I think both you and Andy easily convinced me about this, so +1 for
having the docs people be voted for full karma access, because
1) Andy is right, documentation and code have at least the same level of
importance, and since they are related, should stay in the same CVS,
even conceptually
2) For us committers are just committers, there are no second-level
citizens; if the documentation is where the code is, then there
shouldn't be different types of committers.
> PS, nice addendum Ken :)
:-D
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
