On Thu, 20 Sep 2007 18:02:56 +0200, Christian Perrier <[EMAIL PROTECTED]> said:
> Quoting Lars Wirzenius ([EMAIL PROTECTED]): >> I'd start with amending the Developers' Reference, then having a test >> added to lintian and linda, and after that announcing it on >> debian-devel-announce. Then next year, after everyone's had time to >> react and upload new packages, do a mass bug filing. > I'd probably add a changes to section 5.6 of the Policy (List of > fields) before adding a test to lintian and linda. > Then file a bug against *apt* packages and p.d.o to have them support > displaying info from that field, before or after the d-d-a > announcement. > I'm not sure whether to amend the DevRef first as it usually documents > "best practices"....which will probably become best practices once > enough people started using them. > So, maybe documenting the field in the Policy, first, would be the > best to do. > Then DevRef, then lintian/linda, the d-d-a announcement. Actually, policy is usually the last thing that you want to do, in the general case. Policy is usually stable (well, not quite as stable as it has been this year, but work seems to be easing up a trifle, so expect a policy release in a couple of weeks). But the idea is that policy documents mature practice, and only when it is deemed really required. Since so few packages do the Homepage thing, I would much rather see a working design, supported by apt and p.d.o, make any changes or tweaks as are needed; and _then_ we look at policy. If very few packages are using it still, you'll have to start with a MAY or suggests, anyway. Oh, if anyone has any ideas about the docbook template for policy rules, now is the time to send them in. I am planning on spending time on all the policy related proposals I talked about at debconf. manoj -- Murder is contrary to the laws of man and God. M-5 Computer, "The Ultimate Computer", stardate 4731.3 Manoj Srivastava <[EMAIL PROTECTED]> <http://www.debian.org/~srivasta/> 1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]