John Morrison wrote: > [Vote 1] > [+1] Seperate "apps" module: xml-cocoon2-apps
+1 > [Vote 2] > [+1] cvs ci for xml-cocoon2-apps goes to list xml-cocoon2-cvs +1 > [-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> Agreed, this is community building. Also apps developers need to see the cvs commits from the main project to know when changes affect their apps. > [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 +1 ... I am such an example. To do the doco for the entity resolver, i also needed to tweak config files and occasional Java. Besides, we need people to be doing Javadocs stuff inside the code and integration with the main docs. Samples is another area where they will work. > <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> > > J. > > PS, nice addendum Ken :) Yes, thanks. It now needs a few changes for module names. Are these documents available somewhere? I have never seen one. --David --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
