Hi Peter,

I totally agree on the need to involve the community in the future design of 
OpenSolaris. I'd even go so far as to say that the community should be involved 
in creating an official OpenSolaris Standard the defines a whole range of 
things (packaging, proper locations for things, interfaces, etc.). Plus the 
community should be involved in setting the roadmap for OpenSolaris. Empowering 
the community like that will go a long way to getting developers involved.

 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Virtualization Architect and Consultant
Web: http://unixconsole.blogspot.com
E-Mail: unixcons...@yahoo.com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*



----- Original Message ----
From: Peter Tribble <peter.trib...@gmail.com>
To: Garrett D'Amore <garr...@damore.org>
Cc: ogb-discuss@opensolaris.org
Sent: Thu, April 15, 2010 3:22:18 PM
Subject: Re: [ogb-discuss] Call for Action

On Thu, Apr 15, 2010 at 6:50 PM, Garrett D'Amore <garr...@damore.org> wrote:
>
> PS: In my own personal opinion, there is almost zero *net* value in the
> "Open Development" process where we run open ARC cases and invite external
> developers to partake in product development.  I would hazard a guess that
> the cost of this effort has far exceeded any benefit realized as a result of
> this effort.  On the other hand, I think *Open Source* makes incredibly good
> sense for Oracle and Open Solaris.  Customers and ISVs benefit from being
> able to probe into the guts, it still can serve educational purposes, and
> probably doesn't cost the company much money.  Its my hope that Oracle will
> continue to keep doing this.  On the other hand, I won't much miss the whole
> Open Development thing if it goes away -- even though I'm probably one of
> the more frequent participants from Oracle in the open development aspects
> of Open Solaris.

I disagree. I'm not going to argue that open development has been a
success, but the failure of it to produce results is largely because it
hasn't happened, not because it's fundamentally a bad idea.

Open development means far more than allowing external bug fixes
to the corporate codebase. It includes participation all the way back
to the design. The community is a hugely valuable resource that
could be used to help drive better design, and thus fewer (expensive)
mistakes in implementing wrong solutions.

Having involvement at the design stage is also crucial to getting
buy-in and thus future involvement of the community. People are far
more likely to work on - and evangelise - something that they have a
stake in; I see this as a critical reason for lack of community involvement.

-- 
-Peter Tribble
http://www.petertribble.co.uk/ - http://ptribble.blogspot.com/
_______________________________________________
ogb-discuss mailing list
ogb-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/ogb-discuss



      
_______________________________________________
ogb-discuss mailing list
ogb-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/ogb-discuss

Reply via email to