[opensolaris-summit] My comments (very subjective) on proposed Summit topics

Brandorr brandorr at opensolaris.org
Wed Sep 19 18:08:02 PDT 2007


I figured I'd roll this down the hill and see what others say.

(I just realized that biggest thing I want to hear from the Indiana team, is
not on the list: What's been done and what needs to be done. The meeting
should be about fleshing that out and obtaining buy in to get it done.) (I
think)

Anyway, on with the list....

---------------------------------------------------------------------------------------------------------------------------------------------------

Darren Reed  Community Structure

          Elaboration needed.
---------------------------------------------------------------------------------------------------------------------------------------------------

Glynn Foster  How to plan time based releases in a non-time based release
world  One of the primary social goals of Project Indiana focus around the
release roadmap, and in particular getting to a point where we can regularly
do 6 month time based releases of our binaries creating predictable cycles
for developers who target that distribution, and users downloading,
installing and upgrading. Many popular open source communities have found
benefits of this time based approach, and others are starting to move
towards it as a way of managing their software. While this is nice in
theory, it very much relies on a strict development ethic. How can we get to
a stage of providing time based releases when the world around us has
traditionally been feature based? Is there a best of both worlds approach,
and how can our influence change the way distributions are created both
internal and external to Sun?

             Mark Kupfer's blogged about this very issue. I suggest reading
it. http://blogs.sun.com/kupfer/entry/what_i_learned_from_ubuntu
---------------------------------------------------------------------------------------------------------------------------------------------------

Brian Gupta  Developing/supporting a User community, and portal, etc.  As
Sun is marketing/pushing Indiana, Solaris, and OpenSolaris, we are
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

           No comment since this is my suggestion. :)
---------------------------------------------------------------------------------------------------------------------------------------------------

John Plocher  Architecture Community's relationship to Indiana, PSARC and
other distros.  I'm looking for direction and consensus on several
fundamental issues:

Problem: What is needed to do good systems architecture in a world that has
multiple systems? i.e., what is good for Solaris Express may not be good for
Indiana or Schillix...

              I think this is an Indiana talk... this may be off topic

Problem: What needs to be done to enable effective ARC participation by
external-to-Sun members? i.e., web services, tools, materials submission,
case creation, voting, etc

               I think this might be incorporate in a larger question about
including the community.

Problem:  What does it mean to be an external ARC member?  Job description,
scope of job, time needed, tasks, authority...?

               I view this as an important question, but might we be able to
take this question directly to the arc members on the mailing list?

Problem:  How are appeals handled?  Who makes the unpopular
decisions?  Where is the "teeth"?

              As I understand there is a Constitution that handles appeals.
Unpopular with whom? Teeth??
---------------------------------------------------------------------------------------------------------------------------------------------------

Stephen Lau  Is it hard to contribute to OpenSolaris?  How can we make it
easier?  The "is it hard" is a rhetorical question, really. Its fairly
obvious there are some barriers to contribution. This will be a gathering of
people to figure out what those barriers are, identify concrete things that
suck, and try to figure out how to reduce the suck. It is not a session
about distro specific stuff, it is not a session about adding new features
or changing things in OpenSolaris other than the contribution barriers.

               NC
---------------------------------------------------------------------------------------------------------------------------------------------------

Ben Rockwood  The Future of Patching and Upgrades (OS & Apps)

              Is there more to this topic than the current SXCE upgrade
process?
---------------------------------------------------------------------------------------------------------------------------------------------------

John Sonnenschein  Increasing community participation while maintaining
traditional stability & compatibility, or "avoiding the Linux free-for-all
mess"

               Please elaborate and give examples... (Remember we are
talking about the Indiana distro, not everything in th OpenSolaris/Solaris
universe.)
---------------------------------------------------------------------------------------------------------------------------------------------------

Tim Foster  Project Indiana, an exercise in compromise (in the UK/Ireland
sense)  Because we all have to agree to drop things that may be near/dear to
us in order to actually get something out the door. We don't have to get
everything right, but we do have to show progress. Endlessly arguing about
what's the default shell, or which version of tar we use isn't the way to
get from here to there.

               This get's me plus one, with a slight change. Basically we
need to decide what is important for Project Indiana. What do we need to
address before our first binary shipment?
---------------------------------------------------------------------------------------------------------------------------------------------------

Jim Walker  How do we test OpenSolaris?

                This get's my plus one. As I understand all Solaris Express
testing is currently done behind closed walls. If this can't be brought out
into the open, what is involved in setting up an equivelant e;nvironment
---------------------------------------------------------------------------------------------------------------------------------------------------

Dave Stewart  What is Intel doing to help OpenSolaris drivers?
                Please eleborate how the Summit can address this?
---------------------------------------------------------------------------------------------------------------------------------------------------

Ian Murdock  ZFS to the max  (justification from timf)
# fsck /dev/dsk/c0d0s4
** /dev/rdsk/c0d0s4

CANNOT READ: BLK 62217648
CONTINUE? n

         This needs more elaboration
---------------------------------------------------------------------------------------------------------------------------------------------------

Ian Murdock  Laptop support

         This needs more elaboration
---------------------------------------------------------------------------------------------------------------------------------------------------

Ian Murdock  User experience

         This needs more elaboration
---------------------------------------------------------------------------------------------------------------------------------------------------

Sara Dornsife  Naming

         This needs more elaboration
---------------------------------------------------------------------------------------------------------------------------------------------------

Brian Gupta  Opensolaris.org OSOL Infrastructure Support to the outside
community.  Currently the Opensolaris.org infrastructure (
www.opensolaris.org and the mailing lists being two example pieces of
infrastructure) is completely maintained by Sun employees. This limits
available resources.

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?

             No comment, my topic again. :)
---------------------------------------------------------------------------------------------------------------------------------------------------

Shawn Walker  Creating custom distributions using Indiana and possible legal
obligations / requirements.

            I don't know if there are going to be lawyers there. If not, I
suggest we best not speculate.
---------------------------------------------------------------------------------------------------------------------------------------------------

Stefan Teleman  C++ Standard Compliant: Sun Studio 12, BOOST, and the Apache
Standard C++ Library

            I am not sure how this directly relates to project Indiana.
---------------------------------------------------------------------------------------------------------------------------------------------------

Stuart Kreitman   Parity: Making Open Solaris equal or better than Linux as
a development desktop

            Please eleborate
---------------------------------------------------------------------------------------------------------------------------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.opensolaris.org/pipermail/opensolaris-summit/attachments/20070919/36d888d9/attachment-0001.html 


More information about the opensolaris-summit mailing list