This page tracks the project status, incubator-wise. For more general project status, look on the project website.
Livy Project Incubation Status
Description
Livy is web service that exposes a REST interface for managing long running Apache Spark contexts in your cluster. With Livy, new applications can be built on top of Apache Spark that require fine grained interaction with many Spark contexts.
News
- 2017-06-05 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:
| item | type | reference |
|---|---|---|
| Website | www | https://livy.incubator.apache.org/ |
| . | wiki | . |
| Mailing list | dev | dev@livy.incubator.apache.org |
| . | commits | commits@livy.incubator.apache.org |
| . | user | user@livy.incubator.apache.org |
| . | issues | issues@livy.incubator.apache.org |
| . | reviews | reviews@livy.incubator.apache.org |
| Bug tracking | . | [ provide expected link ] |
| Source code | GIT | |
| Mentors | bikas | Bikas Saha |
| . | brock | Brock Noland |
| . | lresende | Luciano Resende |
| . | jbonofre | Jean-Baptiste Onofré |
| Committers | vanzin | Marcelo Vanzin |
| . | . | Alex Man |
| . | zjffdu | Jeff Zhang |
| . | jshao | Saisai Shao |
| . | . | Kostas Sakellis |
| Extra | . | . |
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
| date | item |
|---|---|
| ....-..-.. | Make sure that the requested project name does not already exist. Please follow the guide to ensure a suitable project/product name. |
Infrastructure
| date | item |
|---|---|
| ....-..-.. | Ask infrastructure to set up and archive mailing lists. Done using mlreq. |
| ....-..-.. | Ask infrastructure to create source repository modules and grant the committers karma. |
| ....-..-.. | Ask infrastructure to set up issue tracker and do import if needed (file against INFRA JIRA). |
| ....-..-.. | Ask infrastructure to set up wiki (Confluence, Moin). |
| ....-..-.. | Migrate the project to our infrastructure. |
Mentor-related responsibility/oversight
| date | item |
|---|---|
| ....-..-.. | Subscribe all Mentors on the pmc and general lists. |
| ....-..-.. | Give 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) |
| ....-..-.. | Tell Mentors to track progress in the file 'incubator/projects/{project.name}.html' |
Copyright
| date | item |
|---|---|
| ....-..-.. | 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
| date | item |
|---|---|
| ....-..-.. | 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. |
| ....-..-.. | 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 |
|---|---|
| ....-..-.. | Check that all active committers have submitted a contributors agreement. |
| ....-..-.. | Add all active committers in the relevant section above. |
| ....-..-.. | Ask root for the creation of committers' accounts in LDAP. |
Project specific
Add project specific tasks here.
| date | item |
|---|---|
| ....-..-.. | Cloudera currently owns the domain name: http://livy.io/. Once all the documentation has moved over to ASF infrastructure, the main landing page will become livy.incubator.apache.org and the old domain will just act as a redirect. |
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?