2009/11/3 Alan Coopersmith <[email protected]>:
> ольга крыжановская wrote:
>> It is not too late. The OGB can terminate the XWiki migration on the
>> spot if it turns out to be impractical for the community.
>
> No, they can't - you greatly overestimate the power of the OGB.
> (It is really tempting sometimes to revert the name back to the
>  Community Advisory Board to better reflect the level of power
>  the board actually has.)
>

True.  But the OGB at least stop perpetuating the fiction and could
dissolve the team's status as an official community (and thereby
terminating their voting rights).  They do not act with the same
covenants and principles as the rest of the community.  Ascribing
labels or attributes to that group as given the rest of the community
is just a facade.   There's no reason that the benevolence can
continue, we should just quit pretending that it's done in the spirit
or within the provenance of the "community".  At least then people
would quit trying to escalate issues to the OGB, as it would be
patently obvious that what the website team does is under the complete
and sole direction of SMI.

> The website team works for Sun, not the OGB.  The OGB can only
> ask Sun management if they are willing to make changes to
> the site infrastructure that Sun provides the community.

The resources that "Sun provides the community" as in the charter are
arguably serving the community needs less and less as time progresses.
 The "community" is *clearly* not a stakeholder in determining the
changes that the website team provides.

>
> You'll get far more results, far faster, by engaging the website
> team directly with calm, reasoned conversation than trying to
> escalate through governance boards & management chains which
> cause unnecessary friction and turmoil.
>
> (You may not get what you want either way, but odds are better
>  with the direct, friendly approach.)

Care to share examples where this has actually /ever/ worked?  I can
give plenty of examples that contradict your theory.
_______________________________________________
website-discuss mailing list
[email protected]

Reply via email to