These are good and reasonable suggestions, but I hope we don't get into
a game of could-of/should-of/would-of w.r.t. Blackdown project
communications. The team communicated news when there was news, and did
have to deal with a lot of persistent "when is it coming?" questions
they could not answer.
My point was that responsiveness has been a real problem. The reaction
to this meltdown, "Inprise didn't try hard enough to reach us", has been
disappointing and I continue to be disappointed by the Blackdown refusal
to accept *any* of the responsibility for the disconnect with Inprise.
It wouldn't be the end of the world to admit that mistakes were made,
and to figure out how to prevent them in the future. I'd even be so bold
as to suggest that doing so would make a cooperative project to merge
all the fixes much more likely.
Nathan
Peter Pilgrim wrote:
>
> [EMAIL PROTECTED] wrote:
> >
> > Mike Ajemian wrote:
> > > > Let me suggest a motive that makes sense. Inprise makes IDEs. IDEs
> > > > include debuggers...Connect the dots.
> > >
> > > This was the point, Einstein. Inprise relies on its brand. I didn't
> > > think I had to spell this out to the nth degree (I mean, who in this
> > > discussion doesn't know about ownership of Java and the JDK?).
> >
>
> > I'm sorry to keep hammering on the communications thing, but there is a
> > lot of experience in this group to support it. When I tried to contact
> > Blackdown about including the Blackdown JDK with my book (a simple
> > enough question), it took me many attempts to get an answer. My other
> > book-related queries were ignored completely. A look through past mail
> > turns up many similar experiences: developers willing to sign the SCSL
> > but unable to participate, questions about schedule and availability
> > that were never answered, and so on. How about that JDK1.2.2... did you
> > know it was coming? As far as I can tell, nobody else outside of
> > Blackdown did (and, BTW, JBuilder3 requires 1.2.2).
> >
> > To quote Einstein (where did I see his name recently? :-), "Things
> > should be made as simple as possible, but not any simpler." I've
> > presented a simple explanation supported by facts and experience. I'm
> > ready to hear your simple explanation.
>
> Well there is a poor communication from Blackdown
> particularly in terms what they could have achieved from the
> web. There was JDK1.2 status page but it was poor compared
> to the efforts of Mozilla or even java.apache.org. Imagine
> we have all of this fabulous technology ...
>
> Ok nobody expected web designers, but they could recruited a good
> webmaster or content designer to keep all of us up to date
> on what was really going on. In other words get some more
> recruits. I am sure they could have found a volunteer to go
> act as go-between between the developers and the public list.
> I think I read somewhere that a Top Sun bloke did try
> to contact the blackdown list, but could n;t get thru.
> Reminds me of Banarama "Hanging on the telephone ..."
> If they 'd have asked for some perl scripts or java scripts
> to turn simple text changelog into a web page, then they'd
> have gotten em. I find it incredible that you can find
> out what "Alan Cox has been hacking today.", but you can't
> do they same for "Blackdown". May be the sun license prevents
> them ...
>
> --
>
> Adios
> Peter
>
> -----------------------------------------------------------------
> import std.Disclaimer; // More Java for your Lava, Mate.
> T H E R E D A R M Y ! ! ! http://www.manutd.com/
> http://www.xenonsoft.demon.co.uk/dairy/dairy.html
>
> ----------------------------------------------------------------------
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
