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 33 kB

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