...
Excerpt |
---|
|
Timezone: US afternoon and APAC morning
...
- Name (organization) <email>
- Richard Esplin (Evernym) <richard.esplin@evernym.com>
- Alan Krassowski (Kiva) <alank@kiva.org>
- Cam Parra (Kiva) <camilop@kiva.org>
- Kyle Den Hartog
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
...
- Catch up on previous calls:
- Should track exceptions to Indy Node review policy in the Git commit message.
- 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?
- Answered questions about the Transaction Author Agreement.
- 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?
- Closing the PR doesn't get rid of the work. The author can reopen at any time.
- 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
- Kyle will continue reviewing PRs, but does not want to be a bottleneck slowing down the process.
- How to handle old pull requests that failed DCO Checks? Close?
- Future calls:
- Cancel the call September 30 for IIW
- Cancel the call October 14
- Should we do another security audit?
- Results from the last security audit: Security Code Audits
- 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
- Catch up on previous calls:
...
- HIPE #138, Issue #144 (Ken and Brent)
- Create a PR for changing status to ACCEPTED
- Check for an Aries RFC
- PR to RFC #0019 to compare pack/upack to msgpack (Sergey)
Call Recording
View file | ||||
---|---|---|---|---|
|