Re: PROPOSAL: A mechanism for updating Debian Policy documents
Hi,
>>"Buddha" == Buddha Buck <bmbuck@acsu.buffalo.edu> writes:
Buddha> When August 22nd rolls around, and a consensus has been
Buddha> reached (which it looks like it will), who will make the necessary
Buddha> changes (such as eliminating the "enacting language", renumbering the
Buddha> sections, rewriting "I propose..."-type sentences to exact statements
Buddha> of policy, etc)? The policy maintainers? In direct contradiction to
Buddha> the policy of this proposal?
Right now, I do not feel comfortable amending policy with this
proposal. So, when the date comes around, and we have agreed to this
process, I, as in individual developer, shall formally send in an
amendment to policy. When I move for the amedment to policy
documents, rest assured that the language of the aforementioned
amendment shall be precise.
This proposal does not change policy. One of the first things
to be done, of this proposal passes, shall be the policy change that
would codify it.
The fact that I may be a policy maintainer does in no way
lessen my ability, as a Debian developer, to send in a proposal to
amend policy.
Buddha> I would much rather have, in addition to the proposal that Manoj has
Buddha> already made, a section such as:
Buddha> 4. Formal Amendment
I would rather not. I want to have an proposal to amend policy
pass, and then using the process formally change policy.
As far as policy is concerned, we should never be in a
hurry. Passing this proposal can allow us fix overdue flaws in policy
-- while we debate the formal amendment.
I would also like us all to have a taste of how this new
process works before we write it into stone.
manoj
--
He that loses hope may part with anything. -- Congreve
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: