From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,706866ab9089906d X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-06-19 15:28:54 PST Path: archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!news.tele.dk!193.174.75.178!news-fra1.dfn.de!news-koe1.dfn.de!news-han1.dfn.de!news.fh-hannover.de!news.cid.net!news.enyo.de!news1.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: GCC 3.0 released Date: 20 Jun 2001 00:43:14 +0200 Organization: Enyo's not your organization Message-ID: <874rtcum4d.fsf@deneb.enyo.de> References: <2BpX6.13114$pb1.478251@www.newsranger.com> <86ithtpvmp.fsf@acm.org> <871yohih9w.fsf@deneb.enyo.de> <_pOX6.1713$yp1.49933@www.newsranger.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Xref: archiver1.google.com comp.lang.ada:8900 Date: 2001-06-20T00:43:14+02:00 List-Id: Ted Dennison writes: > In article <871yohih9w.fsf@deneb.enyo.de>, Florian Weimer says... >> >>Yes, that's true. Shall we guess what is causing problems? Legal >>matters (i.e. the copyright assignment to the FSF)? > > That can take a while. Robert Dewar told me via email that this is not the problem. The copyright was executed years ago, and apparently it is not necessary to assign copyright for the components which are not directly part of the compiler. > I'm trying to go through the process with the SETI@Home Service, and > its been incredibly slow going. Well, it happens quite fast if you've contributed some code to GNU Emacs through some backdoor without signing any document. ;-) OTOH, the copyright assignment stuff really slows down development in some areas. For example, at the moment, our university cannot donate code to the FSF because of legal matters (the assignment contract is completely incompatible with German law). In fact, someone already partly reimplemented a security fix for GNU Emacs because of this problem. As a result, we do not work on improving software (beyond our immediate needs) any more unless contributing something does not require any paperwork. (Forking is not an option of course, because of the additional work required.) > So it does look like most of the stuff in there is already FSF, and > I'd guess (just my guess) the rest isn't FSF *on purpose*, and will > probably remain that way. Yes, I think so. > Which begs the question (and this is just genuine curiosity), what > exactly is going into the official baseline when it gets merged? > Will it just be the FSF code? (probably not) Just the GPL'ed code? The latter is not an option, I think. After all, you need quite a bit of source code which is covered by the ARM copyright in order to be able to compile typical Ada programs.