[Openid-specs-risc] Notes from today's call

[Atul Tulshibagwale]

Hi all,
Here are the notes from today's call. These are also available here
<https://bitbucket.org/openid/risc/wiki/SSE_WG-20220125>.

Thanks for your attendance and participation,
Atul

2022-01-25Attendees

   - Atul Tulshibagwale (SGNL)
   - Mike Kiser (SailPoint)
   - Shayne Miel (Cisco)
   - Tom Sato (VeriClouds)
   - Mike Lezcz (OpenID Foundation)
   - Rifaat Shekh Yusef (Okta)
   - Stefan Duernberger (Cisco)
   - Joshua Matz (Cisco)
   - Stan ()
   - Tim Cappalli (Microsoft)

Agenda

   - Intros and Reintros
   - Test/demo resources vs certification
   - Decision to begin OpenID Review of RISC spec
   - Github transition
   - Website content discussion

Notes

   - Can we begin the review process for the RISC draft? No objections
   heard on the call
   - Github transition:
   -
      - We are porting over the repository from Bitbucket to Github
   -
      - We tested this previously by importing the repository to Github.
   -
      - There are no open PRs and no active branches other than the main
      branch
   -
      - Will we be able to import the issues?
   -
      - A: In the test, Tim believes that the issues came over. If the
      issues do not transfer over, Tim will create them manually
   -
      - Tim will create the wiki manually and import the Google docs
   -
      - Voice vote by Shayne, Tom, Mike K., Rifaat and Atul
   -
      - No objections heard on the call.
   -
      - Tim to complete the transition by February 4th including the
      source, the open issues and the current wiki contents.
   -
      - Everyone to send Tim a message on the wg-sse Slack Channel in the
      OpenID workspace to be given access to the Github repository
   -
      - Tim to specify the process in the Github repo to request access
   -
      - Github repo to automatically send email to openid-specs-risc
      mailing list
   -
      - Mike L. to investigate if there can be a separate mailing list for
      sending Github notifications
   -
      - Shayne to help Tim to setup the notifications appropriately
   -
      - Markdown is a desirable source format for the specs, but the SSE
      and RISC specs are in XML. They may be converted to Markdown
manually after
      the transition is complete
   -
      - Once transition is complete, Atul repo link from the WG home page
      to point to Github
   -
      - We will figure out how to ensure that people accidentally landing
      at the BitBucket repo are directed to the Github repo
   -
      - Do we have the opportunity to rename the repo to "shared signals
      and events"? Tim: Yes, the new repo name will be sse
   - Website content
   -
      - FAPI Microsite background
   -
      - We can use the content organization from the FAPI microsite
   -
      - We may have to fit in the new content in the existing design and
      layout of the website
   -
      - Work in the SSE WG will help inform the rest of the WGs
   -
      - New design being proposed by the OIDF will have more features such
      as mobile friendly presentation (and better overall)
   -
      - Tom has not been able to post to the mailing list, but Mike L. has
      now fixed this
   -
      - Tom has proposed links to a variety of resources such as Cisco's
      "sharedsignals.guide", blog pages and pages within the OpenID
website that
      need to be included
   -
      - Atul to send a draft "story" by Friday of how to present the SSE WG
      (i.e. main content when someone lands at the WG home page)
   - Intros and Reintros
   -
      - Stefan Duernberger: Attending out of private interest
   - Outreach:
   -
      - Identity Week in summer in London. Tom is talking to them about SSE
   -
      - Tom reaching out to all identity related events
   - Test demo / certification
   -
      - Joseph Heenan and Mike L. have been working on 2022 certification
      program plans. SSE is on the short list
   -
      - When will the working group be ready to take on certification work?
      Earliest can be second half of Q2 or Q3 or Q4
   -
      - We need to start the conversation about the conformance test
   -
      - OIDF has created a budget for SSE to use for certification and
      interoperability
   -
      - We needed an online service which implementations can test against,
      some budget could be used for such a service
   -
      - Potential timeline: Q3 timeframe for defining the online service
      and start development
   - Question about Adoption:
   -
      - Is there some place we can learn about adoption
   -
      - Google RISC impl. Microsoft CAEP Events implmentation and Cisco SSE
      website / open-source samples
   -
      - Are there any open implementations? Cisco has published an open
      source version of the Transmitter spec (of SSE, not specific
events) here:
      https://github.com/duo-labs/sharedsignals
   -
      - SailPoint has an older version of the data model:
      https://github.com/sailpoint-oss/openid-sse-model
   -
      - Agenda for next call (2/1)
   -
      - Technical call
   -
      - (Tentative) Discuss Stream ID proposals for SSE
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-risc/attachments/20220125/3829f077/attachment-0001.html>