The Apache Ivy project has completed incubation, more
information will become available from the Ant website soon.
Until the migration has finished, more information on Ivy is
avaliable from http://incubator.apache.org/ivy/.
Ivy is a tool for managing (recording, tracking, resolving and reporting)
project dependencies. It is characterized by the following:
1. flexibility and configurability - Ivy is essentially process agnostic
and is not tied to any methodology or structure.
Instead it provides the necessary flexibility and configurability to be
adapted to a broad range of dependency management and build processes.
2. tight integration with Apache Ant - while available as a standalone
tool, Ivy works particularly well with Apache Ant providing a number of
powerful Ant tasks ranging from dependency resolution to dependency
reporting and publication.
This is the first phase on incubation, needed to start the
project at Apache. DONE.
| Date |
Item |
| 2006-10-26 |
Identify all the Mentors for the incubation, by asking all
that can be Mentors.
|
| 2006-10-26 |
Subscribe all Mentors on the pmc and general lists. |
| 2006-10-26 |
Give all Mentors access to all incubator SVN modules. (to be
done by PMC chair)
|
| 2006-10-26 |
Tell Mentors to track progress in the file
'incubator/projects/ivy.html' which is generated
from the XML status file.
|
| Date |
Item |
| 2006-11-22 |
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.
|
| 2007-04-20 |
Check and make sure that the files that have been donated
have been updated to reflect the new ASF copyright.
|
| Date |
Item |
| 2007-04-20 |
Check and make sure that for all code included with the
distribution that is not under the Apache license have the
right to combine with Apache-licensed code and redistribute.
|
| 2007-04-20 |
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 |
| 2006-11-22 |
Check that all active committers have submitted a contributors
agreement.
|
| 2006-11-27 |
Add all active committers in the STATUS file. |
| 2006-11-22 |
Ask root for the creation of committers' accounts on
people.apache.org.
|
| Date |
Item |
| 2006-11-09 |
Create source repository modules and
grant the committers karma. Done.
|
| 2006-10-31 |
Ask infrastructure to set up and archive Mailing lists.
Done.
|
| 2006-10-31 |
Ask infrastructure to setup an issue
tracking system (Jira). Done.
|
| 2006-12-08 |
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?
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.)
Ivy started with two committers and added the
most active contributor rather quickly. The three of
them work for different entities. Upon graduation all
Ant committers will become Ivy committers as well
since Ant uses a single ACL for all subprojects.
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
-
Are all licensing, trademark, credit issues being taken care of
and acknowleged by all committers?
Yes
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?
Yes
-
If graduating to a new PMC, has the board voted to accept it?
-
Has the Incubator decided that the project has accomplished
all of the above tasks?
Yes
Incubation status reports