www-legal-discuss mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis E. Hamilton (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LEGAL-264) Fork and distribute JAXB
Date Mon, 01 Aug 2016 02:22:21 GMT

    [ https://issues.apache.org/jira/browse/LEGAL-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401449#comment-15401449
] 

Dennis E. Hamilton commented on LEGAL-264:
------------------------------------------

I appreciate the language difficulty and how it takes some experience to navigate the various
open-source licenses and understand how to comply with them.

With regard to developing an external fork and complying with the license of the code on which
the fork is based, I have nothing to offer. 

On the assumption that the forks will themselves develop sources under the original license,
there is perhaps something to be discovered in how existing Apache Projects handle dependencies
on Category B software and perhaps specifically EPL and CDDL licenses.  

For these, you can find how the Category B licenses are provided and how NOTICE files are
worded.  It should be possible to know what must be provided with the distribution having
such a dependency.  The licenses make it rather clear what must be supplied.  Your PMC needs
to resolve that on its own account.  

> Fork and distribute JAXB
> ------------------------
>
>                 Key: LEGAL-264
>                 URL: https://issues.apache.org/jira/browse/LEGAL-264
>             Project: Legal Discuss
>          Issue Type: Question
>            Reporter: Andreas Beeker
>
> We would like (to try) to adapt JAXB ([1],[2]) to replace xmlbeans and to support android
- this would be a substantial part of Apache POI.
> JAXB is dual licensed under GPL v2 and CDDL 1.1 [3]
> The process of adapting JAXB would include repacking a current version and changing the
source [1] - after this modification the new library probably won't be changed until a new
JAXB version appears. 
> So would it be possible to distribute a JAXB fork and link to it from an ASF project?
[4]
> If yes, what would be the process to do so? (e.g. a new incubator project or simply another
POI module? how are new versions handled?)
> [1] http://www.docx4java.org/blog/2012/05/jaxb-can-be-made-to-run-on-android/
> [2] http://apache-poi.1045710.n5.nabble.com/xmlbeans-successor-tt5722870.html
> [3] https://issues.apache.org/jira/browse/LEGAL-121
> [4] http://stackoverflow.com/questions/2388786/i-cant-distribute-jaxb-closed-code



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org


Mime
View raw message