source: release-kits/lirk3/bin/ant-installer/web/manual1.6.2/bylaws.html@ 14982

Last change on this file since 14982 was 14982, checked in by oranfry, 16 years ago

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