Chad Z. Hower aka Kudzu wrote: >> Someone will probably say this already exists. I don't know. My major >> recommendation right now is establishment of a build master, who owns >> > > Where is it documented? :) What is the process of conflict resolution? I > don't just mean build team vs doc team type things. > > >> check, and the build master normalizes the code to a coding standard >> before committing it to the trunk. Trying to get rid of William >> > > We can use code formatters for such items in many places. > > >> I've been kicking for this for awhile. Currently it's more a code- >> write-architecture-later. The largest part of the system, the compiler, >> is AOT-only, and only one person knows its architecture. I've been very >> vocal about that. Don't know if Chriss has gotten anywhere with >> documenting the architecture. >> > > The problem is that docs get too far behind too quickly and people forget > why/what. I can take a stab at this - but it will also force a lot of review > IMO of architecture and I wont be hesitant to bring issues up and push for > change when needed, especially in core. We HAVE to get core RIGHT. > > >> Already exists, for both VMWare and Bochs >> > > Ok, then change Item 3 to - Make a new, better, easier to understand > website. I can do that too, if you don't care what tool I use. That failing > I can make a fork with my own info. :) > > Definitely not disagreeing with any of the above. I'm taking all next week off for a vacation, so I have the time to do this. But within all the flurry of email, we haven't heard from William or Chriss, who so far are the two main devs of the existing codebase. There's been a general consensus of "what we have already works", even if it isn't formalized or documented, which makes the "professional software engineer" side of me grumble.
The biggest thing is whether William and Chriss would agree to stop kernel and compiler development until we have a chance to look back over the architecture, agree and document said new architecture, and look back over existing code to massage it accordingly. ------------------------------------------------------------------------- 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
