Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Remember the Hyperledger Code of Conduct

Anti-Trust Policy:

Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.


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.

Attendees


Resources

Status updates

Agenda

  • Record the meeting
  • From our last meeting:
    • Support for Deno
    • Generic ledger module + using qualified identifiers
  • Mediator scalability issues (Jakub Koci)
    • AFJ as a mediator.  Needed by edge agents.
      • More than 5 clients causes failures, if you start 10 then maybe 1 or 2 will timeout during provisioning
      • Do we have a guide for configuring an AFJ mediator?
      • Latest version fixes 15 second timeout
    • ACA-py mediator
      • Timo has done some work with ACA-py mediator, scaling to millions of agents
      • ACA-py based Indicio mediator was also tried, behaved similar to ACA-py results
    • The PR for mediation issue: https://github.com/hyperledger/aries-framework-javascript/pull/946
  • Karim Documentation discussions, to get your feedback and suggestions
  • Pain points and improvements
    • When to favor documentation?
      • ESLint
      • Issue Templates
      • Continous Integration checks
    • How to incentivize or guide developers towards building documentation?
    • List of things that could be added for new developers
      • Code Style
      • Patterns
      • Tips
    • Docusaurus contributions
      • Framework considerations?
  • Special considerations for AFJ, AFJ-Extensions, and Bifold?
  • Cross repo documentation
  • Contributors want to get on-board rapidly
    • Rating issues for beginner, intermediate, advanced?

Meeting Notes

Future topics

  • React Native testing
  • Monorepo dependencies
    • TypeScript types
  • ACA-py and AFJ performance/scale documentation
  • Mike's modularization, etc documentation


Meeting recording:

  File Modified
No files shared here yet.






  • No labels