From owner-freebsd-ports-bugs@freebsd.org  Wed Aug  5 13:56:09 2015
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@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 0B4639B4F32
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Wed,  5 Aug 2015 13:56:09 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (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 CC4BA11B8
 for <freebsd-ports-bugs@FreeBSD.org>; Wed,  5 Aug 2015 13:56:08 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t75Du8wP011039
 for <freebsd-ports-bugs@FreeBSD.org>; Wed, 5 Aug 2015 13:56:08 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 201035] Accept more than one maintainer for ports (and issues
 in bugzilla)
Date: Wed, 05 Aug 2015 13:56:08 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Ports Framework
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: feature
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: koobs@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: portmgr@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: component short_desc keywords version product cc
 assigned_to
Message-ID: <bug-201035-13-7DHfWxWLEf@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201035-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-201035-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Aug 2015 13:56:09 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201035

Kubilay Kocak <koobs@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|Bug Tracker                 |Ports Framework
            Summary|Accept more than one        |Accept more than one
                   |maintainer for PR and       |maintainer for ports (and
                   |ports.                      |issues in bugzilla)
           Keywords|                            |feature
            Version|unspecified                 |Latest
            Product|Services                    |Ports & Packages
                 CC|                            |freebsd-ports-bugs@FreeBSD.
                   |                            |org, koobs@FreeBSD.org
           Assignee|bugmeister@FreeBSD.org      |portmgr@FreeBSD.org

--- Comment #1 from Kubilay Kocak <koobs@FreeBSD.org> ---
This is a feature request, and will require some initial and further thought
and discussion about:

 * how it could/should be implemented
 * what the benefits and risks might be
 * potential impact on consumers (users and systems) that utilize MAINTAINER in
its current form.

This is definitely within the remit of the Ports Management team, thus will be
re-classified/assigned accordingly.

I would strongly recommend/suggest you create (along with feedback from others)
a detailed proposal summary in Gist or Wiki page format, that goes over the
details.

A format similar to a Python Enhancement Proposal (PEP) would be a good
starting point.

-- 
You are receiving this mail because:
You are on the CC list for the bug.