public inbox for gentoo-python@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dirkjan Ochtman <djc@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: [gentoo-python] Adding new packages
Date: Thu, 21 Jun 2012 13:47:31 +0200	[thread overview]
Message-ID: <CAKmKYaAW64umYzLK7ENFQB5iKoM7r4Kx8bQ9gLkL4VyZE==pPA@mail.gmail.com> (raw)

I was wondering: what do you all think about putting new python
packages in the tree?

The idea here is IMO we shouldn't add more packages to the tree than
we can manage. We have a pretty big open bug list and enough version
bumps to go around as it is. If we move packages into the tree just
because a single user asked for it, I worry it might not be a good
trade-off: we're more or less committed to maintaining it forever, and
we do this at the cost of maintenance for other packages.

Maybe the answer is I just shouldn't worry so much, or maybe we should
try have some informal criteria for when we allow a package to go into
the tree? For instance, if one of the python devs is using a package
himself, I have no qualm about letting him add it to the tree, since
he'll probably also be able to do some maintenance. If there are 10
guys asking for it in Bugzilla, we should also include it. If we have
something in the tree already that starts depending on it, that also
probably is good enough (although this may not be always true, for
optional dependencies). But for the other cases, should we be
conservative about adding packages or just add away whenever we feel
like it?

Cheers,

Dirkjan



                 reply	other threads:[~2012-06-21 11:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAKmKYaAW64umYzLK7ENFQB5iKoM7r4Kx8bQ9gLkL4VyZE==pPA@mail.gmail.com' \
    --to=djc@gentoo.org \
    --cc=gentoo-python@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox