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

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