From owner-freebsd-ports@FreeBSD.ORG Mon Nov 10 02:59:12 2003 Return-Path: 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 BC0AA16A4CE for ; Mon, 10 Nov 2003 02:59:12 -0800 (PST) Received: from bloodwood.hunterlink.net.au (mail.hunterlink.net.au [203.12.144.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFFE743FAF for ; Mon, 10 Nov 2003 02:59:10 -0800 (PST) (envelope-from boris@brooknet.com.au) Received: from [202.7.67.78] (as1-p78.mait.hunterlink.net.au [202.7.67.78]) hAAAwnAF025970 for ; Mon, 10 Nov 2003 21:58:59 +1100 From: Sam Lawrance To: ports@freebsd.org Content-Type: text/plain Message-Id: <1068458390.38101.19.camel@dirk.no.domain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Mon, 10 Nov 2003 20:59:51 +1100 Content-Transfer-Encoding: 7bit Subject: Ability for maintainers to update own ports X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Nov 2003 10:59:12 -0000 Greetings all, Neglecting implementation details, has anybody considered the possibility of allowing MAINTAINERs who don't have commit privileges to somehow commit updates to ports they maintain? Where do people see problems lie with such an idea? (Eg. keeping the tree sane, controlling access, vetting changes etc) I feel that a well thought out and implemented system could be highly beneficial to everyone, reducing the number of ports PRs and letting port updates flow through a little faster. Pick it to bits, if there are solutions I want to find them :) -Sam.