Meetings/Telecon2014.04.22

Event details

• https://www.oasis-open.org/apps/org/workgroup/oslc-automation/event.php?event_id=37752

  Chat room: http://webconf.soaphub.org/conf/room/oslc-automation

Agenda

• Roll Call
• Scribe nomination
• Review minutes of previous meeting
• Look for volunteer for note taker
• Approval of last week's minutes
• Discussion of scenarios, with a view to move towards deciding on the ones to include in the next specification deliverable

  • Scenario submitted on mailing list:deploying build artifacts as part of Continuous Integration

• Any other business
• Adjourn

Resolutions

Minutes

Chair

Martin Pain

Scribe

John Arwe

Attendees

John Arwe (IBM), Martin Pain (IBM), Uri Shani (IBM), Umberto Caselli (IBM). Quorum not achieved.

Regrets

Florian Georg and Steve Speicher

Original Chat transcript from room: oslc-automation

[16:13] John Arwe (IBM): scribe: John Arwe

[16:13] John Arwe (IBM): ... under the assumption that either (a) we will get to quorum eventually or (b) others will use them to catch up.

[16:14] John Arwe (IBM): Topic: Scenario submitted via email

[16:14] John Arwe (IBM): https://www.oasis-open.org/apps/org/workgroup/oslc-automation/email/archives/201404/msg00008.html

[16:17] John Arwe (IBM): some recap of concepts coverable via oslc automation 2.0, which is an accepted contribution.

[16:17] Martin Pain (IBM): http://open-services.net/wiki/automation/Automation-Scenarios/

[16:18] Martin Pain (IBM): http://open-services.net/wiki/automation/

[16:19] John Arwe (IBM): scenarios link above is from oslc automation 2.0; second link is working group's home page, which also has information about scope and has companion documents like best practices and primer that might help those new to automation 2.0

[16:20] John Arwe (IBM): Uri notes that scenarios are software-build oriented, whereas same basic process applies to other things like simulation, optimization, ....

[16:21] John Arwe (IBM): reading the oasis wiki scenario, C3 variant B refers to parallel builds... first I'm seeing that requirement emerging, on a top to bottom read. seems like a good one (non-obvious) if we are capturing reqts somewhere.

[16:22] John Arwe (IBM): back to Martin's scenario: automation 2.0 does not cover hand-offs across providers, e.g. (in this case) how to "map" the build artifacts (outputs) from one step to input parameters on a later step. discussion with Uri about SOA.

[16:23] John Arwe (IBM): Uri: SOA has been around a long time, has solutions for that problem.

[16:28] John Arwe (IBM): Uri: is it a goal of this spec that the inter-service bindings (mapping of parameters) could be automatically generated? Martin: not one has asked for that yet.

[16:31] John Arwe (IBM): ... Martin's scenario leaves that to the user to do.

[16:35] John Arwe (IBM): Uri: SOA may not be an issue here, you're trying to be more concrete here.

[16:36] John Arwe (IBM): Uri: should address lifecycle aspects beyond testing and software

[16:48] John Arwe (IBM): adjourned

Membership changes

At the end of this meeting:

• Members who lost voting rights:

  • Bill Chown (Mentor Graphics) group role has been changed to Member

  • Lin Ju (IBM) role has been changed to Member

  • Steve Speicher (IBM) group role has been changed to Member

• Members who gained voting rights:

  • None
• Leave of Absence
  • None
• Membership changes

  • Kyle Perkuhn (National Instruments) has left the TC

• TC summary
  • The TC has 4 voting members, 6 non-voting members, and 2 observers.

• The latest TC roster is at: https://www.oasis-open.org/apps/org/workgroup/oslc-automation/members/roster.php

Next meeting:

• Members who will lose voting rights if they do not attend:

  • Florian Georg (IBM)

• Members who will gain voting rights if they attend:

  • Lonnie VanZandt (Sodius SAS)

  • Uri Shani (IBM)

(See OASIS TC Process - Membership and participation - Voting member)