Arkady V.Belousov schreef:
1) implement your codePPS: About discussion of planned changes: how many times I wrote here? How many times I get any answer? If I will wait answers for my proposals before doing something, I will do nothing forever. :(
PPPS: Of course, I open for discussion anyway.
2) bugfix your code
3) make code understandable
4) upload up-to-date sourcecode to website
5) write to mailinglist about your changes, and point people to your sourcecode
this way there is a discussion possible, as people can look into your code changes.
You write the code, and then people ask you questions about your design decisions, and you defend your code changes.
That's called discussion. Finally, people will approve your changes, and that makes your changes official, I guess :)
be prepared to defend yourself against Tom's and Lucho's comments. I believe it's called "peer review".
I'm not one of those "peers", the people who work(ed) on the kernel are.
Bernd
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Freedos-kernel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freedos-kernel
