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.

...

• What is the next step we can take:
  • Order of work
    • Move Indy-SDK into Aries-Core (October release)
    • Split out wallet into Aries-Wallet (November release)
    • Define the resolver interface (November effort)
    • Split out resolver into Indy-Resolver (December release)
  • Questions
    • Iterative approach: do something that we can improve on.
    • Maintain Indy-SDK alongside Aries-Core / Aries-Wallet / Aries-Resolver?
    • Who will be the maintainers of the new libraries? Do we want cross-organization PR reviews?
    • Best way to maintain history, and  make the reorg transparent (concerns with old DCO process).
    Order of work
    • Move Indy-SDK into Aries-Core (October release)
    • Split out wallet into Aries-Wallet (November release)
    • Define the resolver interface (November effort)
    • Split out resolver into Indy-Resolver (December release)What to do with the Indy CLI?
    • CI / CD in Jenkins or GitLab?
• Architecture of Aries core library
  • What is our fastest path to a library that framework implementors could consider using?
  • Daniel's analysis of Aries API Surfaces https://docs.google.com/presentation/d/1ODtHCeB6x7yVGfhyJHFUKn0f070sqZXhff1C8M7jfTY/edit?ts=5d658905#slide=id.p
  • Background in previous meetings: July 31, August 14
  • Progress of Ken's POC
  • Key questions: https://docs.google.com/document/d/1w_n8EztyLbNlRa3FfuuN8YXKUISYRfM5p_6ijIig6jk/edit#

...