diff --git a/docs/ant15_todo.html b/docs/ant15_todo.html deleted file mode 100644 index 06951f6fb..000000000 --- a/docs/ant15_todo.html +++ /dev/null @@ -1,606 +0,0 @@ - - - - - - - - Apache Ant - Ant 1.5 Release To-Do List - - - - - - - - -
- - - - - - -
Apache Ant siteApache Ant logo -
- - - - - - - - - - - - - - -
- - - - -
- the Apache Ant site -
-
-
-
- -
- - - - - -
- - - - -
Home
-
- - - - -
Projects
-
-
- -
- - -
 
-
-
-

Ant 1.5 Release To-Do List

-

- - Ant 1.5 Release To-Do List -

-

- - Open -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Item - - Details - - Assigned -
- Bugzilla bugs under 30 - - or at least address most of them in some way - - All Committers -
- Document Path datatype - - It's documented, but more hidden than the other types - - Erik -
- Novell NetWare support - -   - - Jeff Tulley -
- XMLCatalog more integrated - - Several tasks could still use XMLCatalog integration - -   -
- Make default excludes customizable - - With the setting of an ant.default.excludes property? - - Erik -
- Fully functional on Java 1.4 - - Fix outstanding java1.4 defects, maybe add an - assertions datatype for java and other tasks (junit?) - which lets people turn on asserts. - - - Steve + any other help he can get -
-

- - Done -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Item - - Details - - Assigned -
- Selectors - -   - - Bruce -
- Extension utilities - - Port across task that prints out details of extensions for - a certain library/jar, or all jars in a path. Port across task - that generates a manifest (including dependencies and extension - specification) based on a set of jars in path. Port across task - that checks that the list of pre-req extensions are present in - path. - - Peter -
- XmlLogger implements BuildLogger - - Its currently a BuildListener, lets remove the confusion - - Erik -
- Dotnet library tweaks - - update to release, add uptodateness, add a web service - import (for Axis interop testing) - - Steve, in a really long meeting -
- compiler attribute for rmic - -   - - Stefan -
- PGP signing task if possible - - Not done, but deemed impossible - at least in the 1.5 - time frame. - - Stefan -
- JUnit's System.err/.out handling - - showoutput attribute has been added - doesn't work in - some cases yet (same reason as bug PR 7980) - - Stefan -
- Base compiler command line switches on the selected - compiler, not the current JDK - -   - - Stefan -
- <input> - -   - - Stefan -
- Make javadoc a real directory based task - -   - - Stefan -
-

- - Bug Reports Short-Cuts -

-

Note: You can sort the report results by clicking on the column-headings.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- New|Assigned|Reopened Bug Reports: -
- All - -
- - minus Enhancements - -
- New|Assigned|Reopened Bug Reports by Component: -
- Build Process - -
- - minus Enhancements - -
- Core - -
- - minus Enhancements - -
- Core Tasks - -
- - minus Enhancements - -
- Documentation - -
- - minus Enhancements - -
- Optional Tasks - -
- - minus Enhancements - -
- Other - -
- - minus Enhancements - -
- Wrapper Scripts - -
- - minus Enhancements - -
- -
-
- - - - - - - - - - - - - diff --git a/proposal/ant-site/anakia/docs/breadcrumbs.js b/proposal/ant-site/anakia/docs/breadcrumbs.js deleted file mode 100644 index f03dabb45..000000000 --- a/proposal/ant-site/anakia/docs/breadcrumbs.js +++ /dev/null @@ -1,257 +0,0 @@ -/* - - ============================================================================ - The Apache Software License, Version 1.1 - ============================================================================ - - Copyright (C) 2002 The Apache Software Foundation. All rights reserved. - - Redistribution and use in source and binary forms, with or without modifica- - tion, are permitted provided that the following conditions are met: - - 1. Redistributions of source code must retain the above copyright notice, - this list of conditions and the following disclaimer. - - 2. Redistributions in binary form must reproduce the above copyright notice, - this list of conditions and the following disclaimer in the documentation - and/or other materials provided with the distribution. - - 3. The end-user documentation included with the redistribution, if any, must - include the following acknowledgment: "This product includes software - developed by the Apache Software Foundation (http://www.apache.org/)." - Alternately, this acknowledgment may appear in the software itself, if - and wherever such third-party acknowledgments normally appear. - - 4. The names "Jakarta", "Avalon", "Excalibur" and "Apache Software Foundation" - must not be used to endorse or promote products derived from this software - without prior written permission. For written permission, please contact - apache@apache.org. - - 5. Products derived from this software may not be called "Apache", nor may - "Apache" appear in their name, without prior written permission of the - Apache Software Foundation. - - THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, - INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND - FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE - APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, - INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- - DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS - OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON - ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT - (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF - THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - - This software consists of voluntary contributions made by many individuals - on behalf of the Apache Software Foundation. For more information on the - Apache Software Foundation, please see . - -*/ - -/** - * This script, when included in a html file, builds a neat breadcrumb trail - * based on its url. That is, if it doesn't contains bugs (I'm relatively - * sure it does). - * - * Typical usage: - * - * - *@author Leo Simons (main author) - *@author Nicola Ken Barozzi (integration in skin) - *@created July 12, 2002 - *@version 1.0 - */ - -/* ======================================================================== - CONSTANTS - ======================================================================== */ - -/** - * Two-dimensional array containing extra crumbs to place at the front of - * the trail. Specify first the name of the crumb, then the URI that belongs - * to it. You'll need to modify this for every domain or subdomain where - * you use this script (you can leave it as an empty array if you wish) - */ -var PREPREND_CRUMBS = new Array(); - if(!("apache"=="")){ - PREPREND_CRUMBS.push( new Array( "apache", "http://www.apache.org/" ) ); - } - if(!("xml.apache"=="")){ - PREPREND_CRUMBS.push( new Array( "ant.apache", "http://ant.apache.org/" ) ); - } - if(!(""=="")){ - PREPREND_CRUMBS.push( new Array( "", "" ) ); - } - -/** - * String to include between crumbs: - */ -var DISPLAY_SEPARATOR = " > "; -/** - * String to include at the beginning of the trail - */ -var DISPLAY_PREPREND = ""; -/** - * String to include at the end of the trail - */ -var DISPLAY_POSTPREND = ""; - -/** - * CSS Class to use for a single crumb: - */ -var CSS_CLASS_CRUMB = "breadcrumb"; - -/** - * CSS Class to use for the complete trail: - */ -var CSS_CLASS_TRAIL = "breadcrumbTrail"; - -/** - * CSS Class to use for crumb separator: - */ -var CSS_CLASS_SEPARATOR = "crumbSeparator"; - -/** - * Array of strings containing common file extensions. We use this to - * determine what part of the url to ignore (if it contains one of the - * string specified here, we ignore it). - */ -var FILE_EXTENSIONS = new Array( ".html", ".htm", ".jsp", ".php", ".php3", ".php4" ); - -/** - * String that separates parts of the breadcrumb trail from each other. - * When this is no longer a slash, I'm sure I'll be old and grey. - */ -var PATH_SEPARATOR = "/"; - -/* ======================================================================== - UTILITY FUNCTIONS - ======================================================================== */ -/** - * Capitalize first letter of the provided string and return the modified - * string. - */ -function sentenceCase( string ) -{ - var lower = string.toLowerCase(); - return lower.substr(0,1).toUpperCase() + lower.substr(1); -} - -/** - * Returns an array containing the names of all the directories in the - * current document URL - */ -function getDirectoriesInURL() -{ - var trail = document.location.pathname.split( PATH_SEPARATOR ); - - // check whether last section is a file or a directory - var lastcrumb = trail[trail.length-1]; - for( var i = 0; i < FILE_EXTENSIONS.length; i++ ) - { - if( lastcrumb.indexOf( FILE_EXTENSIONS[i] ) ) - { - // it is, remove it and send results - return trail.slice( 1, trail.length-1 ); - } - } - - // it's not; send the trail unmodified - return trail.slice( 1, trail.length ); -} - -/* ======================================================================== - BREADCRUMB FUNCTIONALITY - ======================================================================== */ -/** - * Return a two-dimensional array describing the breadcrumbs based on the - * array of directories passed in. - */ -function getBreadcrumbs( dirs ) -{ - var prefix = "/"; - var postfix = "/"; - - // the array we will return - var crumbs = new Array(); - - if( dirs != null ) - { - for( var i = 0; i < dirs.length; i++ ) - { - prefix += dirs[i] + postfix; - crumbs.push( new Array( dirs[i], prefix ) ); - } - } - - // preprend the PREPREND_CRUMBS - if(PREPREND_CRUMBS.length > 0 ) - { - return PREPREND_CRUMBS.concat( crumbs ); - } - - return crumbs; -} - -/** - * Return a string containing a simple text breadcrumb trail based on the - * two-dimensional array passed in. - */ -function getCrumbTrail( crumbs ) -{ - var xhtml = DISPLAY_PREPREND; - - for( var i = 0; i < crumbs.length; i++ ) - { - xhtml += ''; - xhtml += sentenceCase( crumbs[i][0] ) + ''; - if( i != (crumbs.length-1) ) - { - xhtml += DISPLAY_SEPARATOR; - } - } - - xhtml += DISPLAY_POSTPREND; - - return xhtml; -} - -/** - * Return a string containing an XHTML breadcrumb trail based on the - * two-dimensional array passed in. - */ -function getCrumbTrailXHTML( crumbs ) -{ - var xhtml = ''; - xhtml += DISPLAY_PREPREND; - - for( var i = 0; i < crumbs.length; i++ ) - { - xhtml += ''; - xhtml += sentenceCase( crumbs[i][0] ) + ''; - if( i != (crumbs.length-1) ) - { - xhtml += '' + DISPLAY_SEPARATOR + ''; - } - } - - xhtml += DISPLAY_POSTPREND; - xhtml += ''; - - return xhtml; -} - -/* ======================================================================== - PRINT BREADCRUMB TRAIL - ======================================================================== */ - -// check if we're local; if so, only print the PREPREND_CRUMBS -if( document.location.href.toLowerCase().indexOf( "http://" ) == -1 ) -{ - document.write( getCrumbTrail( getBreadcrumbs() ) ); -} -else -{ - document.write( getCrumbTrail( getBreadcrumbs( getDirectoriesInURL() ) ) ); -} - diff --git a/proposal/ant-site/anakia/docs/bylaws.html b/proposal/ant-site/anakia/docs/bylaws.html deleted file mode 100644 index bf644ee23..000000000 --- a/proposal/ant-site/anakia/docs/bylaws.html +++ /dev/null @@ -1,874 +0,0 @@ - - - - - - - - Apache Ant - Apache Ant Project Bylaws - - - - - - - - - - - -
- - - - - - - - - - - -
Apache Ant siteApache Ant logo -
- - - - - - - - - - -
-
- - the Apache Ant site - - -
-
-
-
- - - - - -
- - - - -
Home
-
-
-
- - - - -
- - - - - - - - - - -
- - - - - - - - - - -
 
-
- -
-
- - - - - - - - - - - - - -
-   - -   -
-
- - - - -
-

Apache Ant Project Bylaws

-
-
- - -
Apache Ant Project Bylaws
-

- This document defines the bylaws under which the Apache Ant project - operates. It defines the roles and responsibilities of the - project, who may vote, how voting works, how conflicts are resolved, - etc. -

-

- Ant is a project of the - Apache Software - Foundation. The foundation holds the copyright on Apache - code including the code in the Ant codebase. The - foundation FAQ - explains the operation and background of the foundation. -

-

- Ant is typical of Apache projects in that it operates under a set of - principles, known collectively as the "Apache Way". If you are - new to Apache development, please refer to the - Incubator project - for more information on how Apache projects operate. Note: the - incubator project has only been recently set up and does not yet explain - the Apache Way in great detail. -

- -
- - -
Roles and Responsibilities
-

- Apache projects define a set of roles with associated rights and - responsibilities. These roles govern what tasks an individual may perform - within the project. The roles are defined in the following sections -

- -
- - - -
- - Users - -
-

- 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. -

-

- Users contribute to the Apache projects by providing feedback to - developers in 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. -

-
- - - -
- - Developers - -
-

- 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 may be invited to become a - Committer, though the exact timing of such invitations depends on many - factors. -

-
- - - -
- - Committers - -
-

- The project's Committers are responsible for the project's technical - management. All committers have write access to the project's source - repositories. Committers may cast binding votes on any technical - discussion regarding the project. -

-

- Committer access is by invitation only and must be approved by lazy - consensus of the active PMC members. A Committer is considered emeritus - by their own declaration or by not contributing in any form to the - project for over six months. An emeritus committer may request - reinstatement of commit access from the PMC. Such reinstatement is - subject to lazy consensus of active PMC members. -

-

- Commit access can be revoked by a unanimous vote of all the active - PMC members (except the committer in question if they are also a PMC member). -

-

- All Apache committers are required to have a signed Contributor License - Agreement (CLA) on file with the Apache Software Foundation. There is a - Committer FAQ - which provides more details on the requirements for Committers -

-

- A committer who makes a sustained contribution to the project may be - invited to become a member of the PMC. The form of contribution is - not limited to code. It can also include code review, helping out - users on the mailing lists, documentation, etc. -

-
- - - -
- - Project Management Committee - -
-

- The Project Management Committee (PMC) for Apache Ant was created by a - resolution of the board of the Apache - Software Foundation on 18th November 2002. The PMC is - responsible to the board and the ASF for the management and oversight - of the Apache Ant codebase. The responsibilities of the PMC include -

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

- Membership of the PMC is by invitation only and must be approved by a - lazy consensus of active PMC members. A PMC member is considered - "emeritus" by their own declaration or by not contributing in - any form to the project for over six months. An emeritus member may - request reinstatement to the PMC. Such reinstatement is subject to lazy - consensus of the active PMC members. Membership of the PMC can be - revoked by an unanimous vote of all the active PMC members other than - the member in question. -

-

- 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 2/3 Majority may recommend a new chair to the board. - Ultimately, however, it is the board's responsibility who it chooses - to appoint as the PMC chair. -

-
- - -
Decision Making
-

- Within the Ant project, different types of decisions require different - forms of approval. For example, the - previous section describes - several decisions which require "lazy consensus" approval. This - section defines how voting is performed, the types of approvals, and which - types of decision require which type of approval. -

-
- - - -
- - Voting - -
-

- Decisions regarding the project are made by votes on the primary project - development mailing list (ant-dev@jakarta.apache.org). Where necessary, - PMC voting may take place on the private Ant PMC mailing list. - Votes are clearly indicated by subject line starting with [VOTE] or - [PMC-VOTE]. Votes may contain multiple items for approval and these - should be clearly separated. Voting is carried out by replying to the - vote mail. Voting may take four flavours -

- - - - - - - - - - - - - - - - - -
- +1 - - - "Yes," "Agree," or "the action should be - performed." In general, this vote also indicates a willingness - on the behalf of the voter in "making it happen" - -
- +0 - - - This vote indicates a willingness for the action under - consideration to go ahead. The voter, however will not be able - to help. - -
- -0 - - - This vote indicates that the voter does not, in general, agree with - the proposed action but is not concerned enough to prevent the - action going ahead. - -
- -1 - - - This is a negative vote. On issues where consensus is required, - this vote counts as a veto. All vetoes must - contain an explanation of why the veto is appropriate. Vetoes with - no explanation are void. It may also be appropriate for a -1 vote - to include an alternative course of action. - -
-

- All participants in the Ant project are encouraged to show their - agreement with or against a particular action by voting. For technical - decisions, only the votes of active committers are binding. Non binding - votes are still useful for those with binding votes to understand the - perception of an action in the wider Ant community. For PMC decisions, - only the votes of PMC members are binding. -

-

- Voting can also be applied to changes made to the Ant codebase. These - typically take the form of a veto (-1) in reply to the commit message - sent when the commit is made. -

-
- - - -
- - Approvals - -
-

- These are the types of approvals that can be sought. Different actions - require different types of approvals -

- - - - - - - - - - - - - - - - - - - - - -
- Consensus - - - For this to pass, all voters with binding votes must vote and there - can be no binding vetoes (-1). Consensus votes are rarely required - due to the impracticality of getting all eligible voters to cast a - vote. - -
- Lazy Consensus - - - Lazy consensus requires 3 binding +1 votes and no binding vetoes. - -
- Lazy Majority - - - A lazy majority vote requires 3 binding +1 votes and more binding +1 - votes that -1 votes. - -
- Lazy Approval - - - An action with lazy approval is implicitly allowed unless a -1 vote - is received, at which time, depending on the type of action, either - lazy majority or lazy consensus approval must be obtained. - -
- 2/3 Majority - - - Some actions require a 2/3 majority of active committers or PMC - members to pass. Such actions typically affect the foundation - of the project (e.g. adopting a new codebase to replace an existing - product). The higher threshold is designed to ensure such changes - are strongly supported. To pass this vote requires at least 2/3 of - binding vote holders to vote +1 - -
-
- - - -
- - Vetoes - -
-

- A valid, binding veto cannot be overruled. If a veto is cast, it must be - accompanied by a valid reason explaining the reasons for the veto. The - validity of a veto, if challenged, can be confirmed by anyone who has - a binding vote. This does not necessarily signify agreement with the - veto - merely that the veto is valid. -

-

- If you disagree with a valid veto, you must lobby the person casting - the veto to withdraw their veto. If a veto is not withdrawn, the action - that has been vetoed must be reversed in a timely manner. -

-
- - - -
- - Actions - -
-

- This section describes the various actions which are undertaken within - the project, the corresponding approval required for that action and - those who have binding votes over the action. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- Action - - Description - - Approval - - Binding Votes -
- Code Change - - - A change made to a codebase of the project and committed - by a committer. This includes source code, documentation, website - content, etc. - - - - Lazy approval and then lazy consensus. - - - - Active committers. - -
- Release Plan - - - Defines the timetable and actions for a release. The plan also - nominates a Release Manager. - - - - Lazy majority - - - - Active committers - -
- Product Release - - - When a release of one of the project's products is ready, a vote is - required to accept the release as an official release of the - project. - - - - Lazy Majority - - - - Active PMC members - -
- Adoption of New Codebase - - -

- When the codebase for an existing, released product is to be - replaced with an alternative codebase. If such a vote fails to - gain approval, the existing code base will continue. -

- -

- This also covers the creation of new sub-projects - within the project -

- -
- - 2/3 majority - - - - Active committers - -
- New Committer - - - When a new committer is proposed for the project - - - - Lazy consensus - - - - Active PMC members - -
- New PMC Member - - - When a committer is proposed for the PMC - - - - Lazy consensus - - - - Active PMC members - -
- Committer Removal - - -

When removal of commit privileges is sought.

-

Note: Such actions will also be referred to the ASF - board by the PMC chair

- -
- - Consensus - - - - Active PMC members (excluding the committer in question if a - member of the PMC). - -
- PMC Member Removal - - -

When removal of a PMC member is sought.

-

Note: Such actions will also be referred to the - ASF board by the PMC chair

- -
- - Consensus - - - - Active PMC members (excluding the member in question). - -
-
- - - -
- - Voting Timeframes - -
-

- Votes are open for a period of 1 week to allow all active voters - time to consider the vote. Votes relating to code changes are not - subject to a strict timetable but should be made as timely as possible. -

- - -
-
-
- - - - - - - -
- - - - - - - - - - - diff --git a/proposal/ant-site/anakia/docs/page.css b/proposal/ant-site/anakia/docs/page.css deleted file mode 100644 index 8462a8635..000000000 --- a/proposal/ant-site/anakia/docs/page.css +++ /dev/null @@ -1,52 +0,0 @@ -body { background-color: #FFFFFF; margin: 0px 0px 0px 0px; font-family: Verdana, Helvetica, sans-serif; font-size : 90%; } - -a:link { color: #0F3660; } -a:visited { color: #009999; } -a:active { color: #000066; } -a:hover { color: #000066; } - -.menu { background-color: #4C6C8F; margin: 0px; padding: 3px 8px 5px 3px; font-size : 90%; } -.menu a:link { color: #FFFFFF; text-decoration : none; } -.menu a:visited { color: #FFFFFF; text-decoration : none; } -/*.menu a:active { font-weight: bold }*/ -.menu a:hover { color: #FFCC00; text-decoration : none; } -.menu ul { margin: 0px 0px 0px 20px; padding: 0px; } -.menu li { list-style-image: url('images/label.gif'); font-weight : bold; } -.menu ul ul li .sel { list-style-image: url('images/current.gif'); font-weight : normal; } -.menu ul ul li { list-style-image: url('images/page.gif'); font-weight : normal; } - -table .title { background-color: #FFFFFF; width:100%; border: 0px; } -.dida { font-size: 60%; } - -.pre { white-space: pre;} -.nowrap { white-space: nowrap;} - -.content { padding: 5px 5px 5px 10px; font : small; font-size : 90%; } -.content .ForrestTable { width: 100%; background-color: #7099C5; color: #ffffff; font-size : 90%;} -.content .ForrestTable caption { text-align: left; color: black; font-weight: bold; } -.content .ForrestTable th { text-align: center; } -.content .ForrestTable td { background-color: #f0f0ff; color: black; } - -.frame { margin: 5px 20px 5px 20px; font-size: 90%; } -.frame .content { margin: 0px; } - -.note { border: solid 1px #7099C5; background-color: #f0f0ff; } -.note .label { background-color: #7099C5; color: #ffffff; } - -.warning { border: solid 1px #D00000; background-color: #fff0f0; } -.warning .label { background-color: #D00000; color: #ffffff; } - -.fixme { border: solid 1px #C6C600; background-color: #FAF9C3; } -.fixme .label { background-color: #C6C600; color: #ffffff; } - -.code { border-color: #CFDCED; border-style: solid; border-width: 1px; } -.codefrag { font-family: "Courier New", Courier, monospace; } - -.highlight { background-color: yellow; } - -.minitoc {margin: 5px 5px 5px 40px;} - -.dtdElement { width: 100%; font-size: 90%; background-color : #ffffff; } - -.dtdTag { color: #990000; text-transform : uppercase; font-style : normal; font-size : 120%; font-weight : bold; } - diff --git a/proposal/ant-site/anakia/xdocs/bylaws.xml b/proposal/ant-site/anakia/xdocs/bylaws.xml deleted file mode 100644 index 265691e35..000000000 --- a/proposal/ant-site/anakia/xdocs/bylaws.xml +++ /dev/null @@ -1,460 +0,0 @@ - - - - - Apache Ant Project Bylaws - - - -
-

- This document defines the bylaws under which the Apache Ant project - operates. It defines the roles and responsibilities of the - project, who may vote, how voting works, how conflicts are resolved, - etc. -

- -

- Ant is a project of the - Apache Software - Foundation. The foundation holds the copyright on Apache - code including the code in the Ant codebase. The - foundation FAQ - explains the operation and background of the foundation. -

- -

- Ant is typical of Apache projects in that it operates under a set of - principles, known collectively as the "Apache Way". If you are - new to Apache development, please refer to the - Incubator project - for more information on how Apache projects operate. Note: the - incubator project has only been recently set up and does not yet explain - the Apache Way in great detail. -

- - - -
- -
-

- Apache projects define a set of roles with associated rights and - responsibilities. These roles govern what tasks an individual may perform - within the project. The roles are defined in the following sections -

- - - - -

- 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. -

- -

- Users contribute to the Apache projects by providing feedback to - developers in 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. -

- -
- - -

- 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 may be invited to become a - Committer, though the exact timing of such invitations depends on many - factors. -

-
- - -

- The project's Committers are responsible for the project's technical - management. All committers have write access to the project's source - repositories. Committers may cast binding votes on any technical - discussion regarding the project. -

- -

- Committer access is by invitation only and must be approved by lazy - consensus of the active PMC members. A Committer is considered emeritus - by their own declaration or by not contributing in any form to the - project for over six months. An emeritus committer may request - reinstatement of commit access from the PMC. Such reinstatement is - subject to lazy consensus of active PMC members. -

- -

- Commit access can be revoked by a unanimous vote of all the active - PMC members (except the committer in question if they are also a PMC member). -

- -

- All Apache committers are required to have a signed Contributor License - Agreement (CLA) on file with the Apache Software Foundation. There is a - Committer FAQ - which provides more details on the requirements for Committers -

- -

- A committer who makes a sustained contribution to the project may be - invited to become a member of the PMC. The form of contribution is - not limited to code. It can also include code review, helping out - users on the mailing lists, documentation, etc. -

-
- -

- The Project Management Committee (PMC) for Apache Ant was created by a - resolution of the board of the Apache - Software Foundation on 18th November 2002. The PMC is - responsible to the board and the ASF for the management and oversight - of the Apache Ant codebase. The responsibilities of the PMC include -

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

- Membership of the PMC is by invitation only and must be approved by a - lazy consensus of active PMC members. A PMC member is considered - "emeritus" by their own declaration or by not contributing in - any form to the project for over six months. An emeritus member may - request reinstatement to the PMC. Such reinstatement is subject to lazy - consensus of the active PMC members. Membership of the PMC can be - revoked by an unanimous vote of all the active PMC members other than - the member in question. -

- -

- 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 2/3 Majority may recommend a new chair to the board. - Ultimately, however, it is the board's responsibility who it chooses - to appoint as the PMC chair. -

-
-
- -
-

- Within the Ant project, different types of decisions require different - forms of approval. For example, the - previous section describes - several decisions which require "lazy consensus" approval. This - section defines how voting is performed, the types of approvals, and which - types of decision require which type of approval. -

- - -

- Decisions regarding the project are made by votes on the primary project - development mailing list (ant-dev@jakarta.apache.org). Where necessary, - PMC voting may take place on the private Ant PMC mailing list. - Votes are clearly indicated by subject line starting with [VOTE] or - [PMC-VOTE]. Votes may contain multiple items for approval and these - should be clearly separated. Voting is carried out by replying to the - vote mail. Voting may take four flavours -

- - - - - - - - - - - - - - - - - - - - - -
+1 - "Yes," "Agree," or "the action should be - performed." In general, this vote also indicates a willingness - on the behalf of the voter in "making it happen" -
+0 - This vote indicates a willingness for the action under - consideration to go ahead. The voter, however will not be able - to help. -
-0 - This vote indicates that the voter does not, in general, agree with - the proposed action but is not concerned enough to prevent the - action going ahead. -
-1 - This is a negative vote. On issues where consensus is required, - this vote counts as a veto. All vetoes must - contain an explanation of why the veto is appropriate. Vetoes with - no explanation are void. It may also be appropriate for a -1 vote - to include an alternative course of action. -
- -

- All participants in the Ant project are encouraged to show their - agreement with or against a particular action by voting. For technical - decisions, only the votes of active committers are binding. Non binding - votes are still useful for those with binding votes to understand the - perception of an action in the wider Ant community. For PMC decisions, - only the votes of PMC members are binding. -

- -

- Voting can also be applied to changes made to the Ant codebase. These - typically take the form of a veto (-1) in reply to the commit message - sent when the commit is made. -

-
- - -

- These are the types of approvals that can be sought. Different actions - require different types of approvals -

- - - - - - - - - - - - - - - - - - - - - - - - - - -
Consensus - For this to pass, all voters with binding votes must vote and there - can be no binding vetoes (-1). Consensus votes are rarely required - due to the impracticality of getting all eligible voters to cast a - vote. -
Lazy Consensus - Lazy consensus requires 3 binding +1 votes and no binding vetoes. -
Lazy Majority - A lazy majority vote requires 3 binding +1 votes and more binding +1 - votes that -1 votes. -
Lazy Approval - An action with lazy approval is implicitly allowed unless a -1 vote - is received, at which time, depending on the type of action, either - lazy majority or lazy consensus approval must be obtained. -
2/3 Majority - Some actions require a 2/3 majority of active committers or PMC - members to pass. Such actions typically affect the foundation - of the project (e.g. adopting a new codebase to replace an existing - product). The higher threshold is designed to ensure such changes - are strongly supported. To pass this vote requires at least 2/3 of - binding vote holders to vote +1 -
-
- - -

- A valid, binding veto cannot be overruled. If a veto is cast, it must be - accompanied by a valid reason explaining the reasons for the veto. The - validity of a veto, if challenged, can be confirmed by anyone who has - a binding vote. This does not necessarily signify agreement with the - veto - merely that the veto is valid. -

- -

- If you disagree with a valid veto, you must lobby the person casting - the veto to withdraw their veto. If a veto is not withdrawn, the action - that has been vetoed must be reversed in a timely manner. -

-
- - -

- This section describes the various actions which are undertaken within - the project, the corresponding approval required for that action and - those who have binding votes over the action. -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
ActionDescriptionApprovalBinding Votes
Code Change - A change made to a codebase of the project and committed - by a committer. This includes source code, documentation, website - content, etc. - - Lazy approval and then lazy consensus. - - Active committers. -
Release Plan - Defines the timetable and actions for a release. The plan also - nominates a Release Manager. - - Lazy majority - - Active committers -
Product Release - When a release of one of the project's products is ready, a vote is - required to accept the release as an official release of the - project. - - Lazy Majority - - Active PMC members -
Adoption of New Codebase -

- When the codebase for an existing, released product is to be - replaced with an alternative codebase. If such a vote fails to - gain approval, the existing code base will continue. -

- -

- This also covers the creation of new sub-projects - within the project -

-
- 2/3 majority - - Active committers -
New Committer - When a new committer is proposed for the project - - Lazy consensus - - Active PMC members -
New PMC Member - When a committer is proposed for the PMC - - Lazy consensus - - Active PMC members -
Committer Removal -

When removal of commit privileges is sought.

-

Note: Such actions will also be referred to the ASF - board by the PMC chair

-
- Consensus - - Active PMC members (excluding the committer in question if a - member of the PMC). -
PMC Member Removal -

When removal of a PMC member is sought.

-

Note: Such actions will also be referred to the - ASF board by the PMC chair

-
- Consensus - - Active PMC members (excluding the member in question). -
-
- -

- Votes are open for a period of 1 week to allow all active voters - time to consider the vote. Votes relating to code changes are not - subject to a strict timetable but should be made as timely as possible. -

-
-
- -
diff --git a/proposal/ant-site/anakia/xdocs/stylesheets/project.xml b/proposal/ant-site/anakia/xdocs/stylesheets/project.xml deleted file mode 100644 index bb99416a3..000000000 --- a/proposal/ant-site/anakia/xdocs/stylesheets/project.xml +++ /dev/null @@ -1,49 +0,0 @@ - - - - Apache Ant - Apache Ant - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - diff --git a/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl b/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl deleted file mode 100644 index bccb5a15a..000000000 --- a/proposal/ant-site/anakia/xdocs/stylesheets/site.vsl +++ /dev/null @@ -1,209 +0,0 @@ -#* - * ============================================================================ - * The Apache Software License, Version 1.1 - * ============================================================================ - * - * Copyright (C) 2000-2002 The Apache Software Foundation. All - * rights reserved. - * - * Redistribution and use in source and binary forms, with or without modifica- - * tion, are permitted provided that the following conditions are met: - * - * 1. Redistributions of source code must retain the above copyright notice, - * this list of conditions and the following disclaimer. - * - * 2. Redistributions in binary form must reproduce the above copyright notice, - * this list of conditions and the following disclaimer in the documentation - * and/or other materials provided with the distribution. - * - * 3. The end-user documentation included with the redistribution, if any, must - * include the following acknowledgment: "This product includes software - * developed by the Apache Software Foundation (http://www.apache.org/)." - * Alternately, this acknowledgment may appear in the software itself, if - * and wherever such third-party acknowledgments normally appear. - * - * 4. The names "Ant" and "Apache Software Foundation" must not be used to - * endorse or promote products derived from this software without prior - * written permission. For written permission, please contact - * apache@apache.org. - * - * 5. Products derived from this software may not be called "Apache", nor may - * "Apache" appear in their name, without prior written permission of the - * Apache Software Foundation. - * - * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, - * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND - * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE - * APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, - * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- - * DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS - * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON - * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT - * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF - * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - * - * This software consists of voluntary contributions made by many individuals - * on behalf of the Apache Software Foundation. For more information on the - * Apache Software Foundation, please see . - * - *# - - -## Content Stylesheet for Site - ## Defined variables - #set ($lightbg = "#ffffff") - #set ($lightfg = "#ffffff") - #set ($darkfg = "#000000") - #set ($active = "#ffcc00") - #set ($blue3 = "#294563") - #set ($blue2 = "#4C6C8F") - #set ($blue1 = "#CFDCED") - #set ($sourceborder = "#023264") - #set ($pound = "#" ) -## start the processing -#document() -## end the processing - -## This is where the common page macro's live - -#macro ( subsection $subsection) -
- - - -
- - $subsection.getAttributeValue("name") - -
- #foreach ( $items in $subsection.getChildren() ) - #if ($items.getName().equals("img")) - #image ($items) - #elseif ($items.getName().equals("source")) - #source ($items) - #elseif ($items.getName().equals("table")) - #table ($items) - #else - $xmlout.outputString($items) - #end - #end -#end - -#macro ( section $section) -
- - -
$section.getAttributeValue("name")
- #foreach ( $items in $section.getChildren() ) - #if ($items.getName().equals("img")) - #image ($items) - #elseif ($items.getName().equals("source")) - #source ($items) - #elseif ($items.getName().equals("table")) - #table ($items) - #elseif ($items.getName().equals("subsection")) - #subsection ($items) - #else - $xmlout.outputString($items) - #end - #end -#end - -## This is where the FAQ specific macro's live - -#macro (toc $section) -
- - -
- - $section.getAttributeValue("title") - -
- -#end - -#macro (subtoc $faq) - #set ($id = $faq.getAttributeValue("id")) -
  • - $xmlout.outputString($faq.getChild("question"), true) -
  • -#end - -#macro (answers $section) - #foreach ($faq in $section.getChildren("faq") ) - #faq ($faq) - #end -#end - -#macro (faq $faq) - #set ($id = $faq.getAttributeValue("id")) -
    - - - -
    - - - $xmlout.outputString($faq.getChild("question"), true) - - -
    - #foreach ($item in $faq.getChild("answer").getChildren()) - #if ($item.getName().equals("img")) - #image ($item) - #elseif ($item.getName().equals("source")) - #source ($item) - #elseif ($item.getName().equals("table")) - #table ($item) - #else - $xmlout.outputString($item) - #end - #end -#end - -#macro (document) - #header() - - - - -
    -

    $root.getChild("properties").getChild("title").getText()

    -
    - #set ($allSections = $root.getChild("body").getChildren("section")) - #foreach ( $section in $allSections ) - #section ($section) - #end - - #if ($root.getChildren("faqsection").size() > 0) - #set ($allFaqSections = $root.getChildren("faqsection")) - - -
    - - Questions - -
    - #foreach ( $faqSection in $allFaqSections ) - #toc ($faqSection) - #end - - - -
    - - Answers - -
    - #foreach ( $faqSection in $allFaqSections ) - #answers ($faqSection) - #end - #end - - #footer() -#end diff --git a/proposal/ant-site/anakia/xdocs/stylesheets/templates.vm b/proposal/ant-site/anakia/xdocs/stylesheets/templates.vm deleted file mode 100644 index a86f238c1..000000000 --- a/proposal/ant-site/anakia/xdocs/stylesheets/templates.vm +++ /dev/null @@ -1,334 +0,0 @@ -#* - * ============================================================================ - * The Apache Software License, Version 1.1 - * ============================================================================ - * - * Copyright (C) 2000-2003 The Apache Software Foundation. All - * rights reserved. - * - * Redistribution and use in source and binary forms, with or without modifica- - * tion, are permitted provided that the following conditions are met: - * - * 1. Redistributions of source code must retain the above copyright notice, - * this list of conditions and the following disclaimer. - * - * 2. Redistributions in binary form must reproduce the above copyright notice, - * this list of conditions and the following disclaimer in the documentation - * and/or other materials provided with the distribution. - * - * 3. The end-user documentation included with the redistribution, if any, must - * include the following acknowledgment: "This product includes software - * developed by the Apache Software Foundation (http://www.apache.org/)." - * Alternately, this acknowledgment may appear in the software itself, if - * and wherever such third-party acknowledgments normally appear. - * - * 4. The names "Ant" and "Apache Software Foundation" must not be used to - * endorse or promote products derived from this software without prior - * written permission. For written permission, please contact - * apache@apache.org. - * - * 5. Products derived from this software may not be called "Apache", nor may - * "Apache" appear in their name, without prior written permission of the - * Apache Software Foundation. - * - * THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, - * INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND - * FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE - * APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, - * INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLU- - * DING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS - * OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON - * ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT - * (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF - * THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - * - * This software consists of voluntary contributions made by many individuals - * on behalf of the Apache Software Foundation. For more information on the - * Apache Software Foundation, please see . - * - *# - -## This is where the common macro's live - -#macro ( table $table) - - #foreach ( $items in $table.getChildren() ) - #if ($items.getName().equals("tr")) - #tr ($items) - #end - #end -
    -#end - -#macro ( tr $tr) - - #foreach ( $items in $tr.getChildren() ) - #if ($items.getName().equals("td")) - #td ($items) - #elseif ($items.getName().equals("th")) - #th ($items) - #end - #end - -#end - -#macro ( td $value) - #if ($value.getAttributeValue("colspan")) - #set ($colspan = $value.getAttributeValue("colspan")) - #else - #set ($colspan = 1) - #end - #if ($value.getAttributeValue("rowspan")) - #set ($rowspan = $value.getAttributeValue("rowspan")) - #else - #set ($rowspan = 1) - #end - - #if ($value.getText().length() != 0 || $value.hasChildren()) - $xmlout.outputString($value, true) - #else -   - #end - -#end - -#macro ( th $value) - #if ($value.getAttributeValue("colspan")) - #set ($colspan = $value.getAttributeValue("colspan")) - #else - #set ($colspan = 1) - #end - #if ($value.getAttributeValue("rowspan")) - #set ($rowspan = $value.getAttributeValue("rowspan")) - #else - #set ($rowspan = 1) - #end - - #if ($value.getText().length() != 0 || $value.hasChildren()) - $xmlout.outputString($value, true) - #else -   - #end - -#end - -#macro ( projectanchor $name $value ) - #if ($value.startsWith("http://")) - $name - #elseif ($value.startsWith("/site")) - $name - #else - $name - #end -#end - -#macro ( metaauthor $author $email ) - - -#end - -#macro ( image $value ) - #if ($value.getAttributeValue("width")) - #set ($width=$value.getAttributeValue("width")) - #end - #if ($value.getAttributeValue("height")) - #set ($height=$value.getAttributeValue("height")) - #end - #if ($value.getAttributeValue("align")) - #set ($align=$value.getAttributeValue("align")) - #end - #if ($value.getAttributeValue("alt")) - #set ($align=$value.getAttributeValue("alt")) - #end - $!alt -#end - -#macro ( source $value) -
    $escape.getText($value.getText())
    -#end - -#macro ( makeProject ) - #set ($menus = $project.getChild("body").getChildren("menu")) - -#end - -#macro (getProjectImage) - #if ($project.getChild("logo")) - - Apache Jakarta Project - - - #set ( $logoString = $project.getChild("logo").getAttributeValue("href") ) - #if ( $logoString.startsWith("/") ) - $project.getChild( - #else - $project.getChild( - #end - - #else - - Apache Jakarta Project - - #end -#end - -#macro (header) - - - - - $project.getChild("title").getText() - $root.getChild("properties").getChild("title").getText() - - #set ($authors = $root.getChild("properties").getChildren("author")) - #foreach ( $au in $authors ) - #metaauthor ( $au.getText() $au.getAttributeValue("email") ) - #end - - - - - - - - - - -
    - - - - - - - - - - - -
    Apache Ant siteApache Ant logo -
    - - - - - - - - - - -
    -
    - - the Apache Ant site - - -
    -
    -
    -
    - - - - - -
    - - - - -
    Home
    -
    -
    -
    - - - - -
    - - - - - - - - - - -
    - - - - - - - - - - -
     
    -
    - #makeProject() -
    -
    - - - - - - - - - - - - - -
    -   - -   -
    -
    -#end - -#macro (footer) -
    -
    -
    - - - - - - - -
    - - -#end diff --git a/proposal/ant-site/anakia/xdocs/velocity.properties b/proposal/ant-site/anakia/xdocs/velocity.properties deleted file mode 100644 index 7327d96fb..000000000 --- a/proposal/ant-site/anakia/xdocs/velocity.properties +++ /dev/null @@ -1,2 +0,0 @@ -file.resource.loader.path=xdocs/stylesheets -velocimacro.library=templates.vm