fork()

Hello everybody,
thxs thxs thxs for all the replys.
Thats just a lot. It toked me more than an hour to read trough all the 
e-mails :)

So what's next?
I think many community members are ready and willing to support a new 
fork of Y-Windows.
So here it is.
I'm proud to announce the fork of Y-Windows.
My fork hasn't gotten a name yet but that's in the upcoming.

First of all there will be absolutely no news from me for 7 days by now.
Because of my work as a System Administrator i have to do some business 
traveling, next week.
I'll use this time to make the following things:
    - A new basic Road map
    - A working Y- Windows GCC 3.4.4 / GCC 4 port *i'm almost finished 
this one*
    - A new Wiki based with as much as possible basic informations
    - Create a small Project Page for Sources and Release Notes/News
    - Additionally: I'll try to setup a Arch Server with an WebFrontend
    - Find a new name for the Project

So i'm now going to explain why i do things like i'm planning to do them.
I thing the new Road map is absolutely clear.
The GCC port is very important.
I discovered many old aged functions that prevent y- windows to compile 
cleanly
in it's current state on new vanilla GCC's.
Thats isn't much a problem so i hope i can manage this on my own.
The Wiki will be based upon Dustin's existing one.
I'll write a small community page which coordinates news, wiki, 
releases, and the new forum engine.
I decided sticking to ARCH.
I tried several things with ARCH and it proved to be worth using it for 
the Project.
I'm not 100% familiar with ARCH because up to now i managed almost all 
my projects
using subversion or CVS.
In this matter hanks to Dustin again and Kristian for showing me the 
advances of ARCH.

The second priority is to find a new name.
The new name shouldn't be too far away from y-windows 'cause we are just 
a fork of it.

Jost Boekermeier, a German developer,
made me aware of an implementation problem in the y-windows protocol.
He discovered a problem of how the Client Server communication is 
handling bandwidth and connections.
I'm not that familiar enough with the existing code to tell how hard it 
i'll be to change things in the  basic protocol.
But we 'll manager this and other issues wen the new project is up and 
running.
---


So that's it for now.
I'll be at available till Sunday CET.
Please try to use this week for productive thinks.
Like finding a new name.

Special thanks to Jost, Dustin, Kristian
and all the other who tried help me figuring out what to do next.


Greets, Robert.