From owner-freebsd-ports@FreeBSD.ORG  Wed Nov 18 08:26:53 2009
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 8F316106566C
	for <ports@freebsd.org>; Wed, 18 Nov 2009 08:26:53 +0000 (UTC)
	(envelope-from linimon@lonesome.com)
Received: from mail.soaustin.net (lefty.soaustin.net [66.135.55.46])
	by mx1.freebsd.org (Postfix) with ESMTP id 723238FC0C
	for <ports@freebsd.org>; Wed, 18 Nov 2009 08:26:53 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
	id 0BD738C065; Wed, 18 Nov 2009 02:26:53 -0600 (CST)
Date: Wed, 18 Nov 2009 02:26:53 -0600
From: Mark Linimon <linimon@lonesome.com>
To: Peter Jeremy <peterjeremy@acm.org>
Message-ID: <20091118082653.GC6300@lonesome.com>
References: <4B02C70F.4050906@point-group.ru>
	<20091117175204.GA12873@server.vk2pj.dyndns.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20091117175204.GA12873@server.vk2pj.dyndns.org>
User-Agent: Mutt/1.5.18 (2008-05-17)
Cc: ports@freebsd.org, Yuri Gorchakov <yuri.gorchakov@point-group.ru>
Subject: Re: ossec port is outdated and no maintainer replies
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
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, 18 Nov 2009 08:26:53 -0000

On Wed, Nov 18, 2009 at 04:52:04AM +1100, Peter Jeremy wrote:
> It is the maintainer's responsibility to update the port.  If the
> existing maintainer has vanished, you can take over maintainership by
> submitting a PR that updates the port and changes the MAINTAINER line.
> If the ports team are unable to contact the maintainer after a suitable
> period then your PR will be committed and you will become the maintainer.

This isn't quite accurate.

If you submit a PR, and the maintainer does not respond within 2 weeks,
it is eligible for any ports committer to commit.

A maintainer who does not respond to PRs or email for 3 months can be
reset by any committer.  However, I am often the person that does it,
because I look for "committed via: maintainer-timeout" in commit messages
and keep track of them.

The periods were picked to be "give them enough time to be on vacation"
and "let enough time have elapsed to show they are no longer interested."

mcl