river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: v0.2 Draft Proposal - River basic dev process
Date Fri, 07 Sep 2007 19:01:48 GMT
Hi Jim,

On Sep 7, 2007, at 8:19 AM, Jim Hurley wrote:

> * Code Reviews
>      - for public API changes:
>             RTC <http://apache.org/foundation/ 
> glossary.html#ReviewThenCommit>
>             These changes have potentially broad effects on developers
>             and users, and therefore will require a code review and  
> vote.
>             Since some of these changes will effect the API docs  
> ('specs'),

typo: effect should be affect.

>             everyone within the Jini/River community is encouraged  
> to review
>             and vote.  The PPMC member votes are binding, but the  
> sentiment

You will need to change this upon graduation to remove references to  
PPMC. In the incubator, you might consider giving committers binding  
votes instead of PPMC members. Once you graduate, there might be no  
need to change it if everyone is happy with committers having binding  

In practice, there's not much difference between committers and PMC  
members. One Apache guideline is that people affected by a change  
should be able to influence that change. So a goal is to have most if  
not all committers in mature projects actually be PMC members. Also,  
a committer-but-not-PMC-member will probably be able to affect a vote  
by being very active in trying to modify a change that they don't  
agree with.


>             of the entire Jini/River community will certainly be  
> strongly considered.

Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!

View raw message