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

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