Cygwin/XFree86 - No longer associated with XFree86.org

[Harold L Hunt II]

It seems that David Dawes has made his decision not to let the 
Cygwin/XFree86 project commit patches directly to the XFree86.org CVS 
tree; he doesn't seem to want to go on record saying this, but he has 
written several messages during this discussion about ftp servers, cvs 
servers, etc., while making no attempt to provide a direct answer to my 
question.  Had he intended otherwise he could have easily said, Gotta 
wait until the next board meeting, or Sorry, server died, gonna have 
to wait a couple days.  I can only interpret his ignoring the issue as 
a passive refusal to grant Cygwin/XFree86 CVS commit access.

In the interests of providing a more open development model, the 
Cygwin/XFree86 project will no longer be maintaining code in the 
XFree86.org CVS tree.  Maintaining code in XFree86.org's CVS tree 
provides little benefit in relation to the amount of time required to do 
so; XFree86.org is passively unwilling to work with Cygwin/XFree86 to 
reduce the amount of time required.

What this means for Cygwin/XFree86 users and developers
===
1) No major changes to the files currently distributed with 
Cygwin/XFree86 for at least a month.

2) The Cygwin/XFree86 mailing lists and project pages will stay at 
cygwin.com.

3) Builds will continue to be made from the 4.3.0 snapshot, patched with 
the latest Cygwin/XFree86 patches.

4) A 4.4.0 snapshot may be pulled to make builds from.

5) Patches for Cygwin-specific code will no longer be sent to 
XFree86.org.  Non Cygwin-specific patches should still be sent, to be 
dealt with as XFree86 pleases.

6) Alternatives are being evaluated for hosting Cygwin/XFree86 code in 
CVS.  Hosts that can provide CVS commit access for at least five 
Cygwin/XFree86 developers will be given priority.

What this means for Cygwin
==
Nothing.  Nada.  Zilch.  They were not involved in this at all.
What this means for XFree86
===
Some will say nothing.  Some will say good riddance.  Some will say this 
is the beginning of the end.  Who knows?  Who cares?  Let /. figure it out.

Harold

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: Cygwin/XFree86 - No longer associated with XFree86.org

[Alan Hourihane]

On Mon, Oct 27, 2003 at 11:35:20AM -0500, Harold L Hunt II wrote:
 6) Alternatives are being evaluated for hosting Cygwin/XFree86 code in 
 CVS.  Hosts that can provide CVS commit access for at least five 
 Cygwin/XFree86 developers will be given priority.

Harold,

I thought you already had the CVS for Cygwin/XFree86 sorted out, by
using what you'd already setup in http://sf.net/projects/xoncygwin ?

You and Alexander Gottwald (and myself) have already been using this for
quite some time now. Couldn't you give Kensuke et al commit access there rather 
than seeking out yet another repository ?

Alan.
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel

Re: Cygwin/XFree86 - No longer associated with XFree86.org

[Harold L Hunt II]

Alan Hourihane wrote:

On Mon, Oct 27, 2003 at 11:35:20AM -0500, Harold L Hunt II wrote:

6) Alternatives are being evaluated for hosting Cygwin/XFree86 code in 
CVS.  Hosts that can provide CVS commit access for at least five 
Cygwin/XFree86 developers will be given priority.


Harold,

I thought you already had the CVS for Cygwin/XFree86 sorted out, by
using what you'd already setup in http://sf.net/projects/xoncygwin ?
It is something I am looking into.

It all depends on if we want to have to import and maintain the clients.

You and Alexander Gottwald (and myself) have already been using this for
quite some time now. Couldn't you give Kensuke et al commit access there rather 
than seeking out yet another repository ?
Looking into it.

Harold

___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel