How Do You Define a 'Sick' Open Source Community?


When Sun Microsystems has restructured much of its business around open source, its leaders probably don't want to hear that one of the projects it sponsors, OpenOffice.org, is "profoundly sick" and "a dying horse." But that's exactly what contributor Michael Meeks has said.


ZDNet Asia points to an October blog post in which Meeks suggests Sun's stringent control of the project is strangling the community and discouraging developers from participating. He also calls for Sun to give up some of that control for the good of the project.


It isn't the first time Sun has been criticized for its management of an open source project. However, other industry observers who spoke to ZDNet Asia don't necessarily agree, according to writer Eileen Yu:

David Mitchell, senior vice president of IT research at Ovum, disagreed that a lack of community contribution should be interpreted negatively, noting that the success of open source products depends on user adoption, not developer profile. "Projects will have entirely different developer commit patterns, depending on their maturity. Mature projects are potentially always going to have less new code commits than fledgling ones," Mitchell explained.

Moreover, Mitchell also noted that the community could suffer if Sun followed Meeks' advice and distanced itself from the project.