From: Jonathan Larmour <jifl@eCosCentric.com>
To: "Ferguson, Ian" <Ian.Ferguson@idt.com>
Cc: "'ecos-maintainers@sources.redhat.com'"
<ecos-maintainers@sources.redhat.com>,
"Chang, Sandra" <Sandra.Chang@idt.com>
Subject: Re: eCos port to IDT processors
Date: Wed, 16 Oct 2002 06:39:00 -0000 [thread overview]
Message-ID: <3DAD6C09.10904@eCosCentric.com> (raw)
In-Reply-To: <C8AEE7623CD92344B097388DA0ABD05CD4DFE6@corpexchange1.corp.idt.com>
Ferguson, Ian wrote:
> IDT has just completed (via an external contractor very familiar with the
> eCos operating system) a eCos port (v2.0) to an existing embedded processor.
> This CPU core uses a 32-bit MIPS CPU core.
>
> I have looked quickly through the FAQ and the license agreement, but I
> wanted to check with you on the next steps we must take to get this code
> released via yourselves into the public domain.
>
> Should we be emailing source code over to someone there once we sign the
> license agreement?
Well, the first thing to be aware of with respect to the licence is that
most of the web site refers to the licence for eCos 1.3.1, which, while it
is the "latest" release, is in fact a very old release. The licence for
new code has in fact changed. So be sure you are using the new licence
text based on the GPL and not the RHEPL.
The next step in any case is to get the copyright assignment sorted. That
should still be mailed to Red Hat. See
http://sources.redhat.com/ecos/assign.html for the two forms required for
that. The developer(s) sign the form and IDT sign the copyright disclaimer
form.
Then, finally :-), you send the code to ecos-patches@sources.redhat.com
where a maintainer will go through it and apply it. It's good to split it
up into manageable chunks if possible rather than a massive patch. Each
patch needs review, and the maintainer may give you review comments
indicating if something could be done a better way. Although most times
the maintainer will just make the changes themselves anyway!
After that, it's checked in and freely available with the main eCos
sources to the world!
> Sorry for such a basic question, but as it is the first time for us in the
> eCos world, we have a bit of a learning curve to go up.
No problems. We'll help where we can :-).
Jifl
--
eCosCentric http://www.eCosCentric.com/ <info@eCosCentric.com>
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
next prev parent reply other threads:[~2002-10-16 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 11:13 Ferguson, Ian
2002-10-16 6:39 ` Jonathan Larmour [this message]
2003-02-13 1:36 Chang, Sandra
2003-02-13 1:43 ` Jonathan Larmour
2003-02-13 18:01 Chang, Sandra
2003-02-13 18:06 ` Jonathan Larmour
2003-02-13 18:48 Chang, Sandra
2003-02-13 18:51 ` Jonathan Larmour
2003-02-13 18:59 Chang, Sandra
2003-02-13 19:01 ` 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=3DAD6C09.10904@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=Ian.Ferguson@idt.com \
--cc=Sandra.Chang@idt.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).