Hi, Lars Wirzenius wrote:
> After the policy team takes over maintenance of the DEP5 spec, > you can use the policy process to suggest changes to it. The DEP5 spec is already in the policy repo. Is there any reason not to move to that way of working now (which does not imply anything about when the Format header changes or the next version of policy is released)? > If Steve, as a DEP5 driver, can build consensus that other changes > should happen now, rather than after policy team adoption, then > very well, I do not oppose that, but I don't think it is a good > idea, and I will not work for it. This points to a potential reason --- that maybe there are changes that would be easier to carry out through the DEP process than through policy bugs. But I am skeptical --- it's pretty easy to get a couple of seconds on a good patch. :) In other words: Charles, if you file a separate bug for your change, I'll be happy to consider it and give any advice I can think of (which could result in the document changing ASAP or once the document is adopted by the policy team, depending on the answers to the above questions). -- To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110829234858.ga17...@elie.gateway.2wire.net
