Summary

Community Meeting Policies

Welcome and Introductions

Take the opportunity to introduce yourself or organization. Let the community know what interest you have in the Bifold effort.

Attendees

Record your attendance for posterity, and allow others may contact you if needed.

• Name (Organization) <email>

• James Ebert (Indicio) <james.ebert@indicio.tech>

• Sam Curren (Indicio) <sam@indicio.tech>

• Lance Byrd (RootsID) <lance.byrd@rootsid.com>

• Clecio Varjao (Gov. of BC) <clecio.varjao@gov.bc.ca>

Announcements

Deployments and Work Updates

• Biometrics - mostly done, still WIP

  • According to the targeted NIST Spec – you can't upgrade, you can only downgrade

  • https://csrc.nist.gov/publications/detail/sp/800-63/3/final

  • Add a key check to AFJ or Indy SDK / Indy Credx

• Technical debt cleanup and documentation planned.

  • Improving the unit test coverage

  • Getting started documentation

  • Yarn package manager

• Initial work started on working with OCA

  • Aspects planned for integration

    • Branding

    • Credential Internationalization

    • https://oca.colossi.network/v1.1.0-rc.html#label-overlay

• React Native update to 0.70.1 by Indicio.

  • iOS Sleep/Lock Crash (ZMQ) - https://github.com/hyperledger/aries-mobile-agent-react-native/issues/469

Agenda

• Bifold Fork Management Strategy Discussion - Sam

  • At least 2 orgs maintaining "forks" of Bifold to ship applications

  • Is there guidance on how to best stay close to Hyperledger Bifold Main

  • What are the strategies here?

  • Other questions

    • Bifold as a fork – very hard to keep things together (contribution becomes hard to stay in sync)

    • Contribution after the fact – figure out what to contribute, create a PR, rebase if needed, etc

  • Android & iOS folders are fairly specific to the individual app, etc

    • Tool or generator to scaffold a Bifold app - Lance love this

  • "Fork" – not meaning going away from Bifold. Eventually an org will need to make deviations from Bifold, such as brand/color changes, logos, navigation

    • Not "Fork and Forget"

    • "Close Fork"

  • Modularization - Contributing on a component-basis would be easier

    • We also need something for someone to start from – defaults

    • Framework – how to manage screens, components, navigation, etc

      • Peer dependencies are a mess in React Native

      • Library vs Framework

        • Framework is in control and manages things

        • Library has re-usable pieces that an end developer can use

          • Does AFJ fill this role?

          • Bifold fills a valuable role in the community – fully featured application, an example

          • How do we make it the easiest for people to contribute back to Bifold – not a launchpad but rather a ship

    • Navigation stack is a bit of a mess

      • Very business-case centric

      • Components could be passed a callback that handles navigation (meaning the end-developer/app can handle it)

      • This could be a boundary line – a component doesn't do

  • Collaboration between organizations

  • "It would be easier to contribute if..."

  • Is React Native the right place? – Yes, for today

  • Technical Process for managing forks

    • BCWallet – Bifold is set up as a Git Submodule

• OCA in Bifold (followup from the Aries WG)

  • Draft PR for an API

    • Issues running in Bifold

    • Goal is to just get started, using layers, configuration, etc. May need to refactor

• Timing of first credential issue

• Q/A w/Maintainers

• Review PRs.

• Review relevant issues.

Next Meeting

• TBD

Future Topics

• Machine Readable Governance Presentation - Mike

• How should we implement Machine Readable Governance?

Action items

• How to move from v1 to v2 for present proof and issue credential. Will we need to deal with two different screens as both v1 and v2 are supported.

• Support OOB.

Recording