Versions Compared

Version Old Version 1 New Version Current
Changes made by

Stephen Curran

Sean Bohan

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

...

...

...

...

...

...

...

...

Summary:

Excerpt

Topics:

  • Release Planning:
    • 0.12.1
    • PR Merges for pending 1.0.0
  • Open Discussion

...


Video:
Widget Connector
urlhttp://

...

youtube.

...

com/

...

watch?

...

v=

...

W_CCERuiw3g

Call Time: 8:00 Pacific / 17:00 Central Europe

Recordings From the Call:  


Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Welcome, Introductions and Announcements

  • IIW coming up this week, April 16-18.
    • Thread in Hyperledger Discord on IIW.
  • Identity Working Group – this Thursday Jorge Flores on ecosystem building

Attendees

Documentation:

Agenda

  • Status Updates:AnonCreds RS in of ACA-Py PRs for AnonCreds+CredX concurrently – after the 0.12.0 release
  • Upgrade script – complete.
  • did:peer and AFJ Interop
    • Connection reuse for did:peer:2/4
    • Status of ACA-Py 1
    • Tag on main or on the 0.12.0
    • Additional PRs to go into the release? Yes – list: 
    • Another update – missing verification method in VC-DI.
    • Additional concepts? No
  • Status of ACA-Py 1.0.0 Release:
    • Checklist Issue, labelled Issues and PRs
      • Other issues/PRs to be added?
      • PR 2860 - handling authorization to update base/tenant wallet.
    • Should we wait on the AnonCreds RS work?
    • LTS Considerations per Aries RFC 0799 Long Term Support
    • Other considerations?
  • Logging for Tenants - Akiff Manji is working on this.
    • Trying to refactor it a bit – goal is to make it multi-tenant
    • Any ideas on thoughts on making it easier/cleaner?
    • First time – change every instance of logger being used – painful change.
      • Should be able to configure it without changing every instance.
      • Use the logging interface and inject something about the tenant.
    • Should the multi-tenant be separated from the single-tenant logging?
  • Should we switch to "mutli-tenancy" always – where the current non-multi-tenant is simply multi-tenant with just one tenant.
    • Reduce complexity, reduce branches in code.
    • Once Indy SDK support is dropped, it will be easier since Askar is inherently like that.
    • Interesting differences in approaches, both of which are viable:
      • Traction – independent controllers one per traction tenant.
      • Single controller – that manages each of the tenants.
  • DISCUSS: When to officially drop support for the Indy SDK?
  • How to transition to did:indy?
  • Vulnerability in an OpenSSH dependency library disclosed last Friday
    • Long time GitHub contributor tried to push a remote execution – in xz-utils - bleeding edge version, but caught before it got to the major distributions.
    • Reminder to stay on the lookout for dependencies and vulnerabilities

Upcoming Meeting Topics:

...

    • branch?
      • Let's tag off main
    • What PRs to include?
      • Merged since 0.12.0
      • 3 code PRs and a dependabot PR already merged.
      • Fix for the issue reported by Sheldon today
  • Timing of existing PRs – ready to go?
    • Ready for a 1.0.0rcX?
    • Include the tenant authorization changes?
    • Include logging changes?
    • Wait for the drop Indy SDK to be ready to merge?

Upcoming Meeting Topics:

Future Topics

  • Formal test plan
    • We go through a process of release candidates but we often still end up discovering bugs after releases are out
    • Daniel to create an issue to start a discussion

Action items