BEGIN:VCALENDAR
X-LOTUS-CHARSET:UTF-8
VERSION:2.0
PRODID:-//Lotus Development Corporation//NONSGML Notes 8.5.3//EN_S
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:19501105T020000
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:19500312T020000
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID="America/Los_Angeles":20120522T060000
DTEND;TZID="America/Los_Angeles":20120522T070000
TRANSP:OPAQUE
DTSTAMP:20120516T200856Z
SEQUENCE:0
ATTENDEE;ROLE=CHAIR;PARTSTAT=ACCEPTED;CN="Nick Crossley/Irvine/IBM"
 ;RSVP=FALSE:mailto:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE
 :mailto:[email protected]
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION
 ;CN="Sampath Sriramadhesikan/Bedford/IBM";RSVP=TRUE
 :mailto:[email protected]
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION
 ;CN="Darcy Wiborg Weber/Irvine/IBM";RSVP=TRUE
 :mailto:[email protected]
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION
 ;CN="Gray Bachelor/UK/IBM";RSVP=TRUE:mailto:[email protected]
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION
 ;CN="John Arwe/Poughkeepsie/IBM";RSVP=TRUE
 :mailto:[email protected]
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION
 ;CN="John Kellerman/Raleigh/IBM";RSVP=TRUE
 :mailto:[email protected]
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION
 ;CN="Kartik Kanakasabesan/Durham/IBM";RSVP=TRUE
 :mailto:[email protected]
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE
 :mailto:[email protected]
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE
 :mailto:[email protected]
CLASS:PUBLIC
DESCRIPTION;ALTREP="CID:<[email protected]>":I
 t has been a long time since our last workgroup meeting\, and while th
 e spec has still not been finalized\, there have been several developm
 ents in the configuration management space and some new requirements f
 rom other OSLC domain including the PLM-ALM workgroup.\n\n\nI would li
 ke to explain to the workgroup why the spec has not progressed to fina
 lization\, some of the reasons for the lack of adoption\, and how we m
 ight address those issues by broadening the potential audience while a
 t the same time lowering the cost of adoption by simplifying the spec.
   After this initial discussion\, it is my hope that we will commence 
 a new stage in the life of the workgroup\, resuming regular meetings a
 s we work on a revised spec.  For this reason\, please also consider 
 what times would work for you in the future.\n\n\nIf you are unable to
  attend but you are still interested in the future of OSLC SCM\, pleas
 e nominate a substitute.\n
SUMMARY:OSLC SCM WG Meeting
LOCATION:Conf call:  US 888-426-6840\, 215-861-6239\, Tie line
 :  650-6840\; Passcode: 73872710\n
ORGANIZER;CN="Nick Crossley/Irvine/IBM":mailto:[email protected]
UID:C1950BBA0425B115882579FB004EC14D-Lotus_Notes_Generated
X-LOTUS-BROADCAST:FALSE
X-LOTUS-UPDATE-SEQ:1
X-LOTUS-UPDATE-WISL:$S:1;$L:1;$B:1;$R:1;$E:1;$W:1;$O:1;$M:1
X-LOTUS-NOTESVERSION:2
X-LOTUS-NOTICETYPE:I
X-LOTUS-APPTTYPE:3
X-LOTUS-CHILD-UID:C1950BBA0425B115882579FB004EC14D
END:VEVENT
END:VCALENDAR
It has been a long time since our last workgroup meeting, and while the spec has still not been finalized, there have been several developments in the configuration management space and some new requirements from other OSLC domain including the PLM-ALM workgroup.


I would like to explain to the workgroup why the spec has not progressed to finalization, some of the reasons for the lack of adoption, and how we might address those issues by broadening the potential audience while at the same time lowering the cost of adoption by simplifying the spec. After this initial discussion, it is my hope that we will commence a new stage in the life of the workgroup, resuming regular meetings as we work on a revised spec.  For this reason, please also consider what times would work for you in the future.


If you are unable to attend but you are still interested in the future of OSLC SCM, please nominate a substitute.

Attachment: c140859.ics
Description: Binary data



Reply via email to