Date: Sun, 26 Apr 2015 16:31:29 +0000 (UTC) From: Eitan Adler <eadler@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46604 - head/en_US.ISO8859-1/articles/committers-guide Message-ID: <201504261631.t3QGVTdv025104@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: eadler Date: Sun Apr 26 16:31:29 2015 New Revision: 46604 URL: https://svnweb.freebsd.org/changeset/doc/46604 Log: committer guide: igor and whitespace cleanup - clean up whitespace in committer guide Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/committers-guide/article.xml Sun Apr 26 16:13:03 2015 (r46603) +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml Sun Apr 26 16:31:29 2015 (r46604) @@ -323,17 +323,20 @@ You need a Passphrase to protect your se <sect1 xml:id="kerberos-ldap"> <title>Kerberos and LDAP web Password for &os; Cluster</title> - <para>The &os; cluster requires a Kerberos password to access certain - services. The Kerberos password also serves as the LDAP web password, - since LDAP is proxying to Kerberos in the cluster. Some of the services + <para>The &os; cluster requires a Kerberos password to access + certain services. The Kerberos password also serves as the + LDAP web password, since LDAP is proxying to Kerberos in the + cluster. Some of the services which require this include:</para> <itemizedlist> <listitem> - <para><link xlink:href="https://bugs.freebsd.org/bugzilla">Bugzilla</link></para> + <para><link + xlink:href="https://bugs.freebsd.org/bugzilla">Bugzilla</link></para> </listitem> <listitem> - <para><link xlink:href="https://jenkins.freebsd.org">Jenkins</link></para> + <para><link + xlink:href="https://jenkins.freebsd.org">Jenkins</link></para> </listitem> </itemizedlist> @@ -416,15 +419,15 @@ You need a Passphrase to protect your se of the tree where the work is occurring.</para> <sect2> - <title>Policy for Committer Activity In Other Trees</title> + <title>Policy for Committer Activity in Other Trees</title> <itemizedlist> <listitem> <para>All committers may modify - <filename>base/head/share/misc/committers-*.dot</filename>, - <filename>base/head/usr.bin/calendar/calendars/calendar.freebsd</filename>, - and - <filename>ports/head/astro/xearth/files</filename>.</para> + <filename>base/head/share/misc/committers-*.dot</filename>, + <filename>base/head/usr.bin/calendar/calendars/calendar.freebsd</filename>, + and + <filename>ports/head/astro/xearth/files</filename>.</para> </listitem> <listitem> @@ -2462,8 +2465,7 @@ ControlPersist yes</screen> <para>Avoid obfuscating the email address of the submitter as this adds additional work when searching - logs.</para> - </entry> + logs.</para></entry> </row> <row> @@ -2928,7 +2930,8 @@ Relnotes: yes</programlisting> build infrastructure, approving new documentation committers, and ensuring that the &os; website and documentation on the FTP site is up to date with respect - to the <application>subversion</application> tree. It is not a conflict resolution body. + to the <application>subversion</application> tree. It is + not a conflict resolution body. The vast majority of documentation related discussion takes place on the &a.doc;. More details regarding the doceng team can be found in its <link @@ -3801,16 +3804,16 @@ Relnotes: yes</programlisting> Tier 3 platforms are architectures in the early stages of development, for non-mainstream hardware platforms, or which are considered legacy systems unlikely to see broad future - use. Initial support for Tier 3 platforms should be worked on in - external SCM repositories. + use. Initial support for Tier 3 platforms should be worked on + in external SCM repositories. The transition to &os;'s subversion should take place after the platform boots multi-user on hardware; sharing via subversion is needed for wider exposure; and multiple developers are actively working on the platform. Platforms that transition to Tier 3 status may be - removed from the tree if they are no longer actively supported by the - &os; developer community at the discretion of the release - engineer.</para> + removed from the tree if they are no longer actively supported + by the &os; developer community at the discretion of the + release engineer.</para> <para>Tier 3 platforms may have ports support, either integrated or external, but do not require it.</para> @@ -3830,8 +3833,8 @@ Relnotes: yes</programlisting> project.</para> <para>All systems not otherwise classified into a support tier - are Tier 4 systems. The &arch.ia64; platform is transitioning to - Tier 4 status in &os; 11.</para> + are Tier 4 systems. The &arch.ia64; platform is transitioning + to Tier 4 status in &os; 11.</para> </sect2> <sect2> @@ -4003,9 +4006,9 @@ Relnotes: yes</programlisting> <important> <para>Do not use <command>svn add</command> to add the - port. Follow these steps. If they are unclear, or are - not working, ask for help, do not just <command>svn - add</command> the port.</para> + port. Follow these steps. If they are unclear, or + are not working, ask for help, do not just + <command>svn add</command> the port.</para> </important> <procedure> @@ -4684,7 +4687,7 @@ bak/packages packages from last complet <literal>MFH:</literal> line, for example:</para> <programlisting>MFH: <replaceable>2014Q1</replaceable></programlisting> - + <para>It will automatically notify &a.ports-secteam; and &a.portmgr;. They will then decide if the commit can be merged and answer with the procedure.</para> @@ -4755,8 +4758,7 @@ Property changes on: 2015Q1 ___________________________________________________________________ Modified: svn:mergeinfo Merged /head:r380362 -Do you want to commit? (no = start a shell) [y/n] - </screen> +Do you want to commit? (no = start a shell) [y/n]</screen> <para>At that point, the script will either open a shell for you to fix things, or open your text editor with the @@ -4987,7 +4989,7 @@ Do you want to commit? (no = start a she <question> <para>Are there any perks of being an &os; committer?</para> </question> - + <answer> <para>Recognition as a competent software engineer is the longest lasting value. In addition, getting a chance @@ -5002,9 +5004,11 @@ Do you want to commit? (no = start a she <para>In addition, developers may request a cloaked hostmask for their account on the Freenode IRC network in the form of - <literal>freebsd/developer/</literal><replaceable>freefall name</replaceable> + <literal>freebsd/developer/</literal><replaceable>freefall + name</replaceable> or - <literal>freebsd/developer/</literal><replaceable>NickServ name</replaceable>. + <literal>freebsd/developer/</literal><replaceable>NickServ + name</replaceable>. To request a cloak, send an email to &a.irc.email; with your requested hostmask and NickServ account name.</para>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201504261631.t3QGVTdv025104>