os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Reword the timeout policies to be more readable [1]. While here, add

Browse source 
a bit about the GNATS autoassigner.

Suggested by:	swills, gjb [1]
This commit is contained in:
Mark Linimon 2011-08-20 18:35:40 +00:00
parent d9f645645b
commit e47666362f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=37580
1 changed files with 10 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

17
en/portmgr/policies_contributors.sgml
View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
<!ENTITY date "$FreeBSD: www/en/portmgr/policies_contributors.sgml,v 1.1 2005/12/15 01:10:43 linimon Exp $">
<!ENTITY date "$FreeBSD: www/en/portmgr/policies_contributors.sgml,v 1.2 2006/08/19 21:20:41 hrs Exp $">
<!ENTITY title "Policies of the Ports Management Team: Maintainers and Committers">
<!ENTITY % navinclude.about "INCLUDE">
]>
@ -19,7 +19,11 @@ responses to issues brought to their attention via email.</p>
commit the change. If it is a major change (e.g. would require a
regression run), please contact portmgr first.</p>
<p>Since GNATS does not automatically notify maintainers of PRs, please
<p>We have an add-on to the GNATS database known as the auto-assigner,
which attempts to automatically notify maintainers of PRs; however,
it depends on the Synopsis containing category/portname. In general,
various people attempt to catch and fix cases where it does not work,
but you should not assume so. Therefore, please
check to see whether or not the maintainer knows about the PR before
declaring a timeout. You can generally tell this from the Audit-Trail
and Cc: lines in the PR.</p>
@ -27,9 +31,8 @@ responses to issues brought to their attention via email.</p>
<a name="maintainer_reset"></a>
<h3>Maintainer Reset</h3>
<p>The time limit for a maintainer to respond to port problems (such
as build errors, PRs, and needed updates) is three months. After that
period, any ports committer can reset the maintainer. If you are
<p>A maintainer who does not respond to any port issues for 3 months may
be reset by any ports committer. If you are
a committer and concerned about whether you are doing the right
thing, please contact portmgr.</p>
@ -41,8 +44,8 @@ responses to issues brought to their attention via email.</p>
<a name="commit_privileges"></a>
<h3>Commit Privileges</h3>
<p>The time limit for a committer to keep commit rights within the
ports tree ("commit bit") is one year. portmgr will contact the
<p>Ports committers who are not active for one year will lose commit
privileges. portmgr will contact the
committer by email before invoking this limit.</p>
&footer ;