Airflow sounds like an interesting workflow project!
You will need to review the licenses of dependencies - some of them are not compatible with ASF policy [1], e.g. https://pypi.python.org/pypi/psycopg2 is LGPL, which is not permitted. (I didn't check all of them) You may be able to work around this particular one if you are using Python's DB API 2.0 and don't have an explicit dependency on psycopg2 (e.g. so a downstream user can reasonably use Airflow without psycopg2) (Note: you can solve this as part of incubation process - but say if your project strongly used 15 GPL and LGPL dependencies, then your project might want to reconsider if it would be worth the effort) I recognize the challenge of engaging extension developers to also care about the 'core'. Moving to an "Apache Way" open development will probably help for this, as all dev discussions are in the open. Is your plan to move the existing Airflow Google Groups to what will be the d...@airflow.incubator.apache.org mailing list? Have you been talking to the SciDap folks doing Common Workflow Language [3] support with Airflow? That could be one angle to look at increasing the user base. We're also working on Docker and CWL support in Apache Taverna [4] - so I'm interested in seeing what we could have in common! [1] http://www.apache.org/legal/resolved.html [2] https://github.com/SciDAP/scidap [3] http://www.commonwl.org/ [4] http://taverna.incubator.apache.org/ On 17 March 2016 at 00:28, Siddharth Anand <san...@agari.com.invalid> wrote: > https://wiki.apache.org/incubator/AirflowProposal > > Thoughts and comments are welcome! > -s (Sid) -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718 --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
