OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

tcadmin-appeals message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Fwd: [OASIS-Appeal-001] Background and Facts for the Action Being Appealed




---------- Forwarded message ----------
From: Chet Ensign <chet.ensign@oasis-open.org>
Date: Tue, Jul 2, 2013 at 3:24 PM
Subject: The summary of facts: [OASIS-Appeal-001] Background and Facts for the Action Being Appealed
To: Laurent Liscia <laurent.liscia@oasis-open.org>


All, 

I am a day late in delivering the determination of validity and background and facts for this appeal. My apologies to you all for the delay. Given my schedule, I do not think I will have the final decision drafted by noon tomorrow so I will submit it to you all on Monday as we discussed in the call last Friday. 

This document determines the validity of the appeal and provides the facts that will be used in making a decision. 

1. Is the appeal valid? 

This appeal is valid. 

In order to be valid, an appeal must:

(a) be submitted by an Eligible Person; 

(b) be submitted to either the TC Administrator or to the OASIS Board of Directors; 

(c ) assert that an action taken or not taken either by a TC or by the TC Administrator violates the procedures set forth in the TC Process or in other OASIS policies specified by the OASIS Board of Directors; 

(d) be filed within 30 days of the action being appealed or at any time if the appeal is on an inaction; and

(e) state the nature of the objection(s), including any direct and material adverse effects upon the appellants; the section(s) of this TC Process or OASIS policies at issue; the actions or inactions at issue; and the specific remedial action(s) that would satisfy the appellants' concerns. 

The OASIS members presenting the appeal are Eligible Persons. Their appeal was submitted to the TC Administrator via the tc-administration@lists.oasis-open.org mailing list. The appeal asserts that the TC has changed its charter under section 2.11 of the TC Process (charter clarification) but should have addressed the change under section 2.12 (charter revision). The appeal was made within 30 days of the announcment of the clarified charter. The appeal requests that TC Administration invalidate the vote on charter clarification and require the TC to recharter. 

All the requirements listed above having been made, I find this appeal to be valid. 

2. Facts and Timeline 

This appeal concerns an action of the TOSCA TC [1], specifically its vote to clarify its charter. The appeal contends that the changes to the charter approved by the TC expand the charter's scope and thus must be handled via the rechartering process specified in section 2.12 of the TC Process [2]. (The specific points made in the appeal will be detailed in the final decision.) 

The timeline of key events is as follows: 

a) "Topology and Orchestration Specification for Cloud Applications Version 1.0" Committee Specification 01 was approved by the TC on 18 March 2013. A subsequent Committee Specification 02 was approved on 09 May 2013. 

b) At about the time of the approval of the Committee Specification, in preparation for the next round of work, the TC began discussions about changes to charter. At least one issue was opened in the TC's JIRA project to manage this: https://tools.oasis-open.org/issues/browse/TOSCA-81 

c) On Monday, 13 March 2013, Paul Lipton and I talked about the proposed changes to TOSCA charter and discussed whether the TC should recharter or could clarify its charter. On 14 March 2013, I sent Paul an email confirming our conversation and agreeing that the TC could vote to clarify. The email to Paul read as follows: 

----------------------
"Hi Paul, 

This email is simply to document our discussion about the TOSCA charter and specifically about item 1 in the Out of Scope section which reads: 

1. The definition of concrete cloud services, i.e. the definition of concrete component types, relationship types, and topology templates. However, standardization of a basic set of concrete component types, relationship types and properties is intended to be enabled by this work, and could begin in parallel with this project, with appropriate coordination

I fully agree with your interpretation that the word "However" beginning the second sentence clearly demonstrates the intention of the TC to retrain for itself the ability to develop a basic set of concrete types or proporties that would be useful for building concrete cloud services. While particular, vendor-specific concrete cloud services are deemed out of scope for the TC, these more generic definitions are clearly still in scope. 

The TC can choose to clarify this if it wishes by restating the same in the scope section or the deliverables or it can operate under the charter as it stands. That is your call. 

Let me know if I can help in any other ways with this discussion. "

----------------------

d) On 09 April 2013, a Special Majority Ballot was opened for the members of the TOSCA TC to vote on approving the clarification of the TOSCA charter [3]. The ballot closed on 16 April 2013. The ballot passed with 15 members voting in favor of the clarification and none voting in opposition. 

e) On 01 May 2013, I updated the TOSCA charter and announced the clarification to the membership of OASIS [4]. 

f) On 16 May 2013, after discussions on the procedure to follow for an appeal, Martin Chapman on behalf of himself and OASIS members Patrick Durusau and Jacques Durand submitted an appeal of the clarification to TC Administration [5]. 

g) On 24 May 2013 at 11:00 AM EDT, a conference call was held to attempt to resolve the issue without the need for a formal TC Administration ruling. Attending the call were Chet Ensign (OASIS), Martin Chapman, Patrick Durusau, and from the TOSCA TC Paul Lipton, Simon Moser, Doug Davis, Richard Probst, Thomas Spatzier, and Matthew Rutkowski. The appeal was reviewed and the basis for the TC's belief that they properly clarified their charter was presented. At the end of the call, Martin and Patrick stated that they continued to feel that clarification was not the appropriate choice and that they wished to continue with the appeal. 

h) I ended the call with a commitment to summarize the facts of the case by Wednesday, 29 May 2013 and present my decision by Monday, 03 June 2013 at the latest.  

This document fulfills the first half of my commitment. Please contact the list if you feel that are any elements of these facts that require restatement or that are not germane to the appeal or if you feel that any pertinent facts have been left out. 

--- 
[1] OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
https://www.oasis-open.org/committees/tosca/

[2] 2.12 TC Rechartering
https://www.oasis-open.org/policies-guidelines/tc-process#rechartering

[3] Special Majority Vote ballot
https://www.oasis-open.org/apps/org/workgroup/tosca/ballot.php?id=2390

[4] Email: "Clarification of TOSCA TC Charter"
https://lists.oasis-open.org/archives/tosca/201305/msg00002.html

[5] Email: "Appeal to the charter clarification recently made by the TOSCA TC"
https://lists.oasis-open.org/archives/tc-administration/201305/msg00000.html

--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open



--

/chet 
----------------
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society
http://www.oasis-open.org

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]