Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Robert Praetorius" Organization: Ministry of Hobo Regalia, Gauntlet Division To: cygwin AT cygwin DOT com Date: Tue, 25 Mar 2003 15:20:29 -0500 MIME-Version: 1.0 Subject: Re: Another GPL violation: Re: Minimalistic Build-Environmentforwin32 (~7.5MB) Reply-to: RPraetorius AT AspenRes DOT Com Message-ID: <3E8073BD.934.1F293006@localhost> In-reply-to: <5.2.0.9.2.20030325114157.029e76f0@pop3.cris.com> References: Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body > > FWIW: I am not a lawyer. > And therefore, everything you have said may be safely ignored. Just for reference, if someone's looking for a lawyer not to ignore, that would probably Eben Moglen, FSF general counsel and board member (also a professor of law and legal history, formerly a clerk to Thurgood Marshall and, in the early 80s, a programmer): http://www.google.com/search?q=site%3Awww.gnu.org+moglen http://www.google.com/search?q=site%3Aemoglen.law.columbia.edu+gpl Naturally, in a legal context, all us nonlawyers ain't qualified to interpret what he says (which apparently doesn't mean anything until it's made it to court), but ya gotta start somewhere. I'd say that he ought to be prevailed upon to right a document on how non-lawyers can help with GPL enforcement, but he probably has and I just haven't found that link yet. However, GPL aside, there's the issue of ensuring that people who acquire software one makes publicly available can rebuild it on their platform of choice, fix bugs, make improvements, etc. That would seem to amount to common open source courtesy. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/