From owner-freebsd-ports@FreeBSD.ORG Mon Dec 13 17:01:52 2004 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 BB36716A4CE for ; Mon, 13 Dec 2004 17:01:52 +0000 (GMT) Received: from smtp.unsam.edu.ar (smtp.unsam.edu.ar [170.210.48.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id DCBE643D4C for ; Mon, 13 Dec 2004 17:01:47 +0000 (GMT) (envelope-from fernan@iib.unsam.edu.ar) Received: from pi.iib.unsam.edu.ar (pi.iib.unsam.edu.ar [192.168.10.11]) by smtp.unsam.edu.ar (8.12.6/8.12.6) with ESMTP id iBDHCd6X027465; Mon, 13 Dec 2004 14:12:40 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: from pi.iib.unsam.edu.ar (localhost.iib.unsam.edu.ar [127.0.0.1]) by pi.iib.unsam.edu.ar (8.12.11/8.12.9) with ESMTP id iBDH1Qq9059622; Mon, 13 Dec 2004 14:01:26 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) Received: (from fernan@localhost) by pi.iib.unsam.edu.ar (8.12.11/8.12.11/Submit) id iBDH1Q5H059621; Mon, 13 Dec 2004 14:01:26 -0300 (ART) (envelope-from fernan@iib.unsam.edu.ar) X-Authentication-Warning: pi.iib.unsam.edu.ar: fernan set sender to fernan@iib.unsam.edu.ar using -f Date: Mon, 13 Dec 2004 14:01:26 -0300 From: Fernan Aguero To: Kris Kennaway Message-ID: <20041213170126.GC4121@iib.unsam.edu.ar> Mail-Followup-To: Kris Kennaway , ports@freebsd.org References: <20041212000009.GB86390@xor.obsecurity.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041212000009.GB86390@xor.obsecurity.org> User-Agent: Mutt/1.5.6i cc: ports@freebsd.org Subject: Re: "Being a port maintainer" document 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, 13 Dec 2004 17:01:52 -0000 +----[ Kris Kennaway (13.Dec.2004 10:04): | [snipped] | -- but we need | some form of document we can show them that lists the rights and | responsibilities of port maintainers, so they have an idea of what's | expected from them. The porters' handbook does a good job of | describing the details of constructing a port, but not the | higher-level aspects of being a port maintainer. I completely agree. | e.g. | | * Updating the port when a new version is released | | * Pushing local changes back upstream to the original authors | | * Fixing port errors reported by the package build cluster | | * Dealing with user support requests, at least by pointing them to the | upstream developers for cases where it's not clearly a FreeBSD | port-specific problem. | | * Evaluating PRs submitted against the port | | * Responding to change requests in a timely manner (2 weeks). | | * ... I would add a section on uses and costumes on the relationship between maintainers and committers. What mailing lists are read by committers? When is it OK to bug a committer personally? Is it OK to bug the same committer that worked on the same port on a previous PR? Do all committers work on any PR? Or perhaps they like to restrict themselves to a few areas or categories (perl, gnome, etc.) Perhaps this more for a FAQ ... in any case these are all questions that I've asked myself over time. If you've been reading a few freebsd mailing lists for some time, you get to know the answers. Some of these are flexible issues (every committer/maintainer would of course have their personal preferences), but I think a rough guide can be of much help to newbie maintainers. Fernan | | Can someone write up such a document? | | Kris | +----]