public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jim Grisanzio <jim.grisanzio@sun.com>
To: linux-kernel@vger.kernel.org
Subject: Opening Day for OpenSolaris
Date: Tue, 14 Jun 2005 11:00:24 -0500	[thread overview]
Message-ID: <0II2009R4XOZVX@olm-ms1.sun.com> (raw)

You are receiving this e-mail at linux-kernel@vger.kernel.org <because you requested a reminder from OpenSolaris.org for additional information. To update your communications preferences, please see the link at the bottom of this message. We respect your privacy and post our privacy policy at www.sun.com/privacy  
----------------------------------------------------------

Sun is Open Sourcing Solaris OS
Today, June 14, 2005, is Opening Day for OpenSolaris.
http://see.sun.com/Apps/DCS/mcp?r=70043his4ElHi012000418NO043his0mRdwBRd7v&=1

Dear Sun Community Member:

I'm happy to tell you that the OpenSolaris project is now open, and we welcome your participation at our new community site: 

http://see.sun.com/Apps/DCS/mcp?r=70043his4ElHi012000418NP043his0mRdwBRd7v&=1

When you visit the site you'll see we have the OpenSolaris source code, a new source browser, build tools, documentation, a community portal, mailing lists, blogs, and much more. 

There are many ways for developers to immediately start contributing to the project, such as testing code, fixing bugs, documenting processes, and suggesting RFEs. You can also follow the technical conversations among Solaris engineers and the community on the long-term co-development model. Additionally, Sun is collaborating with the OpenSolaris Community Advisory board (CAB) on the overall governance proposal -- which will be debated, iterated, and ratified in the open right on opensolaris.org. 

There are also 145 OpenSolaris Pilot Program participants from around the world who have been working with Sun for nine months on the project. They have detailed knowledge of the code and tools, so many of them -- in collaboration with engineers at Sun -- can help educate new community members. The best place to meet these developers is the project's main discuss list. 

The OpenSolaris source base is large, around 10 million lines, but if you go to http://see.sun.com/Apps/DCS/mcp?r=70043his4ElHi012000418NM043his0mRdwBRd7v&=1 you will see hundreds of OpenSolaris engineering blogs from across Sun's engineering community explaining in detail the code they have written. The amount of technical content in these engineering blogs is impressive, and you can expect even more as we go. You can also find those blogs, as well as the pilot community blogs, at opensolaris.org. 

We have tried to make the OpenSolaris project a place where engineers talk directly to engineers. This is the first step in the process, and we welcome your involvement. This is a community that takes collaboration and quality seriously. It's a community that has a lot of offer, and it's a community that's open minded. Come join us. 

Best,
Jim Grisanzio 
Community Manager, OpenSolaris 
http://blogs.sun.com/jimgris

---------------------------------------------------------
 
(c) 2005 Sun Microsystems, Inc. All rights reserved. For information on Sun's trademarks see: http://www.sun.com/suntrademarks 

To update your Sun subscription preferences or unsubscribe to Sun news services, use this link: https://see.sun.com/Apps/DCS/mcp?r=70043his4ElHi012000418NN043his0mRdwBRd7v&=1

Sun Microsystems, 18 Network Circle, MS: UMPK17-307, Menlo Park, CA,  94025, USA  

 


-----------------
annmn:[743his043his4ElHi0120000043his0mRdwBRd7v]




             reply	other threads:[~2005-06-14 15:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14 16:00 Jim Grisanzio [this message]
2005-06-14 15:59 ` Opening Day for OpenSolaris Jeff Garzik
2005-06-14 16:10   ` bert hubert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0II2009R4XOZVX@olm-ms1.sun.com \
    --to=jim.grisanzio@sun.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox