[Oslc-steeringcommittee] AI: keeping the initial assessment document as a living and ongoing assessment

Mon Jul 23 17:18:30 EDT 2012

Those metrics look good.  Additionally I think that we should carefully
track a small number of metrics that are indicative of real adoption and not
"vanity metrics" in that they lean towards being indicative of real adoption
and less suitable for marketing momentum.  Here is a quick pass at choosing
a few from the list below:
* Number of products implementing OSLC (a less inflated listing than on the
"Software" page, i.e., Kovair and Tasktop Sync should be one entry, not
multiple)
* Number of products supported by OSLC integrations (more similar to
"Software" page) 
* Number of products that build on Lyo

Mik

From:  "Ersch, Rainer" <rainer.ersch at siemens.com>
Date:  Monday, 23 July, 2012 5:38 AM
To:  "oslc-steeringcommittee at open-services.net"
<oslc-steeringcommittee at open-services.net>
Subject:  Re: [Oslc-steeringcommittee] AI: keeping the initial assessment
document as a living and ongoing assessment

Dear StC Colleagues,
this mail is in response to the action item Sean assigned to me from our
last meeting:

4. Rainer: open the subject of ³keeping the initial assessment document as a
living and ongoing assessment² on the mailing list, cover the benefits of
doing so, and propose how we¹ll cover the cost (in time) of doing so

This action item was based on my comment, when Sean presented the ³OSLC
initial assessment², not to stop here with the assessment. As indicated in
the action item, my proposal was to keep this document (work) going and
monitor progress over time. Especially some of the numbers (members,
participating companies, workgroup sessions and participants, etc.) could
serve as a base matrix to monitor. Based on these numbers, ³someone² should
draw conclusions from time to time, and some of these numbers should be
published to document OSLC success.

As far as the numbers are concerned, hopefully the new governance model
(OSLC membership, WPA signees, ..) and the new infrastructure (page hits,
etc) will make it easier to get such numbers. For some others, we could ask
e.g. the WG leads to provide them on quarterly bases (e.g. number of WG
meetings and participants). Publishing could be done by the COM WG. StC (and
analysts?) could evaluate and draw conclusions.

What are the right numbers we want to monitor?
Here are some examples:
-            Number of OSLC members

-            Number of participating companies (companies of OSLC members)

-            Number of released spec (versions)

-            Number of WG meetings, participants, Š

-            Number of partners (SDO, other associations and such we work
with, ..)

-            Number of contributors on Lyo

-            Number of contributions on Lyo

-            Number of implementations (as listed on ³Software²)

-            Number of vendors with released products with OSLC
implementations

-            Number of publications (webcasts, conference talks, Š)

-            Some Page hits on ³open-services.net² (e.g. ³ABOUT² as
indicator for ³new² interest, ³BLOG² as info about active users, Š)

-            Š

There are some more suggestions in Sean initial assessment paper (see
attached). The basic question is: how do we come to useful and easy to
maintain list?  The next question is, what kind of conclusions do we expect
(growth rates expectations, release frequencies, Š). We could monitor the
numbers for a while and then identify areas to work on.
If this topic is important to us, we should give our Operation Coordinator
to collect these numbers with the help of some other roles. Keep in mind, we
only have one Operation Coordinator and we should keep an eye on the
workload and priorities we assign to him.

Please feel free to comment on this and add your ideas and concerns.

Bye and have a nice day
Rainer

From: oslc-steeringcommittee-bounces at open-services.net
[mailto:oslc-steeringcommittee-bounces at open-services.net] On Behalf Of Sean
Kennedy
Sent: Thursday, July 19, 2012 10:20 PM
To: oslc-steeringcommittee at open-services.net
Subject: [Oslc-steeringcommittee] (draft) Minutes from 19 July 2012 meeting
are now available

Hello Steering Committee members:

The minutes of today's meeting are now available:
http://open-services.net/wiki/120719-StC-Meeting/#minutes
Please review and comment if you spot an inaccuracy or have another concern.

At the bottom of that document you will also find all the action items
<http://open-services.net/wiki/120719-StC-Meeting/#action-items>  grouped
together. Steve Speicher, John Wiegand, Rainer Ersch, and myself have action
items.
Although not called out as an "action item from this meeting", I think it
would be good for everyone to take a look at the ideas for raising the
profile of OSLC 
<http://open-services.net/bin/view/Main/AwarenessRaisingActivities#ideas>
that the Communications WG has compiled. If you have thoughts for more
ideas, please feel free to add them directly to that page.

The agenda for the August meeting
<http://open-services.net/wiki/1208-StC-Meeting/>  is also available, and
has three draft topics (you may also want to look at the StC agenda topics
backlog <http://open-services.net/wiki/StC-Agenda-Topics-Backlog/> ).

Sean Kennedy <mailto:seanpk at ca.ibm.com>

Phone: 905-413-4385 (Internal: 313-4385)
Email: seanpk at ca.ibm.com <mailto:seanpk at ca.ibm.com>
LinkedIn: seanpk <http://ca.linkedin.com/in/seanpk>
There is nothing more powerful than an idea whose time has come. -- Victor
Hugo
_______________________________________________ Oslc-steeringcommittee
mailing list Oslc-steeringcommittee at open-services.net
http://open-services.net/mailman/listinfo/oslc-steeringcommittee_open-servic
es.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20120723/59216e09/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 166 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20120723/59216e09/attachment.png>