Page Comparison

Summary

...

Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

...

• Name (organization) <email>
• Richard Esplin (Evernym) <richard.esplin@evernym.com>
• Alan Krassowski (Kiva) <alank@kiva.org>
• Cam Parra (Kiva) <camilop@kiva.org>

Announcements

• Community project: Aries RFCs - process to move HIPES; RFCs that have been moved concepts / features / pull requests.
• Aries Workshop/Connectathon December 3-5 in Provo, Utah (details to follow)
• Internet Identity Workshop — want to coordinate demos
• Hyperledger Maintainers Summit: Minneapolis October 8-10
• Bootcamp Russia: Event Location

...

• Documentation improvements: Michael B and Stephen C
  • Need to review and prune out-of-date documentation (Alice / Faber treatment of pairwise DIDs is a key pain point)
  • Michael is working on Indy Agent walkthrough using C#
  • Finishing work on ReadTheDocs (2 more weeks?)
  • Cloud Compass is building the Linux Foundation EdX courses for Indy and Aries
• SDK 2.0 architecture / Indy-Aries split (Sergey)
  • Anxious to start moving, and iterating.
  • Kiva is working on a Futures implementation of threading (instead of call-backs) (https://github.com/kiva/aries-sdk.git)
• CI / CD: GitLab migration (Mike and Steve G)
  • Demos in the Identity Implementers WG calls
  • Issues with Jenkins machines because Rust builds run out of memory—workaround increased build time but is a temporary solutionHyperledger is also evaluating Azure Pipelines
• Advanced Schemas and W3C creds (Ken)
  • Can successfully write and retrieve the Context object from the node code. Will track through all layers up to Aries.
    • https://github.com/ken-ebert/indy-node/commits/master
  • 5 additional objects need to be added.
  • Working on the HIPE for the new Schema object.
• Warnings from rust cargo clippy (Mike and Axel)
  • IS-1270 through IS-1274
• New design for revocation / Anoncreds 2.0 (Mike)
  • Would be useful to have a comparison in performance between Anoncreds 1.0 and Anoncreds 2.0
  • First draft is latex document in Ursa repo. Will be published as PDF and HTML.
    • https://github.com/hyperledger/ursa-docs/tree/master/specs/anoncreds2
  • Need a plan for changes to Indy Node
    • HIPE for overall changes, then a design PR for the changes specific to the different repos.
      https://github.com/hyperledger/indy-node/tree/master/design
• Getting Ursa artifacts published that can be used by Indy Node and Indy SDK (Mike and Cam)

...

• • Ursa and AMCL:  Discussed in the Ursa call (August 21), but no decision yet.
  • Architecture questions for Indy SDK, and progress on Indy / Aries split 
  • Handling pull requests.
    • How to handle old pull requests that failed DCO Checks? Close?
    • How to handle pull requests for IOS / Swift wrappers? Close and encourage the move to Aries?
    • How to handle pull requests for LibVCX? Deprecate?
    • Close PR https://github.com/hyperledger/indy-sdk/pull/1048 as something that will be replaced by the advanced schema work?
    • HIPE pull requests: https://github.com/hyperledger/indy-hipe/pulls
  • New Auth rules: If a non-owner can edit the attribs of a DID or rotate a DID key, then is the DID owner actually an owner?

Future Calls

• Define pull request review process for Indy Node.
  • Should define the process, including how we handle exceptions (emergency fixes shouldn't be blocked, but would require notification)
  • What is important in a good review?
• Fully Qualified DID support in Indy SDK
• fuzzing libindy https://github.com/AxelNennker/indy-sdk/tree/fuzzing/
  `cargo +nightly fuzz run fuzz_target_1 -- -only_ascii=1`
  Worried about unsafe code in libindy
  ```
  ignisvulpis@namenlos:~/development/hyperledger/indy-sdk/libindy$ find src -name \*\.rs -exec fgrep unsafe {} \; | wc -l
  61
  ```

...