Solaris at OSCON

Last week a contingent from Sun showed up at OSCON to talk about Solaris 10, meet with some community leaders to discuss building a community around open source Solaris, and of course learn from the other conference attendees.

Simon Phipps gave a talk on open source development and the meaning of freedom which was quite interesting. One of his points was that freedom for deployers is as important as freedom for developers, and that while licenses can help to build a community around a piece of software by giving the developers freedom, this is not sufficient as an end in itself. This is one of the things we're looking at as we get ready to release Solaris under an OSI-approved license of some as yet undetermined kind. Governance and community structure are at least as important as the license we eventually choose, and we have much more direct and immediate participation in these aspects. One point I've tried to emphasize is that successful communities form spontaneously and organically; they cannot be constructed from scratch, purchased, or willed into existence. Our challenge is to get people excited about Solaris and interested in being a part of that community, then to provide them with infrastructure and a reasonable way to make their voices heard as we proceed. Many people at the conference had some helpful suggestions for doing this.

Perhaps the most important thing to remember is that developers are fundamentally attracted by two things: exciting technology and a meaningful opportunity to work on it. The success of the BOF that Adam, Andy, Bart, and Eric put on showed many people just how exciting some of these technologies are. The feedback we received was overwhelmingly positive. Rarely does such a demo-friendly piece of technology as DTrace come along, and many of the attendees were clearly impressed. Still, it's only one of many major enhancements in S10; it's fairly obvious that there will be plenty of developers attracted to our technology provided we can generate enough awareness.

But as we've seen, compelling technology and an open license are not enough to make for a successful project. GCC and XFree86 had both, but neither project was successful in building and sustaining a community (GCC of course has been reborn since the quagmire of the 2.8 era). Many things make up a project's public perception as one which is easy and fun, or frustrating and counterproductive, in which to participate. Infrastructure, governance, and developer resources each play a role. My focus at the moment is on our efforts to help developers get started; this means providing good documentation and keeping the barriers to entry as low as possible. As one of the people who will be creating the developer documentation, tutorials, and examples, I'd be very interested in your feedback. When you're attracted to a project, what type of resource increases your desire to participate? What dissipates your interest and turns it into frustration?


I totally agree with what you had to say about open sourcing S10. It's going to be difficult and it'll definitely be interesting. The governance will be a tricky issue, but I think that Sun should be strict and organized on that. I think what would make it fun to participate will be a developer and end-user oriented web portal. I've been part of the external customer beta program for S10 through centercode and I think it has a grasp on what should be available. It has the ability to submit reports on testing, RFE's, bugs, support questions, etc. So I think it could be a good model for the components of a OpenSolaris portal. I know that getting Solaris to run on other platforms would be a huge plus for the industry since there are soo many sites with PA-RISC, MIPS, ALPHA, etc. that could reuse their equipment with a modern OS. Also the ability to port Solaris to Itanium, Power, and the PowerPC(which should not be too difficult since it was done back in 2.5.1) would be a huge bust for Solaris.

Posted by Octave Orgeron on August 06, 2004 at 02:08 PM UTC #

Post a Comment:
  • HTML Syntax: NOT allowed



« February 2016