Open Source at Sun
"When you open source a formerly proprietary product, and want external developers to participate, you must give them more than just the source code. The external folks need to know as much about the code standards, architecture, release plans, open bugs, development priorities, etc. as the internal developers. If you just dump the source over the wall, the chances are you'll get patches back that don't integrate with the rest of what you're doing. When you reject a patch, frame it as "here's how we'd write it, here are the guidelines we follow"."
(Submitted by Noel Sat Sep 18, 2004 )
Our content can be syndicated: Main page Mac Page
Copyright 1999-2005 Noel Davis. Noel also runs web sites about sailing and kayaking.
All trademarks are the property of their owners.
All articles are owned by their author