From owner-freebsd-ports@FreeBSD.ORG  Wed Apr 13 20:17:54 2005
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 96FC916A4CE
	for <ports@freebsd.org>; Wed, 13 Apr 2005 20:17:54 +0000 (GMT)
Received: from mail.soaustin.net (mail.soaustin.net [207.200.4.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 61A1343D54
	for <ports@freebsd.org>; Wed, 13 Apr 2005 20:17:54 +0000 (GMT)
	(envelope-from linimon@lonesome.com)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 01E3A149CA; Wed, 13 Apr 2005 15:17:53 -0500 (CDT)
Date: Wed, 13 Apr 2005 15:17:53 -0500 (CDT)
From: Mark Linimon <linimon@lonesome.com>
X-X-Sender: linimon@pancho
To: Marc Rassbach <bsdwrangler@gmail.com>
In-Reply-To: <26788d7e050413101411dfde32@mail.gmail.com>
Message-ID: <Pine.LNX.4.44.0504131515490.21966-100000@pancho>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: ports@freebsd.org
Subject: Re: Pointer to 'how to become a port maintainer'? OR a 'mentor'?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Apr 2005 20:17:54 -0000

On Wed, 13 Apr 2005, Marc Rassbach wrote:

> I looked thru the handbook and didn't spot 'this is what ya do' - more
> 'this is what ya do to update//take over an abandoned ports'.

A draft that adds more information about the rights and responsibilities
of ports maintainers is currently under review by the Ports Management
Team (two separate drafts, actually).  To some degree this is already
covered in the Porter's Handbook, but this will make it more explicit.

mcl