http://git-wip-us.apache.org/repos/asf/incubator/blob/d8d548ab/content/projects/bluesky.html ---------------------------------------------------------------------- diff --git a/content/projects/bluesky.html b/content/projects/bluesky.html deleted file mode 100644 index 6f3f992..0000000 --- a/content/projects/bluesky.html +++ /dev/null @@ -1,466 +0,0 @@ - - - - - - - - Apache Bluesky Incubation Status - Apache Incubator - - - -
-
The Apache Software Foundation
-
The Apache Software Foundation Incubator
-
-
-

-
- - -
-

-
-

2011/07/05 - Bluesky has been retired.

-
-

Bluesky Project Incubation Status

-
-

This page tracks the project status, incubator-wise. For more general - project status, look on the project website.

-

The Bluesky project retired on 2011-07-05

-
-

Description

-
-

The Bluesky Project is an e-learning solution designed to help solve the disparity in availabilty of education - between well-developed cities and poorer regions of China. - It had been deployed to 12 + 5 primary/high schools with positive reviews. We enter the incubation to revolve our system so that - poor regions around the world could share higher education resources.

-
-

News

-
-
    -
  • 2008-01-12 Project enters incubation.
  • -
  • 2009-09-15 New Committer: mabowen
  • -
  • 2009-09-15 New Committer: ping
  • -
  • 2009-09-15 Committers revoked: okid stellagjj zhangfan
  • -
  • 2011-07-05 Project removed from incubation.
  • -
-
-

Project info

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
itemtypereference
Official Websitewww - http://incubator.apache.org/bluesky/ -
.wiki - http://wiki.apache.org/incubator/BlueSky/ -
Developer's Mailing Listdevbluesky-dev@incubator.apache.org - (archive)
Commits Mailing Listcommitsbluesky-commits@incubator.apache.org - (archive)
User Mailing Listuserbluesky-user@incubator.apache.org - (archive)
Bug trackingJira - http://issues.apache.org/jira/browse/BLUESKY
Source codesvn - http://svn.apache.org/repos/asf/incubator/bluesky/ -
MentorsstoddardBill Stoddard
.farraAaron Farr
CommitterstpengTing Peng
.dane0101Jiang Shan
.mabowenBowen Ma
.pingPing Chen
Extra..
-
-

Incubation status reports

- -

Incubation work items

-
-

Project Setup

-
-

This is the first phase on incubation, needed to start the project at Apache.

-

- Item assignment is shown by the Apache id. - Completed tasks are shown by the completion date (YYYY-MM-dd). -

-

Identify the project to be incubated

-
- - - - - - - - - - - - - - - - - - - - - -
dateitem
2007-10-23Make sure that the requested project name does not already exist and - check www.nameprotect.com to be sure that the name is not already - trademarked for an existing software product.
N/AIf request from an existing Apache project to adopt an external - package, then ask the Apache project for the SVN module and mail - address names.
N/AIf request from outside Apache to enter an existing Apache project, - then post a message to that project for them to decide on acceptance.
....-..-..If request from anywhere to become a stand-alone PMC, then assess the - fit with the ASF, and create the lists and modules under the - incubator address/module names if accepted.
-
-

Interim responsibility

-
- - - - - - - - - - - - - - - - - - - - - -
dateitem
2008-01-12Identify all the Mentors for the incubation, by asking all that can - be Mentors.
2008-01-12Subscribe all Mentors on the pmc and general lists.
2009-09-15Give new committers access to the incubator SVN repository. - Revoke the inactive committers.
....-..-..Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html'
-
- -
- - - - - - - - - - - - - -
dateitem
....-..-..Check and make sure that the papers that transfer rights to the ASF - been received. It is only necessary to transfer rights for the - package, the core code, and any new code produced by the project. -
....-..-..Check and make sure that the files that have been donated have been - updated to reflect the new ASF copyright.
-
-

Verify distribution rights

-
- - - - - - - - - - - - - -
dateitem
....-..-..Check and make sure that for all code included with the distribution - that is not under the Apache license, e have the right to combine - with Apache-licensed code and redistribute. -
....-..-..Check and make sure that all source code distributed by the project - is covered by one or more of the following approved licenses: Apache, - BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially - the same terms.
-
-

Establish a list of active committers

-
- - - - - - - - - - - - - - - - - -
dateitem
2009-09-15Check that all active committers have submitted a contributors - agreement.
....-..-..Add all active committers in the STATUS file.
....-..-..Ask root for the creation of committers' accounts on - people.apache.org.
-
-

Infrastructure

-
- - - - - - - - - - - - - - - - - - - - - -
dateitem
....-..-..Ask infrastructure to create source repository modules and grant the - committers karma.
....-..-..Ask infrastructure to set up and archive Mailing lists.
....-..-..Decide about and then ask infrastructure to setup an issuetracking - system (Bugzilla, Scarab, Jira).
....-..-..Migrate the project to our infrastructure.
-
-

Project specific

-
-

- Add project specific tasks here. -

-
-
-

Incubation

-
-

These action items have to be checked for during the whole incubation process.

-

- These items are not to be signed as done during incubation, as they - may change during incubation. - They are to be looked into and described in the status reports and - completed in the request for incubation signoff. -

-

Collaborative Development

-
-
    -
  • Have all of the active long-term volunteers been identified and - acknowledged as committers on the project? -
  • -
  • Are there three or more independent committers? (The legal definition - of independent is long and boring, but basically it means that there - is no binding relationship between the individuals, such as a shared - employer, that is capable of overriding their free will as - individuals, directly or indirectly.)
  • -
  • Are project decisions being made in public by the committers?
  • -
  • Are the decision-making guidelines published and agreed to by all of - the committers?
  • -
-
-

Licensing awareness

-
-
    -
  • Are all licensing, trademark, credit issues being taken care of and - acknowleged by all committers?
  • -
-
-

Project Specific

-
-

- Add project specific tasks here. -

-
-
-

Exit

-
-

- Things to check for before voting the project out. -

-

Organizational acceptance of responsibility for the project

-
-
    -
  • If graduating to an existing PMC, has the PMC voted to accept it?
  • -
  • If graduating to a new PMC, has the board voted to accept it?
  • -
-
-

Incubator sign-off

-
-
    -
  • Has the Incubator decided that the project has accomplished all of - the above tasks?
  • -
-
-
-
-
-
- -

-
- -
-
- - http://git-wip-us.apache.org/repos/asf/incubator/blob/d8d548ab/content/projects/blur.html ---------------------------------------------------------------------- diff --git a/content/projects/blur.html b/content/projects/blur.html deleted file mode 100644 index 333364e..0000000 --- a/content/projects/blur.html +++ /dev/null @@ -1,506 +0,0 @@ - - - - - - - - Apache Blur (Incubating) Status - Apache Incubator - - - -
-
The Apache Software Foundation
-
The Apache Software Foundation Incubator
-
-
-

-
- - -
-

Blur Project Incubation Status

-
-

This page tracks the project status, incubator-wise. For more general - project status, look on the project website.

-
-

Description

-
-

Blur is a search platform capable of searching massive amounts of data - in a cloud computing environment.

-

The Blur project retired on 2017-06-22

-
-

News

-
-
    -
  • 2012-07-24 Project enters incubation.
  • -
-
-

Project info

-
-
    -
  • link to the main website
  • -
-
    -
  • link to the page(s) that tell how to participate (Website,Mailing - lists,Bug tracking,Source code)
  • -
-
    -
  • link to the project status file (Committers,non-incubation action - items,project resources, etc)
  • -
-

If the project website and code repository are not yet setup, use the - following table:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
itemtypereference
Websitewww - http://incubator.apache.org/blur/ -
.wikihttp://wiki.apache.org/blur/FrontPage
Mailing listdevblur-dev@incubator.apache.org
.userblur-user@incubator.apache.org
.commitsblur-commits@incubator.apache.org
Bug tracking. - https://issues.apache.org/jira/browse/BLUR -
Source codegit - https://git-wip-us.apache.org/repos/asf/incubator-blur.git -
Documentation Sourcesvn - https://svn.apache.org/repos/asf/incubator/blur/site/trunk/ -
MentorstwilliamsTim Williams
.phuntPatrick Hunt
.cuttingDoug Cutting
CommittersamccurryAaron McCurry
.twilliamsTim Williams
.phuntPatrick Hunt
.cuttingDoug Cutting
.sleberknScott Leberknight
.rgimmyRyan Gimmy
.crohrChris Rohr
.rkinsRahul Challapalli
.gagzGagan
-
-

Incubation status reports

-
-
    -
  • none yet
  • -
-
-

Incubation work items

-
-

Project Setup

-
-

This is the first phase on incubation, needed to start the project at Apache.

-

- Item assignment is shown by the Apache id. - Completed tasks are shown by the completion date (YYYY-MM-dd). -

-

Identify the project to be incubated

-
- - - - - - - - - - - - - - - - - - - - -
dateitem
- Make sure that the requested project name does not already exist and - check www.nameprotect.com to be sure that the name is not already - trademarked for an existing software product. (See PODLINGNAMESEARCH-34)
n/aIf request from an existing Apache project to adopt an external - package, then ask the Apache project for the SVN module and mail - address names.
n/aIf request from outside Apache to enter an existing Apache project, - then post a message to that project for them to decide on acceptance.
doneIf request from anywhere to become a stand-alone PMC, then assess the - fit with the ASF, and create the lists and modules under the - incubator address/module names if accepted.
-
-

Infrastructure

-
- - - - - - - - - - - - - - - - - - - - - - - - - -
dateitem
2012-08-07Ask infrastructure to create source repository modules - and grant the committers karma.
2012-08-01Ask infrastructure to set up and archive mailing lists.
2012-08-01Ask infrastructure to set up issue tracker (JIRA, Bugzilla).
done.Ask infrastructure to set up wiki (Confluence, Moin).
2012-09-02Migrate the project to our infrastructure.
-
-

Mentor-related responsibility/oversight

-
- - - - - - - - - - - - - - - - - - - - - -
dateitem
2012-07-25Identify all the Mentors for the incubation, by asking all - that can be Mentors.
2012-08-01Subscribe all Mentors on the pmc and general lists.
2012-09-02Give all Mentors access to the incubator SVN repository. - (to be done by the Incubator PMC chair or an Incubator PMC - Member wih karma for the authorizations file)
2012-07-25Tell Mentors to track progress in the file - 'incubator/projects/{project.name}.html'
-
- -
- - - - - - - - - - - - - -
dateitem
doneCheck and make sure that the papers that transfer rights to the ASF - been received. It is only necessary to transfer rights for the - package, the core code, and any new code produced by the project. -
doneCheck and make sure that the files that have been donated have been - updated to reflect the new ASF copyright.
-
-

Verify distribution rights

-
- - - - - - - - - - - - - -
dateitem
doneCheck and make sure that for all code included with the distribution - that is not under the Apache license, we have the right to combine - with Apache-licensed code and redistribute. -
doneCheck and make sure that all source code distributed by the project - is covered by one or more of the following approved licenses: Apache, - BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially - the same terms.
-
-

Establish a list of active committers

-
- - - - - - - - - - - - - - - - - -
dateitem
2012-08-01Check that all active committers have submitted a contributors - agreement.
no?Add all active committers in the STATUS file.
done.Ask root for the creation of committers' accounts on - people.apache.org.
-
-

Project specific

-
-

- Add project specific tasks here. -

-
-
-

Incubation

-
-

These action items have to be checked for during the whole incubation process.

-

- These items are not to be signed as done during incubation, as they - may change during incubation. - They are to be looked into and described in the status reports and - completed in the request for incubation signoff. -

-

Collaborative Development

-
-
    -
  • Have all of the active long-term volunteers been identified and - acknowledged as committers on the project? -
  • -
  • Are there three or more independent committers? (The legal definition - of independent is long and boring, but basically it means that there - is no binding relationship between the individuals, such as a shared - employer, that is capable of overriding their free will as - individuals, directly or indirectly.)
  • -
  • Are project decisions being made in public by the committers?
  • -
  • Are the decision-making guidelines published and agreed to by all of - the committers?
  • -
-
-

Licensing awareness

-
-
    -
  • Are all licensing, trademark, credit issues being taken care of and - acknowleged by all committers?
  • -
-
-

Project Specific

-
-

- Add project specific tasks here. -

-
-
-

Exit

-
-

- Things to check for before voting the project out. -

-

Organizational acceptance of responsibility for the project

-
-
    -
  • If graduating to an existing PMC, has the PMC voted to accept it?
  • -
  • If graduating to a new PMC, has the board voted to accept it?
  • -
-
-

Incubator sign-off

-
-
    -
  • Has the Incubator decided that the project has accomplished all of - the above tasks?
  • -
-
-
-
-
-
- -

-
- -
-
- - http://git-wip-us.apache.org/repos/asf/incubator/blob/d8d548ab/content/projects/brooklyn.html ---------------------------------------------------------------------- diff --git a/content/projects/brooklyn.html b/content/projects/brooklyn.html deleted file mode 100644 index 49e78b2..0000000 --- a/content/projects/brooklyn.html +++ /dev/null @@ -1,559 +0,0 @@ - - - - - - - - Brooklyn Project Incubation Status - Apache Incubator - - - -
-
The Apache Software Foundation
-
The Apache Software Foundation Incubator
-
-
-

-
- - -
-

Brooklyn Project Incubation Status

-
-

This page tracks the project status, incubator-wise. For more general - project status, look on the project website.

-

The Brooklyn project graduated on 2015-11-18

-
-

Description

-
-

Brooklyn is a framework for modelling, monitoring, and managing applications through autonomic blueprints.

-
-

News

-
-
    -
  • 2015-11-18: ASF board passes our resolution to graduate.
  • -
-
    -
  • 2015-09-07: Welcome Ciprian Ciubotariu as new committer and PPMC member.
  • -
-
    -
  • 2015-08-08: Welcome Svetoslav Neykov as new committer and PPMC member.
  • -
-
    -
  • 2015-07-30: Welcome Hadrian Zbarcea as new committer and PPMC member.
  • -
-
    -
  • 2015-07-27: Apache Brooklyn 0.7.0 (incubating) released.
  • -
-
    -
  • 2014-12-23: Apache Brooklyn 0.7.0-M2 (incubating) released.
  • -
-
    -
  • 2014-07-04: Welcome Andrea Turli as new committer and PPMC member.
  • -
-
    -
  • 2014-06-30: Welcome Samuel Corbett as new committer and PPMC member.
  • -
-
    -
  • 2014-05-02: Source code available via the ASF git repos. The project uses the RTC workflow.
  • -
-
    -
  • 2014-05-02: Mailing lists created and activity begins.
  • -
-
    -
  • 2014-05-01: Project enters incubation.
  • -
-
-

Project info

-
- - -
    -
  • link to the project status file (Committers,non-incubation action - items,project resources, etc)
  • -
-

If the project website and code repository are not yet setup, use the - following table:

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
itemtypereference
Websitewww - http://brooklyn.incubator.apache.org/ -
.wiki.
Mailing listdevdev@brooklyn.incubator.apache.org
.commitscommits@brooklyn.incubator.apache.org
Bug tracking. - https://issues.apache.org/jira/browse/BROOKLYN/ -
Source codeGit - https://git-wip-us.apache.org/repos/asf/incubator-brooklyn.git -
.Git - https://git-wip-us.apache.org/repos/asf/incubator-brooklyn.git -
MentorshogstromMatt Hogstrom
.akarasuluAlex Karasulu
.ke4qqqDavid Nalley
.marrsMarcel Offermans
.jbonofreJean-Baptiste Onofré
.olamyOlivier Lamy
.chipchildersChip Childers
.asavuAndrei Savu
.jzbJoe Brockmeier
.jimJim Jagielski
CommittersaledsageAled Sage
.heneveldAlex Heneveld
.andreaturliAndrea Turli
.grkvltAndrew Kennedy
.cipiCiprian Ciubotariu
.hadrianHadrian Zbarcea
.richardRichard Downer
.sjcorbettSam Corbett
.svetSvetoslav Neykov
-
-

Incubation status reports

- -

Incubation work items

-
-

Project Setup

-
-

This is the first phase on incubation, needed to start the project at Apache.

-

- Item assignment is shown by the Apache id. - Completed tasks are shown by the completion date (YYYY-MM-dd). -

-

Identify the project to be incubated

-
- - - - - - - - - - - - - - - - - -
dateitem
2014-05-01, 2015-09-18Make sure that the requested project name does not already exist. Please follow - the guide to ensure a suitable project/product name.
2014-04-23If request from outside Apache to enter an existing Apache project, - then post a message to that project for them to decide on acceptance.
2014-05-05If request from anywhere to become a stand-alone PMC, then assess the - fit with the ASF, and create the lists and modules under the - incubator address/module names if accepted.
-
-

Infrastructure

-
- - - - - - - - - - - - - - - - - - - - - - - - - -
dateitem
2014-05-15Ask infrastructure to create source repository modules - and grant the committers karma.
2014-05-02Ask infrastructure to set up and archive mailing lists.
2014-05-14Ask infrastructure to set up issue tracker (JIRA, Bugzilla).
N/AAsk infrastructure to set up wiki (Confluence, Moin).
2014-05-15Migrate the project to our infrastructure.
-
-

Mentor-related responsibility/oversight

-
- - - - - - - - - - - - - - - - - -
dateitem
2014-05-05Subscribe all Mentors on the pmc and general lists.
2014-05-02Give all Mentors access to the incubator SVN repository. - (to be done by the Incubator PMC chair or an Incubator PMC - Member wih karma for the authorizations file)
2104-05-15Tell Mentors to track progress in the file - 'incubator/projects/brooklyn.html'
-
- -
- - - - - - - - - - - - - -
dateitem
2014-05-03Check and make sure that the papers that transfer rights to the ASF - been received. It is only necessary to transfer rights for the - package, the core code, and any new code produced by the project. -
2014-05-30Check and make sure that the files that have been donated have been - updated to reflect the new ASF copyright.
-
-

Verify distribution rights

-
- - - - - - - - - - - - - -
dateitem
2015-07-27Check and make sure that for all code included with the distribution - that is not under the Apache license, we have the right to combine - with Apache-licensed code and redistribute. -
2015-07-27Check and make sure that all source code distributed by the project - is covered by one or more of the following approved licenses: Apache, - BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially - the same terms.
-
-

Establish a list of active committers

-
- - - - - - - - - - - - - - - - - -
dateitem
2014-05-15Check that all active committers have submitted a contributors - agreement.
2014-05-27Add all active committers in the STATUS file.
2014-06-03Ask root for the creation of committers' accounts on - people.apache.org.
-
-

Project specific

-
-

- Add project specific tasks here. -

-
-
-

Incubation

-
-

These action items have to be checked for during the whole incubation process.

-

- These items are not to be signed as done during incubation, as they - may change during incubation. - They are to be looked into and described in the status reports and - completed in the request for incubation signoff. -

-

Collaborative Development

-
-
    -
  • Have all of the active long-term volunteers been identified and - acknowledged as committers on the project? -
  • -
  • Are there three or more independent committers? (The legal definition - of independent is long and boring, but basically it means that there - is no binding relationship between the individuals, such as a shared - employer, that is capable of overriding their free will as - individuals, directly or indirectly.)
  • -
  • Are project decisions being made in public by the committers?
  • -
  • Are the decision-making guidelines published and agreed to by all of - the committers?
  • -
-
-

Licensing awareness

-
-
    -
  • Are all licensing, trademark, credit issues being taken care of and - acknowleged by all committers?
  • -
-
-

Project Specific

-
-

- Add project specific tasks here. -

-
-
-

Exit

-
-

- Things to check for before voting the project out. -

-

Organizational acceptance of responsibility for the project

-
-
    -
  • If graduating to an existing PMC, has the PMC voted to accept it?
  • -
  • If graduating to a new PMC, has the board voted to accept it?
  • -
-
-

Incubator sign-off

-
-
    -
  • Has the Incubator decided that the project has accomplished all of - the above tasks?
  • -
-
-
-
-
-
- -

-
- -
-
- - http://git-wip-us.apache.org/repos/asf/incubator/blob/d8d548ab/content/projects/buildr.html ---------------------------------------------------------------------- diff --git a/content/projects/buildr.html b/content/projects/buildr.html deleted file mode 100644 index 8c4eaf5..0000000 --- a/content/projects/buildr.html +++ /dev/null @@ -1,475 +0,0 @@ - - - - - - - - Buildr Incubation Status - Apache Incubator - - - -
-
The Apache Software Foundation
-
The Apache Software Foundation Incubator
-
-
-

-
- - -
-

Buildr Project Incubation Status

-
-

This page tracks the project status, incubator-wise. For more general - project status, look on the project website.

-

The Buildr project graduated on 2009-02-23

-
-

Description

-
-

Buildr is a build system for Java applications written in Ruby. We wanted something that’s simple and intuitive to use, so we only need to tell it what to do, and it takes care of the rest. But also something we can easily extend for those one-off tasks, with a language that’s a joy to use. And of course, we wanted it to be fast, reliable and have outstanding dependency management.

-
-

News

-
-
    -
  • 2008-10-16 Buildr 1.3.3 release.
  • -
  • 2008-08-20 Antoine Contal has been voted in the Buildr PPMC.
  • -
  • 2008-08-20 Antoine Contal has been accepted as a new committer.
  • -
  • 2008-07-24 Buildr 1.3.2 release.
  • -
  • 2008-05-28 Buildr 1.3.1 release.
  • -
  • 2008-04-30 Buildr 1.3 release.
  • -
  • 2008-04-25 Victor Hugo Borja has been accepted in the Buildr PPMC.
  • -
  • 2008-01-30 Victor Hugo Borja is a new committer.
  • -
  • 2007-11-01 Buildr enters the Incubator.
  • -
-
-

Project info

-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
itemtypereference
Websitewww - http://incubator.apache.org/buildr/ -
Mailing Listdevbuildr-dev@incubator.apache.org
.commitsbuildr-commits@incubator.apache.org
Bug trackingJira - https://issues.apache.org/jira/browse/BUILDR -
Source codesvn - http://svn.apache.org/repos/asf/incubator/buildr/ -
MentorsjimJim Jagielski
.yoavsYoav Shapira
.mriouMatthieu Riou
CommittersassafAssaf Arkin
.boisvertAlex Boisvert
.lactonAntoine Contal
.mriouMatthieu Riou
.vborjaVictor Hugo Borja
-
-

Incubation status reports

- -

Incubation work items

-
-

Project Setup

-
-

This is the first phase on incubation, needed to start the project at Apache.

-

- Item assignment is shown by the Apache id. - Completed tasks are shown by the completion date (YYYY-MM-dd). -

-

Identify the project to be incubated

-
- - - - - - - - - - - - - - - - - - - - - -
dateitem
2007-11-15Make sure that the requested project name does not already exist and - check www.nameprotect.com to be sure that the name is not already - trademarked for an existing software product.
N/AIf request from an existing Apache project to adopt an external - package, then ask the Apache project for the SVN module and mail - address names.
N/AIf request from outside Apache to enter an existing Apache project, - then post a message to that project for them to decide on acceptance.
N/AIf request from anywhere to become a stand-alone PMC, then assess the - fit with the ASF, and create the lists and modules under the - incubator address/module names if accepted.
-
-

Interim responsibility

-
- - - - - - - - - - - - - - - - - - - - - -
dateitem
2007-11-01Identify all the Mentors for the incubation, by asking all that can - be Mentors.
2007-11-13Subscribe all Mentors on the pmc and general lists.
2007-11-13Give all Mentors access to the incubator SVN repository. - (to be done by the Incubator PMC chair or an Incubator PMC - Member wih karma for the authorizations file)
2007-11-13Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html'
-
- -
- - - - - - - - - - - - - -
dateitem
2007-11-10Check and make sure that the papers that transfer rights to the ASF - been received. It is only necessary to transfer rights for the - package, the core code, and any new code produced by the project. -
2008-10-17Check and make sure that the files that have been donated have been - updated to reflect the new ASF copyright.
-
-

Verify distribution rights

-
- - - - - - - - - - - - - -
dateitem
2008-04Check and make sure that for all code included with the distribution - that is not under the Apache license, e have the right to combine - with Apache-licensed code and redistribute. -
2008-04Check and make sure that all source code distributed by the project - is covered by one or more of the following approved licenses: Apache, - BSD, Artistic, MIT/X, MIT/W3C, MPL 1.1, or something with essentially - the same terms.
-
-

Establish a list of active committers

-
- - - - - - - - - - - - - - - - - -
dateitem
2007-11-01Check that all active committers have submitted a contributors - agreement.
2007-11-01Add all active committers in the STATUS file.
2007-11-01Ask root for the creation of committers' accounts on - people.apache.org.
-
-

Infrastructure

-
- - - - - - - - - - - - - - - - - - - - - -
dateitem
2007-11-02Ask infrastructure to create source repository modules and grant the - committers karma.
2007-11-01Ask infrastructure to set up and archive Mailing lists.
2007-11-01Decide about and then ask infrastructure to setup an issuetracking - system (Bugzilla, Scarab, Jira).
2007-11-13Migrate the project to our infrastructure.
-
-

Project specific

-
- - - - - - - - - -
dateitem
2008-03-22Clarify policy regarding Gem dependencies and the Ruby license.
-
-
-

Incubation

-
-

These action items have to be checked for during the whole incubation process.

-

- These items are not to be signed as done during incubation, as they - may change during incubation. - They are to be looked into and described in the status reports and - completed in the request for incubation signoff. -

-

Collaborative Development

-
-
    -
  • Have all of the active long-term volunteers been identified and - acknowledged as committers on the project? -
  • -
  • Are there three or more independent committers? (The legal definition - of independent is long and boring, but basically it means that there - is no binding relationship between the individuals, such as a shared - employer, that is capable of overriding their free will as - individuals, directly or indirectly.)
  • -
  • Are project decisions being made in public by the committers?
  • -
  • Are the decision-making guidelines published and agreed to by all of - the committers?
  • -
-
-

Licensing awareness

-
-
    -
  • Are all licensing, trademark, credit issues being taken care of and - acknowleged by all committers?
  • -
-
-
-

Exit

-
-

- Things to check for before voting the project out. -

-

Organizational acceptance of responsibility for the project

-
-
    -
  • If graduating to a new PMC, has the board voted to accept it? Yes.
  • -
-
-

Incubator sign-off

-
-
    -
  • Has the Incubator decided that the project has accomplished all of - the above tasks?
  • -
  • Yes. The resolution to make Buildr a TLP has been approved in Dec. 2008.
  • -
-
-
-
-
-
- -

-
- -
-
- - --------------------------------------------------------------------- To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org For additional commands, e-mail: cvs-help@incubator.apache.org