From owner-freebsd-python@FreeBSD.ORG Thu Jan 8 17:15:14 2004 Return-Path: Delivered-To: freebsd-python@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 949) id 34CE716A4D0; Thu, 8 Jan 2004 17:15:14 -0800 (PST) Date: Fri, 9 Jan 2004 01:15:14 +0000 From: Hye-Shik Chang To: Mark Linimon Message-ID: <20040109011514.GA11169@hub.freebsd.org> References: <20040109002854.GA1667@k7.mavetju> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: ports@FreeBSD.org cc: Edwin Groothuis cc: python@FreeBSD.org Subject: Re: New mailing list: freebsd-python X-BeenThere: freebsd-python@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD-specific Python issues List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Jan 2004 01:15:14 -0000 On Thu, Jan 08, 2004 at 06:41:29PM -0600, Mark Linimon wrote: > > Can we change the owner of a PR to python now just like the java@ > > and gnome@ PRs and lists? > > Recently when the perl@ mailing list was created, there was discussion > about assigning all the perl ports to it. I objected at that time, > saying that there was a canonical name for "unmaintained" and that > was "ports@FreeBSD.org". I think the consensus was that only the > critical (for some definition of critical) PRs would be so assigned. > > My own research shows me that PRs assigned to kde, gnome, emulation, > and phoenix, tend to rot. The java folks are a little more focussed > and thus tend to be better. > I will not assign MAINTAINER of python ports to python@freebsd.org yet, because python ports are simple enough to maintain by myself. But I think assigning PR to python@ is okay. Any other committers interested in python will be able to track them easily by that and python-related port maintainers will be able to test co-operation between their ports before it's committed. Hye-Shik