Re: Making sure that policy amendments don't die
Hi,
From the experiences we have had in tha last few months, I
have come to realize that there may be a better method of tracking
the progress of proposals in the BTS. (Note: these are proposed
procedures, not the ones we currently follow). I have tried to relate
all this to the stages in a proposals life
a) Pre discussion period, an idea is
floated, and kicked around and wishlist bug, titled [PROPOSAL]
polished for a bit
b) Formally seconded, and a time
table set for discussion (normally normal bug, titled [AMENDMENT yy/mm/dd]
10 days to a month)
c) End of discussion period.
i) Consensus: forwarded, titled [ACCEPTED yy/mm/dd]
ii) Stalled closed, titled [REJECTED]
d) edited into the policy doc closed
Should we keep the rejected proposals around in the BTS in
state fixed, so that one does not have to redo the old arguments over
again?
I hope this use of the BTS makes clearer distinctions between
the different statuses of proposals.
manoj
--
We must make the best of those ills which cannot be
avoided. Alexander Hamilton
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
Reply to: