[Oslc-steeringcommittee] OSLC Steering Committee Panels atInnovate 2013

Tue Jan 15 16:30:29 EST 2013

Hi Sean,

Thanks a lot for submitting these two placeholders! I'm available for the SSE Panel. I like the idea of addressing two different tracks like ALM and SE!

I already have a speaker profile, so you should be able to add me.

Best regards,

Andreas

From: Oslc-steeringcommittee [mailto:oslc-steeringcommittee-bounces at open-services.net] On Behalf Of Sean Kennedy
Sent: 15 January 2013 20:26
To: Ersch, Rainer
Cc: oslc-steeringcommittee at open-services.net
Subject: Re: [Oslc-steeringcommittee] OSLC Steering Committee Panels atInnovate 2013

Hi Rainer,

Thanks for your reply.

I think I prefer the modification:
"1. make integrations easier and more robust, "
I think the change you propose would lead us to:
"1. make software, systems engineering, integrated system management, ... integrations easier and more robust"
i.e. we'll need to add all the different fields that are touched by OSLC.

I still have to follow up on BoFs ... I thought they'd be at lunch again, with packed lunches. We could have one for OSLC.
I plan to organize a hospitality suite like last year as well. That will likely be Monday or Tuesday evening.

I've made the two proposals because there are two tracks and I wanted to give us the opportunity to reach the greatest audience. Also, it seems some of the terminology used in the two fields is somewhat different (see the special meaning placed on "software" that led to the comment about the abstract), so we can use the right language with the right groups.

"We should prepare a presentation about the OASIS transition status to start with, and focus, but not limit, the discussion to organizational topics. Technical topics (RDF syntax and such) are hard to explain in such open sessions, due to different levels of knowledge in the audience. Nevertheless, we should have technical experts (e.g. WG leads) present to address technical topics or connect them with the interested parties for offline discussions.  
We should also spend some time to explain how people can get involved in OSLC. The ultimate goal of the sessions should be to recruit some members for the active participation in the workgroups. "
I think we could cover these things through some of the "prepared questions" in the panel discussions. Does that make sense? Given how "sliced and diced" the conference is amongst streams and tracks, if we could pick another track for a third presentation, we'd likely get a whole new audience, even if we covered the info in the panels too.

EVERYONE: what do you think?
If you sign in to the Innovate site [1] and create a speaker profile, I can add you as a speaker to either session.

[1]: https://www.ibm.com/events/tools/innovate/innovate2013ems 

Sean Kennedy  

________________________________

OSLC: Lifecycle integration inspired by the web -- http://open-services.net/ <http://open-services.net/> 
Eclipse Lyo: Enabling tool integration with OSLC -- http://eclipse.org/lyo/ <http://eclipse.org/lyo/>  

There is nothing more powerful than an idea whose time has come. -- Victor Hugo

 "Ersch, Rainer" ---2013/01/15 11:43:39 AM---Hi Sean, I like your session proposals very much. I would suggest only a slight change in the line:

From: "Ersch, Rainer" <rainer.ersch at siemens.com>
To: Sean Kennedy/Toronto/IBM at IBMCA, "oslc-steeringcommittee at open-services.net" <oslc-steeringcommittee at open-services.net>, 
Date: 13/01/15 11:43 AM
Subject: RE: [Oslc-steeringcommittee] OSLC Steering Committee Panels at Innovate 2013

________________________________

Hi Sean,
I like your session proposals very much. I would suggest only a slight change in the line:
    from:              "1. make software integrations easier and more robust,"
    modify to:       "1. make software & system engineering integrations easier and more robust,"

I'm available for both, if it's not on Thursday. We should not run the session against each other (at the same time).
I like evening sessions (e.g. BOFs), because people are not rushing so much anymore, from one session to another.
We could call it "OSLC Café" like the "Jazz Café" in previous years. 
If we want to go for BOFs, Monday and Tuesday evening would be the choices. Maybe we can have a mix too: 
One regular session during the day and one evening session. 
I would not distinguish too much between ALM and System. Just leave it to the audience which topics are more interesting.
We should prepare a presentation about the OASIS transition status to start with, and focus, but not limit, the discussion to organizational topics. Technical topics (RDF syntax and such) are hard to explain in such open sessions, due to different levels of knowledge in the audience. Nevertheless, we should have technical experts (e.g. WG leads) present to address technical topics or connect them with the interested parties for offline discussions.  
We should also spend some time to explain how people can get involved in OSLC. The ultimate goal of the sessions should be to recruit some members for the active participation in the workgroups. 

Bye and have a nice day
Rainer

From: Oslc-steeringcommittee [mailto:oslc-steeringcommittee-bounces at open-services.net] On Behalf Of Sean Kennedy
Sent: Tuesday, January 15, 2013 4:35 PM
To: oslc-steeringcommittee at open-services.net
Subject: [Oslc-steeringcommittee] OSLC Steering Committee Panels at Innovate 2013

Hello OSLC Steering Committee members:

I have submitted two "place holder" sessions for Innovate 2013. One for the Lifecycle Management track, and one for the Systems Engineering track.
They are basically the same idea, though the first takes an ALM slant while the second focuses on systems engineering.

Here is the abstract (it is common for both):
The "integration problem" is one faced by all businesses and is often solved in an unsatisfactory manner. e.g.: tight coupling makes changes difficult; multiple copies of data can slow down workflows, increase storage requirements, and worse; problem determination and resolution in such systems can be quite costly. Through OSLC, industry experts have gathered together for public discussion of common problems and solutions, and have published open specifications to: 
1. make software integrations easier and more robust, and 
2. expose more lifecycle data so that it can be effectively used. 
Join members of the OSLC Steering Committee for an insightful discussion covering the common problems faced by software teams, the solutions available to those teams today, and a look ahead to what stubborn problems are the next to be tackled. 

This is the common presentation outline:
The panel discussion will be directed by the moderator, asking prepared and previously submitted questions, and taking questions from the audience. 

Improvements to the abstract are certainly welcome, but it is probably more important that you confirm you'd like to participate in one (or both) of these panels.
My initial (and maybe simplistic) assignments are:
Me as the moderator for both.
ALM Panel: Dave, Mik, and John
SSE Panel: Rainer, Andreas, and Bola

Best regards,  

Sean Kennedy   

________________________________

OSLC: Lifecycle integration inspired by the web -- http://open-services.net/ <http://open-services.net/> 
Eclipse Lyo: Enabling tool integration with OSLC -- http://eclipse.org/lyo/ <http://eclipse.org/lyo/>   

There is nothing more powerful than an idea whose time has come. -- Victor Hugo 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20130115/9fa9f6ee/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 166 bytes
Desc: image001.png
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20130115/9fa9f6ee/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.gif
Type: image/gif
Size: 105 bytes
Desc: image002.gif
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20130115/9fa9f6ee/attachment.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 166 bytes
Desc: image003.png
URL: <http://open-services.net/pipermail/oslc-steeringcommittee_open-services.net/attachments/20130115/9fa9f6ee/attachment-0001.png>