Page Comparison

Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: Hyperledger Code of Conduct

...

• Release status: Pam/Joe: Dashboard: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104
  
  • Channel Participation API
    • Doc updates, removal of the term "consortium" - Joe
      • Latest PR: https://github.com/hyperledger/fabric/pull/2208/files
    • Test network Sample update - Will/Julian
      
  • Programming model update:
    • Node SDK 1.4.15 release https://github.com/hyperledger/fabric-sdk-node/releases/tag/v1.4.15
    • Node SDK 2.2.4 release https://github.com/hyperledger/fabric-sdk-node/releases/tag/v2.2.4
    • Go SDK rc1 - GA end of the year or first thing in new year
  • Samples status - Chris/Nik
• Fabric Docs translation video update (David)
  • New Fabric Docs Translation Campaign Wiki
• 2021 Documentation Goals:
  • Currency/Tech Debt:
    
    • Prune Jira Backlog
    • Finish system channel remove/update Test network & tutorial
    • Getting Started
      
    • Add/Remove Raft ordering node tutorial
    • Content Refresh
      • Do we still need 2 Introductions?
      • Arch Reference topic
  • Encourage users to migrate off of older releases/Deprecation banner on earlier release topics
  • Fabric Documentation Translation Campaign
  • New Deprecations Strategy and Page
  • How can we improve Caliper and Explorer Docs
  • Add/Remove Raft ordering node tutorial
  • Assess need for Migration Guide. How to get from 1.x to 3.x

Discussion

Minutes:1.

1. See Joe's Jira for updates on progress with removal of system channel from docs.
2.  Test network samples update - using osnadmin CLI
   1. Creating app channel genesis block instead of system channel
   2. directly joning the orderers to create the channel
   3. anchor peer update is tricky because test network is using deprecated feature of configtxgen
   4. restructure and refactor to reuse what we can for org1 and org2 peers.
   5. Do we need a different CLI container per org? Or can we reuse a single CLI container
      1. Nik's suggestion - move away from using the container all together. could require that `jq` is available?
      2. Chris: Could keep a single CLI and swap environment variables
      3. Is the CLI container deprecated in the Fabric tools?

Quarterly reports

Upcoming reports

...