source: other-projects/trunk/realistic-books/packages/AntInstaller/web/manual1.7.0/bylaws.html@ 19253

Last change on this file since 19253 was 19253, checked in by davidb, 15 years ago

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