[License-review] Submission of the Upstream Compatibility License v1.0 (UCL-1.0) for approval

[Josh berkus]

On 10/24/2016 09:43 PM, Nigel T wrote:
> Josh,
> 
> Well, it's copyleft so you have to publish the changes made by your
> derivative work to anyone you release it to.
> 
> In the 4th generation derivative work, anything after your first
> contribution you have Apache.  Anything before your first contribution
> you have UCL.  I guess you can diff with your own repo to see where it
> first forked and if they have pulled since.  If the code is from a
> foreign repo then more archeology may be required.
> 
> As to why not just saying that all additional code added as derivative
> works is published under Apache 2.0...um...I don't have a good answer. :)
> 
> I'm releasing this code as copyleft but everything added by anyone else
> is permissive.  Hmmm...I'll sleep on that but seems like it would work
> and be conceptually simpler.  If that removes any OSD 5 concerns then it
> might be the way to go.  Thanks.

Yes, and speaking as a developer, I would really appreciate having a
requirement that derivative works developers publish release notes
summarizing their changes, so that I know which portions are Apache and
which are UPL.  I've seen this in some other licenses.