RE: [PEAR-DEV] RFC - Rules on 'Rules and Guideline Proposals.
| From: | Richard York | Date: | Tue, 09 Mar 2004 23:30:22 +0000 |
| Subject: | RE: [PEAR-DEV] RFC - Rules on 'Rules and Guideline Proposals. | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-26240@lists.php.net to get a copy of this message | ||
> o BIG warning messages on the bottom of package comments
> should say 'DO NOT EVER RESPOND TO THIS COMMENT - update
> your package, package description or RFC to reflect these
> opinions'
> o reply to address on comments messages should be
> idiot@localhost!!
Just thinking aloud here.. but wouldn't it be fantastic if those who reply
to PEPr comments by replying to the email would get those comments
automatically added to the proposal on PEPr via the mailing list manager?
In which case those who are annoyed by people who reply to PEPr comments by
email would be satisfied and the process of commenting would be somewhat
simplified. Obviously not everyone who subscribes to the PEAR-DEV list is
going to know that you aren't supposed to reply to comments via email and
should use the PEPr interface itself instead. Well they'd certainly know if
they saw 'idiot@localhost' and other such warnings. I just think that
instead of inventing rules in this manner, that such things could be
corrected with code (as much as is possible anyway).
Well that's just my .02 anyway.
Regards,
Richard York