BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VEVENT
DTSTART:20180620T150000Z
DTEND:20180620T160000Z
DTSTAMP:20180615T135153Z
ORGANIZER;CN=cbrookes@redhat.com:mailto:cbrookes@redhat.com
UID:1ee38ouatcmmthj782ea5n5chg@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=cbrookes@redhat.com;X-NUM-GUESTS=0:mailto:cbrookes@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=pgough@redhat.com;X-NUM-GUESTS=0:mailto:pgough@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=davmarti@redhat.com;X-NUM-GUESTS=0:mailto:davmarti@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=pbrookes@redhat.com;X-NUM-GUESTS=0:mailto:pbrookes@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=ansible-service-broker@redhat.com;X-NUM-GUESTS=0:mailto:ansible-ser
 vice-broker@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=jesusr@redhat.com;X-NUM-GUESTS=0:mailto:jesusr@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=ernelson@redhat.com;X-NUM-GUESTS=0:mailto:ernelson@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=shurley@redhat.com;X-NUM-GUESTS=0:mailto:shurley@redhat.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=rhallise@redhat.com;X-NUM-GUESTS=0:mailto:rhallise@redhat.com
CREATED:20180612T151259Z
DESCRIPTION:\nhttps://bluejeans.com/2730432953/\n\nAfter the community meet
 ing. Setting this up for those interested in learning more and understandin
 g the issues.\n\nWould like to outline what we are looking into\n\n\nDiscus
 s whether the automation broker is the right place for the work and also go
  through some of the ideas around implementation. \n\n\nDiscuss option of s
 hared service broker\n\nGet general feedback\n\n\nIssues covering this work
 :\nhttps://github.com/openshift/ansible-service-broker/issues/979\nhttps://
 github.com/openshift/ansible-service-broker/issues/982\n\nGeneral user stor
 y\nAs an operator of a managed service\, I want to be able to provision a s
 ervice in a restricted namespace but allow any user in my cluster to provis
 ion a slice of that service without needing to know the specific location o
 r credentials of the service.\n\nRoles user story\nAs an operator of a mana
 ged service\, I would like the option to restrict which users can request a
  slice of this service based on the roles the user has.\n\n-::~:~::~:~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\nPl
 ease do not edit this section of the description.\n\nView your event at htt
 ps://www.google.com/calendar/event?action=VIEW&eid=MWVlMzhvdWF0Y21tdGhqNzgy
 ZWE1bjVjaGcgYW5zaWJsZS1zZXJ2aWNlLWJyb2tlckByZWRoYXQuY29t&tok=MTkjY2Jyb29rZX
 NAcmVkaGF0LmNvbThmNDhjMzgzZGNlZjdmOWEyNjY1Y2MyZDA5MGRmNjc2NjQyNzM2NzY&ctz=E
 urope%2FDublin&hl=en&es=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20180615T135152Z
LOCATION:
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:managed shared services and the broker
TRANSP:OPAQUE
END:VEVENT
END:VCALENDAR