Title: Fluo Project Incubation Status
This page tracks the project status, incubator-wise. For more general project status, look on the project website.
Fluo is a distributed system for incrementally processing large data sets stored in Accumulo.
The Fluo project graduated on 2017-07-19
2016-05-17 Project enters incubation.
2016-08-07 build-resources-1.0.0-incubating released
2016-08-07 fluo-parent-1-incubating released
2016-10-05 fluo-1.0.0-incubating released
2016-10-27 fluo-recipes-1.0.0-incubating released
2017-05-31 New committer: Christopher McTague
2017-06-12 fluo-1.1.0-incubating released
2017-06-22 fluo-recipes-1.1.0-incubating released
link to the main website: https://fluo.apache.org
link to the page(s) that tell how to participate (Website,Mailing lists,Bug tracking,Source code): How To Contribute and Get Involved
link to the project status file (Committers,non-incubation action items,project resources, etc): Contributors
If the project website and code repository are not yet setup, use the following table:
| item | type | reference |
|---|---|---|
| Website | www | http://fluo.incubator.apache.org/ |
| Mailing lists | dev | dev @ fluo.incubator.apache.org |
| . | notifications | notifications @ fluo.incubator.apache.org |
| . | commits | commits @ fluo.incubator.apache.org |
| Bug tracking | Github Issues | https://github.com/apache/incubator-fluo/issues |
| Bug tracking | Github Issues | https://github.com/apache/incubator-fluo-recipes/issues |
| Bug tracking | Github Issues | https://github.com/apache/incubator-fluo-website/issues |
| Source code | GIT | https://gitbox.apache.org/repos/asf/incubator-fluo.git |
| Source code | GIT | https://gitbox.apache.org/repos/asf/incubator-fluo-recipes.git |
| Source code | GIT | https://gitbox.apache.org/repos/asf/incubator-fluo-website.git |
| Mentors | billie | Billie Rinaldi |
| . | drew | Drew Farris |
| . | elserj | Josh Elser |
| Committers | cjnolet | Corey Nolet |
| . | ctubbsii | Christopher Tubbs |
| . | elserj | Josh Elser |
| . | kturner | Keith Turner |
| . | mwalch | Mike Walch |
| . | cjmctague | Christopher McTague |
| Extra | . | . |
May 2016 (mentioned only)
September 2016 (mentioned only)
October 2016 (mentioned only)
April 2017 (mentioned only)
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 |
|---|---|
| 2016-09-20 | Make sure that the requested project name does not already exist. Please follow the guide to ensure a suitable project/product name. |
| 2016-06-21 | 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 |
|---|---|
| 2016-05-17 | Ask infrastructure to set up and archive mailing lists. |
| 2016-06-21 | Ask infrastructure to create source repository modules and grant the committers karma. |
| 2016-06-21 | Ask infrastructure to set up issue tracker (JIRA, Bugzilla). |
| 2016-06-21 | Migrate the project to our infrastructure. |
| date | item |
|---|---|
| 2016-06-21 | Subscribe all Mentors on the pmc and general lists. |
| 2016-06-21 | 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) |
| 2016-06-21 | Tell Mentors to track progress in the file ‘incubator/projects/{project.name}.xml’ |
| date | item |
|---|---|
| 2016-05-17 | 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. |
| 2017-06-22 | Check and make sure that the files that have been donated have been updated to reflect the new ASF copyright. |
| date | item |
|---|---|
| 2017-06-22 | 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. |
| 2017-06-22 | 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 |
|---|---|
| 2016-05-17 | Check that all active committers have submitted a contributors agreement. |
| 2016-05-17 | Add all active committers in the relevant section above. |
| 2016-05-17 | Ask root for the creation of committers' accounts in LDAP. |
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?