Re: [ros-dev] RE: [ros-svn] [gdalsnes] 16793: my 1st

>   -----Original Message-----
>  From: Richard [mailto:[e-mail]]
>  Sent: Friday, July 29, 2005 12:18 AM
>  To: 'ReactOS Development List'
>  Subject: Re: [ros-dev] RE: [ros-svn] [gdalsnes] 16793: my 1st
>  
>  Then where is this effort?  Why is one developer wandering off on his 
>  own?  How about setting a 'win32k rewrite' as a goal for 0.4?  That is, 
>  if 0.3 ever makes it out the door...
>  
>  Honestly, i think that devs should work towards the feature set we 
>  planned for 0.3, however that is just me.  Granted, there is no money 
>  involved in this project, but not setting goals and randomly doing 
>  rewrites is the fast way to code burnout, boredom, and lost interest.  
>  Drowning yourself in an impossibly large project is nuts.
>  
>  Richard 
Not meeting 0.3 is largely my fault.  I don't even know when I'll be
able to return to writing on it in a consistent way, given my new job :-(.
I've had several offers from others to write on it but it seems that most
people either aren't very interested in what remains, or don't feel
confident about working on kernel code.  The remaining kernel tasks
don't actually involve much know-how about the kernel, and my components
are designed to be easy to understand (with minimal concurrency).

Only three things are needed to meet the 0.3 goal:

1) retest apps on the 0.3 list and fix regressions
2) finish the net cpl and possibly fix bugs in npfs that make CallNamedPipe
   bugcheck
3) (big) finish needed stuff for mozilla compatibility

There are a lot of generic tasks in net that need doing, and could
really be done by anybody.  They affect the kernel but won't use very
much specific kernel code:

1) Plumb remaining ioctls into kernel land (afd/info.c,tcpip/*info.c)
 - Keepalive
 - Nagle
 - TTL (datagram and tcp)
 - Verify behavior of nonblocking sockets
 - send/rcv buf
2) Plumb ARP cache requests (tcpip/iinfo.c,network/neighbor.c)
3) Put together a test matrix for socket end conditions (when I get my
   stuff from chicago next saturday, I'll be able to pass on my test
   apps and notes), and emulate winsock properly.
4) Finish the NTSTATUS -> winsock error conversion and use it everywhere
5) Finish off errno -> NTSTATUS conversion in tcp.c
6) Finish any kernel-related IOCTL changes
7) Write a test tool and verify WSAEnumNetworkEvents
8) Do some refactoring in afd/select.c to make it easier to understand

Hard kernely tasks:

1) Fix IRP cancellation in tcpip
2) Verify CLOSE/CLEANUP in afd and tcpip
3) Better buffer management in afd
4) Fix use of TDI_TRANSPORT_ADDRESS vs TA_ADDRESS and verify 
   correctness based on osr docs
5) Test out our AFD and TCPIP on real windows with kd
6) Replace recursive mutex