From owner-svn-doc-head@FreeBSD.ORG Sat May 24 15:13:10 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 7B6C5303; Sat, 24 May 2014 15:13:10 +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 5C8382381; Sat, 24 May 2014 15:13:10 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s4OFDAgH046917; Sat, 24 May 2014 15:13:10 GMT (envelope-from bcr@svn.freebsd.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s4OFDAm1046916; Sat, 24 May 2014 15:13:10 GMT (envelope-from bcr@svn.freebsd.org) Message-Id: <201405241513.s4OFDAm1046916@svn.freebsd.org> From: Benedict Reuschling Date: Sat, 24 May 2014 15:13:10 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44934 - head/en_US.ISO8859-1/articles/port-mentor-guidelines 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 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: Sat, 24 May 2014 15:13:10 -0000 Author: bcr Date: Sat May 24 15:13:09 2014 New Revision: 44934 URL: http://svnweb.freebsd.org/changeset/doc/44934 Log: Remove contractions, capitalize titles and rephrase one sentence to avoid the use of "e.g.". Modified: head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml Modified: head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml Sat May 24 15:05:41 2014 (r44933) +++ head/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml Sat May 24 15:13:09 2014 (r44934) @@ -26,7 +26,7 @@ - Guideline for Mentor/Mentee relationships + Guideline for Mentor/Mentee Relationships This section is intended to help demystify the mentoring process, as well as a way to openly promote a @@ -38,7 +38,7 @@ assurance of the product we call the Ports Tree. - Why mentor? + Why Mentor? @@ -130,20 +130,20 @@ xlink:href="&url.articles.pr-guidelines;">PR handling guide, and the Committer's - Guide. While it's not necessary to memorize all the + Guide. While it is not necessary to memorize all the details, every committer needs to have an overview of these things to be an effective part of the community (and avoid as many rookie mistakes as possible). - Selecting a mentee + Selecting a Mentee There is no defined rule for what makes a candidate ready; it can be a combination of number of PRs they have submitted to GNATS, the number of ports maintained, frequency of ports updates and/or level of - participation in a particular area of interest, e.g. + participation in a particular area of interest like GNOME, KDE, Gecko or others. @@ -179,7 +179,7 @@ - Mentorship duration + Mentorship Duration As the trust level develops and grows, the mentee may be granted implicit commit rights. This can @@ -204,7 +204,7 @@ - Mentor/Co-Mentor debate + Mentor/Co-Mentor Debate When a request gets to portmgr, it usually reads as, I propose 'foo' for a ports commit bit, I will @@ -229,7 +229,7 @@ We expect mentees to be prepared for constructive criticism from the community. There's still a lot of - lore that isn't written down. Responding well + lore that is not written down. Responding well to constructive criticism is what we hope we are selecting for by first reviewing their existing contributions on IRC and mailing lists.