Hi,

Well I don't think the community should dictate what Sun should do with their 
products. But I think that if both were to work together in a clear and 
consistent manner, it benefits everyone. By having Sun employees and non-Sun 
employees working together to continue the development of OpenSolaris, it can 
reach a wider audience. I think everyone wants to see success for OpenSolaris 
and its derivatives. Having an open community enables Sun, its customers, and 
developers around the world to participate. Ultimately, it's the level of 
participation that will either strengthen us or break us.

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
Octave J. Orgeron
Solaris Systems Engineer
http://www.opensolaris.org/os/community/sysadmin/
http://unixconsole.blogspot.com
unixconsole at yahoo.com
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

----- Original Message ----
From: Stephen Lau <ste...@opensolaris.org>
To: Octave Orgeron <unixconsole at yahoo.com>
Cc: MC <rac at eastlink.ca>; ogb-discuss at opensolaris.org
Sent: Sunday, January 27, 2008 7:19:25 PM
Subject: Re: [ogb-discuss] Ben's Agenda Items for Jan 23rd, 2008


Hi 
Octave,

I 
disagree.  
The 
point 
of 
OpenSolaris 
was 
not 
to 
open 
up 
Solaris 
development 
and 
incorporate 
everyone's 
individual 
opinion 
and 
thoughts 
into 
Sun's 
business 
or 
technical 
decisions.  
OpenSolaris 
exists 
so 
people 
can 
work 
on 
OpenSolaris; 
whatever 
Sun 
choose's 
to 
do 
(whether 
wisely 
or 
poorly) 
with 
its 
own 
Sun 
branded 
work 
such 
as 
Indiana 
is 
up 
to 
Sun.

Everyone 
repeat 
after 
me:
OpenSolaris 
does 
not 
give 
me 
the 
right 
to 
tell 
Sun 
what 
to 
do.
(as 
much 
as 
we'd 
like 
to 
think 
it 
does) 
:)

cheers,
steve

Octave 
Orgeron 
wrote:
> 
Hi 
Everyone,
>
> 
This 
does 
bring 
up 
some 
interesting 
topics. 
While 
I 
agree 
it's 
important 
for 
Sun 
to 
protect 
it's 
IP 
during 
the 
development 
phase, 
the 
side 
effect 
is 
that 
there 
can 
be 
a 
disconnect 
when 
a 
new 
technology 
is 
released 
into 
the 
OpenSolaris 
community. 
Indiana 
for 
example 
was 
a 
huge 
undertaking 
and 
caused 
a 
lot 
of 
head 
*turning*. 
It 
would 
appear 
to 
me 
that 
this 
kind 
of 
a 
situation 
causes 
conflict 
because 
the 
community 
was 
not 
involved 
in 
the 
decisions 
or 
the 
design. 
So 
how 
can 
we 
fix 
this 
process 
and 
prevent 
such 
*surprises*? 
>
> 
Well, 
I 
think 
the 
best 
place 
to 
start 
is 
to 
have 
the 
community 
drive 
the 
roadmap 
for 
OpenSolaris. 
This 
means 
that 
we 
as 
a 
community 
come 
together, 
discuss 
the 
design 
choices, 
and 
make 
the 
decisions. 
Sun 
should 
be 
involved, 
since 
they 
have 
a 
vested 
interest 
in 
maintaining 
compatibility, 
which 
I 
believe 
is 
critical 
for 
the 
success 
of 
both 
Solaris 
and 
any 
OpenSolaris 
distros. 
However, 
the 
driving 
force 
should 
be 
the 
community. 
So 
the 
question 
is 
how 
do 
we 
protect 
Sun's 
IP 
during 
the 
design 
phase 
of 
a 
new 
technology 
or 
feature, 
before 
it's 
open 
sourced? 
And, 
how 
do 
we 
as 
a 
community 
ensure 
that 
such 
releases 
do 
not 
negatively 
affect 
current 
community 
efforts? 
I 
think 
the 
answer 
is 
that 
we 
need 
the 
following:
>
> 
1. 
Define 
what 
makes 
components 
are 
part 
of 
OpenSolaris. 
This 
could 
be 
an 
academic 
exercise 
in 
looking 
at 
what's 
already 
open 
sourced 
and 
what 
will 
not 
be 
open 
sourced 
(CDE 
for 
example).
> 
2. 
Define 
an 
OpenSolaris 
standard 
that 
all 
distros 
must 
comply 
to 
for 
OpenSolaris 
branding 
or 
to 
have 
the 
right 
to 
say 
"Based 
on 
OpenSolaris" 
or 
"OpenSolaris 
Compliant".
> 
3. 
Define 
a 
Roadmap 
for 
OpenSolaris. 
This 
would 
involve 
figuring 
out 
when 
projects 
will 
be 
reviewed 
and 
integrated. 
This 
also 
means 
that 
Sun 
would 
have 
to 
atleast 
present 
what 
the 
impact 
of 
a 
new 
technology 
would 
be 
and 
outline 
any 
proposed 
changes 
to 
the 
OpenSolaris 
standard. 
The 
community 
would 
then 
have 
a 
say 
in 
if 
it 
makes 
sense 
or 
not.
> 
4. 
Have 
an 
open 
process 
for 
reviewing 
and 
approving 
items 
for 
integration. 
This 
means 
that 
Sun 
and 
the 
community 
come 
together 
and 
make 
decisions 
based 
on 
an 
agreed 
foundation 
of 
principles.
>
> 
This 
might 
be 
idealistic, 
but 
I 
think 
it 
could 
move 
things 
in 
the 
right 
direction.
>  
> 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
> 
Octave 
J. 
Orgeron
> 
Solaris 
Systems 
Engineer
> 
http://www.opensolaris.org/os/community/sysadmin/
> 
http://unixconsole.blogspot.com
> 
unixconsole at yahoo.com
> 
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*






      
____________________________________________________________________________________
Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping

Reply via email to