public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jifl@jifvik.org>
To: Michael Jones <mike@proclivis.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Freescale and Lua copyrights
Date: Fri, 24 Jan 2014 17:12:00 -0000	[thread overview]
Message-ID: <52E29EE4.5050702@jifvik.org> (raw)
In-Reply-To: <DAC9154A-C99A-49C4-BE56-32A3F7DD9A56@proclivis.com>

On 24/01/14 15:30, Michael Jones wrote:
> 
> I would like to resolve this quickly so I can plan for evolving the current
> semi-hacked working version of the iMX6 hal to a version suitable for
> incorporation (desired), or if the effort is too large, remain independent
> (not desired). It is difficult to know where to invest time without knowing
> what will be allowed.
> 
> Can you accept this Freescale Copyright into the official eCos code base:
>
> /*
>  * Copyright (c) 2012, Freescale Semiconductor, Inc.
>  * All rights reserved.
>  *
>  * THIS SOFTWARE IS PROVIDED BY FREESCALE "AS IS" AND ANY EXPRESS OR IMPLIED
>  * WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
>  * MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
>  * SHALL FREESCALE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
>  * EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT
>  * OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
>  * INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
>  * CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
>  * IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY
>  * OF SUCH DAMAGE.
>  */

Unfortunately that isn't a license, that's a copyright message with all rights
reserved, and a disclaimer. "All rights reserved" means there is no right to
copy, modify, redistribute, etc. You will need to talk to Freescale to get
that resolved, or to recode it, sorry. Note that this restriction on
redistribution applies whether or not you contribute it!

As has happened before, I suspect it's just sloppiness on Freescale's part and
they did intend it to be fully re-distributable, but with what it says above
that legally isn't the case.

> I have a Lua 5.2.3 port that is fully functional. It has minimal modifications. It is called from my telnetd package (will be submitted to eCos with full copyright assignment when mature). There is no way to rewrite this to avoid the copyright, so will you accept this Lua Copyright into the official eCos code base:
[snip]

Yes, the Lua licence is fine. The only thing I would request is that a note is
made in documentation reminding users of this license, since it won't be the
normal eCos one.

Good luck with Freescale!

Jifl

  reply	other threads:[~2014-01-24 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 15:31 Michael Jones
2014-01-24 17:12 ` Jonathan Larmour [this message]
2014-01-24 22:34   ` Michael Jones
2014-01-28 16:34     ` Jonathan Larmour
2014-01-28 22:26       ` Michael Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52E29EE4.5050702@jifvik.org \
    --to=jifl@jifvik.org \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=mike@proclivis.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).