Try as we might, we haven't been able to get all of the "good stuff" on opensolaris.org linked from all the right places. Sorry about that... We are trying to make it better, but in the meantime I thought I'd point out a couple of pages that might be of interest and that you might not find on your own:

• Community code contributions table (http://www.opensolaris.org/os/bug_reports/request_sponsor/): This table lists all code contributions offered to OpenSolaris, mostly through the 'request-sponsor' process/mail list (find out more about how this works on the Participation page or check with individual projects or communities about how they take contributions). This page lists the community code contributions and their status. At the time of this posting, there are 188 contributions submitted, and 102 of those have been integrated. Fantastic!
  
• Requesting ARC cases (http://www.opensolaris.org/os/community/arc/arc-faq/arc-publish-historical-checklist/): Eric Boutilier and John Plocher have published a process for requesting materials for historical ARC cases, and they've even got a ARC request tracking table so people can see the status of their requests. I know at least one person asked how they would know which ARC cases to request. I like the idea Stephen Hahn put forth to me on this topic: any time you see an ARC case referenced -- in the code, email, or other ARC case materials -- submit a request for it. Why not? If it can't be published, we'll figure that out and let everyone know. So, go for it.
  
• OpenSolaris distributions (http://www.opensolaris.org/os/about/distributions/): We've written up a page with short summaries and links for each of the 5 OpenSolaris distributions: BeleniX, marTux, NexentaOS, SchilliX, and Solaris Express Community Release.
  
• OSS bite-sized bugs (http://www.opensolaris.org/os/bug_reports/oss_bite_size/): This table has a list of small, self-contained bugs -- identified with the bug Keyword 'oss-bite-size' -- that are available for anyone to fix. The table is updated every couple of days with the latest status from the bug database. There is also a table (updated at the same frequency) with the list of oss-bite-size bugs that are no longer available at (http://www.opensolaris.org/os/bug_reports/fixed_oss_bite_size/). Hopefully these pages will help people find bugs to work on. Currently there are 163 oss-bite-size bugs available, and I'm hoping there are even more on the way...
  
• Community bugs (http://www.opensolaris.org/os/bug_reports/boo_list/): We also have a table for all bugs filed through opensolaris.org. The table is updated at least once a week and gives a more detailed status than what is visible on bugs.opensolaris.org. This list is a compilation of all bugs with the Keyword 'opensoalris' included in the bug -- which is automatically inserted into all bugs filed through the website.
  
• Becoming a sponsor (http://www.opensolaris.org/os/community/onnv/crt/becoming-a-sponsor/): This page provides details about how someone becomes a sponsor for community code contributions. Because the OpenSolaris source tree and other development tools are not yet available on opensolaris.org, only Sun engineers can be a sponsor at this point. As soon as we have the necessary tools and infrastructure moved to opensolaris.org, the sponsor requirements will be open beyond Sun employees. There are requirements for people to become sponsors, so please do read this page and the links provided on it (e.g., Sponsor Tasks).
  
• Sun Contributor Agreement (http://www.opensolaris.org/os/about/sun_contributor_agreement/): This agreement helps ensure that the code in OpenSolaris can be used by anyone without restriction. A contributor only has to sign this agreement once for all of their contributions, and the signed agreement applies to any Sun-led open source project contribution. The link I provided here explains what the agreement is for, the process for submitting it, and a link to the document itself.

I'll probably try to get more mileage out of this idea by posting additional blog entries with pointers when I think of them. In the meantime, I thought it would be useful to post this rather than just continuing to talk about it like so many other subjects that didn't turn into blog entries. (How is that "blog talk" entry coming along, Sara?)

By the way, please send suggestions for improving opensolaris.org to website-discuss AT opensolaris DOT org.

Anyway, I hope this is useful because I wrote this when I should have been online doing many other things for OpenSolaris...

P.S. In your face non-DJ AM!

tag: OpenSolaris

If you haven't noticed (or don't remember), it is the 1st birthday (or 1-year anniversary) of OpenSolaris today! We've got lots going on at http://www.opensolaris.org/os/, so please check it out.

Exactly 1 year (really 364 days) after we launched the OpenSolaris project, we have 100 community code contributions integrated into OpenSolaris so far -- not counting the numerous code contributions into the active Projects and the consistent non-code contributions from just about everyone in the community! I'm excessively proud and a bit awed by it all.

I'm happy to admit it, but I was wrong. I didn't think it was reasonable to have an goal of 100 community code contributions integrated into OpenSolaris within a year. I didn't have any doubts about the abilities or willingness of the code contributors or sponsors, but I thought it was an overly ambitious goal for our first year.

I was wrong.

I've learned so much since I started working on the OpenSolaris project 2 1/2 years ago, and much of that since the launch.

For the most part, though, the OpenSolaris community has just reaffirmed what I already knew to be true: OpenSolaris has a vibrant and active community of people who are excited about participating in every way they can. There are countless examples of everyone in the community working together to get something done. It is not perfect, but it's not dysfunctional. I would love to point out specific examples, but that feels too exclusionary. You should check out the OpenSolaris Community Awards (OSCAs) Nominees, though because the community has done a good job of identifying some of the key contributors from this past year.

Looking forward to next year, the OpenSolaris engineering/program/marketing team is going to work diligently with the community to get more code released, refine development processes, make building and testing easier, initiate and continue to drive adoption and evangelize OpenSolaris, revamp the web site, and provide more tools for development. It should be an even more exciting year than this one for improving OpenSolaris as a community and source base. We look forward to everyone's help to make it happen.

P.S. For those of you local to the San Francisco Bay Area, some of us are getting together to have a drink at the Oasis Beer Garden in Menlo Park starting at 6pm today. Hope to see you there! Those of you in other areas of the world should check in with community members in your area to see if thye plan to have a local gathering. Or better yet, plan one yourself!