Mailing-List: contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-apps-owner AT sourceware DOT cygnus DOT com
List-Subscribe: <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-apps/>
List-Post: <mailto:cygwin-apps AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs>
Delivered-To: mailing list cygwin-apps AT sources DOT redhat DOT com
Date: Mon, 3 Sep 2001 10:17:35 +0200
From: Corinna Vinschen <cygwin-apps AT cygwin DOT com>
To: Cygwin-Apps <cygwin-apps AT cygwin DOT com>
Subject: Re: cygipc packaging was Updated setup.ini with descriptions, categories, and dependencies
Message-ID: <20010903101735.A23714@cygbert.vinschen.de>
Mail-Followup-To: Cygwin-Apps <cygwin-apps AT cygwin DOT com>
References: <000b01c133a3$0145ec10$7d6707d5 AT BRAMSCHE> <3B92B700 DOT 1050201 AT ece DOT gatech DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3B92B700.1050201@ece.gatech.edu>; from cwilson@ece.gatech.edu on Sun, Sep 02, 2001 at 06:47:28PM -0400

On Sun, Sep 02, 2001 at 06:47:28PM -0400, Charles Wilson wrote:
> Back to cygipc: so, this ain't gonna happen.  If we want to have IPC 
> stuff directly in the cygwin kernel, "we" are going to have to write it 
> ourselves.  (Unfortunately, I am most likely disallowed from helping, as 
> are a number of other people.  "Contaminated" by exposure to the cygipc 
> code.  How can anyone be sure that any code I contribute is not 
> influenced -- or even copied! -- from my knowledge of the cygipc internals?)

That's a shame, IMO.  I can't understand it, honestly.  The way
people learn programming is by looking into code from other, more
experienced people.  This lame licensing issue is slowing down
progress.  Imagine: I take a look into a piece of code to see how
another person implemented functionality `foo'.  This gives me
an idea _how_ to implement it.  Now I begin to implement my own
stuff.  I don't copy it.  I make my own improvements.  I'm just
using the _idea_ how to implement it but I'm coding it "in my
own words".

Why the heck am I violating a license? Why is open source open
source if other open source projects can't learn from that?

Hmmpf, just my naive look into that issue.

Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                                mailto:cygwin AT cygwin DOT com
Red Hat, Inc.