community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ulrich Stärk <>
Subject Re: commit rights to ComDev non-community.a.o site resources
Date Sun, 15 Mar 2015 21:24:34 GMT

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?



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) become writeable for all Apache 
> committers too? Same for
> Regards,
> Hervé
> [1]

View raw message