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
Subject: Re: Questions on patching dcrt0.cc
From: Max Kaehn <slothman AT electric-cloud DOT com>
To: cygwin AT cygwin DOT com
In-Reply-To: <20050526145843.GB5619@trixie.casa.cgf.cx>
References: <1117064831 DOT 5390 DOT 174 DOT camel AT fulgurite> 	 <Pine DOT GSO DOT 4 DOT 61 DOT 0505252005040 DOT 8541 AT slinky DOT cs DOT nyu DOT edu> 	 <20050526145843 DOT GB5619 AT trixie DOT casa DOT cgf DOT cx>
Content-Type: text/plain
Message-Id: <1117129479.5390.225.camel@fulgurite>
Mime-Version: 1.0
Date: Thu, 26 May 2005 10:44:39 -0700
Content-Transfer-Encoding: 7bit
X-Spam-Not-Checked:  Messages over 100K or from internal Electric Cloud machines are not checked
X-IsSubscribed: yes

On Thu, 2005-05-26 at 07:58, Christopher Faylor wrote:
> I don't know what "submit it" means here.  If the submission is for inclusion
> somewhere in the cygwin-specific part of winsup then the code needs to be
> assigned to Red Hat.  Otherwise, why not just make it GPL?

If MSVC code is acceptable for the cygwin-specific part of winsup, it
definitely gets the cygwin license.  If it should go someplace else,
then I want people who have purchased a cygwin license from Red Hat
not to have to worry about the legalities of copying code from the test
program.  If I can use the cygwin license for code in "contrib"
(or wherever), then that's fine.

My intent here is to minimize the barrier to entry of creating
proprietary programs that interoperate well with cygwin.  If someone
makes a proprietary tool and has customers clamoring for it to work
better with cygwin (e.g. doing proper cleanup when getting a ^C while
running in an xterm), I want the business decision to be a matter
of "the integration code is already available; the only question
is whether the value added is greater than the cost of a cygwin
license from Red Hat".

I'm new to actually *selecting* open source licenses, so I'm grateful
for all feedback on selecting an appropriate one for the test
program.  http://www.opensource.org/licenses/bsd-license.php
looks good; is it appropriate for me to assign the copyright to
Red Hat?

I got signal handling working yesterday; it works by spawning
a thread that loops on sigwait().  I want to make another pass
over the program doing cleanup and documentation and it'll be
ready for submission, probably by the time the copyright assignment
forms make it through snail mail.  I'll also see if I can make a
mingw version for winsup/testsuite, as Igor suggested.

Thanks,
Max



--
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/