CFD: changes to the Porter's Handbook about proposing new categories

[Hideyuki KURASHINA]

Hi, Mark,

>>> On Sun, 19 Dec 2004 17:29:39 -0600 (CST), Mark Linimon <linimon at lonesome.com> said:

> After checking where to direct someone who was inquiring about this, I
> found that what I had written last time was in the Committer's Handbook
> and effectively assumes that the proposer is a committer.  What the
> following patch does is split the existing text into two pieces and
> moves the general piece to the Porter's Handbook, after adding several
> paragraphs along the way.  Since it affects policy, portmgr@ is copied.
> 
> (The patch does not include removing the text that moves, yet; the
> implied change is fairly obvious and would collide with my other
> outstanding patch to the CH.)
> 
> Unless there are objections, I'd like to commit this text within the
> next day or so.

Please excuse my reply was late, but I found 1 small typo and 1 style
problem.

> @@ -1965,6 +1948,126 @@
>  	  imported to the wrong category only to be moved right away.
>  	  This causes unnecessary and undesirable bloat in the master
>  	  source repository.</para>
> +      </sect2>
> +
> +      <sect2 id="proposing-categories">
> +	<title>Proposing a new category</title>
> +
> +	<para>As the Ports Collection has grown over time, various new
> +	  categories have been introduced.  New categories can either
> +	  be <emphasis>virtual</emphasis> categories—those that do
> +	  not have a corresponding subdirectory in the ports tree—
> +	  or <emphasis>physical</emphasis> categories—those that
> +	  do.  The following text dicusses the issues involved in creating

                                  discusses

> +	    <itemizedlist>
> +	      <listitem>
> +		<para><filename>Makefile</filename>s for the
> +		  new ports once they are repocopied</para>
[...]
> +	  <step>
> +	    <para>Since it affects the ports infrastructure and involves
> +	      not only performing repo-copies but also possibly running

should be ``repocopies'' for consistancy with above item?

> +	      regression tests on the build cluster, the PR should be
> +	      assigned to the &a.portmgr;.</para>
> +	  </step>

-- rushani