[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: First draft of review of policy must usage

On Wed, 25 Oct 2006 18:51:26 +0200, Luk Claes <luk@debian.org> said: 

> Joerg Jaspert wrote:
>> On 10818 March 1977, Luk Claes wrote:
>>> Can everyone please focus on the release and discuss things that
>>> don't help to release on December 4th at all till after that date?
>> No, the release is no reason to stop everything else.

> It was not meant that way at all. I just don't like that people
> start to discuss topics that are long overdue near release time...

        In a project this size, not all activities come to a dead end
 every couple of years for a few months. Consistent with releasing,
 activities geared towards improving the infrastructure, subsystems,
 and packages can and should still be on going.

        The reason I have initiated this at this point is that I was
 not aware that policy is perceived to be so far out of whack with the
 project processes that violations of MUST directives in policy are
 considered to be unrelated to bugs serious enough to warrant
 fixing -- and that policy directives linking ciolations to bug
 severities are now considered an unreported bug in policy itself.

        I realized that there never has been a comprehensive review
 of the MUST/SHOULD/MAY  dictums in policy, and also, policy has grown
 organically, since until recently there was no single cohesive
 editor -- the old piecemeal approach of any small group of developers
 just adding language for each policy change leads to a disjoint,
 incoherent document. It is about time we started looking at policy
 holistically.  That was the trigger.

        Also, consider the fact that we are all (for the most part),
 volunteers.  there a re number of demands on our time. Real life
 intervenes. Private and pet projects go hot or cold. the release
 process is just one such drain on our timel but there are others.
 For a process like a broad review of policy, where one needs to get
 the buy in and eye balls of a large group of developers, it is
 impossible to pick a time that is convenient for every one.

        Unlike Etch, there is no pressing directive that policy review
 be all done by Dec 4rth; we can and should take our time and do
 this _right_.  Correctness and completeness should be preferred over
 speed at this point.

"Can you program?"  "Well, I'm literate, if that's what you mean!"
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C

Reply to: