Re: RFC - Rules on 'Rules and Guideline Proposals.

Hi Alan, This looks good, with only one major issue left unaddressed, please add this first bullet point: * initial drafts of RFCs may be developed in private or in small

    groups.  Once the RFC reaches a point nearing maturity, it should
    be made public for comment.  Poorly thought-out RFCs should not be
    made public.

Greg Alan Knowles wrote:

The Proposed Solution. ---------------------- * All RFC's should be proposed using the PEPR system (and hence cc'd

     to pear-dev)

* Anyone may comment on the RFC using the PEPR system (or by

     emailing the author directly)

* NOBODY SHOULD RESPOND TO COMMENTS ON THE RFC (including the

     author) - repeated abuse may result in being unsubscribed from
     pear-dev for 1 week. (the only response an author may make is to
     update the RFC)

* The RFC Author should update the RFC based on the comments

     recieved to represent the opinions in the document.

* RFC's should take the form of

         o Introduction
         o The Issues
         o The Proposed  Solution
         o After it has been proposed - a summary of the opinions on
           the RFC (if they are not represent in the updated 'issues')
         o Actions required if accepted.

* RFC's may under go any number of revisions, and put to vote

     (normally after a new revison of the RFC has been issued via PEPR,
     and no comments where added.)