From owner-svn-doc-head@FreeBSD.ORG Tue Sep 9 15:40:40 2014 Return-Path: Delivered-To: svn-doc-head@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 A4152DA8; Tue, 9 Sep 2014 15:40:40 +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 84811D3C; Tue, 9 Sep 2014 15:40:40 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s89FeeKP032651; Tue, 9 Sep 2014 15:40:40 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s89FeeKf032650; Tue, 9 Sep 2014 15:40:40 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409091540.s89FeeKf032650@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Tue, 9 Sep 2014 15:40:40 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45578 - head/en_US.ISO8859-1/books/porters-handbook/keeping-up X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-head@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: SVN commit messages for the doc tree for head List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Sep 2014 15:40:40 -0000 Author: mat (ports committer) Date: Tue Sep 9 15:40:40 2014 New Revision: 45578 URL: http://svnweb.freebsd.org/changeset/doc/45578 Log: igor -Ry and some other rewording and fixes. Differential Revision: https://reviews.freebsd.org/D642 Reviewed by: wblock Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml Tue Sep 9 15:32:10 2014 (r45577) +++ head/en_US.ISO8859-1/books/porters-handbook/keeping-up/chapter.xml Tue Sep 9 15:40:40 2014 (r45578) @@ -19,30 +19,29 @@ One of the easiest ways to learn about updates that have already been committed is by subscribing to FreshPorts. - You can select multiple ports to monitor. Maintainers are + Multiple ports can be monitored. Maintainers are strongly encouraged to subscribe, because they will receive notification of not only their own changes, but also any changes that any other &os; committer has made. (These are often necessary to keep up with changes in the underlying ports framework—although it would be most polite to receive an advance heads-up from those committing such changes, sometimes - this is overlooked or just simply impractical. Also, in some + this is overlooked or impractical. Also, in some cases, the changes are very minor in nature. We expect everyone to use their best judgement in these cases.) - If you wish to use FreshPorts, all you need is an account. - If your registered email address is - @FreeBSD.org, you will see the opt-in link on - the right hand side of the webpages. For those of you who - already have a FreshPorts account, but are not using your - @FreeBSD.org email address, just change your - email to @FreeBSD.org, subscribe, then change - it back again. + To use FreshPorts, an account is required. Those with + registered email addresses at @FreeBSD.org + will see the opt-in link on the right-hand side of the web + pages. Those who already have a FreshPorts account but are not + using a @FreeBSD.org email address can change + the email to @FreeBSD.org, subscribe, then + change it back again. FreshPorts also has a sanity test feature which automatically tests each commit to the &os; ports tree. If - subscribed to this service, you will be notified of any errors - which FreshPorts detects during sanity testing of your + subscribed to this service, a committer will receive notifications + of any errors which FreshPorts detects during sanity testing of their commits. @@ -65,14 +64,14 @@ The &os; Ports Mailing List - If you maintain ports, you should consider following the + As a ports maintainer, consider subscribing to &a.ports;. Important changes to the way ports work will be announced there, and then committed to CHANGES. - If this mailing list is too high volume you may consider - following &a.ports-announce; which is moderated and has no - discussion. + If the volume of messages on this mailing list is too high, + consider following &a.ports-announce; which contains only + announcements. @@ -113,8 +112,8 @@ the maintainer is responsible for, the number of those ports with new distfiles, and the percentage of those ports that are out-of-date. The search function allows for searching by email - address for a specific maintainer, and for selecting whether or - not only out-of-date ports should be shown. + address for a specific maintainer, and for selecting whether + only out-of-date ports are shown. Upon clicking on a maintainer's email address, a list of all of their ports is displayed, along with port category, @@ -142,18 +141,18 @@ future, this will be expanded to include the distfile survey, as well as other sources. - To get started, you can view all information about a - particular port by using the To get started, use the Overview - of One Port. + of One Port search page to find all the information + about a port. - As of this writing, this is the only resource available that - maps GNATS PR entries to portnames. (PR submitters do not + This is the only resource available that + maps PR entries to portnames. PR submitters do not always include the portname in their Synopsis, although we would - prefer that they did.) So, portsmon is a - good place to start if you want to find out whether an existing - port has any PRs filed against it and/or any build errors; or, - to find out if a new port that you may be thinking about + prefer that they did. So, portsmon is a + good place to find out whether an existing + port has any PRs filed against it, any build errors, or + if a new port the porter is considering creating has already been submitted.