youys
/
ant
Not watched
1
0
Fork 1
Code
Releases 0 Wiki Activity
Issues 0 Pull Requests 0 Datasets Model Cloudbrain
You can not select more than 25 topics Topics must start with a chinese character,a letter or number, can include dashes ('-') and can be up to 35 characters long.
Tree: 0d890b4559
Branches Tags
${ item.name }
Create branch ${ searchTerm }
from '0d890b4559'
${ noResults }
ant/proposal/ant-site/anakia/docs/bylaws.html

875 lines
36 KiB
Raw Blame History 

  1. 

  2. 

  3. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

  4.         <html>

  5.     <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->

  6.     <head>

  7.       <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">

  8.         <title>Apache Ant - Apache Ant Project Bylaws</title>

  9.         <link type="text/css" href="page.css" rel="stylesheet">

  10.         </head>

  11. 

  12.     <body text="#000000" bgcolor="#ffffff">

  13.       <table summary="navigation path" width="100%" border="0" cellpadding="0" cellspacing="0">

  14.         <tr>

  15.           <td nowrap="nowrap" valign="middle" bgcolor="#CFDCED" height="20"><img height="1" width="5" alt="" border="0" src="images/spacer.gif"><font size="2" face="Arial, Helvetica, Sans-serif"><script src="breadcrumbs.js" language="JavaScript" type="text/javascript"></script></font></td>

  16.         </tr>

  17.         <tr>

  18.           <td bgcolor="#4C6C8F" height="2"><img height="2" width="2" alt="" border="0" src="images/spacer.gif"></td>

  19.         </tr>

  20.       </table>

  21. 

  22.       <table summary="header with logos" width="100%" border="0" cellpadding="0" cellspacing="0">

  23.         <tr>

  24.           <td bgcolor="#294563"><a href="http://ant.apache.org/"><img border="0" alt="Apache Ant site" src="images/group-logo.gif"></a></td><td width="100%" align="center" bgcolor="#294563"><a href="http://ant.apache.org/"><img alt="Apache Ant logo" border="0" src="images/project-logo.gif"></a></td><td valign="top" rowspan="2" bgcolor="#294563">

  25.             <form target="_blank" onsubmit="q.value = query.value + ' site:ant.apache.org'" action="http://www.google.com/search" method="get">

  26.               <table summary="search" border="0" cellspacing="0" cellpadding="0" bgcolor="#4C6C8F">

  27.                 <tr>

  28.                   <td colspan="3"><img height="10" width="1" alt="" src="images/spacer.gif"></td>

  29.                 </tr>

  30.                 <tr>

  31.                   <td><img height="1" width="1" alt="" src="images/spacer.gif"></td><td nowrap="nowrap"><input name="q" type="hidden"><input size="15" id="query" type="text"><img height="1" width="5" alt="" src="images/spacer.gif"><input name="Search" value="Search" type="submit">

  32.                   <br>

  33.                   <font face="Arial, Helvetica, Sans-serif" size="2" color="white">

  34.                                     the Apache Ant site

  35. 

  36. 

  37.                                     </font></td><td><img height="1" width="1" alt="" src="images/spacer.gif"></td>

  38.                 </tr>

  39.                 <tr>

  40.                   <td><img alt="" border="0" height="10" width="9" src="images/search-left.gif"></td><td><img height="1" width="1" alt="" src="images/spacer.gif"></td><td><img alt="" border="0" height="10" width="9" src="images/search-right.gif"></td>

  41.                 </tr>

  42.               </table>

  43.             </form>

  44.           </td><td bgcolor="#294563"><img height="10" width="10" alt="" src="images/spacer.gif"></td>

  45.         </tr>

  46.         <tr>

  47.           <td valign="bottom" bgcolor="#294563" colspan="2">

  48.             <div class="tab">

  49.               <table summary="tab bar" border="0" cellpadding="0" cellspacing="0">

  50.                 <tr>

  51. 

  52.                   <td width="8"><img alt="" height="8" width="8" src="images/spacer.gif"></td><td valign="bottom">

  53.                     <table summary="selected tab" border="0" cellpadding="0" cellspacing="0">

  54.                       <tr>

  55.                       <td height="30" valign="top" width="5" bgcolor="#4C6C8F"><img height="5" width="5" alt="" src="images/tabSel-left.gif"></td><td valign="middle" bgcolor="#4C6C8F"><font color="#ffffff" size="2" face="Arial, Helvetica, Sans-serif"><b>Home</b></font></td><td valign="top" width="5" bgcolor="#4C6C8F"><img height="5" width="5" alt="" src="images/tabSel-right.gif"></td>

  56.                       </tr>

  57.                     </table>

  58.                   </td>

  59.                 </tr>

  60.               </table>

  61.             </div>

  62.           </td><td bgcolor="#294563"><img alt="" width="1" height="1" src="images/spacer.gif"></td>

  63.         </tr>

  64.         <tr>

  65.           <td bgcolor="#4C6C8F" colspan="4"><img width="1" height="10" alt="" src="images/spacer.gif"></td>

  66.         </tr>

  67.       </table>

  68.       <table summary="page content" bgcolor="#ffffff" width="100%" border="0" cellpadding="0" cellspacing="0">

  69.         <tr>

  70.           <td valign="top">

  71.             <table summary="menu" border="0" cellspacing="0" cellpadding="0">

  72.               <tr>

  73.                 <td rowspan="3" valign="top">

  74.                   <table summary="blue line" border="0" cellpadding="0" cellspacing="0">

  75.                     <tr>

  76.                       <td bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>

  77.                     </tr>

  78.                     <tr>

  79.                       <td bgcolor="#CFDCED"><font color="#4C6C8F" size="4" face="Arial, Helvetica, Sans-serif">&nbsp;</font></td>

  80.                     </tr>

  81.                     <tr>

  82.                       <td bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>

  83.                     </tr>

  84.                   </table>

  85.                 </td><td bgcolor="#294563"><img width="1" height="1" alt="" src="images/spacer.gif"></td><td valign="bottom" bgcolor="#4C6C8F"><img width="10" height="10" alt="" src="images/spacer.gif"></td><td nowrap="nowrap" valign="top" bgcolor="#4C6C8F">

  86.     <div class="menu"><ul>

  87.       <li><font color="#CFDCED">Apache Ant</font>

  88.       <ul>

  89.             <li>

  90.                     <a href="./index.html">Welcome</a>

  91.                 </li>

  92.             <li>

  93.                     <a href="./license.html">License</a>

  94.                 </li>

  95.             <li>

  96.                     <a href="./antnews.html">News</a>

  97.                 </li>

  98.           </ul>

  99.     </li>

  100.       <li><font color="#CFDCED">Documentation</font>

  101.       <ul>

  102.             <li>

  103.                     <a href="./manual/index.html">Manual</a>

  104.                 </li>

  105.             <li>

  106.                     <a href="./projects.html">Related Projects</a>

  107.                 </li>

  108.             <li>

  109.                     <a href="./external.html">External Tools and Tasks</a>

  110.                 </li>

  111.             <li>

  112.                     <a href="./resources.html">Resources</a>

  113.                 </li>

  114.             <li>

  115.                     <a href="./faq.html">Frequently Asked Questions</a>

  116.                 </li>

  117.             <li>

  118.                     <a href="./problems.html">Having Problems?</a>

  119.                 </li>

  120.           </ul>

  121.     </li>

  122.       <li><font color="#CFDCED">Download</font>

  123.       <ul>

  124.             <li>

  125.                     <a href="./bindownload.cgi">Binary Distributions</a>

  126.                 </li>

  127.             <li>

  128.                     <a href="./srcdownload.cgi">Source Distributions</a>

  129.                 </li>

  130.           </ul>

  131.     </li>

  132.       <li><font color="#CFDCED">Get Involved</font>

  133.       <ul>

  134.             <li>

  135.                     <a href="./mail.html">Mailing Lists</a>

  136.                 </li>

  137.             <li>

  138.                     <a href="./cvs.html">CVS Repositories</a>

  139.                 </li>

  140.             <li>

  141.                     <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>

  142.                 </li>

  143.             <li>

  144.                     <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=Enhancement">Enhancement Requests</a>

  145.                 </li>

  146.           </ul>

  147.     </li>

  148.       <li><font color="#CFDCED">Project Management</font>

  149.       <ul>

  150.             <li>

  151.                     <a href="./contributors.html">Contributors</a>

  152.                 </li>

  153.             <li>

  154.                     <a href="./mission.html">Apache Ant Mission</a>

  155.                 </li>

  156.             <li>

  157.                     <a href="./guidelines.html">Project Guidelines</a>

  158.                 </li>

  159.             <li>

  160.                     <a href="./legal.html">Legal</a>

  161.                 </li>

  162.           </ul>

  163.     </li>

  164.     </ul></div>

  165.                 </td><td valign="bottom" bgcolor="#4C6C8F"><img width="10" height="10" alt="" src="images/spacer.gif"></td><td bgcolor="#294563"><img width="1" height="1" alt="" src="images/spacer.gif"></td>

  166.               </tr>

  167.               <tr>

  168.                 <td valign="bottom" align="left" colspan="2" rowspan="2" bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="images/menu-left.gif"></td><td bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="images/spacer.gif"></td><td valign="bottom" align="right" colspan="2" rowspan="2" bgcolor="#4C6C8F"><img height="10" width="10" border="0" alt="" src="images/menu-right.gif"></td>

  169.               </tr>

  170.               <tr>

  171.                 <td height="1" bgcolor="#294563"><img width="1" height="1" alt="" src="images/spacer.gif"></td>

  172.               </tr>

  173.             </table>

  174.           </td><td valign="top" width="100%">

  175.             <table summary="content" width="100%" border="0" cellpadding="0" cellspacing="0">

  176.               <tr>

  177.                 <td colspan="4" bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>

  178.               </tr>

  179.               <tr>

  180.                 <td align="left" width="10" bgcolor="#CFDCED"><img width="10" height="1" alt="" src="images/spacer.gif"></td><td align="left" width="50%" bgcolor="#CFDCED"><font color="#4C6C8F" size="3" face="Arial, Helvetica, Sans-serif">

  181.                 &nbsp;

  182.                 </font><img width="10" height="8" alt="" src="images/spacer.gif"></td><td align="right" width="50%" bgcolor="#CFDCED"><font color="#4C6C8F" size="3" face="Arial, Helvetica, Sans-serif">

  183.                 &nbsp;

  184.                 </font><img width="10" height="8" alt="" src="images/spacer.gif"></td><td width="10" bgcolor="#CFDCED"><img width="10" height="1" alt="" src="images/spacer.gif"></td>

  185.               </tr>

  186.               <tr>

  187.                 <td colspan="4" bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>

  188.               </tr>

  189.               <tr>

  190.                 <td align="left" width="10"><img width="10" height="1" alt="" src="images/spacer.gif"></td><td align="left" width="100%">

  191.                   <div class="content">

  192.       <table class="title">

  193.         <tr>

  194.           <td valign="middle">

  195.             <h1>Apache Ant Project Bylaws</h1>

  196.           </td>

  197.         </tr>

  198.       </table>

  199.           <br/>

  200.   <table class="nowrap" border="0" cellspacing="0" cellpadding="2" width="100%">

  201.     <tr><td bgcolor="#294563"><font color="#ffffff"><a name="Apache Ant Project Bylaws"><strong>Apache Ant Project Bylaws</strong></a></font></td></tr>

  202.   </table>

  203.                         <p>

  204.       This document defines the bylaws under which the Apache Ant project

  205.       operates. It defines the roles and responsibilities of the

  206.       project, who may vote, how voting works, how conflicts are resolved,

  207.       etc.

  208.     </p>

  209.                                 <p>

  210.       Ant is a project of the

  211.       <a href="http://www.apache.org/foundation/">Apache Software

  212.       Foundation</a>.  The foundation holds the copyright on Apache

  213.       code including the code in the  Ant codebase. The

  214.       <a href="http://www.apache.org/foundation/faq.html">foundation FAQ</a>

  215.       explains the operation and background of the foundation.

  216.     </p>

  217.                                 <p>

  218.       Ant is typical of Apache projects in that it operates under a set of

  219.       principles, known collectively as the "Apache Way". If you are

  220.       new to Apache development, please refer to the

  221.       <a href="http://incubator.apache.org">Incubator project</a>

  222.       for more information on how Apache projects operate. <b>Note:</b> the

  223.       incubator project has only been recently set up and does not yet explain

  224.       the Apache Way in great detail.

  225.     </p>

  226.                                 <ul>

  227.         <li><a href="#Roles and Responsibilities">Roles and Responsibilities</a></li>

  228.         <li><a href="#Decision Making">How decisions are made</a></li>

  229.     </ul>

  230.                       <br/>

  231.   <table class="nowrap" border="0" cellspacing="0" cellpadding="2" width="100%">

  232.     <tr><td bgcolor="#294563"><font color="#ffffff"><a name="Roles and Responsibilities"><strong>Roles and Responsibilities</strong></a></font></td></tr>

  233.   </table>

  234.                         <p>

  235.       Apache projects define a set of roles with associated rights and

  236.       responsibilities. These roles govern what tasks an individual may perform

  237.       within the project. The roles are defined in the following sections

  238.     </p>

  239.                                 <ul>

  240.       <li><a href="#Users">Users</a></li>

  241.       <li><a href="#Developers">Developers</a></li>

  242.       <li><a href="#Committers">Committers</a></li>

  243.       <li><a href="#Project Management Committee">

  244.         Project Management Committee (PMC)</a>

  245.       </li>

  246.     </ul>

  247.                                       <br/>

  248.       <a name="Users"></a>

  249.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  250.         <tr><td bgcolor="#4C6C8F">

  251.           <font color="#ffffff" face="arial,helvetica,sanserif">

  252.             <strong>Users</strong>

  253.           </font>

  254.         </td></tr>

  255.       </table>

  256.                         <p>

  257.         The most important participants in the project are people who use our

  258.         software. The majority of our developers start out as users and guide

  259.         their development efforts from the user's perspective.

  260.       </p>

  261.                                 <p>

  262.         Users contribute to the Apache projects by providing feedback to

  263.         developers in the form of bug reports and feature suggestions. As

  264.         well, users participate in the Apache community by helping other users

  265.         on mailing lists and user support forums.

  266.       </p>

  267.                                                     <br/>

  268.       <a name="Developers"></a>

  269.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  270.         <tr><td bgcolor="#4C6C8F">

  271.           <font color="#ffffff" face="arial,helvetica,sanserif">

  272.             <strong>Developers</strong>

  273.           </font>

  274.         </td></tr>

  275.       </table>

  276.                         <p>

  277.         All of the volunteers who are contributing time, code, documentation,

  278.         or resources to the Ant Project. A developer that makes sustained,

  279.         welcome contributions to the project may be invited to become a

  280.         Committer, though the exact timing of such invitations depends on many

  281.         factors.

  282.       </p>

  283.                                                     <br/>

  284.       <a name="Committers"></a>

  285.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  286.         <tr><td bgcolor="#4C6C8F">

  287.           <font color="#ffffff" face="arial,helvetica,sanserif">

  288.             <strong>Committers</strong>

  289.           </font>

  290.         </td></tr>

  291.       </table>

  292.                         <p>

  293.         The project's Committers are responsible for the project's technical

  294.         management. All committers have write access to the project's source

  295.         repositories. Committers may cast binding votes on any technical

  296.         discussion regarding the project.

  297.       </p>

  298.                                 <p>

  299.         Committer access is by invitation only and must be approved by lazy

  300.         consensus of the active PMC members. A Committer is considered emeritus

  301.         by their own declaration or by not contributing in any form to the

  302.         project for over six months. An emeritus committer may request

  303.         reinstatement of commit access from the PMC. Such reinstatement is

  304.         subject to lazy consensus of active PMC members.

  305.       </p>

  306.                                 <p>

  307.         Commit access can be revoked by a unanimous vote of all the active

  308.         PMC members (except the committer in question if they are also a PMC member).

  309.       </p>

  310.                                 <p>

  311.         All Apache committers are required to have a signed Contributor License

  312.         Agreement (CLA) on file with the Apache Software Foundation. There is a

  313.         <a href="http://www.apache.org/dev/committers.html">Committer FAQ</a>

  314.         which provides more details on the requirements for Committers

  315.       </p>

  316.                                 <p>

  317.         A committer who makes a sustained contribution to the project may be

  318.         invited to become a member of the PMC. The form of contribution is

  319.         not limited to code. It can also include code review, helping out

  320.         users on the mailing lists, documentation, etc.

  321.       </p>

  322.                                                     <br/>

  323.       <a name="Project Management Committee"></a>

  324.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  325.         <tr><td bgcolor="#4C6C8F">

  326.           <font color="#ffffff" face="arial,helvetica,sanserif">

  327.             <strong>Project Management Committee</strong>

  328.           </font>

  329.         </td></tr>

  330.       </table>

  331.                         <p>

  332.         The Project Management Committee (PMC) for Apache Ant was created by a

  333.         <a href="mission.html">resolution</a> of the board of the Apache

  334.         Software Foundation on 18<sup>th</sup> November 2002. The PMC is

  335.         responsible to the board and the ASF for the management and oversight

  336.         of the Apache Ant codebase. The responsibilities of the PMC include

  337.       </p>

  338.                                 <ul>

  339.         <li>Deciding what is distributed as products of the Apache Ant project.

  340.             In particular all releases must be approved by the PMC

  341.         </li>

  342.         <li>Maintaining the project's shared resources, including the codebase

  343.             repository, mailing lists, websites.

  344.         </li>

  345.         <li>Speaking on behalf of the project.

  346.         </li>

  347.         <li>Resolving license disputes regarding products of the project

  348.         </li>

  349.         <li>Nominating new PMC members and committers

  350.         </li>

  351.         <li>Maintaining these bylaws and other guidelines of the project

  352.         </li>

  353.       </ul>

  354.                                 <p>

  355.         Membership of the PMC is by invitation only and must be approved by a

  356.         lazy consensus of active PMC members. A PMC member is considered

  357.         "emeritus" by their own declaration or by not contributing in

  358.         any form to the project for over six months. An emeritus member may

  359.         request reinstatement to the PMC. Such reinstatement is subject to lazy

  360.         consensus of the active PMC members. Membership of the PMC can be

  361.         revoked by an unanimous vote of all the active PMC members other than

  362.         the member in question.

  363.       </p>

  364.                                 <p>

  365.         The chair of the PMC is appointed by the ASF board. The chair is an

  366.         office holder of the Apache Software Foundation (Vice President,

  367.         Apache Ant) and has primary responsibility to the board for the

  368.         management of the projects within the scope of the Ant PMC. The chair

  369.         reports to the board quarterly on developments within the Ant project.

  370.         The PMC may consider the position of PMC chair annually and if

  371.         supported by 2/3 Majority may recommend a new chair to the board.

  372.         Ultimately, however, it is the board's responsibility who it chooses

  373.         to appoint as the PMC chair.

  374.       </p>

  375.                                     <br/>

  376.   <table class="nowrap" border="0" cellspacing="0" cellpadding="2" width="100%">

  377.     <tr><td bgcolor="#294563"><font color="#ffffff"><a name="Decision Making"><strong>Decision Making</strong></a></font></td></tr>

  378.   </table>

  379.                         <p>

  380.       Within the Ant project, different types of decisions require different

  381.       forms of approval. For example, the

  382.       <a href="#Roles and Responsibilities">previous section</a> describes

  383.       several decisions which require "lazy consensus" approval. This

  384.       section defines how voting is performed, the types of approvals, and which

  385.       types of decision require which type of approval.

  386.     </p>

  387.                                       <br/>

  388.       <a name="Voting"></a>

  389.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  390.         <tr><td bgcolor="#4C6C8F">

  391.           <font color="#ffffff" face="arial,helvetica,sanserif">

  392.             <strong>Voting</strong>

  393.           </font>

  394.         </td></tr>

  395.       </table>

  396.                         <p>

  397.         Decisions regarding the project are made by votes on the primary project

  398.         development mailing list (ant-dev@jakarta.apache.org). Where necessary,

  399.         PMC voting may take place on the private Ant PMC mailing list.

  400.         Votes are clearly indicated by subject line starting with [VOTE] or

  401.         [PMC-VOTE]. Votes may contain multiple items for approval and these

  402.         should be clearly separated. Voting is carried out by replying to the

  403.         vote mail. Voting may take four flavours

  404.       </p>

  405.                                   <table class="ForrestTable" cellspacing="1" cellpadding="4">

  406.               <tr>

  407.                       <td colspan="1" rowspan="1"

  408.       valign="top" align="left">

  409.           <strong>+1</strong>

  410.       </td>

  411.                           <td colspan="1" rowspan="1"

  412.       valign="top" align="left">

  413.           

  414.             "Yes," "Agree," or "the action should be

  415.             performed." In general, this vote also indicates a willingness

  416.             on the behalf of the voter in "making it happen"

  417.           

  418.       </td>

  419.       </tr>

  420.                   <tr>

  421.                       <td colspan="1" rowspan="1"

  422.       valign="top" align="left">

  423.           <strong>+0</strong>

  424.       </td>

  425.                           <td colspan="1" rowspan="1"

  426.       valign="top" align="left">

  427.           

  428.             This vote indicates a willingness for the action under

  429.             consideration to go ahead. The voter, however will not be able

  430.             to help.

  431.           

  432.       </td>

  433.       </tr>

  434.                   <tr>

  435.                       <td colspan="1" rowspan="1"

  436.       valign="top" align="left">

  437.           <strong>-0</strong>

  438.       </td>

  439.                           <td colspan="1" rowspan="1"

  440.       valign="top" align="left">

  441.           

  442.             This vote indicates that the voter does not, in general, agree with

  443.             the proposed action but is not concerned enough to prevent the

  444.             action going ahead.

  445.           

  446.       </td>

  447.       </tr>

  448.                   <tr>

  449.                       <td colspan="1" rowspan="1"

  450.       valign="top" align="left">

  451.           <strong>-1</strong>

  452.       </td>

  453.                           <td colspan="1" rowspan="1"

  454.       valign="top" align="left">

  455.           

  456.             This is a negative vote. On issues where consensus is required,

  457.             this vote counts as a <strong>veto</strong>. All vetoes must

  458.             contain an explanation of why the veto is appropriate. Vetoes with

  459.             no explanation are void. It may also be appropriate for a -1 vote

  460.             to include an alternative course of action.

  461.           

  462.       </td>

  463.       </tr>

  464.         </table>

  465.                                 <p>

  466.         All participants in the Ant project are encouraged to show their

  467.         agreement with or against a particular action by voting. For technical

  468.         decisions, only the votes of active committers are binding. Non binding

  469.         votes are still useful for those with binding votes to understand the

  470.         perception of an action in the wider Ant community. For PMC decisions,

  471.         only the votes of PMC members are binding.

  472.       </p>

  473.                                 <p>

  474.         Voting can also be applied to changes made to the Ant codebase. These

  475.         typically take the form of a veto (-1) in reply to the commit message

  476.         sent when the commit is made.

  477.       </p>

  478.                                                     <br/>

  479.       <a name="Approvals"></a>

  480.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  481.         <tr><td bgcolor="#4C6C8F">

  482.           <font color="#ffffff" face="arial,helvetica,sanserif">

  483.             <strong>Approvals</strong>

  484.           </font>

  485.         </td></tr>

  486.       </table>

  487.                         <p>

  488.         These are the types of approvals that can be sought. Different actions

  489.         require different types of approvals

  490.       </p>

  491.                                   <table class="ForrestTable" cellspacing="1" cellpadding="4">

  492.               <tr>

  493.                       <td colspan="1" rowspan="1"

  494.       valign="top" align="left">

  495.           <strong>Consensus</strong>

  496.       </td>

  497.                           <td colspan="1" rowspan="1"

  498.       valign="top" align="left">

  499.           

  500.             For this to pass, all voters with binding votes must vote and there

  501.             can be no binding vetoes (-1). Consensus votes are rarely required

  502.             due to the impracticality of getting all eligible voters to cast a

  503.             vote.

  504.           

  505.       </td>

  506.       </tr>

  507.                   <tr>

  508.                       <td colspan="1" rowspan="1"

  509.       valign="top" align="left">

  510.           <strong>Lazy Consensus</strong>

  511.       </td>

  512.                           <td colspan="1" rowspan="1"

  513.       valign="top" align="left">

  514.           

  515.             Lazy consensus requires 3 binding +1 votes and no binding vetoes.

  516.           

  517.       </td>

  518.       </tr>

  519.                   <tr>

  520.                       <td colspan="1" rowspan="1"

  521.       valign="top" align="left">

  522.           <strong>Lazy Majority</strong>

  523.       </td>

  524.                           <td colspan="1" rowspan="1"

  525.       valign="top" align="left">

  526.           

  527.             A lazy majority vote requires 3 binding +1 votes and more binding +1

  528.             votes that -1 votes.

  529.           

  530.       </td>

  531.       </tr>

  532.                   <tr>

  533.                       <td colspan="1" rowspan="1"

  534.       valign="top" align="left">

  535.           <strong>Lazy Approval</strong>

  536.       </td>

  537.                           <td colspan="1" rowspan="1"

  538.       valign="top" align="left">

  539.           

  540.             An action with lazy approval is implicitly allowed unless a -1 vote

  541.             is received, at which time, depending on the type of action, either

  542.             lazy majority or lazy consensus approval must be obtained.

  543.           

  544.       </td>

  545.       </tr>

  546.                   <tr>

  547.                       <td colspan="1" rowspan="1"

  548.       valign="top" align="left">

  549.           <strong>2/3 Majority</strong>

  550.       </td>

  551.                           <td colspan="1" rowspan="1"

  552.       valign="top" align="left">

  553.           

  554.             Some actions require a 2/3 majority of active committers or PMC

  555.             members to pass. Such actions typically affect the foundation

  556.             of the project (e.g. adopting a new codebase to replace an existing

  557.             product). The higher threshold is designed to ensure such changes

  558.             are strongly supported. To pass this vote requires at least 2/3 of

  559.             binding vote holders to vote +1

  560.           

  561.       </td>

  562.       </tr>

  563.         </table>

  564.                                                     <br/>

  565.       <a name="Vetoes"></a>

  566.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  567.         <tr><td bgcolor="#4C6C8F">

  568.           <font color="#ffffff" face="arial,helvetica,sanserif">

  569.             <strong>Vetoes</strong>

  570.           </font>

  571.         </td></tr>

  572.       </table>

  573.                         <p>

  574.         A valid, binding veto cannot be overruled. If a veto is cast, it must be

  575.         accompanied by a valid reason explaining the reasons for the veto. The

  576.         validity of a veto, if challenged, can be confirmed by anyone who has

  577.         a binding vote. This does not necessarily  signify agreement with the

  578.         veto - merely that the veto is valid.

  579.       </p>

  580.                                 <p>

  581.         If you disagree with a valid veto, you must lobby the person casting

  582.         the veto to withdraw their veto. If a veto is not withdrawn, the action

  583.         that has been vetoed must be reversed in a timely manner.

  584.       </p>

  585.                                                     <br/>

  586.       <a name="Actions"></a>

  587.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  588.         <tr><td bgcolor="#4C6C8F">

  589.           <font color="#ffffff" face="arial,helvetica,sanserif">

  590.             <strong>Actions</strong>

  591.           </font>

  592.         </td></tr>

  593.       </table>

  594.                         <p>

  595.         This section describes the various actions which are undertaken within

  596.         the project, the corresponding approval required for that action and

  597.         those who have binding votes over the action.

  598.       </p>

  599.                                   <table class="ForrestTable" cellspacing="1" cellpadding="4">

  600.               <tr>

  601.                       <th colspan="1" rowspan="1"

  602.       valign="top" align="left">

  603.           Action

  604.       </th>

  605.                           <th colspan="1" rowspan="1"

  606.       valign="top" align="left">

  607.           Description

  608.       </th>

  609.                           <th colspan="1" rowspan="1"

  610.       valign="top" align="left">

  611.           Approval

  612.       </th>

  613.                           <th colspan="1" rowspan="1"

  614.       valign="top" align="left">

  615.           Binding Votes

  616.       </th>

  617.       </tr>

  618.                   <tr>

  619.                       <td colspan="1" rowspan="1"

  620.       valign="top" align="left">

  621.           <strong>Code Change</strong>

  622.       </td>

  623.                           <td colspan="1" rowspan="1"

  624.       valign="top" align="left">

  625.           

  626.             A change made to a codebase of the project and committed

  627.             by a committer. This includes source code, documentation, website

  628.             content, etc.

  629.           

  630.       </td>

  631.                           <td colspan="1" rowspan="1"

  632.       valign="top" align="left">

  633.           

  634.             Lazy approval and then lazy consensus.

  635.           

  636.       </td>

  637.                           <td colspan="1" rowspan="1"

  638.       valign="top" align="left">

  639.           

  640.             Active committers.

  641.           

  642.       </td>

  643.       </tr>

  644.                   <tr>

  645.                       <td colspan="1" rowspan="1"

  646.       valign="top" align="left">

  647.           <strong>Release Plan</strong>

  648.       </td>

  649.                           <td colspan="1" rowspan="1"

  650.       valign="top" align="left">

  651.           

  652.             Defines the timetable and actions for a release. The plan also

  653.             nominates a Release Manager.

  654.           

  655.       </td>

  656.                           <td colspan="1" rowspan="1"

  657.       valign="top" align="left">

  658.           

  659.             Lazy majority

  660.           

  661.       </td>

  662.                           <td colspan="1" rowspan="1"

  663.       valign="top" align="left">

  664.           

  665.             Active committers

  666.           

  667.       </td>

  668.       </tr>

  669.                   <tr>

  670.                       <td colspan="1" rowspan="1"

  671.       valign="top" align="left">

  672.           <strong>Product Release</strong>

  673.       </td>

  674.                           <td colspan="1" rowspan="1"

  675.       valign="top" align="left">

  676.           

  677.             When a release of one of the project's products is ready, a vote is

  678.             required to accept the release as an official release of the

  679.             project.

  680.           

  681.       </td>

  682.                           <td colspan="1" rowspan="1"

  683.       valign="top" align="left">

  684.           

  685.             Lazy Majority

  686.           

  687.       </td>

  688.                           <td colspan="1" rowspan="1"

  689.       valign="top" align="left">

  690.           

  691.             Active PMC members

  692.           

  693.       </td>

  694.       </tr>

  695.                   <tr>

  696.                       <td colspan="1" rowspan="1"

  697.       valign="top" align="left">

  698.           <strong>Adoption of New Codebase</strong>

  699.       </td>

  700.                           <td colspan="1" rowspan="1"

  701.       valign="top" align="left">

  702.           

  703.             <p>

  704.             When the codebase for an existing, released product is to be

  705.             replaced with an alternative codebase. If such a vote fails to

  706.             gain approval, the existing code base will continue.

  707.             </p>

  708. 

  709.             <p>

  710.             This also covers the creation of new sub-projects

  711.             within the project

  712.             </p>

  713.           

  714.       </td>

  715.                           <td colspan="1" rowspan="1"

  716.       valign="top" align="left">

  717.           

  718.             2/3 majority

  719.           

  720.       </td>

  721.                           <td colspan="1" rowspan="1"

  722.       valign="top" align="left">

  723.           

  724.             Active committers

  725.           

  726.       </td>

  727.       </tr>

  728.                   <tr>

  729.                       <td colspan="1" rowspan="1"

  730.       valign="top" align="left">

  731.           <strong>New Committer</strong>

  732.       </td>

  733.                           <td colspan="1" rowspan="1"

  734.       valign="top" align="left">

  735.           

  736.             When a new committer is proposed for the project

  737.           

  738.       </td>

  739.                           <td colspan="1" rowspan="1"

  740.       valign="top" align="left">

  741.           

  742.             Lazy consensus

  743.           

  744.       </td>

  745.                           <td colspan="1" rowspan="1"

  746.       valign="top" align="left">

  747.           

  748.             Active PMC members

  749.           

  750.       </td>

  751.       </tr>

  752.                   <tr>

  753.                       <td colspan="1" rowspan="1"

  754.       valign="top" align="left">

  755.           <strong>New PMC Member</strong>

  756.       </td>

  757.                           <td colspan="1" rowspan="1"

  758.       valign="top" align="left">

  759.           

  760.             When a committer is proposed for the PMC

  761.           

  762.       </td>

  763.                           <td colspan="1" rowspan="1"

  764.       valign="top" align="left">

  765.           

  766.             Lazy consensus

  767.           

  768.       </td>

  769.                           <td colspan="1" rowspan="1"

  770.       valign="top" align="left">

  771.           

  772.             Active PMC members

  773.           

  774.       </td>

  775.       </tr>

  776.                   <tr>

  777.                       <td colspan="1" rowspan="1"

  778.       valign="top" align="left">

  779.           <strong>Committer Removal</strong>

  780.       </td>

  781.                           <td colspan="1" rowspan="1"

  782.       valign="top" align="left">

  783.           

  784.             <p>When removal of commit privileges is sought.</p>

  785.             <p><b>Note: </b> Such actions will also be referred to the ASF

  786.             board by the PMC chair</p>

  787.           

  788.       </td>

  789.                           <td colspan="1" rowspan="1"

  790.       valign="top" align="left">

  791.           

  792.             Consensus

  793.           

  794.       </td>

  795.                           <td colspan="1" rowspan="1"

  796.       valign="top" align="left">

  797.           

  798.             Active PMC members (excluding the committer in question if a

  799.             member of the PMC).

  800.           

  801.       </td>

  802.       </tr>

  803.                   <tr>

  804.                       <td colspan="1" rowspan="1"

  805.       valign="top" align="left">

  806.           <strong>PMC Member Removal</strong>

  807.       </td>

  808.                           <td colspan="1" rowspan="1"

  809.       valign="top" align="left">

  810.           

  811.             <p>When removal of a PMC member is sought.</p>

  812.             <p><b>Note: </b> Such actions will also be referred to the

  813.             ASF board by the PMC chair</p>

  814.           

  815.       </td>

  816.                           <td colspan="1" rowspan="1"

  817.       valign="top" align="left">

  818.           

  819.             Consensus

  820.           

  821.       </td>

  822.                           <td colspan="1" rowspan="1"

  823.       valign="top" align="left">

  824.           

  825.             Active PMC members (excluding the member in question).

  826.           

  827.       </td>

  828.       </tr>

  829.         </table>

  830.                                                     <br/>

  831.       <a name="Voting Timeframes"></a>

  832.       <table border="0" cellspacing="0" cellpadding="2" width="100%">

  833.         <tr><td bgcolor="#4C6C8F">

  834.           <font color="#ffffff" face="arial,helvetica,sanserif">

  835.             <strong>Voting Timeframes</strong>

  836.           </font>

  837.         </td></tr>

  838.       </table>

  839.                         <p>

  840.         Votes are open for a period of 1 week to allow all active voters

  841.         time to consider the vote. Votes relating to code changes are not

  842.         subject to a strict timetable but should be made as timely as possible.

  843.       </p>

  844.                               

  845.   

  846.                     </div>

  847.                 </td><td width="10"><img width="10" height="4" alt="" src="images/spacer.gif"></td>

  848.               </tr>

  849.             </table>

  850.           </td>

  851.         </tr>

  852.       </table>

  853.       <table summary="footer" cellspacing="0" cellpadding="0" width="100%" border="0">

  854.         <tr>

  855.           <td colspan="2" height="1" bgcolor="#4C6C8F"><img height="1" width="1" alt="" src="images/spacer.gif"><a href="images/label.gif"></a><a href="images/page.gif"></a><a href="images/chapter.gif"></a><a href="images/chapter_open.gif"></a><a href="images/current.gif"></a><a href="/favicon.ico"></a></td>

  856.         </tr>

  857.         <tr>

  858.           <td colspan="2" bgcolor="#CFDCED" class="copyright" align="center"><font size="2" face="Arial, Helvetica, Sans-Serif">Copyright &copy;

  859.                     2000-2003&nbsp;The Apache Software Foundation. All rights reserved.<script type="text/javascript" language="JavaScript"><!--

  860.                         document.write(" - "+"Last Published: " + document.lastModified);

  861.                       //  --></script></font></td>

  862.         </tr>

  863.       </table>

  864.     </body>

  865.   </html>

  866. 

  867. 

  868. 

  869. 

  870. 

  871. 

  872. 

  873.
Please read the following content carefully:

Dear OpenI User

Thank you for your continuous support to the Openl Qizhi Community AI Collaboration Platform. In order to protect your usage rights and ensure network security, we updated the Openl Qizhi Community AI Collaboration Platform Usage Agreement in January 2024. The updated agreement specifies that users are prohibited from using intranet penetration tools. After you click "Agree and continue", you can continue to use our services. Thank you for your cooperation and understanding.

For more agreement content, please refer to the《Openl Qizhi Community AI Collaboration Platform Usage Agreement》

Agree and continue
Disagree, exit