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

Alan Knowles wrote:

Ok. Final Draft (hopefully)- speak now or forever hold your peace... Title: RFC - Rules on 'Rules and Guideline Proposals. ------------------------------------------------------ Author: alan at akbkhome dot com Revision: 2 Status: Active Due to recent events in the way that regulations have been proposed -the following is put for comment on the future method for introducing new standards, rules, conventions, recommendations or guidelines into the pear community.

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

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

I see one problem here. Since people will end up only criticizing certain points it will not really be possible for people to easily express their approval of a given point, or their disapproval of a given comment on the RFC. This become obvious to me when I saw the recent comments about this point being to strick in trying to prevent flamewars. I think this point is vital in this RFC, since it defines a flame-non-friendly workflow: author rfc publishing others reading rfc others sending comments author reading comments author updating rfc with comments others reading how their comments have been included in the update ... regards, Lukas Smith smith@backendmedia.com _______________________________ BackendMedia www.backendmedia.com berlin@backendmedia.com Linn Zwoch Smith GbR Pariser Str. 44 D-10707 Berlin Tel +49 30 83 22 50 00 Fax +49 30 83 22 50 07