This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Which list should cygwin development be discussed on ?

On Mon, Jul 03, 2006 at 11:10:47PM -0700, Yitzchak Scott-Thoennes wrote:
>On Sat, Jul 01, 2006 at 01:28:08PM -0700, wrote:
>> And of course the discussion and methodology behind the internal
>> development of the cygwin libraries, issues, and future ideas is
>> - in true opensource form (NOT) - on a completely closed list,
>> invite-only, with no public access to any form of archives.
>Where do you get invite-only from?  Seems directly contradicted by
>what you go on to quote.
>> What exactly is the positive purpose behind that?
>> "cygwin-developers: a by-approval developers list for discussing
>> the internals of the Cygwin DLL and all components of the
>> "winsup" directory. Discussions of upcoming net releases are also
>> appropriate. Subscription requests are handled on a case-by-case
>> basis. Only subscribers may submit email to this list. Please do not
>> attempt to join the cygwin-developers mailing list unless 1) you are
>> thoroughly familiar with the cygwin DLL, 2) you have successfully built
>> the DLL from source, 3) you contributed at least one patch to the Cygwin
>> DLL or its utilities, and 4) you intend on being a long-term contributor.
>> Please do not ask for "read-only" access to this mailing list. You either
>> qualify or you don't. There is no middle ground."

Right.  It has never been "invite-only".  You just had to prove that you
were serious about your intent to contribute.  But maybe this
misconception shows why cygwin development is so "special".


Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]