>> Why are Sun developers not part of the OpenSolaris
>> developer community?
>>
>I have never meant that - I have said Sun in driver's seat of the
>community train (IOW the key decision maker, the one who installs all
>the pawns and directs the pieces and controls the rules of th e game)
>is not acceptable for an open project. Sun, in that role, cannot be a
>part of community.

If someone is elected in the OGB, are they then no longer part of the
community?   Which pawns does Sun install and which key decisions have
they made?  They have started the processes and then they empowered the CAB
to setup the consitution and the self-governing rules.  From this
will spring the OGB and the communities self-governance.

>Who set those rules? What if I have a valid reason to change a rule or
>two? Why can the community not set their own rules? Why is that you
>take it for granted that Sun will do things on behalf of t he
>community? To date how many rules were set in stone by the community
>(exclude Sun)? Why do I keep hearing that Sun will setup a SCM, Sun
>will do this, Sun will do that? Where can I see community' s (exclude
>Sun) decisions being taken forward? Examples?

Why do you think the rules weren't set by the community?  They are,
of course, modelled after Sun's development models as those are
part of what Sun is opening up; however, the external community
and the internal community both took part in setting up these rules.

The reason why you keep hearing about "Sun will X" is quite simple;
Sun does not want to throw the sources over the fence and tell people
were to find them and "go now and amuse yourself with them".

For Open Development to work, we need to bridge the internal and the
external community.  Clearly, we can't afford to all stop working on
Solaris until all the issues are solved; instead we're slowly moving
our development processes to the outside; this is a slow process because
the amount of changed involved inside Sun is mind boggling.

>Community in this context is an entity bound together for a cause.
>Your analogy would lead me to b elieve that whole world is a community
>- no distinguishing factors, no barriers, but no cause as well. That
>doesn't make any sense. You have to have a concept of a common, well
>defined, meaningful, non-conflicting cause when you consider a
>community.

In some sens the whole world is, but OpenSolaris narrows the world
down considerably.  I don't agree that a community needs to have a
no-conflicting cause.  A community is defined by those who comprise
it; not by how they feel about one another or a single goal.  Such
definitions are unworkable.  Perhaps you're confused with the term
"commune".  A community is much more loosely coupled than that;
I would define it as "a group of people with a common interest";
there is no consensus, implied or otherwise, in a community.

But I also think I take issue with your implication that somehow
Sun nor its Customers have any cause in common with the
"OpenSolaris community".  I think they do.  But it's more vague than
that, that's why I'd say it's a common interest (in all things
OpenSolaris/Solaris)

>Your definition of community will include all - the hunters, the
>people who destroy weapons, the people who demonstrate against hunting
>and people who don't like people who hunt. That won't make any sense.

No, it doesn't.  You're trying very hard to argue semantics and deliberately
misunderstanding and continuously redirecting the argument.

Clearly, such a group of people would not form a "hunting community".
But they could all be members of the OpenSolaris community if
they share an interest in OpenSolaris.

Now, if for your sake I'd define OpenSolaris' goal as
"furthering the use of OpenSolaris/Solaris, fostering the development
of OpenSolaris/Solaris and improving the quality, funcionality,
reliability, performance etc of OpenSolaris/Solaris", where would Sun's have
a conflict of interest with your mythical not-to-inclusive
OpenSolaris community?

'nuf said.

Casper
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to