Generalize the rules for cross-tree committers
The section previously about doc committers in the src repo had information relevant to all committers. Generalize this section. Approved by: core
This commit is contained in:
parent
525cc2c3f0
commit
b01ccacb90
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=46395
1 changed files with 20 additions and 12 deletions
|
@ -416,12 +416,20 @@ You need a Passphrase to protect your secret key.</screen>
|
|||
of the tree where the work is occurring.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Policy for <filename>doc/</filename> Committer Activity
|
||||
in <filename>src/</filename></title>
|
||||
<title>Policy for Committer Activity In Other Trees</title>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>doc committers may commit documentation changes to src
|
||||
<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>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>doc committers may commit
|
||||
documentation changes to <filename>src</filename>
|
||||
files, such as man pages, READMEs, fortune databases,
|
||||
calendar files, and comment fixes without approval from a
|
||||
src committer, subject to the normal care and tending of
|
||||
|
@ -429,18 +437,18 @@ You need a Passphrase to protect your secret key.</screen>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>doc committers may commit minor src changes and fixes,
|
||||
such as build fixes, small features, etc, with an
|
||||
"Approved by" from a src committer.</para>
|
||||
<para>Any committer may make changes to any other tree
|
||||
with an "Approved by" from a non-mentored committer with
|
||||
the appropriate bit.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>doc committers may seek an upgrade to a src commit bit
|
||||
by acquiring a mentor, who will propose the doc committer
|
||||
to core. When approved, they will be added to 'access'
|
||||
and the normal mentoring period will ensue, which will
|
||||
involve a continuing of <quote>Approved by</quote> for
|
||||
some period.</para>
|
||||
<para>Committers can aquire an additional bit by the usual
|
||||
process of finding a mentor who will propose them to core,
|
||||
doceng, or portmgr, as appropriate. When approved, they
|
||||
will be added to 'access' and the normal mentoring period
|
||||
will ensue, which will involve a continuing of
|
||||
<quote>Approved by</quote> for some period.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
|
|
Loading…
Reference in a new issue