public inbox for
 help / color / mirror / Atom feed
From: Andrew Lunn <>
To: eCos Maintainers <>
Subject: FWD: [ECOS] Procedure to release GPL code for eCos
Date: Mon, 10 Mar 2008 10:39:00 -0000	[thread overview]
Message-ID: <> (raw)

----- Forwarded message from Aditya Vaidya <> -----

X-Spam-Status: No, score=-6.6 required=4.0 tests=BAYES_00,RCVD_IN_DNSWL_MED
	autolearn=ham version=3.2.4
Date: Mon, 10 Mar 2008 15:58:49 +0530
From: Aditya Vaidya <>
Subject: [ECOS] Procedure to release GPL code for eCos

Hi all,
We would like to know the correct procedure to release GPL code for eCos. 
Currently, there seems to be no consensus on this.

Aditya Vaidya
Aftek Ltd.

Before posting, please read the FAQ:
and search the list archive:

----- End forwarded message -----

This poster has a point.

We need to improve the website information about this. 

Jifl, do you have time to work on

and make it clear that people need an FSF assignment and what the
process is to get such an assignment. 

Hopefully now my assignment should be soon in place we can really get
going with the move to FSF.


                 reply	other threads:[~2008-03-10 10:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).