aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml')
-rw-r--r--en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml48
1 files changed, 23 insertions, 25 deletions
diff --git a/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml b/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml
index 5d98119f6a..06576422f7 100644
--- a/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml
+++ b/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml
@@ -1,13 +1,12 @@
<?xml version="1.0" encoding="iso-8859-1"?>
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V4.5-Based Extension//EN"
- "../../../share/xml/freebsd45.dtd">
-
-<article lang="en">
- <articleinfo>
- <title>Port Mentor Guidelines</title>
+<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN"
+ "../../../share/xml/freebsd50.dtd">
+<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en">
+ <info><title>Port Mentor Guidelines</title>
+
<authorgroup>
- <corpauthor>The &os; Ports Management Team</corpauthor>
+ <author><orgname>The &os; Ports Management Team</orgname></author>
</authorgroup>
<pubdate>$FreeBSD$</pubdate>
@@ -19,9 +18,9 @@
<holder role="mailto:tabthorpe@FreeBSD.org">Thomas Abthorpe</holder>
<holder role="mailto:crees@FreeBSD.org">Chris Rees</holder>
</copyright>
- </articleinfo>
+ </info>
- <sect1 id="port-mentor.guidelines">
+ <sect1 xml:id="port-mentor.guidelines">
<title>Guideline for Mentor/Mentee relationships</title>
<para>This section is intended to help demystify the
@@ -33,7 +32,7 @@
working toward a common goal, maintaining the quality
assurance of the product we call the Ports Tree.</para>
- <sect2 id="why.mentor">
+ <sect2 xml:id="why.mentor">
<title>Why mentor?</title>
<itemizedlist>
@@ -55,7 +54,7 @@
</itemizedlist>
</sect2>
- <sect2 id="mentor.comentor">
+ <sect2 xml:id="mentor.comentor">
<title>Mentor/Co-Mentor</title>
<para>Reasons for a co-mentorship:</para>
@@ -109,7 +108,7 @@
</itemizedlist>
</sect2>
- <sect2 id="mentor.expectations">
+ <sect2 xml:id="mentor.expectations">
<title>Expectations</title>
<para>We expect mentors to review and test-build all proposed
@@ -122,17 +121,16 @@
and implicit.</para>
<para>We expect mentors to make sure their mentees read the
- <ulink url="&url.books.porters-handbook;">Porter's
- Handbook</ulink>, the <ulink
- url="&url.articles.pr-guidelines;">PR handling guide</ulink>, and
- the <ulink url="&url.articles.committers-guide;">Committer's
- Guide</ulink>. While it's not necessary to memorize all the
+ <link xlink:href="&url.books.porters-handbook;">Porter's
+ Handbook</link>, the <link xlink:href="&url.articles.pr-guidelines;">PR handling guide</link>, and
+ the <link xlink:href="&url.articles.committers-guide;">Committer's
+ Guide</link>. While it's 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).</para>
</sect2>
- <sect2 id="mentees">
+ <sect2 xml:id="mentees">
<title>Selecting a mentee</title>
<para>There is no defined rule for what makes a candidate ready; it
@@ -171,15 +169,15 @@
and hope that portmgr agrees.</para>
</sect2>
- <sect2 id="mentorship.duration">
+ <sect2 xml:id="mentorship.duration">
<title>Mentorship duration</title>
<para>As the trust level develops and grows, the mentee may be
granted <quote>implicit</quote> commit rights. This can include
trivial changes to a <filename>Makefile</filename>,
<filename>pkg-descr</filename> etc. Similarly, it may include
- <makevar>PORTVERSION</makevar> updates that do not include
- <makevar>plist</makevar> changes. Other circumstances may be
+ <varname>PORTVERSION</varname> updates that do not include
+ <varname>plist</varname> changes. Other circumstances may be
formulated at the discretion of the Mentor. However, during the
period of mentorship, a port version bump that affects dependent
ports should be checked by a mentor.</para>
@@ -195,7 +193,7 @@
mistakes, they still require mentor guidance.</para>
</sect2>
- <sect2 id="mentor.comentor.debate">
+ <sect2 xml:id="mentor.comentor.debate">
<title>Mentor/Co-Mentor debate</title>
<para>When a request gets to portmgr, it usually reads as,
@@ -206,14 +204,14 @@
<quote>first among equals</quote>, the co-mentor is the backup.</para>
<para>Some reprobate, whose name shall be withheld, made the
- <ulink url="http://lists.freebsd.org/pipermail/cvs-ports/2007-September/134614.html">
- first recorded co-mentor commit</ulink>. Similar co-mentor commits
+ <link xlink:href="http://lists.freebsd.org/pipermail/cvs-ports/2007-September/134614.html">
+ first recorded co-mentor commit</link>. Similar co-mentor commits
have also been spotted in the src tree. Does this make it right?
Does this make it wrong? It seems to be part of the evolution of
how things are done.</para>
</sect2>
- <sect2 id="mentee.expectations">
+ <sect2 xml:id="mentee.expectations">
<title>Expectations</title>
<para>We expect mentees to be prepared for constructive criticism