incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "TavernaProposal" by StianSoilandReyes
Date Tue, 14 Oct 2014 13:50:17 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "TavernaProposal" page has been changed by StianSoilandReyes:
https://wiki.apache.org/incubator/TavernaProposal?action=diff&rev1=5&rev2=6

  
  === Initial Goals ===
   * Transition mailing lists to Apache (keep existing subscribers, but invite more)
-  * Taverna developer workshop (2014-10-30)
-  * Prepare git repositories for move:
+  * [[http://dev.mygrid.org.uk/wiki/display/developer/Taverna+Open+Development+Workshop|Taverna
developer workshop]] (2014-10-30)
+  * Stage git repositories for move at https://github.com/taverna-incubator :
    * Update headers/metadata to indicate Apache License 2.0
-   * Restructure git repositories
+   * Restructure git repositories (to ~ 10 repos?)
    * Rename Maven groupIds to org.apache.taverna.*
    * Rename packages to org.apache.taverna.*
-  * Move Github repositories to Apache git
+  * Move staged Github repositories to Apache git
   * Automated builds in Apache's Jenkins
   * Update to latest releases of Apache dependencies
   * Propose updated release and testing procedure under Apache
@@ -138, +138 @@

  
  One  of the reason for many repositories is that we rely on Apache Maven and  a plugin system
(since Taverna 3 OSGi-based) where different modules  have different version numbers and release
cycles (e.g. tags/branches).  This is essential for the plug-in support of Taverna as the
plug-ins  depend on the semantic versioning of the APIs and required  implementations.
  
- It is however in our current plans to merge  repositories that have similar release cycles
and greatly reduce the  number of repositories.
+ It is however in our current plans to merge  repositories that have similar release cycles
and greatly reduce the  number of repositories, to about 10 repositories that would be imported
to Apache's Git server.
+ 
+ We suggest that this would be the first phase of the incubator project, to prepare and stage
the merged repositories to https://github.com/taverna-incubator
  
  Taverna source code uses the package names (and children packages):
  
@@ -151, +153 @@

   * org.purl.wf4ever.provtaverna
   * org.biomart.martservice
  
- We  intend to release only the upcoming Taverna 3.0 version under the  Apache umbrella (not
2.x) - therefore, according to semantic versioning  rules http://semver.org/, the  transition
period of the Apache Incubator would be the best (and  possibly only) chance to rename Java
packages and Maven groupIDs to org.apache.taverna.*  Under OSGi the packaging and JAR goes
hand-in-hand (several JARs don't  normally provide the same package), and therefore any package
rename  would be done together with the repository restructuring.
+ We  intend to release only the upcoming Taverna 3.0 version under the  Apache umbrella (not
2.x) - therefore, according to semantic versioning  rules http://semver.org/, the  transition
period of the Apache Incubator would be the best (and  possibly only) chance to rename Java
packages and Maven groupIDs to ''org.apache.taverna.*''  Under OSGi the packaging and JAR
goes hand-in-hand (several JARs don't  normally provide the same package), and therefore any
package rename  would be done together with the repository restructuring.
  
  === Source and Intellectual Property Submission Plan ===
-  * Taverna source code from http://github.com/taverna/
+  * Taverna source code from http://github.com/taverna/ (as staged to https://github.com/taverna-incubator
)
    * (c) University of Manchester.
    * Signed Apache-like [[http://www.taverna.org.uk/about/legal-stuff/contributors-guide/|CLAs]]
for all external contributors.
-   * Current  license is LGPL 2.1 (and GPL3 for one domain-specific download), as  copyright
holder Manchester can change this to Apache License 2.0
+   * Current  license is LGPL 2.1 (and GPL3 for one domain-specific download), as  sole copyright
holder Manchester will change this to Apache License 2.0
+   * Check-out-all-and-build meta project - https://github.com/taverna/taverna-build
-  * taverna.org.uk domain - registrant University of Manchester
+  * ''taverna.org.uk'' domain - registrant University of Manchester
   * http://www.taverna.org.uk/  content (c) University of Manchester
   * http://dev.mygrid.org.uk/wiki/display/tav250/ Confluence wiki content  (c) University
of Manchester
   * [[http://dev.mygrid.org.uk/wiki/display/developer/Home|http://dev.mygrid.org.uk/wiki/display/developer]]
Confluence wiki content (c) University of Manchester
@@ -170, +173 @@

  
  We are intending for our first Apache-based release to be Taverna 3, which has already reduced
this dependency list.
  
- We have performed an analysis of our dependencies of Taverna 3 at http://dev.mygrid.org.uk/wiki/display/developer/Taverna+Dependencies
- but this is not yet a complete list.
+ We have performed an analysis of our dependencies of Taverna 3 at http://dev.mygrid.org.uk/wiki/display/developer/Taverna+Dependencies
- this list should be complete for the dependencies (and their transitive dependencies) of
Taverna Workbench.
  
- A second analysis looks at the license of those dependencies at http://dev.mygrid.org.uk/wiki/display/developer/Third-party+licenses
 - where we have some incompatible (LGPL) dependencies. Most of these  are resolvable as they
are part of optional plugins to Taverna (e.g. R  support, BioMart). The dependency on Hibernate
requires some developer  effort to be replaced with either Apache Open JPA or a "No-SQL" 
solution.
+ The internal dependencies that are managed by Taverna/myGrid would need to be part of the
transition to Apache so that their license can change from LGPL 2.1 to Apache License 2.0.
As we will change groupId at the same time to ''org.apache.taverna'', it should be fairly
trivial to ensure that no JARs from the original Taverna repositories are included in the
first Apache releases, as
+ 
+  1. They are only available from the [[http://repository.mygrid.org.uk/|Taverna Maven repository]]
+  1. Their groupId (''net.sf.taverna''/''uk.org.mygrid''/''uk.org.taverna'') would be easy
to identify in the distribution folder.
+ 
+ We know that some of the external dependencies are licensed as LGPL, and for AstroTaverna,
some dependencies are licensed as LGPL. As Apache License is incompatible with *GPL (but not
vice versa), the general solution we suggest for this is to either:
+ 
+  * Try to use alternative non-LGPL dependencies, aka. Apache JPA instead of Hibernate
+  * Keep module that requires LGPL dependency as a separate Taverna plugin, maintained and
published independently at Github (e.g. https://github.com/wf4ever/astrotaverna ).
+ 
+ 
  
  === Cryptography ===
  Taverna uses these cryptography dependencies:

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message