From owner-svn-ports-head@freebsd.org  Sun Mar 10 21:40:07 2019
Return-Path: <owner-svn-ports-head@freebsd.org>
Delivered-To: svn-ports-head@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3C2141542D21;
 Sun, 10 Mar 2019 21:40:07 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2610:1c1:1:6074::16:84])
 (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
 server-signature RSA-PSS (4096 bits)
 client-signature RSA-PSS (4096 bits) client-digest SHA256)
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id D593C8F8A2;
 Sun, 10 Mar 2019 21:40:06 +0000 (UTC)
 (envelope-from jbeich@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1354)
 id AF5D7114; Sun, 10 Mar 2019 21:40:06 +0000 (UTC)
From: Jan Beich <jbeich@FreeBSD.org>
To: Niclas Zeising <zeising@FreeBSD.org>
Cc: ports-committers@freebsd.org, svn-ports-all@freebsd.org,
 svn-ports-head@freebsd.org
Subject: Re: svn commit: r495284 - in head/devel: valgrind valgrind-devel
References: <201903101129.x2ABTrCp050295@repo.freebsd.org>
Date: Sun, 10 Mar 2019 22:40:03 +0100
In-Reply-To: <201903101129.x2ABTrCp050295@repo.freebsd.org> (Niclas Zeising's
 message of "Sun, 10 Mar 2019 11:29:53 +0000 (UTC)")
Message-ID: <4l8a-csss-wny@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain
X-Rspamd-Queue-Id: D593C8F8A2
X-Spamd-Bar: --
Authentication-Results: mx1.freebsd.org
X-Spamd-Result: default: False [-2.88 / 15.00];
 local_wl_from(0.00)[freebsd.org];
 NEURAL_HAM_SHORT(-0.90)[-0.901,0];
 ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US];
 NEURAL_HAM_MEDIUM(-0.98)[-0.982,0];
 NEURAL_HAM_LONG(-1.00)[-0.997,0]
X-BeenThere: svn-ports-head@freebsd.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SVN commit messages for the ports tree for head
 <svn-ports-head.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/svn-ports-head>, 
 <mailto:svn-ports-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-ports-head/>
List-Post: <mailto:svn-ports-head@freebsd.org>
List-Help: <mailto:svn-ports-head-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/svn-ports-head>,
 <mailto:svn-ports-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Mar 2019 21:40:07 -0000

Niclas Zeising <zeising@FreeBSD.org> writes:

> Author: zeising
> Date: Sun Mar 10 11:29:53 2019
> New Revision: 495284
> URL: https://svnweb.freebsd.org/changeset/ports/495284
>
> Log:
>   Grab valgrind ports
>   
>   Grab valgrind ports, I know people outside the project who are interested in
>   this.  Grab it in the interim.
>   
>   If you are interested in helping out, please let me know!

Are you planning to maintain it in the meantime? I'm asking because the
rationale looks like maintainer squatting or favoritism. In the past we
had a similar issue with placeholder maintainer of ports-mgmt/portmaster
which confused users about the actual status. The general issue stemmed
from some committers arguing against handing out handing out maintainership
to people who've never submitted a patch (to the port in question).
That got partially addressed by portmgr@ making a policy of revoking
maintainership after 3 months of no feedback or 3 consecutive timeouts.