OpenSolaris Summit07

http://blogs.sun.com/avalon/entry/manufacturing_a_community

And to be more specific: - are contributors and core contributors required? - is the voting mechanism correct to bring in new contributors? - if leaders are just those that can edit web pages, is this the right label?

seeing many people that aren't developers coming to this site.

As this is the first thing they see when they get here, I feel that this should be the logical location for a user oriented welcome page.

I also propose that this welcome page is much simpler, as the current page is a bit overwhelming for newcomers. (Hard to find certain links)

Developers would still have access to a developer homepage that is linked off the new homepage. (We might even setup a redirect: dev.opensolaris.org)

http://www.opensolaris.org/jive/thread.jspa?messageID=148391

The goal for the summit would be identifying resources within and without Sun, that can assist in the creation of said content. (We need a web designer, I'm not sure if we have any in the community yet). Also we need to identify if the URL for said content. (I propose www.opensolaris.com as a minimal page that directs people to the other pages.) Finally we need to identify an infrastructure to run the site on.

The ARC is a systems architecture body.

What can the ARC do for Indiana? That is, what does Indiana need from the ARC so Indiana can be successful for its various releases? [The ideas I've heard concern things like refactoring "the WOS" to allow different rates of change in the various sections, keeping the "core" of OpenSolaris completely compatible while allowing incompatible and disruptive innovation to happen closer to the edge. What explicit actions are needed to make that a reality?]

What can Indiana do for the ARC? Since it is an "Us-ARCing-Our-Stuff" world, what ARC-related resources are Indiana developers willing or able to provide to help deliver those things? (Or is the expectation really "Us-vs-Them", where someone /else/ is expected to do the ARC work?) In any case, what does the ARC community need to do to ensure that those resources are effectively and productively used?

How does the existing community structure need to change? What should happen when the systems architectural needs of Indiana conflict with those of Solaris or one of the other distros? Should there be an "Indiana ARC", a "Solaris ARC", a "Schillix ARC", ...etc? If so, where does an "OpenSolaris ARC" fit? What is in and out of scope for each? The needs of a kernel.org-style community are not the same as the needs of an ubuntu-style one. What needs to be done to move the larger OS.o community from its current kernel.org-ish mindset to more of the uubuntu-style one that Indiana envisions?

# fsck /dev/dsk/c0d0s4
** /dev/rdsk/c0d0s4

CANNOT READ: BLK 62217648
CONTINUE? n 

further thoughts here

There are many of sys-admin types out in the community that are capable, and most likely willing, to help out. (As well as businesses that might be willing to fund contract employees to aid in this endeavor)

Might we explore a path to opening Opensolaris.org's care and feeding to the greater community?

• What is the plan to support distribution creators?
• Will there be a special mailing list just for folks that are creating their own distribution based off of Indiana?
• Will there be special documentation explaining the legal, technical, and other requirements? (i.e. possible redistribution issues, copyright and trademark issues, licensing issues, etc.)
• Can I create a distribution that has a Solaris kernel and GNU userland (and the possible legal implications)?
• Can I redistribute the nVidia drivers with my distribution?

While legal people may not be present, that should not stop getting a list of possible questions for someone qualified to answer at a later date. I would like to see this area addressed within the scope of the OpenSolaris community (not just the Indiana project, although that would be good too).

You're at an open source conference, unconference, hothouse, etc in a room full of Linux laptops. Someone hands you a doc file on a usb stick, but its ext4 and invisible to Solaris. Bzzzt!! Or they bring their laptop up to the podium and it seamlessly syncs to the projector. Now you're really sweating. What are some simple must-have features we're missing which would let us move wirelessly and suavely in a sea of Linux and Mac laptops?

Unix/X11 dinosaur, in Sun's X server group since 2000. X.org Foundation director, trying to reconcile the needs of the X development community with Sun internal development. Currently, I am an adjunct member of the Sunray/Xorg team, helping Sunray become a fully modern Xorg-based package and raising awareness of thin clients in the community. My wife, Gloria, is my better half, and my dog is my better third. I guess that leaves just 1/6 for the real me.

Alumni of UC Santa Cruz (bahahaha) after stopping over in Berkeley for a while. ||

Recently ported compiz on Solaris. see http://blogs.sun.com/erwann/ for details.

Enjoying life in the French Alps (Grenoble) with wife & daughterS.

My main area of expertise are parallel and distributed computing related topics.

I joined OpenSolaris.org in February 2006 and co-founded the "ksh93-integration project" to work on the update of Solaris's old korn shell to the newer version and it's tight integration into the Solaris operating system and the products based on it.

I'm currently a student at the "Fachhochschule Gießen-Friedberg" (Higher Technical Institute/University Of Applied Sciences) in Germany.

• FOSS community for 10 years: GNOME and GNU developer, and FOSS confs speaker.
• Author of the Cherokee web server, GNU MacChanger, ..
• 3 Years at Sun working on the desktop. Currently SXDE technical lead.
• Here is my blog.
• Living in Madrid, Spain.

• Have been with Sun for about four years, worked in different open srouce communities related to the projects: Evolution, Mozilla(Firefox/Thunderbird), OpenSolaris(Mozilla DTrace), Google Code(Google-Breakpad).
• Here is my blog.
• Beijing, China.