From: "Choi, David" <David.Choi@Micrel.Com>
To: "John Dallaway" <john@dallaway.org.uk>
Cc: "Li, Charles" <Charles.Li@Micrel.Com>,
"eCos Maintainers" <ecos-maintainers@ecos.sourceware.org>
Subject: submit process
Date: Wed, 07 Apr 2010 00:17:00 -0000 [thread overview]
Message-ID: <C43529A246480145B0A6D0234BDB0F0D481CD9@MELANITE.micrel.com> (raw)
In-Reply-To: <4BB0CEE1.6090109@dallaway.org.uk>
Hello John,
Based on your suggestion, I filled [the assignment request form] and
sent it to assign@gnu.org last week.
But I have not received any feedback until today. I want to check the
status.
What should I do?
Is it possible to submit my driver before finishing [process of
copyright assignment]?
Thank you in advance for your reply.
Regards,
David J. Choi
-----Original Message-----
From: John Dallaway [mailto:john@dallaway.org.uk]
Sent: Monday, March 29, 2010 9:02 AM
To: Choi, David
Cc: Li, Charles; eCos Maintainers
Subject: Re: boot loader
Hi David
Choi, David wrote:
> Under eCos, I make a network device driver for ks8851 MLL from Micrel
> Inc.
>
> I want to put my driver in eCos source tree.
>
> Could you tell me the procedure to put my driver in eCos so that
> everybody can use it?
Firstly, thank you for your interest in contributing to the eCos
project.
The basic procedure for contributing code is described at:
http://ecos.sourceware.org/contrib.html
Note that all contributions are subject to review and that everyone who
has contributed to the device driver will need to assign copyright to
the Free Software Foundation.
I recommend that you start the process of copyright assignment as soon
as possible as it can take some time to complete. Ref:
http://ecos.sourceware.org/assign.html
When your driver is ready for review, please create a new Bugzilla
report at http://bugs.ecos.sourceware.org and attach your source code to
the Bugzilla report.
John Dallaway
eCos maintainer
next prev parent reply other threads:[~2010-04-07 0:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C43529A246480145B0A6D0234BDB0F0D481CAC@MELANITE.micrel.com>
[not found] ` <4B6BD6D8.3010906@dallaway.org.uk>
[not found] ` <C43529A246480145B0A6D0234BDB0F0D481CAD@MELANITE.micrel.com>
[not found] ` <4B6C5F41.5020000@dallaway.org.uk>
[not found] ` <C43529A246480145B0A6D0234BDB0F0D481CD3@MELANITE.micrel.com>
2010-03-29 16:01 ` boot loader John Dallaway
2010-04-07 0:17 ` Choi, David [this message]
2010-04-07 7:16 ` submit process 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=C43529A246480145B0A6D0234BDB0F0D481CD9@MELANITE.micrel.com \
--to=david.choi@micrel.com \
--cc=Charles.Li@Micrel.Com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=john@dallaway.org.uk \
/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).