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

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