Mailing-List: contact dev-help@community.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@community.apache.org
Received-SPF: pass (athena.apache.org: domain of uli@spielviel.de designates
 83.223.83.232 as permitted sender)
Message-ID: <5505F892.5080401@spielviel.de>
Date: Sun, 15 Mar 2015 22:24:34 +0100
From: =?windows-1252?Q?Ulrich_St=E4rk?= <uli@spielviel.de>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10;
 rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: dev@community.apache.org
Subject: Re: commit rights to ComDev non-community.a.o site resources
References: <17612679.0LQvIchjWZ@herve-desktop>
In-Reply-To: <17612679.0LQvIchjWZ@herve-desktop>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit

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
>