[
https://issues.apache.org/jira/browse/COMMONSSITE-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551810
]
Simon Kitching commented on COMMONSSITE-21:
-------------------------------------------
Sebb, it would be good if you could find a link to that email thread re LICENSE
because that is not my understanding of how it works.
AIUI, we *always* distribute software under just the APL2. And that means that
anyone who wants to use any part of our software can always do so under the
terms of that license. There *might* be parts that are even more liberal, but
it is not our responsibility to point those bits out. So just an APL2 license
file is all that is needed.
I vaguely remember that there are cases where we do distribute the occasional
file that has a less liberal licence, eg xml schemas.. But in that case, the
file itself carries the necessary license. Of course we only do this where
redistribution is legal, and anyone wanting to *modify* cannot possibly be
unaware that the file they are modifying has another license because the terms
are in the file. We may need to acknowledge the provider of that software - but
that's what NOTICE is for. NOTE: this bit is from memory, don't sue me over it
:-)
> commons-parent-6 pom changes
> ----------------------------
>
> Key: COMMONSSITE-21
> URL: https://issues.apache.org/jira/browse/COMMONSSITE-21
> Project: Commons All
> Issue Type: Improvement
> Components: Commons Parent Pom
> Reporter: Niall Pemberton
> Attachments: commons-valdiator-generated-NOTICE.txt,
> COMMONSSITE-21-commons-parent-pom-v1.patch,
> COMMONSSITE-21-commons-parent-pom-v2.patch
>
>
> Opening this ticket to discuss changes for Version 6 of the commons-parent
> pom.
> See thread: http://tinyurl.com/39eo9z for related discussion/issues
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
