Date: Fri, 8 Oct 1999 18:46:54 -0400
Message-Id: <199910082246.SAA18841@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <199910081802.NAA00521@darwin.sfbr.org> (message from Jeff
	Williams on Fri, 8 Oct 1999 13:02:18 -0500 (CDT))
Subject: Re: djgpp project management
References:  <199910081802 DOT NAA00521 AT darwin DOT sfbr DOT org>
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> Is it DJGPP `policy' that proposed patches be submitted to the DJGPP list
> for review, discussion, etc.?  I think it is a fine idea, either way.

That's not policy, that's process.  There is no other way to get
changes into djgpp (unless you're one of the three people who have
access to cvs).

> The reason I ask is because I know of a software development project
> with great promise, but IMHO without the leadership it needs to stay on
> target.  The DJGPP development project seems to function so smoothly
> and efficiently---did it just happen that way, or was the project
> management planned out in some sense?  I think that DJGPP could be a
> role model for many nascent or struggling projects.

It started with just me controlling everything that went into djgpp,
so whatever I said was what people had to do.  Eventually, others got
so used to doing it the (my) "right way" that I was able to delegate
some of the work to them directly.

Remember that DJGPP is now about 12 years old.  We didn't just think
up this process; this is simply what worked for us.