This page tracks the project status, incubator-wise. For more general
project status, look at the
project website.
The Etch project graduated on 2013-01-16
Etch - a cross-platform, language- and transport-independent
framework for building and consuming network services.
Etch is a cross-platform, language- and transport-independent
framework for building and consuming network services. The Etch
toolset includes a network service description language, a compiler,
and binding libraries for a variety of programming languages. Etch is
also transport-independent, allowing for a variety of different
transports to used based on need and circumstance. The goal of Etch is
to make it simple to define small, focused services that can be easily
accessed, combined, and deployed in a similar manner. Ultimately with
Etch, service development and consumption becomes no more difficult
than library development and consumption.
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 |
note |
| 2012-04-16 |
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.
|
Prior to acceptance there was a great deal of discussion whether
Apache Etch would interfere with the Debian Etch distribution. The
sceptics meant that Debian Etch is extremely well-known name and
should be avoided. The team defended the position by pointing out
that by the time Apache Etch graduates, Debian Lenny has taken
over the world and another year or two the Debian Etch is just a
distant memory.
In 2012 Scott Corner has completed a suitable name search and didn't
uncover any issues. VP Trademarks has signed off the suitable name
search on 2012-04-16
|
| 2012-12-18 |
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 |
| 2008-07 |
Identify all the Mentors for the incubation, by asking all
that can be Mentors.
|
| 2008-10 |
Subscribe all Mentors on the private and development lists. |
| 2008-10 |
Give all initial committers access to the incubator SVN repository.
(to be done by PMC chair)
|
| 2008-11 |
Tell Mentors to track progress in the file
'incubator/projects/etch.html'
|
Copyright
| date |
item |
| 2011-08-20 |
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.
|
| 2009-06-12 |
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 |
| 2009-06-12 |
Check 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.
|
| 2009-06-12 |
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
| status |
item |
| 2008-10-22 |
Check that all active committers have submitted a contributors
agreement.
|
| 2008-10-25 |
Ask root for the creation of committers' accounts on
people.apache.org.
|
Infrastructure
| status |
item |
| 2008-11-11 |
Ask infrastructure to create source repository modules and
grant the committers karma.
|
| 2008-10-02 |
Ask infrastructure to set up and archive Mailing lists. |
| 2008-09-24 |
Decide about and then ask infrastructure to setup an issue
tracking system (Bugzilla, Scarab, Jira).
|
| 2008-11-10 |
Migrate the project to our infrastructure. |
Project specific
| status |
item |
| 2008-11-09 |
transfer project wiki pages from developer.cisco.com |
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
| status |
item |
| 2012-12-18 |
Have all of the active long-term volunteers been identified and
acknowledged as committers on the project? |
| 2012-12-18 |
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.) |
| 2012-12-18 |
Are project decisions being made in public by the committers? |
| 2012-12-18 |
Are the decision-making guidelines published and agreed to by all of
the committers? |
Licensing awareness
| status |
item |
| 2012-12-18 |
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
| status |
item |
| 2013-01-16 |
If graduating to a new PMC, has the board voted to accept it? |
Incubator sign-off
| status |
item |
| 2013-01-16 |
Has the Incubator decided that the project has accomplished all of
the above tasks? |
Etch Project Incubation Status