From owner-svn-doc-all@FreeBSD.ORG Fri Jul 4 16:47:12 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CBC5F21C; Fri, 4 Jul 2014 16:47:12 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (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 B823E2C02; Fri, 4 Jul 2014 16:47:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s64GlCT2055365; Fri, 4 Jul 2014 16:47:12 GMT (envelope-from mat@svn.freebsd.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s64GlCsu055364; Fri, 4 Jul 2014 16:47:12 GMT (envelope-from mat@svn.freebsd.org) Message-Id: <201407041647.s64GlCsu055364@svn.freebsd.org> From: Mathieu Arnold Date: Fri, 4 Jul 2014 16:47:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45207 - head/en_US.ISO8859-1/books/porters-handbook/makefiles X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jul 2014 16:47:12 -0000 Author: mat (ports committer) Date: Fri Jul 4 16:47:12 2014 New Revision: 45207 URL: http://svnweb.freebsd.org/changeset/doc/45207 Log: Add portmgr's blanket approval, and update what being a maintainer means. PH: D342 Reviewed by: wblock, swills, erwin... Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Fri Jul 4 11:38:09 2014 (r45206) +++ head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Fri Jul 4 16:47:12 2014 (r45207) @@ -2719,21 +2719,66 @@ ALWAYS_KEEP_DISTFILES= yes :-) - Note that only a single address without the comment part is + Only a single address without the comment part is allowed as a MAINTAINER value. The format - used should be user@hostname.domain. Please - do not include any descriptive text such as your real name in - this entry—that merely confuses - bsd.port.mk. + used is user@hostname.domain. Please + do not include any descriptive text such as a real name in + this entry. That merely confuses the Ports infrastructure + and most tools using it. The maintainer is responsible for keeping the port up to - date, and ensuring the port works correctly. For a detailed + date and making sure that it works correctly. For a detailed description of the responsibilities of a port maintainer, refer - to the The - challenge for port maintainers section. + challenge for port maintainers. - Changes to the port will be sent to the maintainer of a port + + A maintainer volunteers to keep a port in good working + order. Maintainers have the primary responsibility for their + ports, but not exclusive ownership. Ports exist for the + benefit of the community and, in reality, belong to the + community. What this means is that people other than the + maintainer can make changes to a port. Large changes to the + Ports Collection might require changes to many ports. The + &os; Ports Management Team or members of other teams might + modify ports to fix dependency issues or other problems, like + a version bump for a shared library update. + + Some types of fixes have blanket approval + from the &a.portmgr;, allowing any committer to fix those + categories of problems on any port. These fixes do not need + approval from the maintainer. Blanket approval does not apply + to ports that are maintained by teams like autotools@FreeBSD.org, x11@FreeBSD.org, gnome@FreeBSD.org, or kde@FreeBSD.org. These teams use + external repositories and can have work that would conflict + with changes that would normally fall under blanket + approval. + + Blanket approval for most ports applies to these types of + fixes: + + + + Most infrastructure changes to a port (that is, + modernizing, but not changing the functionality). For + example, converting to staging, + USE_GMAKE to + USES=gmake, the new + LIB_DEPENDS format... + + + + Trivial and tested build + fixes. + + + + + Other changes to the port will be sent to the maintainer for review and approval before being committed. If the maintainer does not respond to an update request after two weeks (excluding major public holidays), then that is considered a @@ -2748,7 +2793,8 @@ ALWAYS_KEEP_DISTFILES= yes We reserve the right to modify the maintainer's submission to better match existing policies and style of the Ports - Collection without explicit blessing from the submitter. Also, + Collection without explicit blessing from the submitter or the + maintainer. Also, large infrastructural changes can result in a port being modified without the maintainer's consent. These kinds of changes will never affect the port's functionality.