Page Comparison

Summary

Zoom: https://zoom.us/j/93198495358?pwd=TS80VklHVElJS3lEcjUzQjV0VHVtUT09

Recording

...

:

Widget Connector
url http://youtube.com/watch?v=As_ONGxLp3c

Welcome and Introductions

...

• Coordinating Ubuntu-22.04 release
  • https://github.com/hyperledger/indy-node/pull/1870
  • Kim did Indy Plenum updates, Wade fixed the pipelines, next step was Indy Node release
  • Kim integrated the updated release for plenum + other pipeline changes
  • Next step is to fix the pipelines again
    • Do a pass, get it up and running
    • Determine next steps from there
  • Indy test automation is integrated into the pipeline
    • To Do: Update containers that the tests are being run on
    • Currently uses whatever package the Indy build uses
  • Create tickets for work items
  • Fix issues on the ubuntu-22.04 branch, then merge to main
  • Tools for coordination/regular updates
    • Tatsu: based on Slack https://tatsu.io/
    • Stephen will invite folks to Tatsu
  • To Do: define initial tasks on Jan 14th call, then assign
    • First thing: Enable the 22.04 branch in the workflows (only enabled on main currently)
    • Change FROM line on Dockerfiles to ubuntu-22.04 (including indy automation, needs a ubuntu-22.04 branch too)
  • Wade Barnes will write issues
• Updates
  
  • Indy Besu updates and discussionTrust DID Web
    • Deploy with Kubernetes and AWS
    • Finish before the end of the year
    • Try Indy Besu not only locally, but deployed
      • Test migration from existing indy network to Besu
  • DID Web VH
    • 0.5 almost ready
      • Updates on pre-rotation and witnesses
      • Will evolve into 1.0
    • Name change 
    • Resolver into Credo
    • Resolver and registrar into ACA-Py
    • Deployed did:webvh server, hosting dids there (still tdw or web)
    • Talking to Bluesky
    • Most controversial: portability
      • Not helpful for Bluesky
• Open Discussion

Next Meeting

...