Title: depot
This page tracks the project status, incubator-wise. For more general project status, look on the project website.
The Depot project retired on 2004-10-28
The Depot Project deals with integrated tools for automating downloading (with security checks), publishing (new artifacts) and managing the contents of the apache repository.
It also focuses on additional tools for manipulating metadata of the artifacts.
| item | type | reference |
|---|---|---|
| Website | www | http://incubator.apache.org/depot/ |
| . | wiki | . |
| Mailing list | dev | depot-dev@incubator.apache.org |
| . | cvs | depot-cvs@incubator.apache.org |
| Bug tracking | JIRA | . |
| Source code | SVN | /repos/asf/depot/ |
| Mentors | nicolaken | Nicola Ken Barozzi |
| Committers | ajack | Adam Jack |
| . | nickchalko | Nick Chalko |
| . | anou_mana | Anou Manavalan |
| . | mmay | Markus M. May |
| Extra | proposal | http://nagoya.apache.org/wiki/apachewiki.cgi?RepoProposal |
1). Is the STATUS file up to date? Yes. 2). Any legal, cross-project or personal issues that still need to be addressed? No. 3). What has been done for incubation since the last report? Project closed for lack of development. 4). Plans and expectations for the next period? Collaborate with Ant and Maven for artifact downloading. Hang out on the repository@apache.org. Eventually continue development on Sourceforge. 5). Any recommendations for how incubation could run more smoothly for you? The closing of the project is not due to problems/issues with Incubation.
1). Is the STATUS file up to date? No 2). Any legal, cross-project or personal issues that still need to be addressed? No, all files licensed, all commiters have singed CLA 3). What has been done for incubation since the last report? * Site update. * Packages renamed to "depot" 4). Plans and expectations for the next period? * Delete unused under developed code. * Complete Download manger for use by gump and others. * Support "directory artifacts" for use by antworks and others. 5). Any recommendations for how incubation could run more smoothly for you? n/a
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).
| date | item |
|---|---|
| 2003-12-04 | 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-12-04 | 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. |
| date | item |
|---|---|
| 2003-12-04 | Identify all the Mentors for the incubation, by asking all that can be Mentors. |
| 2003-12-04 | Subscribe all Mentors on the pmc and general lists. |
| 2003-12-04 | Give all Mentors access to all incubator CVS modules. (to be done by PMC chair) |
| 2003-12-04 | Tell Mentors to track progress in the file ‘incubator/projects/{project.name}.cwiki’ |
| date | item |
|---|---|
| 2003-12-04 | 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. |
| date | item |
|---|---|
| 2003-12-04 | 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. |
| 2003-12-04 | 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. |
| date | item |
|---|---|
| 2003-12-20 | Check that all active committers have submitted a contributors agreement. |
| 2003-12-20 | Add all active committers in the STATUS file. |
| 2003-12-20 | Ask root for the creation of committers' accounts on cvs.apache.org. |
| date | item |
|---|---|
| 2003-12-20 | Ask infrastructure to create source repository modules and add thecommitters to the avail file. |
| 2003-12-20 | 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. |
Add project specific tasks here.
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.
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?
Add project specific tasks here.
Things to check for before voting the project out.
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?