Date: Mon, 18 Mar 2013 18:29:18 +0000 (UTC) From: Gabor Pali <pgj@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r41263 - head/en_US.ISO8859-1/htdocs/internal Message-ID: <201303181829.r2IITI0e047116@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: pgj Date: Mon Mar 18 18:29:18 2013 New Revision: 41263 URL: http://svnweb.freebsd.org/changeset/doc/41263 Log: - Add guidelines on proposing committers Approved by: core Added: head/en_US.ISO8859-1/htdocs/internal/proposing-committers.xml (contents, props changed) Modified: head/en_US.ISO8859-1/htdocs/internal/Makefile head/en_US.ISO8859-1/htdocs/internal/new-account.xml Modified: head/en_US.ISO8859-1/htdocs/internal/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/Makefile Mon Mar 18 16:30:15 2013 (r41262) +++ head/en_US.ISO8859-1/htdocs/internal/Makefile Mon Mar 18 18:29:18 2013 (r41263) @@ -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 Modified: head/en_US.ISO8859-1/htdocs/internal/new-account.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/new-account.xml Mon Mar 18 16:30:15 2013 (r41262) +++ head/en_US.ISO8859-1/htdocs/internal/new-account.xml Mon Mar 18 18:29:18 2013 (r41263) @@ -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> Added: head/en_US.ISO8859-1/htdocs/internal/proposing-committers.xml ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/en_US.ISO8859-1/htdocs/internal/proposing-committers.xml Mon Mar 18 18:29:18 2013 (r41263) @@ -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>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201303181829.r2IITI0e047116>