public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: "Linda Wang" <linda@decru.com>
To: ecos-maintainers@sources.redhat.com
Subject: eCos license questions
Date: Mon, 25 Jul 2005 20:52:00 -0000	[thread overview]
Message-ID: <web-3953827@mail1.decru.com> (raw)

Dear eCos Maintainers,

We're researching the possibility of using eCos in one of
our products, but we have some questions regarding the
license.

Th eCos License Overview says that "the license does not
require users to release the source code of any
applications that are developed with eCos."  What exactly
defines an eCos application?  Does it include drivers?
 Does it include any code statically linked into eCos?

The overview then goes on to say "if anybody makes changes
to code covered by the eCos license, or writes new files
derived in any way from the eCos code," then the source
code should be made public.  What does it mean to derive
code from eCos?  Does deriving code include using eCos
library functions and headers?

In the overview's Q&A section, it says "you would not need
to make available... the code of a wholly separate
application."  What does "wholly separate" mean?  Does it
remain wholly separate if the application is statically
linked into the eCos kernel?  Does it remain separate if it
calls eCos library functions?

Sorry if my questions are somewhat nit-picky.  Since we
make security products, our products must be certified by
various government agencies that require that we clearly
define our legal obligations.

Thanks in advance for your help,

Linda Wang
Software Engineer
Decru, Inc.
650-413-6737
linda@decru.com
http://www.decru.com

 

             reply	other threads:[~2005-07-25 20:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-25 20:52 Linda Wang [this message]
2005-07-28 12:06 ` 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=web-3953827@mail1.decru.com \
    --to=linda@decru.com \
    --cc=ecos-maintainers@sources.redhat.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).