[openstack-dev] [all] "All rights reserved" V.S. "Apache license"
aji.zqfan at gmail.com
Mon Jan 19 01:32:06 UTC 2015
Yes, the main point is the conflict of reserved all, and abandon some
According to the order the last will take effect IIUC Monty Taylor's
I'm thinking that we should remove the "all rights reserved" words if we're
using Apache license.
Misleading is not a good thing, especially when it is for legal issue.
On Mon, Jan 19, 2015 at 6:53 AM, Stefano Maffulli <stefano at openstack.org>
> On Sat, 2015-01-17 at 16:07 -0500, Monty Taylor wrote:
> > It's actually a set of words that is no longer necessary as of the year
> > 2000. It's not communicating anything about a granted license, which is
> > what the Apache License does - it's actually just asserting that the
> > original copyright holder asserts that they have not waived any of their
> > rights as a copyright holder. However, the Berne convention grants this
> > automatically without a positive assertion.
> I think ZhiQiang Fan's question is about the sentence "all rights
> reserved" followed by the implicit "some rights not reserved" granted by
> the Apache license, rather than the meaning of 'all rights reserved'
> alone. You're right that such sentence by itself is meaningless but in
> the context of the Apache license I think it's confusing at best,
> probably wrong.
> I don't remember seeing this case discussed on legal-discuss and I'm
> quite sure that the right way to apply the Apache license to source code
> is *not* by saying "(C) `date +%Y` Foo Corp, All Rights Reserved"
> followed by Apache license (see appendix on
> Maybe a passage on legal-discuss would be better?
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev