I think we need to work on structure for committing to the trunk. We have a lot of people doing commits, without a lot of peer review before the patches go in. I think a good idea would be a sort of "buddy system", where a dev gets another dev's word on the patch before committing, and in the commit log that person is cited for accountability. No single dev here can attest to knowing all the happenings of the kernel or AOT so we should try to improve our kernel death probabilities. There is usually one or two of us in the IRC channel anyway so getting confirmation should be easy. What do you think?
I don't think this necessarily applies to original work by the developers, even though it's a good idea (using sandboxes instead of patches). -- fury long name: William Lahti handle :: fury freenode :: xfury blog :: http://xfurious.blogspot.com/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ SharpOS-Developers mailing list SharpOS-Developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sharpos-developers
