New subject: Agenda for UMA telecon 2017-03-09 (attendance is important -- thank you)

8 Mar 2017


      http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2017-03-09
Date and Time

   - *Thursdays,* final *special meeting time: 8:30-10am PT*
      - Screenshare *AND* dial-in: http://join.me/findthomas
      - UMA calendar:
      http://kantarainitiative.org/confluence/display/uma/Calendar

Agenda

   -

   Roll call
   -

   Approve minutes of UMA telecon 2017-03-02
   <http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2017-03-02>

   - Logistics:
      - This is our *last 90-minute meeting*
      - We plan to vote on our specs as WG drafts (simple majority
      required) and let them percolate for four weeks as "last call"
drafts while
      we invite people to join the group to finalize them with us and implement
      them
   -

   UMA V2.0 work:
   - 2016 roadmap
      <http://kantarainitiative.org/confluence/display/uma/UMA+Roadmap+for+2016>
       / GitHub issues for V2.0
      <https://github.com/KantaraInitiative/wg-uma/issues?q=is%3Aopen+is%3Aissue+label%3AV2.0>
(all
      issues to be kept here for the duration!) / dynamic swimlane
      <http://www.websequencediagrams.com/files/render?link=Pu0sP0Oe2kjKc2WgdKZd>
      - Core is up to 18
      <https://docs.kantarainitiative.org/uma/ed/uma-core-2.0-18.html>
(updated)
      and RReg is up to 06
      <http://docs.kantarainitiative.org/uma/ed/oauth-resource-reg-2.0-06.html>
(updated) –
      hope to do an big editorial pass for a Core 19 and RReg 07 before the call
      - #288 <https://github.com/KantaraInitiative/wg-uma/issues/288> is
      open and worth discussing (OpenAPI)
      - #252 <https://github.com/KantaraInitiative/wg-uma/issues/252> is
      open and worth discussing briefly regarding how to handle editorially and
      succession-wise (pointing to the V1 security extension spec – ticket
      rotation)
      - #270 <https://github.com/KantaraInitiative/wg-uma/issues/270> (URIs
      as arrays/wildcards) is open but hasn't gotten a lot of support – needs
      some really good explanation or it will die
      - Shall we simply close #277
      <https://github.com/KantaraInitiative/wg-uma/issues/277>? (not doing
      CRUD rreg in bulk)
      - I proposed in email
      <https://groups.google.com/forum/#!searchin/kantara-initiative-uma-wg/$2331%7Csort:relevance/kantara-initiative-uma-wg/ujy9jBRpZ6w/T2_K4ef1AgAJ>
that
      we close #31 <https://github.com/KantaraInitiative/wg-uma/issues/31> with
      no action – it sort of wants an “extension” tag, but really it
is just open
      for anyone to make extensions if they need them
      -

      #273 <https://github.com/KantaraInitiative/wg-uma/issues/273> is open
      (did the shallow s/user/resource owner/ fix)
      - Other issues are tagged with "process" or "ediorial" and can or
      must be done later
   - WG draft vote if we're ready
   - Discuss review period logistics
   - AOB


*Eve Maler*Cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl

Agenda for UMA telecon 2017-03-09 (attendance is important -- thank you)

Eve Maler

Eve Maler

tags

participants (1)