Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Summary

  • The Bifold Summit is a focused effort to provide time for the community to discuss issues and the future of the project. There are currently scheduled two sessions:
    • Session #1 - 1/10 10:00 AM MT - 12:00 PM MT (12:00 PM ET - 2:00 PM ET)
      • New Bifold Architecture
    • Session #2 - 1/11 9:00 AM MT - 11:00 AM MT (11:00 AM ET - 1:00 PM ET)
      • Bifold AIPv3 wants/needs discussion
      • Lanugage Discussions, Indy wrappers, Shared Libraries
      • Updating Bifold to AFJ 0.3.2
      • Ad Hoc topics
  • Zoom Link (the same used for the bi-weekly calls): https://zoom.us/my/hyperledger.community?pwd=STZQd0xMZU9xRVVOVnpQM3JNQ2dqZz09

Meeting Policies

Hyperledger is committed to creating a safe and welcoming

community for all. For more information

please visit the Hyperledger Code of Conduct.

Session #1

Attendees:

...

  • Bifold AIPv3 wants/needs discussion
  • Deep Linking
    • Mattr – Chapi to redirect
    • Work item to experiment / RFC creation
    • We don't want to hardcode / lock to wallets – splintering of wallets
  • Lanugage Discussions, Indy wrappers, Shared Libraries
  • Updating Bifold to AFJ 0.3.2
    • Almost done - Jason
  • Upgrading React Native
    • 0.68+
    • ZMQ
      • Short-term – Indy-VDR as a Proxy Server
      • Long-term – Talk directly to the nodes over HTTP/HTTPS
    • James to provide a branch to Clecio
  • Shared Components / Indy-VDR / Aries-Askar
  • Followup Architecture Discussion
    • Do we want to utilize context providers?
      • Proposal – Bifold Context Provider
        • Services configured/passed to the context provider
      • State management?
        • Event creation – just need a little bit of structure
          • Exposed as a service
        • Pluggable State management – not required
          • More modular ideally
        • Remove the state management out of Bifold Core
          • Reference Implementation needs state management
    • How do you customize a component
      • We should crawl > walk > run – start with simpler cases as we learn more and then slowly add more complexity
    • I'm trying to create a wallet from Bifold components, what does that look like?
    • Workflows
      • Pull out the workflow/logic to the app logic
    • How do we ensure we maintain/update the reference implementation
      • We need to make a commitment to keeping
      • Project/goal statement
    • Navigation stack – Leaving to the end developer
      • Could abstract/bundle some navigation stacks, such as the onboarding or pin creation
      • Navigation stacks
        • Opinionated navigation across multiple components/building blocks
        • Must NOT be required – needs to be not required
      • Action Menu
      • Generally avoid navigation
  • Ad Hoc topics

Notes:

Recordings

...