From: Alex Schuilenburg <alexs@ecoscentric.com>
To: eCos Disuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Re: HOWTO: eCos on QEMU PC emulator
Date: Tue, 29 Mar 2011 12:01:00 -0000 [thread overview]
Message-ID: <4D9074DD.70302@ecoscentric.com> (raw)
On 2011-03-25 15:26, John Dallaway wrote:
> Drasko
>
> Drasko DRASKOVIC wrote:
>
>>>> Second, if you re-distribute it, can not you do it the way you like -
>>>> for example putting it in git repository.
>>> Yes, you certainly can.
>> So why then the authors must assign copyright to the FSF and
>> contribute it in the order for us to put eCos sources in git tree ?
> You can put eCos-licensed sources in your _own_ repository and
> redistribute them without issue. However, it is eCos project policy that
> copyright in all contributions to the official eCos project repository
> must be assigned to the FSF. [ There are a few exceptions. ]
The only benefit I can think of wanting to publish your own repository
would be for the rapid-turnaround in shared development of your port.
While you can redistribute freely, there are a few good reasons why you
should consider contributing after the work is completed rather than
continuing to publish the code in your own repository.
1. Your repository will need to be updated regularly to benefit from
new features and prevent it from being left behind.
Don't underestimate the effort involved in keeping private
repositories updated.
2. Unless you provide a license and the usual guarantees associated
with an assignment, you are not likely to get many others using
your sources in commercial products for fear of running the risk
of violating patents or using source code of dubious/unknown origin.
The eCos assignment process overseen by the FSF provides a high
level of assurance of the origin of the source code as well as
ensures that the code can be used without the risk of running into
patent violations. This adds significantly to the strength of the
eCos brand.
3. If you start publishing the site, you must ensure that you follow
the eCos trademark usage policy at
http://www.ecoscentric.com/trademark_usage.shtml
Read the FAQ as to why we enforce this policy.
-- Alex Schuilenburg
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2011-03-28 11:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 12:01 Alex Schuilenburg [this message]
2011-03-29 12:56 ` Grant Edwards
[not found] ` <AANLkTi=2DOgy7xpyGBnbvf5gEfM2kE6PRDcyCqzyUM7b@mail.gmail.com>
2011-03-29 23:09 ` ricky wu
-- strict thread matches above, loose matches on Subject: below --
2011-03-24 11:11 [ECOS] " Grant Edwards
2011-03-24 12:34 ` Drasko DRASKOVIC
2011-03-24 16:26 ` [ECOS] " Grant Edwards
2011-03-24 16:44 ` Drasko DRASKOVIC
2011-03-24 16:48 ` Grant Edwards
2011-03-24 17:06 ` Grant Edwards
2011-03-24 17:12 ` John Dallaway
2011-03-24 17:19 ` Drasko DRASKOVIC
2011-03-24 17:41 ` Sergei Gavrikov
2011-03-24 21:30 ` John Dallaway
2011-03-24 17:59 ` Grant Edwards
2011-03-24 18:17 ` Sergei Gavrikov
2011-03-24 18:26 ` Sergei Gavrikov
2011-03-24 18:44 ` Grant Edwards
2011-03-24 18:51 ` Sergei Gavrikov
2011-03-24 19:06 ` Grant Edwards
2011-03-24 19:16 ` Sergei Gavrikov
2011-03-24 19:48 ` Grant Edwards
2011-03-25 8:26 ` Sergei Gavrikov
2011-03-24 22:19 ` John Dallaway
2011-03-25 14:10 ` Grant Edwards
2011-03-24 17:11 ` Drasko DRASKOVIC
2011-03-24 17:20 ` Grant Edwards
2011-03-24 17:45 ` Drasko DRASKOVIC
2011-03-25 14:48 ` Grant Edwards
2011-03-25 14:50 ` Drasko DRASKOVIC
2011-03-25 15:00 ` Grant Edwards
2011-03-25 15:02 ` Drasko DRASKOVIC
2011-03-25 15:17 ` ricky wu
2011-03-25 15:24 ` Grant Edwards
2011-03-25 15:27 ` Drasko DRASKOVIC
2011-03-25 15:37 ` John Dallaway
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=4D9074DD.70302@ecoscentric.com \
--to=alexs@ecoscentric.com \
--cc=ecos-discuss@ecos.sourceware.org \
/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).