HistoryViewLinks to this page 2013 February 11 | 02:10 pm

11 February 2013
6 PM GMT / 1 PM EST / 10 AM PST
Virtual meeting details

Contents


Agenda

1. Proposal: new formal role: OSLC StC Technical Coordinator

Proposed by Rainer
[discussion | vote]

  • idea: formalize the link between the Core WG and the Steering Committee
  • nomination: Steve Speicher

2. Prepare for Feb 20 webcast

Start time: 11 AM EST (Registration Page)

2a Review presentation

Charts sent by Sean on Feb 8
[review | discussion]

2b Discuss delivery

[discussion]

  • Can everyone attend?
  • Who will present what?
  • What will everyone say when they introduce themselves?

3. OASIS Migration Discussion

[discussion]

Not covered; no minutes.

Attendees

Steering Committee

  • Rainer Ersch, Senior Research Scientist at Siemens
  • David Ingram, Managing Director at Accenture
  • Mik Kersten, CEO of Tasktop
  • Bola Rotibi, Research Director at Creative Intellect
  • John Wiegand, Distinguished Engineer and Chief Architect for IBM Rational (StC Chairman)

Regrets

  • Andreas Keis, Manager, Software Engineering at EADS Innovation Works UK

Steering Committee Staff

  • Operations Coordinator, Sean Kennedy, IBM

Presenters

  • Steve Speicher, IBM

Minutes

1. Proposal: new formal role: OSLC StC Technical Coordinator

  • Rainer: Steve is attending every StC meeting, and he is our link to the Core WG, so we should make it formal that he is acting in this role
  • John: I believe the role is an important one; an StC that is not connected to the technical community is not as effective
    • small concern: that we’re filling these Coordinator roles with IBM employees
  • Mik: I’m for Steve
  • John: is there any alternative perspectives on this?
  • Steve: the position could be defined as “the Core WG lead”
  • John: the Core WG is an obvious connection, but I don’t know if we want to force the role to be that person
  • Rainer: I think it is good to keep it independent at the moment, but make use of the fact that Steve is the Core WG lead
  • John: what I’m hearing is that we are collectively good with creating the position and filling it with Steve
    • congratulations Steve

2. Prepare for Feb 20 webcast

  • John: is anyone unable to make this call?
    • Dave: I need to confirm after this call

2a Review presentation

  • John: at a high-level this is fine
    • one thing: it feels like our focus is to let people know about our progress and our openness to other people participating
      • so when I see “what’s new” and “what’s the future” it seems that we’re simply telling the OASIS story
      • is that the right thought? is this what we want to do?
      • say from chart 8 on
      • Bola: this second draft talks to all the relevant pieces; are you saying we shouldn’t talk about OASIS?
        • John: I’m OK talking about OASIS, it is part of it, but is it really the answer to “what is the future of OSLC?”
          • the answer is broader
          • do we want to be aspirational, do we want to talk about some bigger things
      • Bola: maybe it’s a wording thing, maybe we just need to set OASIS as the “immediate” future
        • alternatively, we could do one slide that takes the bigger view
        • John: yes. but we don’t have that slide yet, and I’m not sure its good to do in the next week
        • Bola: OASIS is the immediate future, we can talk about why each of us is involved
    • John: the title is “looking for leaders” but that doesn’t connect well with the rest of the deck
    • Sean: we could create an aspirational slide …
      • Bola: it is probably worth having a good discussion about this at a future meeting
      • Mik: I think it good to have one slide; there is a bigger picture here, and we should connect to that
        • I could help create with a slide like this … we’ve been doing some work like this for Tasktop
      • Sean: will fit well right before we get into the details of OASIS

2b Discuss delivery

  • Bola: how about John, as the chair, starts the the delivery, and run it until we get to slide 9 where we can each say our piece.
    • what is in the slide deck comes from all of us
  • John: I’m glad to kick things off, do some framing
  • Bola: maybe the question we should ask is: does anyone else want to present?
    • Rainer: I’m certainly willing, but my main concern is that we don’t speak to much, but take time to listen
    • Mik: I’m willing to participate, can can do the setup
  • John: easier for folks to listen to one voice at a time, I see:
    • an intro setup
    • acknowledgement of interesting things in the past year
    • news about OASIS
    • then open the conversation to the community
    • try to finish our materials in 20-30 minutes
  • Bola: so we don’t have any “tumbleweed moments”, we need a “plan b”
    • John: great point; I suggest we set up a discussion amongst ourselves
    • Bola: we can also have some seed questions
    • Rainer: can we email folks and ask for questions up front?
      • Sean: yes, we can do that
  • John: Mik will start us off - here’s what OSLC is, and its interesting (slides 4 and 5)
    • Mik: just let me know how much time
  • John: not sure what to do about slide 7
    • Rainer: don’t read this through, just pick a few points and let people follow the links to learn more
      • probably focus on Lyo as a key collaboration area for the community
      • it is impressive to see the list, but lets not dive into detail
  • John: easy transition between slide 8 and slide 9
    • I will cover slide 7 and 9 and start the discussion on slide 9
  • John: what is interesting on slide 9, is for each of us to make a comment about why OSLC is interesting to us and/or our company
    • 1 minute per person, upper bound
    • is everyone OK with that?
      • no response …
    • should we ask Sean and Steve to make observations about what they do?
    • Rainer: the other option, is that you take the conversation back, and also introduce Sean and Steve
  • John: how to divide up slides 11-13
    • Sean: we will put in one aspiration slide too … Mik could present that since we’re drawing from his materials
    • John: lots of people can talk aspirational … Mik can do that
    • Rainer: how much time are we going to spend on this
    • John: when I read this, unless you’re an insider, this is gibberish … it isn’t what people care about
    • John: do we want to this as a report, could give to Steve or Sean to do
    • Rainer: page 12 (stepping up) is enough to tell the story
      • we don’t need to discuss the detailed roadmap on the bottom; we don’t need the backup about V3 specs
      • page 13 (vision for OSLC) can go as backup
  • Rainer: I can take page 15 (call to action).
  • John: we need to think of a set of questions that we want to ask
    • Sean, can you collect and create a script of questions
      • Sean: yes
  • Rainer: we have a follow-up with the INCOSE OSLC interest group this week; in the Q&A section, we could ask the INCOSE folks why they’re interested in OSLC
    • I could ask them to talk for 5 minutes about this
  • John: its great to have pre-primed questions/content form INCOSE and others
    • have to be ready to talk amongst ourselves too
    • Steve: can ask the same of others such as GM and Ericsson
      • Rainer: just don’t want to have too many folks talking on the same thing
    • the other vulnerability when people are disconnected, they ask questions that aren’t meaningful
  • Dave: we could also put a question to the audience
    • say: what are you trying to get out of OSLC?
    • this could be where we invite GM and Ericsson to speak
    • Bola: can we also do some survey questions
      • Rainer: we can use the hand raising to gauge that input … specific questions require time for people to read an answer
        • Sean: I can make a list of such question to use just in case
  • John: Sean, you do the chart rev with the proposed speaking and time assignments (in the speakers notes)
    • Sean: yes

Summary

Agreements and Consensus in this meeting

  1. Steve Speicher is confirmed as Technical Coordinator for the OSLC Steering Committee

Action Items from this meeting

  1. Mik: send on some charts he’s worked on describing the aspirations on OSLC
  2. Sean: curate a list of questions “amongst ourselves” for the webcast
  3. Sean: build a list of “poll” questions we can use if needed in the webcast
  4. Sean: to revise the charts, include speakers and times in the speakers notes as well
  5. Rainer: to follow up with INCOSE and Mike Loeffler about being reading to answer the questions “why are you interested in OSLC?” and “what do you hope to get out of OSLC?”
  6. Steve: to see if Ericsson is able to do the same

Future Agenda Topics from this meeting

  1. what is the “big vision” for OSLC? - looking beyond OASIS

Category:Meeting agendas

Category:Meeting Minutes


Categories