Versions Compared

Key

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

...

Excerpt
<To be completed after the meeting.>

Remember:

Attendees:

  • Richard Esplin
  • Stephen CurranTo be completed.

Release Status:

  • May: Indy SDK 1.9.0
  • June: Indy SDK 1.9.1
    • Bugfixes
    • GitLab migration to replace Jenkins (Foundation)
    • Cached credentials / offline proofs (Evernym)
    • Flexible Credential Attribute Tagging (BC.gov)

...

  • Language specific libraries:
    • List
      • indy-sdk-python: Sam Curren (telegramsam)
      • indy-sdk-ruby: John Callahan (johncallahan)
      • indy-sdk-go: Arjen Arjan Van Eersel (arjanvaneersel)
      • indy-sdk-ios: Norm (nsivraj) is willing, but someone else will understand IOS development better (especially with Swift).
      • indy-sdk-java: Thomas Shelton (twshelton)
      • indy-sdk-android: Mike Lodder (mikelodder7) is willing, but someone else with more interest could take it over
      • indy-sdk-dotnet: Tomislav Markovski (tmarkovski)
      • indy-sdk-javascript: Joe Genereux (thedolie)
    • Nathan says that the repos are in progress.
    • Should they be aries repos?
    • Should each one have a channel on chat.hyperledger.org?
  • GitLab migration
    • Will migrate indy-sdk after migrating LibSovToken.
    • 1) publish the proposal to community, discuss it
      2) implement CI and run it in parallel with current version as optional
      3) implement CD and target file publishing to the temporary location
      4) swap GL CI and Jenkins: make GL required, Jenkins optional
      5) disable Jenkins CD, target GL to actual artifacts location
      6) disable Jenkins CI

  • SDK 2.0 architecture (Sergey)
  • HIPEs (Sergey)
    • Credentials Exchange HIPE
    • Payment decorator
  • Warnings from rust cargo clippy (Mike)
    • Initial evaluation completed
    • Started fixing common errors
      • Using types instead of passing lots of parameters
    • Some of the suggestions break compilation
  • New design for revocation: (Mike)
    • Working on the paper
    • Actively building prototypes
    • Ledger changes will be required, so it will take months to have a usable implementation on the Sovrin network

...