From owner-freebsd-ports@freebsd.org  Mon Feb  6 11:40:30 2017
Return-Path: <owner-freebsd-ports@freebsd.org>
Delivered-To: freebsd-ports@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id E5D7CCD3567
 for <freebsd-ports@mailman.ysv.freebsd.org>;
 Mon,  6 Feb 2017 11:40:30 +0000 (UTC) (envelope-from jhs@berklix.com)
Received: from land.berklix.org (land.berklix.org [144.76.10.75])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 868C01560
 for <freebsd-ports@FreeBSD.org>; Mon,  6 Feb 2017 11:40:30 +0000 (UTC)
 (envelope-from jhs@berklix.com)
Received: from mart.js.berklix.net (pD9FE9781.dip0.t-ipconnect.de
 [217.254.151.129]) (authenticated bits=128)
 by land.berklix.org (8.15.2/8.15.2) with ESMTPA id v16BeUAm017327;
 Mon, 6 Feb 2017 11:40:30 GMT (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (fire.js.berklix.net [192.168.91.41])
 by mart.js.berklix.net (8.14.3/8.14.3) with ESMTP id v16BeLAN020465;
 Mon, 6 Feb 2017 12:40:21 +0100 (CET) (envelope-from jhs@berklix.com)
Received: from fire.js.berklix.net (localhost [127.0.0.1])
 by fire.js.berklix.net (8.14.7/8.14.7) with ESMTP id v16Bdv6j015090;
 Mon, 6 Feb 2017 12:40:09 +0100 (CET) (envelope-from jhs@berklix.com)
Message-Id: <201702061140.v16Bdv6j015090@fire.js.berklix.net>
To: Kurt Jaeger <lists@opsec.eu>
cc: Jochen Neumeister <joneum@bsdproject.de>,
 "freebsd-ports@freebsd.org" <freebsd-ports@FreeBSD.org>
Subject: Re: No reaction - what can I do?
From: "Julian H. Stacey" <jhs@berklix.com>
Organization: http://berklix.eu BSD Unix Linux Consultants, Munich Germany
User-agent: EXMH on FreeBSD http://berklix.eu/free/
X-From: http://www.berklix.eu/~jhs/
In-reply-to: Your message "Mon, 06 Feb 2017 11:55:39 +0100."
 <20170206105539.GI13006@home.opsec.eu>
Date: Mon, 06 Feb 2017 12:39:57 +0100
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
 <mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2017 11:40:31 -0000

Hi, Reference:
> From:		Kurt Jaeger <lists@opsec.eu>
> Date:		Mon, 6 Feb 2017 11:55:39 +0100

Kurt Jaeger wrote:
> Hi!
> 
> > > Is it normal that maintainers / committer will not respond?
> [...]
> > https://www.freebsd.org/portmgr/policies_contributors.html
> >   "The time limit for a maintainer to respond to a PR is two weeks.
> >   After that period, ....."
> 
> The problem in this case is that nobody suggested a solution, so
> what does the timeout help ?

Purpose of Timeouts is to remove a Maintainer that is not responding
&/or maintaining. Timeout works in my experience, eg I've both been
removed from port[s] when not having time to respond & maintain, &
on other ports after MAINTAINER= was zeroed out, I've been invited
to become Maintainer, which put pressure on me spend more time
researching & finding a solution. Zeroing out a Maintainer invites
entire ports user base to volunteer for that port, & saves a
Maintainer being further pestered for something they simply have
no further time to maintain, & saves Ports Mgr & users writing enquiries
for all eternity.

> 
> -- 
> pi@opsec.eu            +49 171 3101372                         3 years to go !
> 


Cheers,
Julian
-- 
Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich
 Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable.
 http://berklix.eu/brexit/#stolen_votes