Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
content-class:	urn:content-classes:message
MIME-Version:	1.0
Subject:	RE: how do I cite cygwin for academic publication?
Date:	Tue, 14 Jun 2005 09:20:29 -0400
Message-ID:	<94BF3137C62D3E4CAED7E97F876585F09DAA61@pauex2ku08.agere.com>
From:	"Williams, Gerald S \(Jerry\)" <gsw AT agere DOT com>
To:	"Cygwin" <cygwin AT cygwin DOT com>
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id j5EDLNCT011774

Peter Waltman wrote:
>> since I used cygwin to implement my masters project (which I'm not 
>> getting into publishable form), 

Arturus Magi wrote:
> Also, as a note: submitting a masters project may still be considered
> distribution.  You may want to solicit advice from a legal authority,
> if possible.

Is it possible that we can give Peter some advice that doesn't
require contacting a lawyer? :-) How about this:

Peter, are you saying that your executables will never leave
your PC? Even if so, you may want to cover yourself by keeping
all of the sources, including the source to Cygwin, together
with the executables. It may even help you at some point in the
future. Personally, I'd download the source to everything that
I needed (e.g., Cygwin, GCC, etc.) and package the whole thing
so it can be easily stored and/or transferred to new media as
needed.

gsw


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -