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

- Add guidelines on proposing committers

Browse source 
Approved by:	core
This commit is contained in:
Gabor Pali 2013-03-18 18:29:18 +00:00
parent 8645a4ce74
commit f0a3748c4e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41263
3 changed files with 60 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
en_US.ISO8859-1/htdocs/internal/Makefile
View file

@ -22,6 +22,7 @@ DOCS+= machines.xml
DOCS+= mirror.xml
DOCS+= new-account.xml
DOCS+= policies.xml
DOCS+= proposing-committers.xml
DOCS+= releng.xml
DOCS+= resources.xml
DOCS+= statistic.xml

4
en_US.ISO8859-1/htdocs/internal/new-account.xml
View file

@ -29,7 +29,9 @@
<p>Any commit bit requests that do not follow the guidelines outlined
above will be delayed (at best) or earn you negative vibrations from the
respective team / team secretary.
respective team / team secretary. For some guidelines on how the
proposal itself should be written, please see <a
href="proposing-committers.html">a brief summary</a>.
</p>
<p>Responsible party for this procedure is:</p>

56
en_US.ISO8859-1/htdocs/internal/proposing-committers.xml Normal file
View file

@ -0,0 +1,56 @@
<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/doc/share/xml/xhtml10-freebsd.dtd" [
<!ENTITY title "Proposing Committers">
]>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
</head>
<body class="navinclude.docs">
<p>The following paragraphs contain an advice from &a.kib;, member of
the Core Team, who summarizes what constitutes a good proposal, how
you as potential mentor, could increase your chances to have your
mentee granted a commit bit.</p>
<p>When proposing somebody, you should just forget for a moment that you
know the candidate personally. After that, look unprejudiced on the
person's activity on the mailing lists, and evaluate the patches
submitted.</p>
<p>Now, you can ask yourself, is it enough confidence in both technical
abilities and the social behavior of the candidate, from what you see
only on the media? If you do, then write down the reasons why are
you sure, using the said list of the contributions as the evidence,
and do include the reasoning in the commit bit application.</p>
<p>Due to several failures of the premature granting of commit bits, the
Core Team became quite sensitive to these criteria. Most of the
members only see the activity of applicants on the lists, and not
seeing much there causes the cautious choice.</p>
<p>The Core Team wants to see a good list of the work already done for
&os; (e.g., the long list of the commits, submitted by the applicant,
the list of PRs opened etc.), which can make us confident that the
person has an established interest in the project, backed by the
technical ability and work done.</p>
<p>Also, the history of the good engagement with the community on the
public media, such as mailing list, is a deciding factor too. The
Core Team wants to filter out the controversial personalities, since
it is almost impossible and highly undesirable to revoke the commit
bit, once granted.</p>
<p>Vendor-proposed maintainers for the hardware drivers usually approved
without applying the listed criteria. Still, the Core Team requires
an experienced mentor for a vendor committer to avoid unwanted tension
and to make sure that vendor commits follow the Project procedures and
community expectations.</p>
</body>
</html>