From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 24059 invoked by alias); 31 Mar 2003 12:18:25 -0000 Mailing-List: contact ecos-maintainers-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Post: List-Help: , Sender: ecos-maintainers-owner@sources.redhat.com Received: (qmail 24052 invoked from network); 31 Mar 2003 12:18:25 -0000 Date: Mon, 31 Mar 2003 12:18:00 -0000 From: Andrew Lunn To: ecos-maintainers@sources.redhat.com Subject: FWD: Re: [gnu.org #25869] eCos as an FSF project? Message-ID: <20030331121818.GK18641@biferten.ma.tech.ascom.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-Filter-Version: 1.6 (ascomax) X-SW-Source: 2003-03/txt/msg00086.txt.bz2 > Becoming a GNU project means that the project developers agree to > GNU policies. These are listed at > . 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