The Airflow project seem to be in good shape! :)
As for mailing list transition, I'm afraid that can be a bit rough for any community. You can't simply set up forwarding as then the users would not get any replies to the new list. Each individual user will have to subscribe again to the new lists, using email commands, like how you subscribed to this list. Here's an example of how we provide instructions: http://taverna.incubator.apache.org/community/lists (You will notice we link to markmail.org as archive, which has a good search facility and seems to pick up emails faster than http://mail-archives.apache.org/ ) If you have access to the existing subscriber list it is possible to script some emails that effectively invite them to the list - they would then need to do the usual confirm reply to sign up. This is what we did with Taverna mailing lists, after extracting the existing subscriber list from Mailman. I am not sure if Google Groups would give you the email addresses though. (If you choose to do this, warn the old list well in advance on the existing lists so people will know to reply!). Let me know if anyone need the evil script .. As for your roadmap, I would recommend doing the first Apache release as a point-release "as is" after clearing any important Intellectual Property issues - and then work on big new features after that. This adds continuity to the project and helps you understand differences in the release process early. (I'm saying this with hindsight bias..:) If there are no further suggestions to your proposal, then I suggest you to send it again, adding [VOTE] to the subject :) On 21 March 2016 at 21:23, Siddharth Anand <san...@agari.com.invalid> wrote: > Hi Stian, > Thanks for the feedback. We are committed to moving towards Apache > community-friendly licensing as documented on > http://www.apache.org/legal/resolved.html#category-x > > I've added this to our Roadmap: > https://github.com/airbnb/airflow/wiki/Roadmap and I expect to tackle it > during the incubation phase. > > Regarding our Google group - yes. We will move to the > d...@airflow.incubator.apache.org mailing list. We currently have *258 > members*, with about 10 new members being added daily! If you have any > thoughts on how to make that transition more amenable to our community, > they are welcome. For one, the google group offers more functionality than > the old-style mailing lists. I don't mind moving. I would like to keep the > old group's messages searchable and provide an announcement feature to > point people to the Apache mailing list so they know where to go next if > they land on the Google group. Some threads will unfortunately be > decapitated, but we can provide a few months' time for our users to > transition to the Apache mailing lists, wrapping up topic threads or > copying them over. We will also need to stop accepting new members and > posts in the existing group, but I think that is pretty simple to do. > > Thanks for the heads up on CWL and Taverna. We will definitely look into > both. On our side, our user base is growing faster than we can keep up. > Hence, we are investing in growing the committer base and documentation, > and in leveraging processes in order to better meet the growing needs of > our community. We hope to reduce turn-around time on PR reviews/merges, > time between releases, bringing new developers on board, and converting > contributors to committers. > > > -s > > On Mon, Mar 21, 2016 at 4:23 PM, Stian Soiland-Reyes <st...@apache.org> > wrote: > >> 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 >> >> -- 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
