This page tracks the project status, incubator-wise. For more general project status, look on the project website .
The Pluto project graduated on 2004-05-15
Pluto Project Incubation Status
Description
Pluto is the Reference Implementation of the Java Portlet Specfication. The current version of this specification is <JSR 168|http://jcp.org/en/jsr/detail?id=168]. Please read the proposal that started the project in the incubator.
News
Pluto Graduated! On May 15, 2004, The Incubator PMC released Pluto to the Portals project. See thread at:
http://mail-archives.apache.org/eyebrowse/BrowseList?listName=general@ ncubator.apache.org&by=thread&from=751960
Project info
Incubation status reports
2004-05-01 Pluto Status
2004-05-01 Pluto Status * Is the STATUS file up to date? (also post
link) Yes. http://incubator.apache.org/projects/pluto.html * Any
legal, cross-project or personal issues that still need to be
addressed? No outstanding issues. * What has been done for incubation
since the last report? All project committers have received
confirmation that CLA's have been received and accepted. The Pluto
has worked hard towards 1.0 release of the Pluto Portlet Container
reference implementation. The release is ready, pending graduation of
Pluto from incubation. The Pluto Web Site has continued to be updated
and built out. http://jakarta.apache.org/pluto Upon graduation from
incubation and acceptance into Apache Portals, Pluto will be moved to
http://portals.apache.org/pluto All source files have been modified
to include the ASF v2.0 copyright notice. The mailing lists
pluto-dev@jakarta.apache.org and pluto-user@jakarta.apache.org are
now being archived at both Apache and MARC. Past list traffic has
been imported into the Apache archives. * What are the project's
plans and expectations for the next period? Put out release 1.0 to
coincide with the Java Portlet API Specification. Future work will
include refactoring and compontenization of Pluto, and support of the
next release of the Java Portlet API Specification. Assemble a to-do
list (roadmap) for future development and publish to the Pluto web
site. Exit the Apache Incubator (hey, it was fun). * Any
recommendations for how incubation could run more smoothly for you?
The current process has worked well for us.
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
| date | item |
|---|---|
| ....-..-.. | 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. |
| 2003-09-13 | If request from an existing Apache project to adopt an external package, then ask the Apache project for the cvs module and mail address names. |
| 2003-09-13 | If request from outside Apache to enter an existing Apache project, then post a message to that project for them to decide on acceptance. |
| 2003-09-13 | 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
| date | item |
|---|---|
| 2003-10-03 | Identify all the Mentors for the incubation, by asking all that can be Mentors. |
| 2003-10-03 | Subscribe all Mentors on the pmc and general lists. |
| 2003-10-03 | Give all Mentors access to all incubator CVS modules. (to be done by PMC chair) |
| 2003-10-03 | Tell Mentors to track progress in the file 'incubator/projects/{project.name}.cwiki' |
Copyright
| date | item |
|---|---|
| 2004-05-03 | 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. |
| 2004-05-03 | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. |
Verify distribution rights
| date | item |
|---|---|
| 2004-04-13 | 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. |
| 2004-04-13 | 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 !
| date | item |
|---|---|
| 2004-01-21 | Check that all active committers have submitted a contributors agreement. |
| 2004-02-13 | Add all active committers in the STATUS file. |
| 2004-01-21 | Ask root for the creation of committers' accounts on cvs.apache.org. |
Infrastructure !
| date | item |
|---|---|
| 2003-09-13 | Ask infrastructure to create source repository modules and grant the committers karma. |
| 2003-09-13 | Ask infrastructure to set up and archive Mailing lists. |
| 2003-09-13 | Decide about and then ask infrastructure to setup an issuetracking system (Bugzilla, Scarab, Jira). |
| 2003-09-13 | Migrate the project to our infrastructure. |
Incubation
Collaborative Development
- Have all of the active long-term volunteers been identified and acknowledged as committers on the project?
Yes.
- 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.)
Yes.
- Are project decisions being made in public by the committers?
Yes.
- Are the decision-making guidelines published and agreed to by all of the committers?
Yes.
Licensing awareness
- Are all licensing, trademark, credit issues being taken care of and acknowleged by all committers?
Yes.
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?
Yes. The Apache Portals Project PMC has voted to unanimously accept Pluto into the Apache Portals project.
- If graduating to a new PMC, has the board voted to accept it?
See above.
Incubator sign-off
- Has the Incubator decided that the project has accomplished all of the above tasks?
Yes. On May 15, 2004, The Incubator PMC released Pluto to the Portals project. See thread at:
http://mail-archives.apache.org/eyebrowse/BrowseList?listName=general@ ncubator.apache.org&by=thread&from=751960