31 Oct
2008
31 Oct
'08
8:58 a.m.
Maya Posch wrote:
I don't know how the Windows internals work or
even
look like, this is my first time I'm working with them.
Then you're falling at the first hurdle. You can't work on ReactOS,
especially at the level you are, without knowing Windows Internals
religiously.
You need to take a step back, put some time into learning the architecture
_and_ how to program for the architecture. Only when you know this will you
be in a position to write good code.
Stefan is an excellent example of this in practice. He came to ReactOS
knowing little about NT. He put in the time and effort and learned the
architecture (very quickly). He's now in a position read and understand the
kernel and is making some valuable contributions.
If those people do not want to write documentation,
fine, have someone
else write the specifications and feed them those. Don't put them in
charge as they clearly aren't thinking about the wellbeing of the
project as a whole but only their small island.
Who? Who is going to write this documentation? Can you recommend anyone?
Anyone with the knowledge to write it is more interested in coding.
Are you volunteering, or do you want to pay someone to do it?
Impractical, insufficient and cop-out are words that
come to mind.
Sorry if I sound harsh, but this is among one of my many pet peeves ^_^
I've said it before and I'll say it again, even though people _hate_ this
answer...
A good programmer, with knowledge of NT doesn't need text.
The design is already established, read Windows Internals 4th. The code is
the fine, granular documentation.
As much as this may annoy you, there is absolutely no way to change this at
the moment.
This is open source....
It's not a great business model, but it's fun :)