http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2015-07-23 <http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2015-07-23> Minutes Roll call Quorum was reached. Minutes approval MOTION: Approve the minutes of UMA telecon 2015-06-25 <http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2015-06-25> and read into today's minutes the notes of UMA telecon 2015-07-01 <http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2015-07-01>, UMA telecon 2015-07-09 <http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2015-07-09>, and UMA telecon 2015-07-16 <http://kantarainitiative.org/confluence/display/uma/UMA+telecon+2015-07-16>. APPROVED by unanimous consent. Macro, micro, and current-plan process We love the idea of treating the future UMA specification process agilely and as if it were software, and using GitHub for managing the process. Mike points out that Kantara already has a GitHub organization <https://github.com/KantaraInitiative>; let's use it. He's been using it for OTTO. Let's figure out the right process and ownership – and document it for use by other groups, Eve suggests. We need to do a final historical checkin on the xmlgrrl repo, and then move on with a native process. Sprint themes and priorities We're good with them. Logistics We plan to nominate issues to pull forward from the backlog on the next call. We will plan for 90-minute calls in August, starting 30 minutes earlier than the "normal" start time, with the "normal" hour being consider the "core" time to meet (recognizing that not everyone can change their schedules very dynamically). Eve will do a cleaning of the voting participation rolls and expects everyone to do their level best to attend in August (and beyond!). Plans for Independent Submission to IETF Should we now wait until V1.0.1 is at the Recommendation stage? Let's, in fact, have the conversation about the the added value of publishing the specs as IETF documents, with Nat and others. Justin recommends recalculating the cons vs. the pros of publishing through IETF, given that the documents may change and there are significant costs. AI status AI: Thomas: Review the charter for potential revisions in this annual cycle. AI: Eve: Review Marcelo Wikipedia comments and take next actions. AI: Sal: Investigate IP implications of formal liaison activities with other Kantara groups with the LC, and ultimately draft an LC Note as warranted. AI: Gil: Edit the UIG to add Ishan's content and excerpt it for Eve to add to the FAQ, pointing everyone to the UIG. AI: Sal: Fill out IDESG form to have UMA adopted as a recommended standard for use in the IDESG framework. AI: Mike: Write SCIM protection case study to highlight client claims-based use case. AI: Eve: Update GitHub. AI: Maciej: Write as many sections for the UIG as he can. AI: Justin: Write a UIG section on default-deny and race conditions. Attendees As of 1 Jul 2015 (pre-meeting), quorum is 7 of 13. (François, Domenico, Sal, Mark, Thomas, Andi, Ishan, Robert, Maciej, Eve, Arlene, Mike, Jin) Eve Arlene Robert Maciej Domenico Mike Sal Non-voting participants: Justin Sarah Scott Adrian Zhanna Regrets: Thomas Andi Eve Maler | cell +1 425.345.6756 | Skype: xmlgrrl | Twitter: @xmlgrrl | Calendar: xmlgrrl@gmail.com