public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: John Dallaway <john@dallaway.org.uk>
To: eCos Discussion <ecos-discuss@ecos.sourceware.org>
Subject: [ECOS] eCos contributions and development projects
Date: Fri, 05 Jun 2009 19:10:00 -0000	[thread overview]
Message-ID: <4A296D9D.2010702@dallaway.org.uk> (raw)

eCos community

Following recent discussion concerning the NAND Flash infrastructure
contributions, the eCos maintainers are introducing a simple process by
which open development projects may be registered with us at an early
stage and listed on the eCos website.

In future, contributions arising from registered projects will be
considered for acceptance into the eCos repository with priority over
broadly equivalent contributions developed in private. This policy is
intended to encourage collaboration on new features and reduce the
possibility of a community development being rejected in favour of a
private development of similar scope and quality.

If you are involved in an eCos-related development which you are
intending to contribute, please do consider registering your project
with us.

Further details at:  http://ecos.sourceware.org/contrib.html

For avoidance of doubt:

a) Contributions from projects which are unable to register for
commercial or contractual reasons are still very welcome.

b) All contributions remain subject to technical review by the eCos
maintainers prior to acceptance into the eCos repository.

John Dallaway
On behalf of the eCos maintainers

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2009-06-05 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-05 19:10 John Dallaway [this message]
2009-06-05 19:46 Øyvind Harboe
2009-06-05 20:16 ` Sergei Gavrikov
2009-06-05 20:38   ` Øyvind Harboe
2009-06-06  9:21     ` Sergei Gavrikov
2009-06-06 10:17       ` Andrew Lunn
2009-06-06 12:34         ` Sergei Gavrikov

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=4A296D9D.2010702@dallaway.org.uk \
    --to=john@dallaway.org.uk \
    --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).