public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: Bart Veer <bartv@ecoscentric.com>
Cc: jifl@ecoscentric.com, ecos-maintainers@ecos.sourceware.org
Subject: Re: Contribution of a DHCP server (µDHCP) port to eCOS
Date: Mon, 30 Aug 2004 07:58:00 -0000	[thread overview]
Message-ID: <20040830075713.GA7542@biferten.ma.tech.ascom.ch> (raw)
In-Reply-To: <20040825222323.71CCBEC10C@delenn.bartv.net>

>     jifl> To other maintainers, I have a suggestion in general: to add
>     jifl> a new and separate CVS module called ecos-gpl, which has
>     jifl> full GPL'd (or LGPL'd) stuff in. This is not checked out by
>     jifl> default, nor would the packages in it be part of the
>     jifl> standard set in a full eCos release (not without explicit
>     jifl> user effort so they can recognise the license implications).
 
[Snip]

> A separate repository is a sensible minimal requirement. We do not
> want users to accidentally include GPL'd code in their application
> without realizing it. However I don't think a separate repository is
> sufficient, we also want explicit support in the host-side tools.
> There is already limited support for this in ecosadmin when installing
> a new package, but I don't think that is good enough. I haven't
> thought through the issues in detail, but two possibilities spring to
> mind:
> 
> 1) add a new CDL property license, probably only usable inside a
>    cdl_package. This would take an arbitrary string, so e.g.:
> 
>      cdl_package CYGPKG_SOMETHING {
>          license GPL
>          ...
>      }
>    
>    or
> 
>      cdl_package CYGPKG_OTHER {
>          license "Proprietary, see http://www.xyzzy.com/OTHER/license.html"
>          ...
>      }

I like this, but i think we are only addressing one of the two
issues. Ownership is the second issue. Code which is not owned by
RedHat, eCosCentric or the maintainers should also be placed into a
separate CVS tree. Its then clear what we can change the license on
and what not. JFFS2 and Gary's NAND flash driver thus should be in the
second tree, even though they both have mod GPL licenses. I would
suggest an "owners" property which is an arbitrary string. It would
take values like:

     owners "FSF"
     or 
     owners "Redhat+Maintainers"
     or 
     owners "Diverse"
     
The last case being used for example for jffs2 and the NAND flash
driver.

        Andrew

  parent reply	other threads:[~2004-08-30  7:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-25 13:20 sebastien Couret
2004-08-25 21:13 ` Jonathan Larmour
2004-08-25 22:23   ` Bart Veer
2004-08-26  0:20     ` Jonathan Larmour
2004-08-26 13:47       ` Bart Veer
2004-08-30  7:58     ` Andrew Lunn [this message]
2004-08-31 15:38     ` John Dallaway
2004-08-26 14:40   ` Contribution of a DHCP server (µDHCP)port " sebastien Couret
2004-08-26 18:52     ` Jonathan Larmour

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=20040830075713.GA7542@biferten.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --cc=bartv@ecoscentric.com \
    --cc=ecos-maintainers@ecos.sourceware.org \
    --cc=jifl@ecoscentric.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).