Right now we're working on updating the Debian Python Policy. Once we'll be happy with the first set of patches, we'll send them to debian-python mailing list. I don't see a reason to make it public right now as it's simply not ready. Does it really matter that I'm not preparing it alone? If I would work on it alone would I still be obligated to make everything public? /me wonders if other Debian cabals do not realize they're a cabal as well ;-) -- Piotr Ożarowski Debian GNU/Linux Developer www.ozarowski.pl www.griffith.cc www.debian.org GPG Fingerprint: 1D2F A898 58DA AF62 1786 2DF7 AEF6 F1A2 A745 7645
Attachment:
signature.asc
Description: Digital signature