From owner-freebsd-python@FreeBSD.ORG Wed Apr 18 10:17:49 2007 Return-Path: X-Original-To: freebsd-python@freebsd.org Delivered-To: freebsd-python@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B6E2016A401 for ; Wed, 18 Apr 2007 10:17:49 +0000 (UTC) (envelope-from mail@sysfault.org) Received: from smtprelay07.ispgateway.de (smtprelay07.ispgateway.de [80.67.29.7]) by mx1.freebsd.org (Postfix) with ESMTP id 1FB4B13C484 for ; Wed, 18 Apr 2007 10:17:48 +0000 (UTC) (envelope-from mail@sysfault.org) Received: (qmail 4938 invoked from network); 18 Apr 2007 09:51:08 -0000 Received: from unknown (HELO medusa.sysfault.org) (936934@[81.14.191.160]) (envelope-sender ) by smtprelay07.ispgateway.de (qmail-ldap-1.03) with AES256-SHA encrypted SMTP for ; 18 Apr 2007 09:51:08 -0000 Received: from localhost ([127.0.0.1] helo=medusa.sysfault.org) by medusa.sysfault.org with esmtp (Exim 4.66 (FreeBSD)) (envelope-from ) id 1He6ot-0008Ck-Tk for freebsd-python@freebsd.org; Wed, 18 Apr 2007 11:51:24 +0200 Received: (from marcus@localhost) by medusa.sysfault.org (8.13.1/8.13.1/Submit) id l3I9pN82031541 for freebsd-python@freebsd.org; Wed, 18 Apr 2007 11:51:23 +0200 (CEST) (envelope-from marcus) Date: Wed, 18 Apr 2007 11:51:22 +0200 From: Marcus von Appen To: freebsd-python@freebsd.org Message-ID: <20070418095122.GA992@medusa.sysfault.org> Mail-Followup-To: freebsd-python@freebsd.org References: <20070417221751.DA4AA3A073@cherenkov.geekfire.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GvXjxJ+pjyke8COw" Content-Disposition: inline In-Reply-To: <20070417221751.DA4AA3A073@cherenkov.geekfire.com> User-Agent: Mutt/1.5.15 (2007-04-06) X-Spam-Score: -4.4 (----) Subject: Re: python@ as ports maintainer X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Marcus von Appen List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Apr 2007 10:17:49 -0000 --GvXjxJ+pjyke8COw Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On, Wed Apr 18, 2007, Alexander Botero-Lowry wrote: > Hi everyone, >=20 > I've been seeing a trend lately that I find a bit disturbing and I just w= anted > to lay down the official python@ policy on this issue. The trend I'm refe= rring > to is the setting of python@ on python consumer ports without first discu= ssing > it with the python@ list. Early on, perky@ and I decided we didn't want p= ython@ > to be a dumping ground for any python consumer and that we wanted to care= fully > think through the ports that were directly maintained by the group with t= he out > look of providing better QA for a small subset of important and critical = ports > related to or used heavily by Python consumers. That being said, we feel = that > if every python consumer in ports is owned by python@ we can not sufficen= tly > provide support to maintain and keep them up to date. What is good for a = small > number of ports becomes unmanigable at a larger number, just like ports > maintained by ports@ though more accessible to committers tend to see less > updates and fixes simply because there are just so many of them. Is there some list if non-important ports, which you would like to hand over to some other maintainer so you can focus on the main tasks for python? If so, I'd be pleased to take over the one or other. Regards Marcus --GvXjxJ+pjyke8COw Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQFGJeoao/JpszXavhwRAiF1AJwOR3dtg3ZdVutUyzlr4V+WL9PWAQCfd3ho 41nRZpFjBv08nDaKShOCcc0= =8OKU -----END PGP SIGNATURE----- --GvXjxJ+pjyke8COw--