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.

...

• Timeline for deprecating Indy wrappers in favor of Aries contributions
  • Focus is on the Aries SDK, no longer on the Indy SDK
  • Moving too fast to deprecate will scare people trying to get started today, because there are no mature alternatives in Aries today.
    • Especially with the mobile wrappers.
      • .NET and Xamarin is used by Open Source Mobile Agent (OSMA), which works today.
      • Team at DIDx is struggling with React Native. Wants to open source a React Native app platform.
      • WebAssembly would be the most performant approach.
    • BC.gov is working on a plan for building on existing Aries today.
• Evaluating Plenum
  • Pros versus other ledgers
  • Improvements we would like to make
  • Recent performance testing (increased batch size and write latency)
  • Top level Hyperledger Project?
• Problems with RBFT replicas:
  • Indy Node Epics
    • INDY-2251: Problems with RBFT Replicas
    • INDY-2250: Removing replicas (move from RBFT to Aardvark)
  • Ken's summary:
    A simplification to our current algorithm to reduce complexity and simplify the method for determining when to perform a view change making our system more resistant to attack. It takes full advantage of our recent PBFT view change and monitoring logic improvements while boosting performance of the system. The cost and risk to make these changes is low.

Future Calls

• Define the pull request review process for Indy Plenum/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?
    • Items from Evernym team:
      • covered by tests
      • has a link to the issue in Jira
      • fixed according to PoA
      • follows https://github.com/hyperledger/indy-node/blob/master/docs/source/write-code-guideline.md
  • Proposed Process (by Evernym team):
    • All Pull Requests can be reviewed by non-Evernym team members
    • Evernym team members will also do internal review in addition to external one
    • All interested parties are notified when a PR is sent
    • If a person wants to do an external review, he or she puts a comment or tag. This needs to be done in X hours.
    • Once a reviewer put a "want-to-review" tag, he or she need to finish review in Y hours
    • If no one wants to review a PR in X hours, or review is not finished in Y hours, we can do our internal review and merge the PR
    • An external review can be done against closed PRs as well, and Evernym team will process all findings ASAP
    • We may merge a PR with internal review only in case of urgency (critical fixes, release preparation etc.)
  • Items to be defined with the Community:
    1. A timeframe for external review (X):
       - X=12 hours, Y=2 days?
    2. What projects it should affect?
       - Plenum and Node?
       - Only Node?
       - We are not proposing SDK as it will be split to Aries in any case
    3. Who is going to commit to participate in this process?
• Migration of Indy-SDK to Aries-Core
• Requirements question: IS-1099, should we allow duplicate credentials from the same issuer?
• Non-secrets in the Indy Wallet
  • Cam is working on pluggable crypto. They wallet shouldn't decide what encryption you should be using.
  • Use cases where we would want to move keys between wallets
    • Moving the link secret / credential data from one device to another (synchronized storage).
    • Debug use cases
    • Richard's hit other uses cases that were better solved with DID Doc,  pre-signing, signing API.
  • Work-around with the web-crypto API

...