Browse Source

First cut at Ant bylaws. Nothing too strange here, I hope.

git-svn-id: https://svn.apache.org/repos/asf/ant/core/trunk@273627 13f79535-47bb-0310-9956-ffa450edef68
master
Conor MacNeill 22 years ago
parent
commit
e1a43a0384
2 changed files with 370 additions and 0 deletions
  1. +251
    -0
      proposal/ant-site/anakia/docs/bylaws.html
  2. +119
    -0
      proposal/ant-site/anakia/xdocs/bylaws.xml

+ 251
- 0
proposal/ant-site/anakia/docs/bylaws.html View File

@@ -0,0 +1,251 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<!-- Content Stylesheet for Site -->

<!-- start the processing -->
<html>
<!-- GENERATED FILE, DO NOT EDIT, EDIT THE XML FILE IN xdocs INSTEAD! -->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/>
<title>Apache Ant - Apache Ant Project Bylaws</title>
</head>
<body bgcolor="#ffffff" text="#000000" link="#525D76">
<table border="0" width="100%" cellspacing="0">
<!-- TOP IMAGE -->
<tr>
<td colspan="2">
<a href="http://ant.apache.org/"><img src="./images/ant_logo_large.gif" alt="Apache Ant" border="0"/></a>
</td>
</tr>
</table>
<table border="0" width="100%" cellspacing="4">
<tr><td colspan="2">
<hr noshade="" size="1"/>
</td></tr>
<tr>
<!-- LEFT SIDE NAVIGATION -->
<td valign="top" nowrap="true">
<p><strong>Apache Ant</strong></p>
<ul>
<li> <a href="./index.html">Front Page</a>
</li>
<li> <a href="./LICENSE">License</a>
</li>
<li> <a href="./antnews.html">News</a>
</li>
</ul>
<p><strong>Documentation</strong></p>
<ul>
<li> <a href="./manual/index.html">Manual</a>
</li>
<li> <a href="./projects.html">Related Projects</a>
</li>
<li> <a href="./external.html">External Tools and Tasks</a>
</li>
<li> <a href="./resources.html">Resources</a>
</li>
<li> <a href="./faq.html">Ant FAQ</a>
</li>
<li> <a href="./problems.html">Having Problems?</a>
</li>
</ul>
<p><strong>Get Involved</strong></p>
<ul>
<li> <a href="./mail.html">Mailing Lists</a>
</li>
<li> <a href="./cvs.html">CVS Repositories</a>
</li>
<li> <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant">Bug Database</a>
</li>
<li> <a href="http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Ant&bug_severity=Enhancement">Enhancement Requests</a>
</li>
</ul>
<p><strong>Project Managment</strong></p>
<ul>
<li> <a href="./contributors.html">Contributors</a>
</li>
<li> <a href="./mission.html">Mission</a>
</li>
<li> <a href="./guidelines.html">Guidelines Notes</a>
</li>
<li> <a href="./legal.html">Legal</a>
</li>
</ul>
</td>
<td align="left" valign="top">
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Apache Ant Project Bylaws"><strong>Apache Ant Project Bylaws</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
This document defines the bylaws under which the Apache Ant project operates.
It defines the the roles and responsibilities of the project, who may vote,
how conflicts are resolved, etc.
</p>
<p>
Ant is typical of Apache projects in that it operates under a set of principles,
known as the Apache Way. If you are new to Apache, please refer to the
<a href="http://incubator.apache.org">Incubator project</a> for more information on
how Apache projects operate.
</p>
</blockquote>
</td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#525D76">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Roles and Responsibilities"><strong>Roles and Responsibilities</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Project Management Committee"><strong>Project Management Committee</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
The Project Management Committee (PMC) for Apache Ant was created by a resolution of the
board of the Apache Software Foundation (ASF)on 18th Novembr 2002. The PMC is responsible
to the board and the ASF for the management and oversight of the Apache Ant codebase.
The responsibilites of the PMC include
</p>
<ul>
<li>Deciding what is distributed as products of the Apache Ant project. In particular
all releases must be approved by the PMC
</li>
<li>Maintaining the project's shared resources, including the codebase respository,
mailing lists, websites.
</li>
<li>Speaking on behalf of the project.
</li>
<li>Resolving license disputes regarding products of the project
</li>
<li>Nominating new PMC members and committers
</li>
<li>Maintaining these bylaws and other guidelines of the project
</li>
</ul>
<p>
Membership of the PMC is by invitation only and must be approved by a consensus of active PMC members.
A PMC member is considered inactive by their own declaration of by not contributing in any form to the
project for over six months. An inactive member can become active again by reversing whichever condition
made them inactive (i.e., by reversing their earlier declaration or by once again contributing toward the
project's work). Membership can be revoked by a unanimous vote of all the active PMC members other
than the member in question.
</p>
<p>
The chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache
Software Foundation (Vice President, Apache Ant) and has primary responsibility to the board for the
management of the projects within the scope of the Ant PMC. The chair reports to the board quarterly
on developments within the Ant project. The PMC may consider the position of PMC chair annually
and if supported by 3/4 Majority may recommend a new chair to the board. Ultimately, however, it is
the board's responsibility who to appoint as the PMC chair.
</p>
</blockquote>
</td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Committers"><strong>Committers</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
The project's Committers are responsible for the project's technical management. All committers have
write access to the project's source repository. Committers may cast binding votes on any technical
discussion regarding the project.
</p>
<p>
Membership as a Committer is by invitation only and must be approved by consensus of the active
PMC members. A Committer is considered inactive by their own declaration or by not contributing
in any form to the project for over six months. An inactive committer can become active again
by reversing whichever condition made them inactive (i.e., by reversing their earlier declaration
or by once again contributing toward the project's work). Commit access can be revoked by a
unanimous vote of all the active PMC members (except the member in question if they are a PMC member).
</p>
<p>
All Apache committers are required to have a signed Contributor License Agreement (CLA) on file
with the Apache Software Foundation.
</p>
<p>
A committer who makes a sustained contibution to the project will usually be invited to become a member of
the PMC.
</p>
</blockquote>
</td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Developers"><strong>Developers</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
All of the volunteers who are contributing time, code, documentation, or resources to the
Ant Project. A developer that makes sustained, welcome contributions to the project for
over six months is usually invited to become a Committer, though the exact timing of
such invitations depends on many factors.
</p>
</blockquote>
</td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="2" width="100%">
<tr><td bgcolor="#828DA6">
<font color="#ffffff" face="arial,helvetica,sanserif">
<a name="Users"><strong>Users</strong></a>
</font>
</td></tr>
<tr><td>
<blockquote>
<p>
The most important participants in the project are people who use our software. The majority of our
developers start out as users and guide their development efforts from the user's perspective.
</p>
<p>
Users contribute to the Apache projects by providing feedback to developers in the the form of
bug reports and feature suggestions. As well, users participate in the Apache community by
helping other users on mailing lists and user support forums.
</p>
</blockquote>
</td></tr>
</table>
</blockquote>
</td></tr>
</table>
</td>
</tr>

<!-- FOOTER -->
<tr><td colspan="2">
<hr noshade="" size="1"/>
</td></tr>
<tr><td colspan="2">
<div align="center"><font color="#525D76" size="-1"><em>
Copyright &#169; 2000-2002, Apache Software Foundation
</em></font></div>
</td></tr>
</table>
</body>
</html>
<!-- end the processing -->





+ 119
- 0
proposal/ant-site/anakia/xdocs/bylaws.xml View File

@@ -0,0 +1,119 @@
<?xml version="1.0"?>
<document>

<properties>
<title>Apache Ant Project Bylaws</title>
</properties>

<body>
<section name="Apache Ant Project Bylaws">

<p>
This document defines the bylaws under which the Apache Ant project operates.
It defines the the roles and responsibilities of the project, who may vote,
how conflicts are resolved, etc.
</p>

<p>
Ant is typical of Apache projects in that it operates under a set of principles,
known as the Apache Way. If you are new to Apache, please refer to the
<a href="http://incubator.apache.org">Incubator project</a> for more information on
how Apache projects operate.
</p>

</section>

<section name="Roles and Responsibilities">
<subsection name="Project Management Committee">
<p>
The Project Management Committee (PMC) for Apache Ant was created by a resolution of the
board of the Apache Software Foundation (ASF)on 18th Novembr 2002. The PMC is responsible
to the board and the ASF for the management and oversight of the Apache Ant codebase.
The responsibilites of the PMC include
</p>

<ul>
<li>Deciding what is distributed as products of the Apache Ant project. In particular
all releases must be approved by the PMC
</li>
<li>Maintaining the project's shared resources, including the codebase respository,
mailing lists, websites.
</li>
<li>Speaking on behalf of the project.
</li>
<li>Resolving license disputes regarding products of the project
</li>
<li>Nominating new PMC members and committers
</li>
<li>Maintaining these bylaws and other guidelines of the project
</li>
</ul>

<p>
Membership of the PMC is by invitation only and must be approved by a consensus of active PMC members.
A PMC member is considered inactive by their own declaration of by not contributing in any form to the
project for over six months. An inactive member can become active again by reversing whichever condition
made them inactive (i.e., by reversing their earlier declaration or by once again contributing toward the
project's work). Membership can be revoked by a unanimous vote of all the active PMC members other
than the member in question.
</p>

<p>
The chair of the PMC is appointed by the ASF board. The chair is an office holder of the Apache
Software Foundation (Vice President, Apache Ant) and has primary responsibility to the board for the
management of the projects within the scope of the Ant PMC. The chair reports to the board quarterly
on developments within the Ant project. The PMC may consider the position of PMC chair annually
and if supported by 3/4 Majority may recommend a new chair to the board. Ultimately, however, it is
the board's responsibility who to appoint as the PMC chair.
</p>
</subsection>
<subsection name="Committers">
<p>
The project's Committers are responsible for the project's technical management. All committers have
write access to the project's source repository. Committers may cast binding votes on any technical
discussion regarding the project.
</p>

<p>
Membership as a Committer is by invitation only and must be approved by consensus of the active
PMC members. A Committer is considered inactive by their own declaration or by not contributing
in any form to the project for over six months. An inactive committer can become active again
by reversing whichever condition made them inactive (i.e., by reversing their earlier declaration
or by once again contributing toward the project's work). Commit access can be revoked by a
unanimous vote of all the active PMC members (except the member in question if they are a PMC member).
</p>

<p>
All Apache committers are required to have a signed Contributor License Agreement (CLA) on file
with the Apache Software Foundation.
</p>

<p>
A committer who makes a sustained contibution to the project will usually be invited to become a member of
the PMC.
</p>
</subsection>
<subsection name="Developers">
<p>
All of the volunteers who are contributing time, code, documentation, or resources to the
Ant Project. A developer that makes sustained, welcome contributions to the project for
over six months is usually invited to become a Committer, though the exact timing of
such invitations depends on many factors.
</p>
</subsection>
<subsection name="Users">
<p>
The most important participants in the project are people who use our software. The majority of our
developers start out as users and guide their development efforts from the user's perspective.
</p>

<p>
Users contribute to the Apache projects by providing feedback to developers in the the form of
bug reports and feature suggestions. As well, users participate in the Apache community by
helping other users on mailing lists and user support forums.
</p>

</subsection>
</section>
</body>
</document>

Loading…
Cancel
Save