+ 1 Best regards,
Pierre Smits *ORRTIZ.COM <http://www.orrtiz.com>* Services & Solutions for Cloud- Based Manufacturing, Professional Services and Retail & Trade http://www.orrtiz.com On Mon, Mar 16, 2015 at 9:39 PM, Hervé BOUTEMY <herve.bout...@free.fr> wrote: > +1 (non-binding) > > Regards, > > Hervé > > Le dimanche 15 mars 2015 22:24:34 Ulrich Stärk a écrit : > > Heh. > > > > When I put that sentence in the board report we didn't have projects-new > > yet. > > > > I don't see a reason why we shouldn't open up those two (or even all of > > /comdev) for all committers as long as changes are first discussed on our > > lists. > > > > What do others think? > > > > Cheers, > > > > Uli > > > > On 2015-03-14 16:38, Hervé BOUTEMY wrote: > > > Hi, > > > > > > I lately gave patches for projects-new that were not applied: it seems > > > there is a problem to determine who should do it (to avoid projects-new > > > to be a single-man affair). > > > > > > Then I made some investigations: in the last board report for ComDev > [1], > > > I > > > think I found the cause: > > > "Since artifacts produced by ComDev are usually documentation on our > > > website which is writable for all Apache committers, we usually do not > > > add committers to the ComDev project." > > > > > > Then should projects(-new).apache.org become writeable for all Apache > > > committers too? Same for reporter.apache.org? > > > > > > Regards, > > > > > > Hervé > > > > > > [1] https://whimsy.apache.org/board/minutes/Community_Development.html > >