apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject RE: cvs commit: apr-core STATUS
Date Wed, 15 Nov 2000 20:32:14 GMT
Never mind - I guess I am subscribed ... locus is slow again today.

> -----Original Message-----
> From: wrowe@locus.apache.org [mailto:wrowe@locus.apache.org]
> Sent: Wednesday, November 15, 2000 1:05 PM
> To: apr-core-cvs@apache.org
> Subject: cvs commit: apr-core STATUS
> 
> 
> wrowe       00/11/15 11:05:05
> 
>   Modified:    .        STATUS
>   Log:
>     Just my $.02
>   
>   Revision  Changes    Path
>   1.12      +80 -25    apr-core/STATUS
>   
>   Index: STATUS
>   ===================================================================
>   RCS file: /home/cvs/apr-core/STATUS,v
>   retrieving revision 1.11
>   retrieving revision 1.12
>   diff -u -r1.11 -r1.12
>   --- STATUS	2000/11/15 16:29:57	1.11
>   +++ STATUS	2000/11/15 19:05:04	1.12
>   @@ -1,6 +1,6 @@
>    APACHE PORTABLE RUNTIME (APR)			PMC 
> Issue Status Document
>    
> --------------------------------------------------------------
> -----------
>   -			  Last modified at [$Date: 2000/11/15 
> 16:29:57 $]
>   +			  Last modified at [$Date: 2000/11/15 
> 19:05:04 $]
>    
>    
>    PMC Members / Committers:
>   @@ -43,9 +43,11 @@
>        The PMC chair
>            Status: taking nominations/votes on pmc@
>    
>   -	Nominees and votes-for:
>   -	  Ryan: Karl, OtherBill, Jeff, Sascha
>   +	Ryan nominated by Karl, OtherBill seconds. Jeff, Sascha 
> in support.
>   +        Accepted: ?
>    
>   +        Other nominations?
>   +
>        Policy on giving out Commit Access
>            Status: see below
>    
>   @@ -55,12 +57,27 @@
>        APR Project guidelines:
>    	Status:
>    
>   +First Meeting Agenda:
>   +
>   +    Acknowledge nominations for the chair, elect the chair.
>   +
>   +    Acknowledge membership of the committee, confirm the members.
>   +
>   +    Note the pmc's vote to agreed-upon Mission statement.
>   +
>   +    Note the pmc's vote to agreed-upon procedural rules, 
> for voting, 
>   +    accepting new committers, apr pmc membership, etc.
>   +
>   +    Set the time and place of next meeting (T+6 mos :-?)
>   +
>   +    Ajourn
>   +
>    To Do:
>        [ maybe move some of this tracking to cvs/apr/STATUS? ]
>    
>        Web site
>    
>   -    Call for a first meeting
>   +    Call for a first meeting - see and modify above agenda
>    	Status: Greg asks, "what the heck is this?"
>    
>        Fill the code repository
>   @@ -89,26 +106,13 @@
>     of C data structures and routines, forming a system portability
>     layer to most Unices and the major commercial operating systems.
>    	Votes:  Karl +1, Greg +1 (maybe tweak the OS stuff), Sascha +1,
>   -		Ryan +1, Jeff +1
>   +		Ryan +1, Jeff +1, OtherBill +0
>    
>   - The core mission of the Apache Portable Run-time is to provide the
>   - comprehensive library of routines to encapsulate all 
> underlying process
>   - and thread management, file systems, communications, and 
> other OS-specific
>   - kernel details.  This allows programmers to write a 
> program once and be
>   - able to compile and run it anywhere.
>   -
>   - With that central goal in mind, the original mission of the Apache
>   - Portable Run-time is to further facilitate programming of 
> daemons (also
>   - known as services) so that these resources are developed 
> quickly, and
>   - work predictably and reliably on a broad array of unix 
> and other servers.
>   -
>   - The broader mission of the Apache Portable Run-time is to 
> provide the
>   - underlying support to allow quality code to be developed 
> in the C language,
>   - without concern for platform issues, including 
> endianness, thread safety,
>   - portability and library availability and their licensing 
> encumberances.
>   - While focused on daemons, the APR will consider any 
> submission that furthers
>   - these objectives.
>   -	Votes:  Bill +1, Greg +0
>   + The Apache Portable Run-time mission is to provide a free library
>   + of C data structures and routines, forming a system portability
>   + layer to as many operating systems as possible, including Unices, 
>   + MS Win32, BeOS and OS/2.
>   +	Votes:  OtherBill +1
>    
>    
> --------------------------------------------------------------
> ---------
>    
>   @@ -133,6 +137,43 @@
>    Votes:
>        +1: Greg, Sascha, Ryan, Jeff
>    
>   +
>   +    Commit access is granted to committers of other open 
> source projects
>   +    depending on those projects' guidelines.  For other 
> developers, apr follows
>   +    the general guidelines of the Apache new-httpd 
> project.  Submissions 
>   +    of names for commit access to the pmc list should 
> include their status 
>   +    on any such projects they have contributed to, have 
> intefered with, been
>   +    granted or denied commit access to, or had commit 
> access revoked from.
>   +
>   +    Approval of commit access is generally automatically 
> granted to 
>   +    commiters of projects that use APR which already use 
> established
>   +    and reasonable commit guidelines.  These projects include:
>   +       The Apache new-httpd project.
>   +
>   +    Approval of commit access may be slower in coming when 
> the developer
>   +    has commit access to a more relaxed project.  While 
> APR does not rely
>   +    strictly to the new-httpd project guidelines, these 
> names should be 
>   +    floated for comment on the pmc list for 72 hours 
> before commit access 
>   +    is granted.  These projects include:
>   +       Subversion
>   +    
>   +    Regardless of their status on other open source 
> projects, if a developer
>   +    submits several reasonable patches that apply well and 
> follow the general 
>   +    guidelines, and that developer appears to "share the 
> goals" and "get the
>   +    process", then the pmc will vote to provide commit 
> access.  While new-httpd 
>   +    criteria may be useful, the apr project does not 
> enforce any specific time 
>   +    period as a condition for commit access.
>   +
>   +    The PMC always reserves the right to suspend commit 
> privileges, by a simple
>   +    majority vote of the PMC.  This especially applies if 
> other APR members end 
>   +    up spending too much time dealing with problematic 
> commits.  While warnings
>   +    are good first steps, commit privileges may be revoked 
> without any notice.
>   +    A veto, with techinical justification, is sufficient 
> to deny granting commit
>   +    access in the first place.
>   +
>   +Votes:
>   +    +1: OtherBill
>   +
>    
> --------------------------------------------------------------
> ---------
>    
>    PMC Membership
>   @@ -149,7 +190,7 @@
>        longevity in dev/doc/admin ability and interest in the 
> APR project.
>    
>    Votes:
>   -    +1: Greg, Sascha, Ryan, Jeff
>   +    +1: Greg, Sascha, Ryan, Jeff, OtherBill
>    
>    
>    (*) the initial group was formed by fiat; no chicken-an-egg exists
>   @@ -164,6 +205,11 @@
>         mechanism by which we can become more formal in the future,
>         should that be necessary. :-) ] 
>    
>   +   [ OtherBill: removed the word "veto", unless it will 
> mean just that,
>   +     the -1 described below is sufficient.  I believe veto 
> != -1, I may
>   +     be against something with no justification 
> whatsoever.  Let's have
>   +     a choice on our votes to vote against.  Added 'veto 
> as a vote'.]
>   +
>    Whenever possible, decisions are made by consensus.  Consensus is
>    reached when both the following conditions are met: a committer
>    indicates that consensus has been reached, and no committer claims
>   @@ -180,7 +226,7 @@
>    
>       +1   : Yes, agree that the choice should be performed.
>       +/-0 : Abstain, no opinion, happy to let others decide this one.
>   -   -1   : No, veto, I am against this choice being performed.
>   +   -1   : No, I am against this choice being performed.
>    
>    Choices receiving positive totals may be performed.
>    
>   @@ -195,11 +241,20 @@
>    at least half of the committers voting, for the change to take
>    effect.
>    
>   +Veto as a vote:
>   +
>   +A voter explicitly stating that they veto the decision, providing a
>   +technical justification of their veto, and with another in 
> agreement 
>   +that the technical issue exists, is sufficient to table a 
> vote until
>   +the technical issue is addressed, and the vetoer or those 
> who agreed
>   +concur that the the issue is addressed.
>   +
>    Voting Procedure Technicalities:
>    
>    Votes are tallied in the STATUS file, adjacent to the action item
>    under vote.  All votes must be either sent to the mailing list or
>    added directly to the STATUS file entry for that action item.
>   +
>    
>    
> --------------------------------------------------------------
> ---------
>    
>   
>   
>   
> 

Mime
View raw message