On 25 September 2014 17:34, David Nalley <da...@gnsa.us> wrote: > Can you make sure a comprehensive list of those currently incompatible > list of dependencies is included in your proposal.
I have added them to http://dev.mygrid.org.uk/wiki/display/developer/Third-party+licenses and added references to this from https://wiki.apache.org/incubator/TavernaProposal#External_Dependencies and added complete resolution of the remaining "unknown" licenses to https://wiki.apache.org/incubator/TavernaProposal#Initial_Goals Should I move those sections from the Taverna wiki to embed in the proposal? (I think it could be a bit noisy). See https://github.com/taverna/taverna-build/tree/master/licenses for the complete lists as generated by Maven. >> Taverna 2 is licensed as LGPL 2.1, which meant we could use several >> LGPL libraries like Hibernate and RShell. Hibernate can be replaced by >> other JPA providers (with some code update to remove Hibernate >> specific calls), while the RShell support would have to be moved out >> to an separately installable plugin. > Do you have adequate rights to change the license wholesale? Yes, as we declare under https://wiki.apache.org/incubator/TavernaProposal#Source_and_Intellectual_Property_Submission_Plan we the University of Manchester is the copyright holder and contributitions from outside the University have all signed CLAs that allow us to change the license and redelegate copyright. > This sounds like fragmenting your existing community before you really > even get started. I believe the ASF is a great place, but I am not > convinced it's the best place for everyone. Yes, I am afraid the AstroTaverna community was not too keen on the perceived fragmentation, but as long as we keep the AstroTaverna developers involved in Apache Taverna (Julián Garrido is included as an Initial Committer), and keep the existing plugin support (with an additional "What do you want" splash screen on first start) it should not be a big change for existing users or indeed for developers. AstroTavena is already a separate project - at https://github.com/wf4ever/astrotaverna (of which I am personally also taking part) - and it is only in the recent Taverna Astronomy Edition (introduced in Taverna 2.5) that this plugin was brought into the release. The Astronomy Edition (if it is with a different plugin system in Taverna 3) can be distributed as a non-Apache release by the AstroTaverna community - our build system already have the editions parametrized so that this is not too difficult. > I see two paragraphs here that don't answer the question posed. Where > will plugin development happen in an ideal world? I guess as separate projects, but with a clear invitation to the Apache project so that such developers also get involved in the Apache Taverna community. One way to do such invitation is to include those plugins in the release (optional on install). > One followup question - what kind of build/CI resources does the > University of Manchester provide? What manner of resources do you > believe you'll need if the project moves to the ASF? We tried to detail this under https://wiki.apache.org/incubator/TavernaProposal#Required_Resources We should be fine with the existing capabilities as ASF already have Jenkins, Jira, Confluence, Git and Maven repositories. There would obviously be migrations jobs needed for existing documentation, issues etc. -- Stian Soiland-Reyes, myGrid team School of Computer Science The University of Manchester http://soiland-reyes.com/stian/work/ 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
