Jim Grisanzio, community manager, OpenSolaris, updated his presentation on OpenSolaris for the one-year anniversary.
On his blog, he recapped some of the significant milestones along the way to the one-year mark: "We welcomed code contributions from two dozen community members totaling 100 putbacks -- a number that is absolutely exceptional. We discussed and wrote a development process that will help ensure technical quality on the project. After an open evaluation process, we selected a source code management system and will implement it this year. We wrote a Charter enfranchising the community, and we are writing a merit-based Constitution so we can truly run the community as a community. We are doing interesting new things with the code, such as creating distributions and porting the technology to new platforms. And OpenSolaris is being taught in dozens of the leading computer science institutions around the world."
He traces back to the origins of the project, the idea that started it. It was a "perfect opportunity to build a community:
- Sun executives - expand the Solaris OS market, drive the Solaris OS into new markets, sell more systems and services
- Solaris engineers - engage developers outside the company, share code, improve an already great system
- Solaris market/community - see the code, optimize apps, contribute to Solaris development, create ports/distros"
"The strategy of OpenSolaris is to transform a market into a community using open communications and open development." Grisanzio states that the strategy "rests on two principles: (1) open conversations and (2) open development." The website blogs.sun.com has become a crucial part of the OpenSolaris success.
Grisanzio's presentation shows the community website and a list of code that has been released, including:
- DS Consolidation: 10/28/05
- FS Project: 11/16/05 - integrated into ON build 27
- Network Storage Consolidation: 1/27/06
- X Window System Consolidation: 3/31/06
- Globalization Consolidation 5/12/06
Also covered are details about the license, the governance, the process of contributing code, and the engineering design principles and community values.
He stated: "We should be proud of all these accomplishments, but humble as well. There remains a great deal of technical work and community building ahead of us, and this will be our challenge for next year."
[...read more...]