Re: Proposal Announce Processes
I'd say announcing it to the "general" developer public would be a courtesy if
nothing else. There might be an issue that someone feels important enough (or
important enough to his packages) that he'd want to participate but not, in
general, be a part of ALL policy discussions.
On 01-Sep-98 Manoj Srivastava wrote:
> I was under the impression that debian-devel-announce was for
> more weithier matters than whatever happens to sieze the policy
> groups fancy for the day ;-) (I know these are loaded words).
>
> Really, I think debian-devel-announce should be reserved for
> the constitutional general resolutions and larger issues; the policy
> amendment guidelines are for things we do not expect to be
> contentious, and there is no need to call in the troops. Even the
> debian-devel announcement is a courtesy.
>
> If it needs a debian-devel-announce announcement, it should
> be handled in a general resolution. The guidelines are fr the
> internal workings of the policy list; and the policy list should be
> able to handle the day-to-day affairs without needing to impinge on
> the general consciousness.
>
> This issue did not come up in the discussion we had on the
> proposal (note that the proposal followed its guidelines fairly
> well); so I though we all agreed.
>
> However, I am willing to be persuaded.
=========================================================================
* http://benham.net/index.html *
* -------------------- * -----BEGIN GEEK CODE BLOCK----- ---------------*
* Darren Benham * Version: 3.1 *
* <gecko@benham.net> * GCS d+(-) s:+ a29 C++$ UL++>++++ P+++$ L++>++++*
* * E? W+++$ N+(-) o? K- w+++$(--) O M-- V- PS-- *
* Debian Developer * PE++ Y++ PGP++ t+ 5 X R+ !tv b++++ DI+++ D++ *
* <gecko@debian.org> * G++>G+++ e h+ r* y+ *
* -------------------- * ------END GEEK CODE BLOCK------ ---------------*
=========================================================================
Reply to: