Do other eclipse projects (non-COSMOS) have admonitions they won't
erode commercial offerings in their mission statements?
Perhaps I am shouldn't worry about this so much and will gladly drop
it, but there was much ado about "not eroding" in the early stages of
COSMOS. Your statements seem to say that the "industry" should not
worry at all if COSMOS erodes or not.
You say:
We have to be very clear about
the difference
between our "vision" and aspirations versus real current commercial
viability.
So, I think where we are at, is that we COSMOS people can do
whatever we want, ignoring the erode thing, because of Harm lemma's
below.
The COSMOS statement is that "Gee, if we erode anything, it will be
at the very bottom end and of no concern, because commercial offerings
have so much more than COSMOS could ever aspire to."
I am totally cool with this. It allows us to do the "right" thing
and ignore the commercial repercussions.
--oec
Harm Sluiman wrote:
Although it is a regular high level
debate that this level of tooling will erode larger commercial
offerings.
There are typically two import
bullets
to shoot that debate.
1. If the level of
function we provide
is a serious threat to the value proposition of the existing commercial
offering, then the offering is at risk anyway as there are many more
functional
offering available at low cost. This is actual an opportunity in that
case
as the offering can extend COSMOS and end up with more value add and be
"open and extensible"
2. A regular add in commercial
offering
is the scalability and direct customer support they provide as well as
ease of install and configuration. Although I am sure the COSMOS
mailing
lists and newsgroups will be highly responsive, it won't equate to
commercial
support. I also don't think a deployment on Derby is the scalable
answer. Install and TCO are just not the prime focus of the project.
Out
of the box experience will be awesome I am sure, but that is not going
to be a secure enterprise or SMB managed deployment.
We have to be very clear about the
difference
between our "vision" and aspirations versus real current commercial
viability.
Thanks for your time.
--------------------------------------------------------------------------
Harm Sluiman, STSM,
phone:905-413-4032 fax: 4920
cell: 1-647-300-4758
mailto:sluiman@xxxxxxxxxx
Admin : Arlene Treanor atreanor@xxxxxxxxxx Tie: 969-2323 1-905-413-2323
Are we "cool" with telling our "sponsors"
(in June) that the intent is to build software that systems management
tools can be built upon?
It is a little of a dance, saying that it won't corrode
commercial opportunities, yet will provide a platform that is fully
intended
to allow someone else to do such.
I can live with it though....
--oec
Marius Slavescu wrote:
This is from the main COSMOS page:
"The COSMOS (COmmunity-driven Systems Management
in Open Source) project aims to provide an extensible, standards-based
platform upon which software developers can create specialized,
differentiated
and inter-operable offerings of tools for system management."
If you replace with platform with framework will read close to what I
said.
In some interpretations platform could provide more that what a
framework
would do and in others they can mean the same thing (I prefer the
second).
Regarding the "commercially competitive" comment, the level of
competitiveness will be set by the participants (I mean the companies
that
contribute) to the project and I think that happens in all the other
Eclipse
projects.
Thanks !
Marius Slavescu
IBM Tivoli Autonomic Computing - Toronto Lab
Phone: 905-413-3610
Agreed on exemplary.
Is COSMOS supposed to provide a software framework? When we
go back to our people in June, do we tell them that the intent is to
provide
a software framework for interoperability? Or is that too close to
the "commercially competitive" trip wire?
--oec
Hawkins, Joel wrote:
+1. Exemplary
implementation
reads better as well.
Cheers,
Joel
-----Original Message-----
From: cosmos-dev-bounces@xxxxxxxxxxx
[mailto:cosmos-dev-bounces@xxxxxxxxxxx]
On Behalf Of Marius Slavescu
Sent: Wednesday, March 21, 2007 10:14 AM
To: Cosmos Dev
Subject: Re: [cosmos-dev] Elevator Speech
I my mind COSMOS was intended to provide an extensible framework that
will
allow interoperability and integration of system management tools (open
source or proprietary), beside of the exploration and reference
implementation
of some existing or emerging standards in this space.
If we tag the result of the project as being just demonstrative instead
of exemplary, in my view we may reduce the attractiveness of the
project.
In the incubation phase it may not reach the exemplary level, which
should
be fine.
Thanks !
Marius Slavescu
IBM Tivoli Autonomic Computing - Toronto Lab
Phone: 905-413-3610
Ok, here is my first cut at the elevator speech for COSMOS, so we have
something to yell about at the beginning of the phone call. Please
feel
free to yell by email beforehand.... Specifically, do each of you
think that your management would agree that they want to continue to
":invest" in COSMOS with this elevator pitch?
-------------------------------------------------------------------------------------------------------------------------------------
COSMOS is an open source, vendor neutral effort to explore emerging
standards in the context of system monitoring. COSMOS is developing
a
demonstration implementation using those open standards to prove the
concepts. Standards being explored are: SML, CML, WSDM..
Questions:
------------
i) Can we list the specific standards that we are exploring? Or
do
we want to say "Standards being explored include..." Is
my list
complete enough?
ii) It would be more powerful to say that montoring vendors are
cooperating together to do this. Can we? Something like "COSMOS
is an
open source, vendor neutral effort to explore emerging standards in the
context of system monitoring. The effort includes monitoring vendors
IBM, CA, CompuWare and GroundWork."
--oec
--
--
--------------------------------------------------------------------
Oliver E Cole
oec@xxxxxxxxxxxxx
OC Systems
www.ocsystems.com
9990 Lee Hwy, Suite 270
(v) 703.359.8160 x160
Fairfax, VA, 22030
(f) 703.359.8161
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
=00
The contents of this e-mail are intended for the named addressee only.
It contains information that may be confidential. Unless you are the
named
addressee or an authorized designee, you may not copy or use it, or
disclose
it to anyone else. If you received it in error please notify us
immediately
and then destroy it.
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
--
--
--------------------------------------------------------------------
Oliver E Cole
oec@xxxxxxxxxxxxx
OC Systems
www.ocsystems.com
9990 Lee Hwy, Suite 270
(v) 703.359.8160 x160
Fairfax, VA, 22030
(f) 703.359.8161 _______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
--
--
--------------------------------------------------------------------
Oliver E Cole
oec@xxxxxxxxxxxxx
OC Systems
www.ocsystems.com
9990 Lee Hwy, Suite 270
(v) 703.359.8160 x160
Fairfax, VA, 22030
(f) 703.359.8161 _______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
_______________________________________________
cosmos-dev mailing list
cosmos-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cosmos-dev
--
--
--------------------------------------------------------------------
Oliver E Cole oec@xxxxxxxxxxxxx
OC Systems www.ocsystems.com
9990 Lee Hwy, Suite 270 (v) 703.359.8160 x160
Fairfax, VA, 22030 (f) 703.359.8161
|