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.

bylaws.html 37 kB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874
  1. <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
  2. <html>
  3. <!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
  4. <head>
  5. <META http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  6. <title>Apache Ant - Apache Ant Project Bylaws</title>
  7. <link type="text/css" href="page.css" rel="stylesheet">
  8. </head>
  9. <body text="#000000" bgcolor="#ffffff">
  10. <table summary="navigation path" width="100%" border="0" cellpadding="0" cellspacing="0">
  11. <tr>
  12. <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>
  13. </tr>
  14. <tr>
  15. <td bgcolor="#4C6C8F" height="2"><img height="2" width="2" alt="" border="0" src="images/spacer.gif"></td>
  16. </tr>
  17. </table>
  18. <table summary="header with logos" width="100%" border="0" cellpadding="0" cellspacing="0">
  19. <tr>
  20. <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">
  21. <form target="_blank" onsubmit="q.value = query.value + ' site:ant.apache.org'" action="http://www.google.com/search" method="get">
  22. <table summary="search" border="0" cellspacing="0" cellpadding="0" bgcolor="#4C6C8F">
  23. <tr>
  24. <td colspan="3"><img height="10" width="1" alt="" src="images/spacer.gif"></td>
  25. </tr>
  26. <tr>
  27. <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">
  28. <br>
  29. <font face="Arial, Helvetica, Sans-serif" size="2" color="white">
  30. the Apache Ant site
  31. </font></td><td><img height="1" width="1" alt="" src="images/spacer.gif"></td>
  32. </tr>
  33. <tr>
  34. <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>
  35. </tr>
  36. </table>
  37. </form>
  38. </td><td bgcolor="#294563"><img height="10" width="10" alt="" src="images/spacer.gif"></td>
  39. </tr>
  40. <tr>
  41. <td valign="bottom" bgcolor="#294563" colspan="2">
  42. <div class="tab">
  43. <table summary="tab bar" border="0" cellpadding="0" cellspacing="0">
  44. <tr>
  45. <td width="8"><img alt="" height="8" width="8" src="images/spacer.gif"></td><td valign="bottom">
  46. <table summary="selected tab" border="0" cellpadding="0" cellspacing="0">
  47. <tr>
  48. <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>
  49. </tr>
  50. </table>
  51. </td>
  52. </tr>
  53. </table>
  54. </div>
  55. </td><td bgcolor="#294563"><img alt="" width="1" height="1" src="images/spacer.gif"></td>
  56. </tr>
  57. <tr>
  58. <td bgcolor="#4C6C8F" colspan="4"><img width="1" height="10" alt="" src="images/spacer.gif"></td>
  59. </tr>
  60. </table>
  61. <table summary="page content" bgcolor="#ffffff" width="100%" border="0" cellpadding="0" cellspacing="0">
  62. <tr>
  63. <td valign="top">
  64. <table summary="menu" border="0" cellspacing="0" cellpadding="0">
  65. <tr>
  66. <td rowspan="3" valign="top">
  67. <table summary="blue line" border="0" cellpadding="0" cellspacing="0">
  68. <tr>
  69. <td bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  70. </tr>
  71. <tr>
  72. <td bgcolor="#CFDCED"><font color="#4C6C8F" size="4" face="Arial, Helvetica, Sans-serif">&nbsp;</font></td>
  73. </tr>
  74. <tr>
  75. <td bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  76. </tr>
  77. </table>
  78. </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">
  79. <div class="menu"><ul>
  80. <li><font color="#CFDCED">Apache Ant</font>
  81. <ul>
  82. <li>
  83. <a href="./index.html">Welcome</a>
  84. </li>
  85. <li>
  86. <a href="./license.html">License</a>
  87. </li>
  88. <li>
  89. <a href="./antnews.html">News</a>
  90. </li>
  91. </ul>
  92. </li>
  93. <li><font color="#CFDCED">Documentation</font>
  94. <ul>
  95. <li>
  96. <a href="./manual/index.html">Manual</a>
  97. </li>
  98. <li>
  99. <a href="./projects.html">Related Projects</a>
  100. </li>
  101. <li>
  102. <a href="./external.html">External Tools and Tasks</a>
  103. </li>
  104. <li>
  105. <a href="./resources.html">Resources</a>
  106. </li>
  107. <li>
  108. <a href="./faq.html">Frequently Asked Questions</a>
  109. </li>
  110. <li>
  111. <a href="./problems.html">Having Problems?</a>
  112. </li>
  113. </ul>
  114. </li>
  115. <li><font color="#CFDCED">Download</font>
  116. <ul>
  117. <li>
  118. <a href="./bindownload.cgi">Binary Distributions</a>
  119. </li>
  120. <li>
  121. <a href="./srcdownload.cgi">Source Distributions</a>
  122. </li>
  123. </ul>
  124. </li>
  125. <li><font color="#CFDCED">Get Involved</font>
  126. <ul>
  127. <li>
  128. <a href="./mail.html">Mailing Lists</a>
  129. </li>
  130. <li>
  131. <a href="./cvs.html">CVS Repositories</a>
  132. </li>
  133. <li>
  134. <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
  135. </li>
  136. <li>
  137. <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant&amp;bug_severity=Enhancement">Enhancement Requests</a>
  138. </li>
  139. </ul>
  140. </li>
  141. <li><font color="#CFDCED">Project Management</font>
  142. <ul>
  143. <li>
  144. <a href="./contributors.html">Contributors</a>
  145. </li>
  146. <li>
  147. <a href="./mission.html">Apache Ant Mission</a>
  148. </li>
  149. <li>
  150. <a href="./guidelines.html">Project Guidelines</a>
  151. </li>
  152. <li>
  153. <a href="./legal.html">Legal</a>
  154. </li>
  155. </ul>
  156. </li>
  157. </ul></div>
  158. </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>
  159. </tr>
  160. <tr>
  161. <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>
  162. </tr>
  163. <tr>
  164. <td height="1" bgcolor="#294563"><img width="1" height="1" alt="" src="images/spacer.gif"></td>
  165. </tr>
  166. </table>
  167. </td><td valign="top" width="100%">
  168. <table summary="content" width="100%" border="0" cellpadding="0" cellspacing="0">
  169. <tr>
  170. <td colspan="4" bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  171. </tr>
  172. <tr>
  173. <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">
  174. &nbsp;
  175. </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">
  176. &nbsp;
  177. </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>
  178. </tr>
  179. <tr>
  180. <td colspan="4" bgcolor="#294563"><img width="10" height="1" alt="" src="images/spacer.gif"></td>
  181. </tr>
  182. <tr>
  183. <td align="left" width="10"><img width="10" height="1" alt="" src="images/spacer.gif"></td><td align="left" width="100%">
  184. <div class="content">
  185. <table class="title">
  186. <tr>
  187. <td valign="middle">
  188. <h1>Apache Ant Project Bylaws</h1>
  189. </td>
  190. </tr>
  191. </table>
  192. <br/>
  193. <table class="nowrap" border="0" cellspacing="0" cellpadding="2" width="100%">
  194. <tr><td bgcolor="#294563"><font color="#ffffff"><a name="Apache Ant Project Bylaws"><strong>Apache Ant Project Bylaws</strong></a></font></td></tr>
  195. </table>
  196. <p>
  197. This document defines the bylaws under which the Apache Ant project
  198. operates. It defines the roles and responsibilities of the
  199. project, who may vote, how voting works, how conflicts are resolved,
  200. etc.
  201. </p>
  202. <p>
  203. Ant is a project of the
  204. <a href="http://www.apache.org/foundation/">Apache Software
  205. Foundation</a>. The foundation holds the copyright on Apache
  206. code including the code in the Ant codebase. The
  207. <a href="http://www.apache.org/foundation/faq.html">foundation FAQ</a>
  208. explains the operation and background of the foundation.
  209. </p>
  210. <p>
  211. Ant is typical of Apache projects in that it operates under a set of
  212. principles, known collectively as the "Apache Way". If you are
  213. new to Apache development, please refer to the
  214. <a href="http://incubator.apache.org">Incubator project</a>
  215. for more information on how Apache projects operate. <b>Note:</b> the
  216. incubator project has only been recently set up and does not yet explain
  217. the Apache Way in great detail.
  218. </p>
  219. <ul>
  220. <li><a href="#Roles and Responsibilities">Roles and Responsibilities</a></li>
  221. <li><a href="#Decision Making">How decisions are made</a></li>
  222. </ul>
  223. <br/>
  224. <table class="nowrap" border="0" cellspacing="0" cellpadding="2" width="100%">
  225. <tr><td bgcolor="#294563"><font color="#ffffff"><a name="Roles and Responsibilities"><strong>Roles and Responsibilities</strong></a></font></td></tr>
  226. </table>
  227. <p>
  228. Apache projects define a set of roles with associated rights and
  229. responsibilities. These roles govern what tasks an individual may perform
  230. within the project. The roles are defined in the following sections
  231. </p>
  232. <ul>
  233. <li><a href="#Users">Users</a></li>
  234. <li><a href="#Developers">Developers</a></li>
  235. <li><a href="#Committers">Committers</a></li>
  236. <li><a href="#Project Management Committee">
  237. Project Management Committee (PMC)</a>
  238. </li>
  239. </ul>
  240. <br/>
  241. <a name="Users"></a>
  242. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  243. <tr><td bgcolor="#4C6C8F">
  244. <font color="#ffffff" face="arial,helvetica,sanserif">
  245. <strong>Users</strong>
  246. </font>
  247. </td></tr>
  248. </table>
  249. <p>
  250. The most important participants in the project are people who use our
  251. software. The majority of our developers start out as users and guide
  252. their development efforts from the user's perspective.
  253. </p>
  254. <p>
  255. Users contribute to the Apache projects by providing feedback to
  256. developers in the form of bug reports and feature suggestions. As
  257. well, users participate in the Apache community by helping other users
  258. on mailing lists and user support forums.
  259. </p>
  260. <br/>
  261. <a name="Developers"></a>
  262. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  263. <tr><td bgcolor="#4C6C8F">
  264. <font color="#ffffff" face="arial,helvetica,sanserif">
  265. <strong>Developers</strong>
  266. </font>
  267. </td></tr>
  268. </table>
  269. <p>
  270. All of the volunteers who are contributing time, code, documentation,
  271. or resources to the Ant Project. A developer that makes sustained,
  272. welcome contributions to the project may be invited to become a
  273. Committer, though the exact timing of such invitations depends on many
  274. factors.
  275. </p>
  276. <br/>
  277. <a name="Committers"></a>
  278. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  279. <tr><td bgcolor="#4C6C8F">
  280. <font color="#ffffff" face="arial,helvetica,sanserif">
  281. <strong>Committers</strong>
  282. </font>
  283. </td></tr>
  284. </table>
  285. <p>
  286. The project's Committers are responsible for the project's technical
  287. management. All committers have write access to the project's source
  288. repositories. Committers may cast binding votes on any technical
  289. discussion regarding the project.
  290. </p>
  291. <p>
  292. Committer access is by invitation only and must be approved by lazy
  293. consensus of the active PMC members. A Committer is considered emeritus
  294. by their own declaration or by not contributing in any form to the
  295. project for over six months. An emeritus committer may request
  296. reinstatement of commit access from the PMC. Such reinstatement is
  297. subject to lazy consensus of active PMC members.
  298. </p>
  299. <p>
  300. Commit access can be revoked by a unanimous vote of all the active
  301. PMC members (except the committer in question if they are also a PMC member).
  302. </p>
  303. <p>
  304. All Apache committers are required to have a signed Contributor License
  305. Agreement (CLA) on file with the Apache Software Foundation. There is a
  306. <a href="http://www.apache.org/dev/committers.html">Committer FAQ</a>
  307. which provides more details on the requirements for Committers
  308. </p>
  309. <p>
  310. A committer who makes a sustained contribution to the project may be
  311. invited to become a member of the PMC. The form of contribution is
  312. not limited to code. It can also include code review, helping out
  313. users on the mailing lists, documentation, etc.
  314. </p>
  315. <br/>
  316. <a name="Project Management Committee"></a>
  317. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  318. <tr><td bgcolor="#4C6C8F">
  319. <font color="#ffffff" face="arial,helvetica,sanserif">
  320. <strong>Project Management Committee</strong>
  321. </font>
  322. </td></tr>
  323. </table>
  324. <p>
  325. The Project Management Committee (PMC) for Apache Ant was created by a
  326. <a href="mission.html">resolution</a> of the board of the Apache
  327. Software Foundation on 18<sup>th</sup> November 2002. The PMC is
  328. responsible to the board and the ASF for the management and oversight
  329. of the Apache Ant codebase. The responsibilities of the PMC include
  330. </p>
  331. <ul>
  332. <li>Deciding what is distributed as products of the Apache Ant project.
  333. In particular all releases must be approved by the PMC
  334. </li>
  335. <li>Maintaining the project's shared resources, including the codebase
  336. repository, mailing lists, websites.
  337. </li>
  338. <li>Speaking on behalf of the project.
  339. </li>
  340. <li>Resolving license disputes regarding products of the project
  341. </li>
  342. <li>Nominating new PMC members and committers
  343. </li>
  344. <li>Maintaining these bylaws and other guidelines of the project
  345. </li>
  346. </ul>
  347. <p>
  348. Membership of the PMC is by invitation only and must be approved by a
  349. lazy consensus of active PMC members. A PMC member is considered
  350. "emeritus" by their own declaration or by not contributing in
  351. any form to the project for over six months. An emeritus member may
  352. request reinstatement to the PMC. Such reinstatement is subject to lazy
  353. consensus of the active PMC members. Membership of the PMC can be
  354. revoked by an unanimous vote of all the active PMC members other than
  355. the member in question.
  356. </p>
  357. <p>
  358. The chair of the PMC is appointed by the ASF board. The chair is an
  359. office holder of the Apache Software Foundation (Vice President,
  360. Apache Ant) and has primary responsibility to the board for the
  361. management of the projects within the scope of the Ant PMC. The chair
  362. reports to the board quarterly on developments within the Ant project.
  363. The PMC may consider the position of PMC chair annually and if
  364. supported by 2/3 Majority may recommend a new chair to the board.
  365. Ultimately, however, it is the board's responsibility who it chooses
  366. to appoint as the PMC chair.
  367. </p>
  368. <br/>
  369. <table class="nowrap" border="0" cellspacing="0" cellpadding="2" width="100%">
  370. <tr><td bgcolor="#294563"><font color="#ffffff"><a name="Decision Making"><strong>Decision Making</strong></a></font></td></tr>
  371. </table>
  372. <p>
  373. Within the Ant project, different types of decisions require different
  374. forms of approval. For example, the
  375. <a href="#Roles and Responsibilities">previous section</a> describes
  376. several decisions which require "lazy consensus" approval. This
  377. section defines how voting is performed, the types of approvals, and which
  378. types of decision require which type of approval.
  379. </p>
  380. <br/>
  381. <a name="Voting"></a>
  382. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  383. <tr><td bgcolor="#4C6C8F">
  384. <font color="#ffffff" face="arial,helvetica,sanserif">
  385. <strong>Voting</strong>
  386. </font>
  387. </td></tr>
  388. </table>
  389. <p>
  390. Decisions regarding the project are made by votes on the primary project
  391. development mailing list (ant-dev@jakarta.apache.org). Where necessary,
  392. PMC voting may take place on the private Ant PMC mailing list.
  393. Votes are clearly indicated by subject line starting with [VOTE] or
  394. [PMC-VOTE]. Votes may contain multiple items for approval and these
  395. should be clearly separated. Voting is carried out by replying to the
  396. vote mail. Voting may take four flavours
  397. </p>
  398. <table class="ForrestTable" cellspacing="1" cellpadding="4">
  399. <tr>
  400. <td colspan="1" rowspan="1"
  401. valign="top" align="left">
  402. <strong>+1</strong>
  403. </td>
  404. <td colspan="1" rowspan="1"
  405. valign="top" align="left">
  406. "Yes," "Agree," or "the action should be
  407. performed." In general, this vote also indicates a willingness
  408. on the behalf of the voter in "making it happen"
  409. </td>
  410. </tr>
  411. <tr>
  412. <td colspan="1" rowspan="1"
  413. valign="top" align="left">
  414. <strong>+0</strong>
  415. </td>
  416. <td colspan="1" rowspan="1"
  417. valign="top" align="left">
  418. This vote indicates a willingness for the action under
  419. consideration to go ahead. The voter, however will not be able
  420. to help.
  421. </td>
  422. </tr>
  423. <tr>
  424. <td colspan="1" rowspan="1"
  425. valign="top" align="left">
  426. <strong>-0</strong>
  427. </td>
  428. <td colspan="1" rowspan="1"
  429. valign="top" align="left">
  430. This vote indicates that the voter does not, in general, agree with
  431. the proposed action but is not concerned enough to prevent the
  432. action going ahead.
  433. </td>
  434. </tr>
  435. <tr>
  436. <td colspan="1" rowspan="1"
  437. valign="top" align="left">
  438. <strong>-1</strong>
  439. </td>
  440. <td colspan="1" rowspan="1"
  441. valign="top" align="left">
  442. This is a negative vote. On issues where consensus is required,
  443. this vote counts as a <strong>veto</strong>. All vetoes must
  444. contain an explanation of why the veto is appropriate. Vetoes with
  445. no explanation are void. It may also be appropriate for a -1 vote
  446. to include an alternative course of action.
  447. </td>
  448. </tr>
  449. </table>
  450. <p>
  451. All participants in the Ant project are encouraged to show their
  452. agreement with or against a particular action by voting. For technical
  453. decisions, only the votes of active committers are binding. Non binding
  454. votes are still useful for those with binding votes to understand the
  455. perception of an action in the wider Ant community. For PMC decisions,
  456. only the votes of PMC members are binding.
  457. </p>
  458. <p>
  459. Voting can also be applied to changes made to the Ant codebase. These
  460. typically take the form of a veto (-1) in reply to the commit message
  461. sent when the commit is made.
  462. </p>
  463. <br/>
  464. <a name="Approvals"></a>
  465. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  466. <tr><td bgcolor="#4C6C8F">
  467. <font color="#ffffff" face="arial,helvetica,sanserif">
  468. <strong>Approvals</strong>
  469. </font>
  470. </td></tr>
  471. </table>
  472. <p>
  473. These are the types of approvals that can be sought. Different actions
  474. require different types of approvals
  475. </p>
  476. <table class="ForrestTable" cellspacing="1" cellpadding="4">
  477. <tr>
  478. <td colspan="1" rowspan="1"
  479. valign="top" align="left">
  480. <strong>Consensus</strong>
  481. </td>
  482. <td colspan="1" rowspan="1"
  483. valign="top" align="left">
  484. For this to pass, all voters with binding votes must vote and there
  485. can be no binding vetoes (-1). Consensus votes are rarely required
  486. due to the impracticality of getting all eligible voters to cast a
  487. vote.
  488. </td>
  489. </tr>
  490. <tr>
  491. <td colspan="1" rowspan="1"
  492. valign="top" align="left">
  493. <strong>Lazy Consensus</strong>
  494. </td>
  495. <td colspan="1" rowspan="1"
  496. valign="top" align="left">
  497. Lazy consensus requires 3 binding +1 votes and no binding vetoes.
  498. </td>
  499. </tr>
  500. <tr>
  501. <td colspan="1" rowspan="1"
  502. valign="top" align="left">
  503. <strong>Lazy Majority</strong>
  504. </td>
  505. <td colspan="1" rowspan="1"
  506. valign="top" align="left">
  507. A lazy majority vote requires 3 binding +1 votes and more binding +1
  508. votes that -1 votes.
  509. </td>
  510. </tr>
  511. <tr>
  512. <td colspan="1" rowspan="1"
  513. valign="top" align="left">
  514. <strong>Lazy Approval</strong>
  515. </td>
  516. <td colspan="1" rowspan="1"
  517. valign="top" align="left">
  518. An action with lazy approval is implicitly allowed unless a -1 vote
  519. is received, at which time, depending on the type of action, either
  520. lazy majority or lazy consensus approval must be obtained.
  521. </td>
  522. </tr>
  523. <tr>
  524. <td colspan="1" rowspan="1"
  525. valign="top" align="left">
  526. <strong>2/3 Majority</strong>
  527. </td>
  528. <td colspan="1" rowspan="1"
  529. valign="top" align="left">
  530. Some actions require a 2/3 majority of active committers or PMC
  531. members to pass. Such actions typically affect the foundation
  532. of the project (e.g. adopting a new codebase to replace an existing
  533. product). The higher threshold is designed to ensure such changes
  534. are strongly supported. To pass this vote requires at least 2/3 of
  535. binding vote holders to vote +1
  536. </td>
  537. </tr>
  538. </table>
  539. <br/>
  540. <a name="Vetoes"></a>
  541. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  542. <tr><td bgcolor="#4C6C8F">
  543. <font color="#ffffff" face="arial,helvetica,sanserif">
  544. <strong>Vetoes</strong>
  545. </font>
  546. </td></tr>
  547. </table>
  548. <p>
  549. A valid, binding veto cannot be overruled. If a veto is cast, it must be
  550. accompanied by a valid reason explaining the reasons for the veto. The
  551. validity of a veto, if challenged, can be confirmed by anyone who has
  552. a binding vote. This does not necessarily signify agreement with the
  553. veto - merely that the veto is valid.
  554. </p>
  555. <p>
  556. If you disagree with a valid veto, you must lobby the person casting
  557. the veto to withdraw their veto. If a veto is not withdrawn, the action
  558. that has been vetoed must be reversed in a timely manner.
  559. </p>
  560. <br/>
  561. <a name="Actions"></a>
  562. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  563. <tr><td bgcolor="#4C6C8F">
  564. <font color="#ffffff" face="arial,helvetica,sanserif">
  565. <strong>Actions</strong>
  566. </font>
  567. </td></tr>
  568. </table>
  569. <p>
  570. This section describes the various actions which are undertaken within
  571. the project, the corresponding approval required for that action and
  572. those who have binding votes over the action.
  573. </p>
  574. <table class="ForrestTable" cellspacing="1" cellpadding="4">
  575. <tr>
  576. <th colspan="1" rowspan="1"
  577. valign="top" align="left">
  578. Action
  579. </th>
  580. <th colspan="1" rowspan="1"
  581. valign="top" align="left">
  582. Description
  583. </th>
  584. <th colspan="1" rowspan="1"
  585. valign="top" align="left">
  586. Approval
  587. </th>
  588. <th colspan="1" rowspan="1"
  589. valign="top" align="left">
  590. Binding Votes
  591. </th>
  592. </tr>
  593. <tr>
  594. <td colspan="1" rowspan="1"
  595. valign="top" align="left">
  596. <strong>Code Change</strong>
  597. </td>
  598. <td colspan="1" rowspan="1"
  599. valign="top" align="left">
  600. A change made to a codebase of the project and committed
  601. by a committer. This includes source code, documentation, website
  602. content, etc.
  603. </td>
  604. <td colspan="1" rowspan="1"
  605. valign="top" align="left">
  606. Lazy approval and then lazy consensus.
  607. </td>
  608. <td colspan="1" rowspan="1"
  609. valign="top" align="left">
  610. Active committers.
  611. </td>
  612. </tr>
  613. <tr>
  614. <td colspan="1" rowspan="1"
  615. valign="top" align="left">
  616. <strong>Release Plan</strong>
  617. </td>
  618. <td colspan="1" rowspan="1"
  619. valign="top" align="left">
  620. Defines the timetable and actions for a release. The plan also
  621. nominates a Release Manager.
  622. </td>
  623. <td colspan="1" rowspan="1"
  624. valign="top" align="left">
  625. Lazy majority
  626. </td>
  627. <td colspan="1" rowspan="1"
  628. valign="top" align="left">
  629. Active committers
  630. </td>
  631. </tr>
  632. <tr>
  633. <td colspan="1" rowspan="1"
  634. valign="top" align="left">
  635. <strong>Product Release</strong>
  636. </td>
  637. <td colspan="1" rowspan="1"
  638. valign="top" align="left">
  639. When a release of one of the project's products is ready, a vote is
  640. required to accept the release as an official release of the
  641. project.
  642. </td>
  643. <td colspan="1" rowspan="1"
  644. valign="top" align="left">
  645. Lazy Majority
  646. </td>
  647. <td colspan="1" rowspan="1"
  648. valign="top" align="left">
  649. Active PMC members
  650. </td>
  651. </tr>
  652. <tr>
  653. <td colspan="1" rowspan="1"
  654. valign="top" align="left">
  655. <strong>Adoption of New Codebase</strong>
  656. </td>
  657. <td colspan="1" rowspan="1"
  658. valign="top" align="left">
  659. <p>
  660. When the codebase for an existing, released product is to be
  661. replaced with an alternative codebase. If such a vote fails to
  662. gain approval, the existing code base will continue.
  663. </p>
  664. <p>
  665. This also covers the creation of new sub-projects
  666. within the project
  667. </p>
  668. </td>
  669. <td colspan="1" rowspan="1"
  670. valign="top" align="left">
  671. 2/3 majority
  672. </td>
  673. <td colspan="1" rowspan="1"
  674. valign="top" align="left">
  675. Active committers
  676. </td>
  677. </tr>
  678. <tr>
  679. <td colspan="1" rowspan="1"
  680. valign="top" align="left">
  681. <strong>New Committer</strong>
  682. </td>
  683. <td colspan="1" rowspan="1"
  684. valign="top" align="left">
  685. When a new committer is proposed for the project
  686. </td>
  687. <td colspan="1" rowspan="1"
  688. valign="top" align="left">
  689. Lazy consensus
  690. </td>
  691. <td colspan="1" rowspan="1"
  692. valign="top" align="left">
  693. Active PMC members
  694. </td>
  695. </tr>
  696. <tr>
  697. <td colspan="1" rowspan="1"
  698. valign="top" align="left">
  699. <strong>New PMC Member</strong>
  700. </td>
  701. <td colspan="1" rowspan="1"
  702. valign="top" align="left">
  703. When a committer is proposed for the PMC
  704. </td>
  705. <td colspan="1" rowspan="1"
  706. valign="top" align="left">
  707. Lazy consensus
  708. </td>
  709. <td colspan="1" rowspan="1"
  710. valign="top" align="left">
  711. Active PMC members
  712. </td>
  713. </tr>
  714. <tr>
  715. <td colspan="1" rowspan="1"
  716. valign="top" align="left">
  717. <strong>Committer Removal</strong>
  718. </td>
  719. <td colspan="1" rowspan="1"
  720. valign="top" align="left">
  721. <p>When removal of commit privileges is sought.</p>
  722. <p><b>Note: </b> Such actions will also be referred to the ASF
  723. board by the PMC chair</p>
  724. </td>
  725. <td colspan="1" rowspan="1"
  726. valign="top" align="left">
  727. Consensus
  728. </td>
  729. <td colspan="1" rowspan="1"
  730. valign="top" align="left">
  731. Active PMC members (excluding the committer in question if a
  732. member of the PMC).
  733. </td>
  734. </tr>
  735. <tr>
  736. <td colspan="1" rowspan="1"
  737. valign="top" align="left">
  738. <strong>PMC Member Removal</strong>
  739. </td>
  740. <td colspan="1" rowspan="1"
  741. valign="top" align="left">
  742. <p>When removal of a PMC member is sought.</p>
  743. <p><b>Note: </b> Such actions will also be referred to the
  744. ASF board by the PMC chair</p>
  745. </td>
  746. <td colspan="1" rowspan="1"
  747. valign="top" align="left">
  748. Consensus
  749. </td>
  750. <td colspan="1" rowspan="1"
  751. valign="top" align="left">
  752. Active PMC members (excluding the member in question).
  753. </td>
  754. </tr>
  755. </table>
  756. <br/>
  757. <a name="Voting Timeframes"></a>
  758. <table border="0" cellspacing="0" cellpadding="2" width="100%">
  759. <tr><td bgcolor="#4C6C8F">
  760. <font color="#ffffff" face="arial,helvetica,sanserif">
  761. <strong>Voting Timeframes</strong>
  762. </font>
  763. </td></tr>
  764. </table>
  765. <p>
  766. Votes are open for a period of 1 week to allow all active voters
  767. time to consider the vote. Votes relating to code changes are not
  768. subject to a strict timetable but should be made as timely as possible.
  769. </p>
  770. </div>
  771. </td><td width="10"><img width="10" height="4" alt="" src="images/spacer.gif"></td>
  772. </tr>
  773. </table>
  774. </td>
  775. </tr>
  776. </table>
  777. <table summary="footer" cellspacing="0" cellpadding="0" width="100%" border="0">
  778. <tr>
  779. <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>
  780. </tr>
  781. <tr>
  782. <td colspan="2" bgcolor="#CFDCED" class="copyright" align="center"><font size="2" face="Arial, Helvetica, Sans-Serif">Copyright &copy;
  783. 2000-2003&nbsp;The Apache Software Foundation. All rights reserved.<script type="text/javascript" language="JavaScript"><!--
  784. document.write(" - "+"Last Published: " + document.lastModified);
  785. // --></script></font></td>
  786. </tr>
  787. </table>
  788. </body>
  789. </html>