public inbox for ecos-maintainers@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew.lunn@ascom.ch>
To: ecos-maintainers@sources.redhat.com
Subject: FWD: Re: [gnu.org #25869] eCos as an FSF project?
Date: Mon, 31 Mar 2003 12:18:00 -0000	[thread overview]
Message-ID: <20030331121818.GK18641@biferten.ma.tech.ascom.ch> (raw)

> Becoming a GNU project means that the project developers agree to
> GNU policies.  These are listed at
> <http://www.gnu.org/prep/maintain_toc.html>.  They are the full
> requirements; beyond what is listed there, the developers have full
> autonomy over the program's development.

I just skimmed through the policies. There are some things which would
cause difficulties, or at least need a lot of work. They specify how
release should be made and the look and feel of the web site etc. It
seems to me this will be the major problem with FSF, not the dealing
with the legal matters and assignments.

     Andrew


             reply	other threads:[~2003-03-31 12:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 12:18 Andrew Lunn [this message]
2003-03-31 15:26 ` 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=20030331121818.GK18641@biferten.ma.tech.ascom.ch \
    --to=andrew.lunn@ascom.ch \
    --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).