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
>
AutomationMeetings20120126
(27 Jan 2012,
MichaelFiedler
)
(raw view)
Time: *1:00PM Eastern US* (contact MichaelFiedler if you'd like to participate) The Automation meetings alternate times each meeting to accommodate the global team. ---++ Agenda * Reoccurring agenda items: * Recap of previous meeting AutomationMeetings20120119 * Main agenda items: * Draft Spec discussion: AutoSpecificationV1 * Continue discussion on parameters * Proposed approach using new resource definitions: [[AutoSpecificationV1#Resource_ParameterDefinition][Parameter Definitions]] and [[AutoSpecificationV1#Resource_ParameterInstance][Parameter Instances]] * General comments on the spec * Next meetings: * 2 February - do we have enough to talk about ---++ Minutes Attending: Michael Fiedler, Charles Rankin, Paul McMahan, Nathan Bak, Lucas Panjer, Pramod Chandoria, Daniel Berg, John Arwe, Eric Bordeau * Primary topic was new proposal for representing parameters as distinct resources * General agreement on the approach with some follow up actions needed: * TODO: Michael Fiedler to kick off investigation of using the instance resource shape to more strongly type the parameter definitions. This would support the scenario raised where an automation consumer would provide its own UI to create automation requests (no delegated UI) and would need the parameter type to display the appropriate type of field in a request creation UI. * TODO: Lucas Panjer will elaborate on the scenarios he is aware of in this area - such as the Mylyn/Hudson scenarios. Lucas will send them to the mailing list * Issue on the naming of the parameters in the result. Some feel =inputParameter= and =outputParameter= are potentially misleading. * Confusing to consumers which parameters it should look at in the result * Intent is that "input" = used to create the request and copied from the request. "output" = modified or added during execution * suggestion: rename to =initialParameter= and =additionalParameter= * Other aspects of the parameter definitions and instances as documented in AutoSpecificationV1 seemed acceptable * Discussion around =automationInstructions= in the Automation Plan * Intent is to provide a place for a plan to expose information on how the automation will take place. Could be binaries, human readable instructions etc. * Is this needed to satisfy the scenarios? Possibly for the test automation scenarios. * TODO: Paul McMahan, Pramod Chandoria and possibly Charles Rankin will investigate/discuss. * Next meeting: 2 February at 10AM Eastern US time
E
dit
|
A
ttach
|
P
rint version
|
H
istory
: r2
<
r1
|
B
acklinks
|
V
iew topic
|
Ra
w
edit
|
M
ore topic actions
Topic revision: r2 - 27 Jan 2012 - 20:04:44 -
MichaelFiedler
Main
Main Web
Create New Topic
Index
Search
Changes
Notifications
RSS Feed
Statistics
Preferences
Webs
Main
Sandbox
TWiki
Български
Cesky
Dansk
Deutsch
English
Español
Français
Italiano
日本語
Nederlands
Polski
Português
Русский
Svenska
简体中文
簡體中文
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