Intro:
Scribe appointment: call for volunteers starting from top of the list [1]
Roll Call
Agenda approval
Minutes:
6th November 2013: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00041.html
- correction needed the minutes approved were for the 30th october 2013.
Notes from Scrum sessions: Session 1: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00051.html
Session 2: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00078.html
Session 3: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00094.html
Action Items:
Administrivia:
Status:
Timeline: https://www.oasis-open.org/apps/org/workgroup/camp/download.php/51056/CAMP%20sched%202013-10-16.pdf
Current open issues: 34 in total; 2 P1, 24 P2, 8 P3.
Status after scrum sessions: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00097.html
Editing Team Update:
WD29: https://www.oasis-open.org/apps/org/workgroup/camp/document.php?document_id=51313
New Issues:
Issue Discussion:
Pre scrum proposal:
https://tools.oasis-open.org/issues/browse/CAMP-72 Error Response Message Resource looks like relic of a bygone age
Proposal in JIRA
Scrum proposals:
Issues with proposal to change the spec:
P1: https://tools.oasis-open.org/issues/browse/CAMP-86 Nature of YAML makes its suitability as a normative reference problematic [trivial/editorial]
https://tools.oasis-open.org/issues/browse/CAMP-80 Section 6.11 "Registering an Application" is unclear about what Content-Type header must be for various scenarios
P2: https://tools.oasis-open.org/issues/browse/CAMP-144 no way to correlate a resource's "type" value with the array of type definitions contained in the TypeDefinitions resource
https://tools.oasis-open.org/issues/browse/CAMP-118 4.3.2.4 services - "application in"? [trivial/editorial]
https://tools.oasis-open.org/issues/browse/CAMP-117 4.3.3 Artifact Specification
https://tools.oasis-open.org/issues/browse/CAMP-116 4.3 Deployment Plan Schema - well-formed/conforms to description [trivial]
https://tools.oasis-open.org/issues/browse/CAMP-113 4.3.2.1 campVersion - SHALL?
https://tools.oasis-open.org/issues/browse/CAMP-109 4.3.1 General Attributes [trivial/editorial]
https://tools.oasis-open.org/issues/browse/CAMP-105 4.2 Deployment Plan Overview - RPM file? [trivial/editorial]
Issues with proposals to close no action:
P2: https://tools.oasis-open.org/issues/browse/CAMP-147 Psuedo schema in section 1.7 is not sufficient
https://tools.oasis-open.org/issues/browse/CAMP-143 Section 2.1.6 is a mess
https://tools.oasis-open.org/issues/browse/CAMP-114 4.3.2.2 origin
https://tools.oasis-open.org/issues/browse/CAMP-88 1.5 PaaS Roles
https://tools.oasis-open.org/issues/browse/CAMP-84 Text highlighting, Section 2.1.6 and following (camp-spec-v1.1-csprd01)
https://tools.oasis-open.org/issues/browse/CAMP-79 Will OASIS manage/approve common artifact types in the future?
https://tools.oasis-open.org/issues/browse/CAMP-42 Spec should say how to limit/specify the scope of returned data
https://tools.oasis-open.org/issues/browse/CAMP-11 Expression of Scaling Policy
P3: https://tools.oasis-open.org/issues/browse/CAMP-69 Need interoperable means to obtain the endpoint(s) of an Application Component
https://tools.oasis-open.org/issues/browse/CAMP-59 Inconsistent definition of link attributes to point at templates used to instantiate resource types
https://tools.oasis-open.org/issues/browse/CAMP-27 Should CAMP surface the names of the application states?
Issues awaiting proposals:
P2: https://tools.oasis-open.org/issues/browse/CAMP-148 Section 3 is redundant, and https://tools.oasis-open.org/issues/browse/CAMP-98 3 Application Management Lifecycle
(148 and 98 to be treated as one issue.
https://tools.oasis-open.org/issues/browse/CAMP-146 campVersion limits future compability
https://tools.oasis-open.org/issues/browse/CAMP-110 Values for "attributeType" are not clearly defined.
https://tools.oasis-open.org/issues/browse/CAMP-102 4.1.2 Validating Integrity
https://tools.oasis-open.org/issues/browse/CAMP-74 Plans resource does not have Parameters (direction proposed in scrum session)
https://tools.oasis-open.org/issues/browse/CAMP-66 Creating instance of a Platform Component (two choices outlined in scrum session)
https://tools.oasis-open.org/issues/browse/CAMP-62 JSON arrays of Links are more constrained than the underlying implementation (direction proposed in scrum)
P3: https://tools.oasis-open.org/issues/browse/CAMP-128 C.1 Mandatory Statements (conflicting proposals)
https://tools.oasis-open.org/issues/browse/CAMP-73 Make the style of figures consistent [trivial/editorial]
https://tools.oasis-open.org/issues/browse/CAMP-63 TypeDefinitions for CAMP-defined types (proposal needs updating)
https://tools.oasis-open.org/issues/browse/CAMP-44 Clarify resource type issues and API
https://tools.oasis-open.org/issues/browse/CAMP-26 Need to define a core set of Platform Component types
AOB:
Straggler roll
-------
[1] Scribe rotations:
Yendluri, Prasad (2)
Johnston-Watt, Duncan (3)
Carlson, Mark (4)
Heneveld, Alex (4)
Byreddy, Bhaskar Reddy (3)
Rutt, Tom (4)
Pilz, Gilbert (10)
Behrens, Michael (2)
Otto, Adrian (7)
Durand, Jacques (7)
Karmarkar, Anish (6)
Agrawal, Roshan (2)
Raman, Krishna (4)
Malhotra, Ashok (4)
|