Yes, there is no way to restrict commit privileges within a project. Neither technical, nor according to the Apache idea. Sandbox is also the place where committers can apply patches much faster with less care. So the committers workload should not be to much a problem IMO.
BTW, +1 for trinidad sandbox Manfred On 12/14/06, Adam Winer <[EMAIL PROTECTED]> wrote:
On 12/14/06, Danny Robinson <[EMAIL PROTECTED]> wrote: > +1 (non binding). > > Q1 - Would this add more workload to those with Commit priviledge, or could > we open up the commit access a little more for this project? I don't think there is any process for a less-restrictive commit access for one portion of the product. My understanding is that a committer is a committer is a committer... Someone with more detailed ASF expertise can confirm. -- Adam > > On 12/14/06, Adam Winer <[EMAIL PROTECTED]> wrote: > > > > I'd like to add a new sandbox project to trinidad, as a parallel directory > > to trinidad and plugins. This'd give us a place to add more substantial > > contributions - Danny Robinson's popup, for example - and give them > > time to be played around with, fixed up, APIs tweaked, etc., before moving > > in to the main libraries. It'd also give me a chance for committers like > > me to add experimental features that definitely shouldn't go into the > > trunk > > immediately, or perhaps ever (some ideas I've been toying with for > > multi-component validation, for example). > > > > Feedback? +1 from me. ;) > > > > -- Adam > > > > > > -- > Chordiant Software Inc. > www.chordiant.com > >
