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


Help: OASIS Mailing Lists Help | MarkMail Help

camp message

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

Subject: Draft Minutes 27th November 2013

Minutes 27th November 2013

Meeting Attendees:   

Software AG, Inc.			Bhaskar Reddy Byreddy	Voting Member
Oracle				Martin Chapman	Chair
Fujitsu Limited			Jacques Durand	Voting Member
Cloudsoft Corporation Limited	Alex Heneveld	Voting Member
Oracle				Anish Karmarkar	Voting Member
Rackspace Hosting, Inc.		Adrian Otto	Secretary
Red Hat				Krishna Raman	Member
Fujitsu Limited			Tom Rutt	Voting Member

Meeting Statistics
Quorum rule	51% of voting members
Achieved quorum	yes
Individual Attendance	Contributing Members: 8 of 38 (21%) 
Voting Members: 7 of 12 (58%) (used for quorum calculation) 


      Bhaskar Reddy assumes scribe duties

      Roll call: Attendees listed above
      7/12 voting members present; 58% attendance
      Quorum obtained

       V2 posted incl new issue 152
       No objection on Agenda; Agenda approved

    20th November 2013: https://www.oasis-open.org/apps/org/workgroup/camp/email/archives/201311/msg00144.html 
      Motion: m: Anish, s: Jacques to approve 20th Nov minutes
      no objections; 20th Nov minutes approved

Editors update:

       WD31: https://www.oasis-open.org/apps/org/workgroup/camp/document.php?document_id=51495 
      TA:  Jacques: Due to refactoring and renaming of the tags, some normative tags have been deleted; will take roughly till second half of Dec

New Issues: 

      https://tools.oasis-open.org/issues/browse/CAMP-151  Style Change to encourage adoption

      This issue is for adopting the resource naming changes
      Motion: m: Adrian, s: Anish to open CAMP-151
      Alex Heneveld: should be across the board -- type names etc
      MartinC: all upper case charaters? i,e. does everything become lowercase with a _ if necessary
      anish: s/Editorial adjustment of all resource names, attribute names to change from camelCase to lowercase_with_underscore style./Editorial adjustment of all resource names, attribute names, and attribute values to change from camelCase to lowercase_with_underscore style. /
      no objections; CAMP-151 open as p2

      CAMP-151 has been updated with the changes proposed by Anish
      Motion: m: Adrian, s: Alex to accept the proposal in CAMP-151 and mark it resolved
      no objections; CAMP-151 is resolved


      Martin: can issue#4 of CAMP-151 be resolved as part of CAMP-102?

      Motion: m: Jacques, s:Anish to open CAMP-152
      no objections; CAMP-152 opened
      CAMP-152 opened as p2

Issue Discussion:

      https://tools.oasis-open.org/issues/browse/CAMP-44  Clarify resource type issues and API

      Anish: has a directional proposal as part of a comment
      Alex Heneveld: @Anish - been reading #44 - almost right
      Alex Heneveld: 4) If a resource type inherits from two types T1 and T2 and both T1 and T2 have an attribute A, then the metadata for both T1.A and T2.A SHALL point to the same or compatible attribute definitions.
      Anish to refine directional proposal and solicit comments from Alec McDonald

      https://tools.oasis-open.org/issues/browse/CAMP-26  Need to define a core set of Platform Component types
      anish: open an issue for delivering a primer
      anish: include in there wish list: scaling policy, component examples
      Motion: m: Anish, s:Alex to close CAMP-26
      no objections; CAMP-26 closed

      https://tools.oasis-open.org/issues/browse/CAMP-66  Creating instance of a Platform Component

      overtaken by events
      Motion: m: Alex, s:Tom to close CAMP-66 with no action
      no objections; CAMP-66 closed

      https://tools.oasis-open.org/issues/browse/CAMP-146 campVersion limits future compability

      Alex: One should be able to mention the compatible version numbers in the plan
      Tom Rutt (Fujitsu): the provider of 3.0 can also support 1.1.  Why is this not just a server imnplementation issue?
      MartinC: what does it mean to support 1.1 - its means its a 1.1 server doesnt it?
      Anish: even with single version number specified in the plan, Provider can decide based on contents of the plan whether it processes it or not
      Martin: concrete proposal needed if we are not closing this issue with no action


      Happy Thanksgiving to US folks...
      stagger roll: none
Meeting adjourned

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