...
| Excerpt |
|---|
Planned:
|
Note: This call is Recorded. Recordings posted at the bottom of the page.
...
- Scheduling future meetings
- January 1: Cancelled
- January 15: Need to select a topic
- Aries language wrappers
- Connect-a-thon proposal: let's only build Frameworks instead of SDKs—let's be opinionated! Simplify the experience of a new developer.
- Merge the SDK and the Framework repositories so developers don't have to choose between them.
- aries-sdk-go should merge into aries-framework-go
- aries-sdk-javascript should move into aries-framework-javascript
- other SDKs renamed as Frameworks?
- Can have a separate SDK artifact in the Framework repository, if desired.
- Merge the SDK and the Framework repositories so developers don't have to choose between them.
- When can we deprecate the Indy SDK wrappers?
- Overlap in development between Indy and Aries. New developers should start in Aries.
- Hard to maintain CI / CD and do bug fixes for environments and wrappers we don't use.
- IS-1423 for DotNet, because the Aries Framework is mature.
- IS-1424 for Java, JavaScript, Android, iOS
- Challenges with Python
- Connect-a-thon proposal: let's only build Frameworks instead of SDKs—let's be opinionated! Simplify the experience of a new developer.
- Misalignment between RFC 0094 and ACA-Py
- ACA-Py pull request: https://github.com/hyperledger/aries-cloudagent-python/pull/240
- Aries KMS design
- Define approved algorithms
- Define plugin interface
- 3rd party libraries we could leverage:
- Google Tink as an encryption library
...