< Return to Calendar Next

* OASIS OSLC Automation TC meeting (Conference Call)
Name * OASIS OSLC Automation TC meeting (Conference Call)
Time Tuesday, 29 July 2014, 11:00am to 12:00pm EDT
(Tuesday, 29 July 2014, 03:00pm to 04:00pm UTC)
Description

These are the fortnightly meetings of the OASIS OSLC Automation TC. In these meetings we discuss the scenarios and use cases that we want the OSLC Automation specifications to support, discuss changes to those specifications to support those scenarios and use cases, and address any issues that implementors of the specification have raised.

It is scheduled for two hours, but we may not always use the second hour, depending on amount of business and members' availability.

Please submit any topics for discussion to the mailing list in advance of a meeting.

The dial-in information is here: https://www.oasis-open.org/apps/org/workgroup/oslc-automation/members/action_item.php?action_item_id=3694

Please join the chat room for the duration of the meeting: http://webconf.soaphub.org/conf/room/oslc-automation

Please RSVP so we know who is available for this meeting: https://www.oasis-open.org/apps/org/workgroup/oslc-automation/planned_attendance.php?event_id=37951

Minutes

Definitive copy of minutes is on the wiki: https://wiki.oasis-open.org/oslc-automation/Meetings/Telecon2014.07.29

Resolutions

None

 

Minutes

Chair

Martin Pain

Scribe

Martin Pain

Attendees

Bill Chown (Mentor Graphics), John Arwe (IBM), Martin Pain (IBM)

Regrets

Uri Shani (IBM), Florian Georg (IBM)

Original Chat transcript from room: oslc-automation

  • Meeting has not met quorum
  • Minute approval not raised, as quorum is not present
  • UseCasesAndRequirements/DeployingBuildArtifactsContinuousIntegration

    • Martin's intention: to create a worked example of how OSLC Automation 2.0 or 2.1 could be used in such a scenario, as: (1) implementation guidance, and (2) an example on which to base more advanced scenarios that might require additions to the 3.0 specification.
    • Bill said that, coming form the perspective of hardware development, the approach to this sort of use case would be different. Bill to write up a scenario of how this might be used in a hardware context, so this example/implementation guidance can show how such a generic client can support both software and hardware development uses. Target date: 3 weeks' time (19th August), in time to be discussed at the subsequent meeting 4 weeks from today (26th August).
  • Meeting adjourned.

 

Membership changes

At the end of this meeting:

Next meeting:

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

    • Umberto Caselli (IBM)

  • Members who will gain voting rights if they attend:

    • None

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



Agenda

We only have 3 RSVPs, but that should be enough for a quick discussion about direction & value in the scenario I shared recently.

Agenda is here: https://wiki.oasis-open.org/oslc-automation/Meetings/Telecon2014.07.29

  • Scenario:
    • Scenario walk-through slides: https://tools.oasis-open.org/version-control/browse/wsvn/oslc-automation/UseCasesAndRequirements/DeployingBuildArtifactsContinuousIntegration/Jenkins%20scenario%20walkthrough%20slides.pdf
    • Scenario wiki page: https://wiki.oasis-open.org/oslc-automation/UseCasesAndRequirements/DeployingBuildArtifactsContinuousIntegration


Submitter Mr. Martin Pain
GroupOASIS OSLC Lifecycle Integration for Automation (OSLC Automation) TC
Access This event is visible to OASIS OSLC Lifecycle Integration for Automation (OSLC Automation) TC and shared with
  • OASIS Open (General Membership)
  • General Public

Repeating Event Details
This event is one in a list of repeating events. All of these events are listed below.