Pieter Mees wrote: > Chriss, > > I don't think anyone here is questioning your contributions. I for one > think you've done a great job with developing something like the AOT. > Due to the very fact that we don't understand how it really works (yet), > makes it impossible for us to check how good it really is. So we can't > comment on the quality of your work. > > By making at least a general architecture design, or even just document > its current design a lot more people will have the chance to help you > out. Most people can only assist in small areas (due to knowledge or > time constraints), so they won't go as far as to read all the code to be > able to add some lines. If on the other hand we had some design > documents (e.g. a general map of the bytecode->asm flow, some class > diagrams, ...) those people will be "in the loop" with much less effort. > What we would do here is instead of all of us doing the same work > (trying to understand the structure), some of us document it for the > rest so they can understand in a fraction of that time. > > This does not only hold true for AOT, but also for the kernel. > > I believe we can all agree that good documentation is a MUST to keep > everything clear and organizable. So I think the question that has to be > answered first is: > Do we continue development and start documenting by following its trail? > Or do we ask Chriss and the others to halt for a moment so we can all > catch up? > > I think the last option is the best one because otherwise we wouldn't > notice architectural problems until it's too late. I agree on that too.
So what we would need now is volunteers to write the documentation. Anyone? Anyone interested, I am on IRC. Or perhaps we should all gather on IRC for Q&A Session this weekend? That way someone can write the documentation, so that everyone can understand it and use it? Chriss. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
