This wiki is locked. Future workgroup activity and specification development must take place at our new wiki. For more information, see this blog post about the new governance model and this post about changes to the website.
TWiki> Main Web>AutomationHome>AutomationMeetings>AutomationMeetings20120322 (02 Apr 2012, MichaelFiedler)
Time: 10:00AM Eastern US (Daylight Savings) (contact MichaelFiedler if you'd like to participate)

The Automation meetings alternate times each meeting to accommodate the global team.

Agenda

* Reoccurring agenda items:

* Main agenda items:
  • Specification version number change
    • Changed to 2.0/V2
    • Please report broken links
  • Draft Spec discussion: AutoSpecificationV2
    • State and verdict properties
    • Minimum attributes required for a name/value parameter definition in an Automation Plan under the current proposals of using oslc.propery
    • Spec completeness issues/Readiness for reviews
    • Implementation plans
  • Next meeting:
    • 5 April, 10AM Eastern US

Minutes

Attending: Michael Fiedler, David Liu, Charles Rankin, Robert Elves, Paul McMahan? , Dan Berg, Pramod Chandoria, Jing Qian

* State and verdict properties

  • General agreement that this approach is useful.
  • Desire for stronger statement. MUST use verdict from Automation Spec, MUST use at least 1 state from Automation and MAY use others. Update issue to reflect this.
* Minimum attributes
  • Group felt this minimal representation of a parameter was reasonable
  • No concerns voiced that it would place an undue burden on implementations
* Desire to have a detailed discussion on implementation plans. Queueing this up for next meeting.
Edit | Attach | Print version | History: r4 < r3 < r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r4 - 02 Apr 2012 - 20:32:15 - MichaelFiedler
 
This site is powered by the TWiki collaboration platform Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use
Ideas, requests, problems regarding this site? Send feedback