From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1Shfrk-0003og-Ef for garchives@archives.gentoo.org; Thu, 21 Jun 2012 11:48:00 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id EA7E1E0A01; Thu, 21 Jun 2012 11:47:56 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 4386DE0A01 for ; Thu, 21 Jun 2012 11:47:56 +0000 (UTC) Received: from mail-wg0-f41.google.com (mail-wg0-f41.google.com [74.125.82.41]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: djc) by smtp.gentoo.org (Postfix) with ESMTPSA id 48C391B400F for ; Thu, 21 Jun 2012 11:47:55 +0000 (UTC) Received: by wgbds1 with SMTP id ds1so4409989wgb.4 for ; Thu, 21 Jun 2012 04:47:52 -0700 (PDT) Received: by 10.216.206.159 with SMTP id l31mr14168650weo.2.1340279272729; Thu, 21 Jun 2012 04:47:52 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org MIME-Version: 1.0 Received: by 10.216.168.82 with HTTP; Thu, 21 Jun 2012 04:47:31 -0700 (PDT) From: Dirkjan Ochtman Date: Thu, 21 Jun 2012 13:47:31 +0200 Message-ID: Subject: [gentoo-python] Adding new packages To: gentoo-python@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 36fe0c78-a6cc-494f-9fc3-08ea36a2c42c X-Archives-Hash: 4e21f831966d8f650c6e567180e9cf10 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