[omniORB] Update Re: [HOW] DOES THIS AFFECT US?

[Duncan Grisby]

On Friday 10 May, steve.white@bnpparibas.com wrote:

> Can you tell me how this impacts us (as OmniORB users)?

See my original posting on the subject:

  http://www.omniorb.org/omniORB/archives/2002-04/0136.html

Since I wrote that, things have moved on a little, so here's an
update. The main change is that I have decided that I am in a position
to offer commercial support.

I'm in the process of creating a company. The current plan is that it
will offer four things: omniORB commercial support of varying levels,
advertising, contract omniORB development, and general consulting.

Support will, to start with at least, be email support only, with the
possibility of on-site visits charged on a daily basis. Different
support levels (and costs) will have different guaranteed response
times, and different numbers of included "incidents".

Advertising will work with a web page and a file in the omniORB
distribution along the lines of "omniORB development is kindly
supported by the following companies..."  Advertising is basically
sponsorship as I outlined in my previous message, but it gives a
concrete basis for a contract. My current thought is that I'll allow
companies to offer whatever they think appropriate for advertising,
but there will clearly be a lower limit below which it's not worth it.

Contract omniORB development is simply implementing something for
someone, priced on a per-contract basis. It can cover either ORB
development, to be released as part of omniORB, or application
development for the specific client. General consulting extends to
things that don't involve omniORB, either using other CORBA ORBs, or
totally unrelated things.

None of this is set in stone yet, but the feedback I've had so far
suggests that it's a sensible route to take. I'd appreciate it if
people could reply to me to say whether their company would be likely
to be interested in any of these options. If you'd be interested in
something else instead, please let me know about that, too.

Yours,

Duncan.

-- 
 -- Duncan Grisby         --
  -- duncan@grisby.org     --
   -- http://www.grisby.org --