At 12:25 AM 16-01-00 -0500, you wrote:

>From: "Kevin Lawrence" <kevin@...>
>Please don't get miffed by any of the following. I don't want to start a
>fight here: this post is meant as constructive criticism, and not to
>offend. I have every motivation to have IB succeed, prosper, and
>grow. My entire business is based on IB/Delphi, and I LOVE these
>tools. I mean it. I am evangelical about the power and elegance of
>them. Going back to Oracle Developer or Microsoft Visual Basic would be
>like trading in my ADSL line for a 14.4k modem.

Kevin, nobody has any right or place to be miffed by constructive
criticism! Keep it coming - THIS is where we get the stuff together.

>
>While I realize that the IBDI is constrained by current events, (I am sure
>there are people involved who would lend great credibility, but are unable
>to publicly participate) I am disappointed/uninspired to date with the
>current situation. My perception, limited by not being one of the "inner
>circle", is that the IBDI does not have the "parts" to effectively manage
>or negotiate either the transition from ISC to OSS, or the life after OSS.

I'm of the "inner circle" (which doesn't mean a coven or anything but just
the group that's doing the actual work to assemble the facts and people
needed to make the new Interbase a success). No, the IBDI does not have
all the parts yet. Neither does the new company. Nevertheless, there is a
whole lot of work going on to get the parts together. It's a hard call but
it IS starting to get easier and more directed as the suitable, capable and
willing get involved. Do keep in mind that everyone is part-time and doing
this on top of day jobs.

>
>That being said, my perceptions are:
>
>1) There does not appear to be a "Linus": a personality with the
>experience with the product knowledge, business experience/savvy,
>leadership, relationship with Borland, and brutal Machiavellian
>focus/commitment to lead the OSS effort.

No: the Interbase situation is a brand-new one. There never was a
Linus. There always was Ann H, though...

Face it, we aren't going to have one 'Linus'. We're going to have an
organisation that achieves all Linus achieves and a lot more besides,
because our operation needs to present profit opportunities somewhere in
the plan.

>
>2) There does not appear to be a "Steve Jobs": IB needs an evangelist. A
>marketer that is not afraid to shout from the rooftops (or whisper on all
>the street corners) why IB is the only possible solution for the middle
>80% of database applications. Someone who can communicate the benefits
>related to: architecture, stability, design, performance, TCO, and not be
>embarrassed by questioning the established dogma.

Ah, now, that is but a temporary condition. One thing I've picked up from
my contacts is that evangelism will be of paramount importance. New
Interbase will not be allowed to hide its light under a bushel, be assured
of that.

>
>3) There does not appear to be a "Marketer", or a person with the industry
>media contacts to get the message out. IB was not even
>mentioned/considered in the last PC Magazine database review: who will:
> - position IB for consideration and organize the technical effort to
> support the next review,
> - route the "IB Success Stories" (the little database that could?) with
> the industry "mavens" (Dvorak and Co.)
> - get IB on the radar screen of Fortune 1000, by getting the ear of
> Gartner Group analysts

Deadlines for publications like that are 3 months before they hit the
shops. It will be different in future reviews. We are going to get
drowned in just this sort of stuff for the next few years.

>
>This is the implementation side of the Steve Jobs character. Marketing
>doesn't define reality, it can certainly improve it.
>
>4) IBDI must, IMO, have the following people on board:
>Paul Beach - can he be Linus?
>Bill K - Were IB 6.0 to follow in a timely manner, with
>substantive technical/functional improvements, it would go far establish
>momentum and credibility: I think BK is key to this.
>Ann H - I really think she would be a great "architectural design"
>asset, and a calming influence when the fights break out. When AH talks,
>everyone seems to stop and listen.

We must just wait and see what comes out of the devolution. There's no
point in our saying "must" about anything, since it's not in our control
who will be appointed to the Executive of the new company. We have to hope
for the best, be glad if we get some of the people we want and be stoical
if we can't have them. There is "what is ideal" and "what is
possible". If we get lucky, we'll get a mixture of both.

>
>5) There does not appear to be a connection with the following
>organizations (in descending order of importance):
> - Microsoft
> - Red Hat (Caldera, Corel)
> - Novell
> - Sun

There might be, there might not be, but my reading is that a group isn't in
a position to make these connections until that group's position is
known. It seems to me that issue is part of the waiting game, until we see
more shape to Inprise's plans for devolving the new company.

>
>6) Where's the money? This can probably be done on the cheap, but
>probably not.

The money is around. It's not so much a matter of where it comes from, but
who gets the chance to invest and who gets control of our
interests. Again, our effort is hobbled until we see the game plan.

>
>7) I am worried about the inevitable IBO/IBX/BDE fight, especially WRT to
>maintaining and improving cross platform connectivity and
>development. IBO seems so much more mature/powerful, but can it port to
>Linux development tools? I am concerned about continued access to the
>BDE, and the Intersolv ODBC driver.

The point to get clear is - if our community has an audible enough voice in
the product development arena, then our concerns will be met on technical
merit. If YOU want something, make a clear technical representation about
it - write a White Paper, ask your peers for advice and feedback. Those
are thing things we should be seeing in this list. Don't look for someone
else to do it for you: if you want it, do something about it
yourself. There is NO other place for you to make this influence. Take
advantage of it - it's the best opportunity you've ever had to get your
important issues to air.

>
>8) Call To Arms: I know it is important to get the basics right, but the
>email traffic I get from IBDI paints a picture of a disjointed, poorly
>informed group that is not a position of strength WRT managing how IB is
>released to OSS. We are the light bulb, not the laser, the mob, not the
>army. Carpe Diem.

The disjointed picture you are getting from this list is a symptom of the
general lurkiveness of 200 of you.
I reiterate what I said above. DO IT! It's up to you. Keep an eye on the
newsgroups and lists and RECRUIT people you think we need. Get involved,
be willing to do something yourself instead of lurking around waiting for
someone else to do it.

>Let's pick a head guy/girl, stop mucking about with philosophy and trite
>examinations of licenses, assign some jobs, and get on with it.

Look, these things ARE happening. The "inner group" is being augmented as
people with leadership qualities in particular areas manifest
themselves. We have a leading group of three on licensing and an overall
leader (Jason) who is going as fast as he can to assemble and group issues
like viable business models and how open source development needs to
work. We have pulled in four technical leaders in the past week. We're
going to need more. Nag-nag again but DO IT! Identify an area that you
care about and want to contribute your time, effort and thought to - and
carry through - and you will be right in there. This is what voluntary
efforts are all about.

>If we are going to be a competent organization, one that is the ONLY
>choice for the future of IB, make it so. We need to put together a
>professional structure, negotiating strategy, and
>transition/development/marketing plan [web site, media releases], and do
>it all soon.

All true. And it is happening. The more active you all get as
individuals, the faster we will get there.

Good to get this out front and up. Talking about it isn't enough. DO IT!

Helen