On Tue, 14 Feb 2006, Alan DuBoff wrote:

> On Tuesday 14 February 2006 12:31 am, Dennis Clarke wrote:
> > Now we have a drop in communications.
> 
> I don't think that is the case at all. It was a legal issue with 
> RealPlayer10, 
> and it's been taken care of I believe.

I respectfully disagree, and from an outsider's perspective, Dennis
is right.  Until I read this 2 minutes ago, all I knew was that there
was some legal issue with build 31+, but no details.  Now that you
have specifically mentioned what the legal problem is--thank you,
by the way--we can more fully understand the situation.

In situations like this, proactive communication is VERY important,
I think, with as many details as possible.

> I'll ignore all the dirty rat comments...it is legal issues with both 
> companies, IMO, and Sun is restricted by licensing from Real. Seriously, 
> that's a pretty big bonus with the new builds, that they'll include 
> RealPlayer10, how about a bit less name calling and just a tad more gratitude 
> for the work that is being done?

I think we're all very greatful, but we can only take into account
info that we have.  This email I'm replying to is the first piece
of concete information I've seen that fully explains the build 31+.
Given that build 31 (source) has been available for weeks now, it's
understandable that people get a little frustrated by the lack of SXCR
ISOs.

All this is a learning process for people inside of SWAN as wel
as outside.  Patience and respect is needed from both sides while
we all learn to understand the new rules.  For the community that
means being more patient when these hiccups happen, and for Sun that
means being more proactive and forthcoming in communications, with
as many details as possible (I know people are very busy, but a
concise email doesn't take THAT long to write).

-- 
Rich Teer, SCNA, SCSA, OpenSolaris CAB member

President,
Rite Online Inc.

Voice: +1 (250) 979-1638
URL: http://www.rite-group.com/rich
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to