Life is so good, it gets better every day

With much of the current growth of the OpenSolaris community coming from the user community, it should not be a surprise for those closely monitoring the lists that the idea of creating a more user focused site would likely be on the cards at some stage. A new site that focuses on using the operating system, rather than necessarily contributing to it’s creation, seems attractive to many - both the existing developers who have been frustrated by simply wanting to focus on writing code, and those who want to use and advocate the operating system they love. It’s clear we’ve come a long, long way from the original vision of an equivalent kernel.org.

The OpenSolaris web infrastructure has not been without problems, however, as most of the tonic web team will attest - issues with shoe-horning in projects infrastructure and source code management systems, re-writing the authentication systems, a new grants and election poll sub-system, the infamous jive-mailman bridge, planet aggregators, bugzilla defect management systems and a whole host of other headaches. It’s a testament to the web team, both past and present, to have what we have. And with all its faults, it does a pretty amazing job, with some great content there. But rarely do we provide the opportunity for the non-contributing user to download binaries and run them, find out about exciting technology that is available to them, and help spread the word about OpenSolaris. opensolaris.org just isn’t that kind of site, to some extent, and I think we can do better.

And that’s why I believe we absolutely need to be looking at building opensolaris.com.

A brief look at some other community sites like ubuntu.com, opensuse.org, and firefox.com shows a very different focus - the minimum mouse clicks needed to download and install a binary artifact, or buy a piece of branded merchandise, or find out about a piece of exciting innovative technology that sets that apart from everything else around it. A few key words come through as themes -

• Get
• Use
• Learn
• Love
• Spread

Only then, in my opinion, can we even think about Contribute, and encouraging those people to come through the system and contribute to its creation.

A couple of us sat down to brainstorm what an initial pass might look like, with heavy influence from some of the many other community sites out there that do a good job.

About

• Featured Articles
  The featured articles would be a series of monthly updates to the home page, which could include information about upcoming events, profiles and interviews, technology overviews and such like. This section would act as the archive behind those feature articles or splashes.
• News
  News would provide the latest information about what is going on in the project. News would be briefly syndicated on the home page, to click through to a series of short paragraphs about the given news item. Press related articles and contact details for press queries may also be provided here.
• FAQ
  The section would list various FAQs related to the project as a whole, rather than individual technology.
• Awards
  This section would list some of the awards that OpenSolaris has won in the past, including some profiles of the developers or technology who were responsible.
• Contact
  This is the phone-book for OpenSolaris, providing details of all types of contacts - site support, press queries, including links into certain mailing lists or user forums.
• Sponsors
  This section would list some of the corporate sponsors of the project, in the form of a small logo and background information about the sponsor and their involvement in the project.

Community

• Discussions
  This section lists all the user oriented forums that participants can contribute to. Those interested in development will be encouraged to join the lists over at opensolaris.org.
• Code of Conduct
  If we had one, we might include it here, documenting the community rules of engagement and encouraging a positive collaborative environment.
• Developer
  This section would be the first landing block to a wider world of OpenSolaris development, introducing a set of guidelines for how to navigate a new domain, opensolaris.org.
• Blogs
  This section could be an aggregation of several existing blogs, or a single blog with multiple authors.
• Events
  The community events guide will list out all the OpenSolaris related events happening during the calendar year - Summits, Developer Conferences, Tech Days
• User Groups
  This section will be a window to the OpenSolaris user groups right across the world, with their own separate portal to allow them to control their own content.

Library

• User Guides
  User guides will be provided in online HTML form, and downloadable PDF for off-line reading and printing. This will act as the core reference library to access a plethora of subjects - from documentation about install and package management, to system resource management and trouble-shooting.
• Manual Pages
  This section will provide a list of all man pages for convenient online viewing.
• Howtos
  This section will detail some of the common tasks during day to day use of OpenSolaris eg. how do I set up a Wordpress instance on OpenSolaris?
• Audio and Video
  This section will provide some of the new media like video screencasts, podcasts or other medium to facilitate on-line learning.
• Books
  This section will detail some of the published books that are available, providing easy links (or associated ISBN information) to make ordering them simple.

Download

• Release Notes
  This section will detail the release notes for the latest releases of OpenSolaris, including any hardware requirements needed to run the image.
• Order a CD
  The section will allow the user to mail order a set of packaged CDs containing the latest release of OpenSolaris for free.
• Other Distributions
  This section will introduce some of the other OpenSolaris distributions available and where they can find out more information about them.
• Archive
  The archive will list all the previous releases of OpenSolaris, allowing the user to download an older release if desired.

Store

• The store will contain a number of OpenSolaris branded articles for the user to order like t-shirts, caps, bags, stickers etc. The store could also contain (or mirror) some of the free items like on-line fan buttons.

Support

• Report a Bug
  The user would be brought to an on-line bug reporting interface, allowing them to submit a bug about a certain problem they have.
• Community Support
  This section will link out some of the support options within the community eg. discussion lists, on-line user guides, IRC channels, FAQs and user groups.
• Professional Support
  This section lists some of the vendor options for professional support.
• Hardware Database
  A fully on-line searchable hardware database, similar to smolt.fedoraproject.org. The hardware database tool would allow users successfully running OpenSolaris to submit to this database.

I can’t claim to be an information architect, and there’s very obvious questions about content currently hosted on opensolaris.org that should move across to its .com equivalent. I’ve also glazed over many of the huge technical challenges ahead of us. What’s missing? What can be simplified? Where should there be close relationships with opensolaris.org, and where should opensolaris.com stand alone? I’ve started a thread about all of this on advocacy-discuss@opensolaris.org and website-discuss@opensolaris.org - come and contribute!

Pretty much since the inception of the OpenSolaris project, we’ve been using the full word-mark as the logo, and it’s worked out pretty well. We’ve produced some pretty awesome looking swag (the hoodies and bags given at at the developer summit count as my favourite so far), but to some extent, it has limited use. For example, try fitting it into a boot screen like Alan struggled last month, or using it in a desktop user interface, and you’ll soon find yourself struggling with the size restrictions. Could we free those up?

So, could we also change the logo to generate better brand affinity, and highlight some of the themes that are central to our project? Innovation? Collaboration? Boundlessness? A couple people at Sun have been looking at this very thing, and recently contracted an agency to start exploring some of these ideas -

There are other designs here - go check them out! Thanks to our lovely assistant Simon, and to James Duncan Davidson for the use of his photo of Simon at EuroOSCON.

What do you think? Are there any strong themes coming through? Could you imagine seeing some of those designs on some swag or in the desktop UI? Do you like the color palette, or the design? Could you suggest some changes?

Good to see the folks at NSA joining the community with their Flexible Mandatory Access Control proposal. Barton has some more details about the announcement. Best of luck with the project Stephen, and welcome to the party!

Over the last couple of days or so, I’ve started to think about the media kits a little more, particularly with respect to get.opensolaris.org for the OpenSolaris release, but also in terms of being able to create derivations targeting specific sets of our potential user base. As I see it, I think it should be possible to create a generic framework that would allow us to swap in and out components, depending on that focus - with the addition of more CD’s depending on the focus.

As such you could think about a number of standalone ‘modules’ -

• OpenSolaris LiveCD ISO image
  This is the standard image that has been part of the OpenSolaris Developer Preview series, providing the user a LiveCD image, with an opportunity to demo it before they install it to their system. This will track the standard ISO images produced as part of Project Indiana, complete with IPS should they wish to download and install additional software from the network package repositories
• OpenSolaris Source Code
  With the very real limitations of network bandwidth across the world, most notably in emerging communities such as India, China and many parts of Africa, it is absolutely vital for people to have easy access to the source code. This module will provide source code to the various consolidations working out on opensolaris.org as a checked out repository (either Mercurial or Subversion), allowing the user to pull updates from the network or browse off-line. Additionally with a simple set of scripts provided, it will provide an opportunity for those running the OpenSolaris distribution to run an OpenGrok instance and allow full searching on the local source code. This could also be useful in a classroom environment, where network access is limited.
• User Documentation
  This module will provide all the user documentation for running the OpenSolaris distribution, complete with a number of tutorials or other guides.
• Developer
  
  In the developer section, it will provide a set of simple tools and applications to develop on OpenSolaris, both for the OpenSolaris community itself and also in the wider developer community.
  • OpenSolaris Community
    • Mercurial, SVN, OpenGrok, ..
    • ON build tools
    • Sun Studio Compiler
  • General Developer Community
    • Netbeans
    • Sun Studio Compiler
• Module Derivatives
  A number of variations of the Media Kit should be possible, including a tailored set of derivations of the OpenSolaris distribution. Some possibilities may include -
  • Wordpress/Roller Blog Appliance
    Run an instance of the popular Wordpress blogging application, with everything automatically configured out of the box, including a web server.
  • Ruby on Rails Web Developer
    Provide a running web server with DTrace enabled Ruby, Firefox and Apache server.
  • HPC Research
    Provide a set of developer tools to monitor performance and throughput for highly parallel tasks.
  • Others Appliances
    Are there other specific appliances we could be doing?
  • Xen Client
    Automatic Xen client configured out of the box.
  • Community Participant
    Provide an out of the box OS that could be installed to automatically mirror sources/binaries or whatever to another part of the world, helping the global distribution of OpenSolaris.

Let me know what you think!

It’s been a very difficult year for most of the OGB members. We came to the table having ratified the current constitution, trying to figure out where we fit in. While I think the OGB made some good positive progress in some areas, it also feels like we lost the ability to talk with our community and pro-actively work on a plan for growth and prosperity for our community. It would be so, so easy to walk away after a year…

But I’m not. Consistency and context of past discussions is hugely important for subsequent boards, and so far in the nomination process, Alan and I are it. I’ve always said that I’ve wanted to stay on at Sun because I think I can still add value. When that day comes when I can’t add that value, and there are other better experienced people around, I’ll leave. The OGB is no exception to that (though the current constitution states there’s a maximum of a 3 year period).

So I’m in. I’d probably give myself a C+/B- on last years performance, and I’m interested to improve that this year - on retrospect, being Secretary sucked a great amount of time and I’d like to move away from that role so I can focus on the discussion rather than trying to take notes.

There’s a couple of things I’d like to see happen next year -

• At least one face-to-face OGB meeting
• At least one face-to-face Sun/OGB meeting (and an option for other meetings with other corporate members - ideally we need to get towards an Advisory board )
• Defined focus areas for each of the OGB members, outside their normal duties
• Working group to start re-assessing the current constitution and figuring out what our community has grown into, and what changes to the constitution are needed to reflect that

Bio: Glynn Foster. Almost 30. Joined Sun in 2000, working on the GNOME project. Past GNOME Foundation Board Director, and current OGB member. Joined the Project Indiana team in 2007 and looking forward to focusing energies to product a first release OpenSolaris OS later this year.

Time is flying. They always say the older you get, the quicker it goes, and that seems true for the latest release of the OpenSolaris Developer Preview, codenamed Project Indiana. The announce mail pretty much covers most of the changes since the last release, and another incremental step towards really changing the delivery model of software for Sun has been made.

Shrinking down to a single CD image has proved massively useful for me as a remote worker, and it’s given me the flexibility of testing several ISOs on the run up to the release, without hurting my broadband plan too much - I can’t help but think that it will give 1000’s of people in developing countries with poor network infrastructure an opportunity to try it out. While the application availability on pkg.opensolaris.org is still poor, the introduction of OpenOffice fills the gap for pretty much all my needs in my day job. I can now install the packages I care about, and my disk feels lighter. Thank you to everyone who’s worked on this over the last couple of months - your patience and dedication are appreciated. Thank you to everyone who have downloaded and installed it, and more importantly, given us feedback.

But controversy continues to be the compromise for that progress.

Stephen’s two blog posts, here and here nail the issues for anyone who hasn’t caught up. It’s been a roller coaster ride over the last few months, both personally, for the project and the wider community. John Plocher has been rocking on putting together a set of draft guidelines for trademark usage and branding, after the official response from Sun on the continued plan to call it OpenSolaris.

At a personal level, being on this project is massively challenging. Not only in the desire to create the best possible user experience while encouraging continued open development, but also in terms of community dynamics and finding the right line to walk between my Sun commitments and my community ones, namely the OGB. There’s no question that there has been a shift in the community, both indicated by Sun’s rightful desire to name the artifact OpenSolaris (of which I agree with), and the interesting discussion in defect.opensolaris.org around the independence of OGB members. Dalibor’s “Finishing governance before finishing bootstrapping is a bad idea” quote highlights one of the main concerns I’ve had from the start - you can’t just switch to a self governing community overnight, you grow into it. Nor can you expect to apply a model that works in one community to another. We are all different. OpenSolaris, comically, is no exception.

So where next for the project? I’m hopeful that it will turn out just fine, perhaps naively so, but I can see people trying out the developer preview and realizing that it’s not too bad. Most of all, we need to execute in a regular and predictable fashion, as a community in as transparent an environment as possible. United. Not just Sun, but everyone.

Just got to FOSS.in this morning to join in the fun during the OpenSolaris and GNOME project days there. Everyone’s pumped up about the conference and you can hear the din of people’s horns acknowledging that right across town. It promises to be a pretty excellent conference. I’m giving a talk this morning on The Secret diary of an OpenSolaris Hacker, aged 13 and 3/4 at 10am. I’ll be stepping through some of the development processes involved in contributing to the project, and helping explain how you can raise your profile in the community based on your contributions. Come join us!

One of the hotly debated issues since we launched last week was around the addition of /usr/gnu/bin to the default path, along with the addition of bash as the default user shell. I’ve been a bash user for a pretty long time, and never really found that it got in the way much (especially compared to the older generation shells). I’ve never really had much of a reason to change.

This week I’ve decided to make ksh93 my default shell, downloaded and installed from Roland’s excellent snapshots. While I use the command-line pretty much every day, I certainly don’t use it extensively for scripting, and I probably mostly care about tab completion, and clearing my terminal window.

For tab completion, ksh93 lists the options by number and details the path, allowing you to choose one by a simple ‘N<tab>’ key combination -

gman@rampage:~$ z
 1) /usr/bin/zipgrep                  10) /usr/bin/zcat
 2) /usr/bin/zsh-4.3.4                11) /usr/bin/zipcloak
 3) /usr/bin/zipsplit                 12) /usr/sbin/zlogin
 4) /usr/bin/zipnote                  13) /usr/sbin/zoneadm
 5) /usr/bin/zip                      14) /usr/sbin/zpool
 6) /usr/bin/zsh                      15) /usr/sbin/zdump
 7) /usr/bin/zipinfo                  16) /usr/sbin/zic
  /usr/bin/zenity                   17) /usr/sbin/zonecfg
 9) /usr/bin/zonename                 18) /usr/sbin/zfs

which feels pretty useful, though less useful when you type ‘gnome <tab>’ since the output is now a single column. With bash you get a similar single column output, but it is piped through more to avoid having to scroll up later. Tab completion also seems a little awkward with ksh93 if you get part of the path wrong, since it seems to add 4 spaces after you tab making it look as if the completion succeeded.

For clearing a screen, ksh93 at the moment seems a lot more irritating. The key combination is ‘<esc><ctrl>l’, whereas bash is just ‘<ctrl>l’. I’m sure the ksh93 one is doing something more, but well, gets in the way for my use.

I’ll continue for the rest of the week and see how it all works out. I do like the shnote, shtinyurl, and shtwitter scripts in /usr/demo/ksh/fun though!

Today we released the first milestone for Project Indiana, the OpenSolaris Developer Preview. Before you even read the rest of this blog entry, start your download. The locals of Guam (the last known inhabitable place in the planet to see the final hours of October pass by) are now celebrating, hopefully with some strong alcohol.

I’d like to shout out some “thank yous” right off the bat. Thanks to everyone involved in the various projects that made up this distribution, not just those on opensolaris.org but the wider free and open source community - you guys are my heros, and I strongly value your continued commitment to freedom. I’d also like to thank those projects a little closer to home that we’ve focused on for this first release, caiman, ips, and modernization (and those behind the scenes herding them - Bill, Dan, Kelly & Bonnie). They’ve survived network outages, fires *and* earthquakes to get this out the door on time - awesome! At a personal level I’d like to particularly thank David, Stephen, Dave, Danek, Sanjay and Bart for their continued patience in answering my many questions. And finally, I’d like to thank my wonderful, wonderful team mates Sara, Patrick, Jesse, Derek, Jim, Terri, and most of all Ian. We got there, woo!

Enough of the oscars, show me the software!

The developer preview is only x86 at this time (for sheer practical reasons of wanting to get something out of the door), and should run on a minimum memory requirement of 512Mb on the metal, but also in VMWare. You’ll also notice when you start playing with it -

• It is a single CD download, so much of the software you’d expect to see in Solaris Express is not there, some of which will be available from a network package repository
• It’s built on Nevada b75a
• It is also a LiveCD, allowing you to try before you install on to your disk
• Contains the latest bits of the new Caiman installer, with a significantly improved user experience
• ZFS as default filesystem - NO WAY! WAY
• IPS as the underlying network based package management system (though SVR4 packaging is still available)
• /usr/gnu/bin has been added to the default path
• bash is the default shell
• GNOME 2.20 goodies

This first release is a prototype - some indication that we really are serious about putting this together. It has come out of the proverbial sausage factory with relatively little testing and could contain bugs that could lead to panics, data corruption or other similarly uncomfortable situations. You should probably not run this in your data center.

Download it, try it, but most importantly, tell us about it! As always, we need your help - join us on indiana-discuss (or one of the other specific project aliases). We’re not done, we’re just getting started.

I’d just like to express a big Thank you to all the people who came to Santa Cruz this weekend for the OpenSolaris Developer Summit. I had an excellent time meeting everyone from right across the community, and I hope those that attended had a bunch of fun too. Hope to see the numbers grow when we do it again in 6 months time.

I’d also, of course, like to thank the people in my team for rocking so hard, especially Jesse. And thanks to Sun too (Dan and Marc) for being willing to fund the event. I’m super pumped for the developer preview release at the end of the month, and charged to make the big push for a first release in Spring 2008.