On Thu, Dec 03 2009, Piotr Ożarowski wrote:
> 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?
Policy decisions, even drafting policy, does not have to be held
in deep dark secret; indeed, policy creation in Debian has usually
been held right out in the open. Going away and crafting what you
think is going to be a finished policy and expecting wide adoption of
the fait accompli is likely to have surprising outcomes for you.
manoj
--
Love the sea? I dote upon it -- from the beach.
Manoj Srivastava <sriva...@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
