2020 10 30 DWG Agenda

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

Announcements

Agenda

• Release status: Pam/Joe: Dashboard: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104
  
  • Programming Model
    • Node SDK v2.2.3 Release notes  https://github.com/hyperledger/fabric-sdk-node/releases/tag/v2.2.3
    • Waiting for approval of Fabric Gateway RFC
  • Ledger snapshot merged!
    
    • Peer snapshot commands merged into master https://hyperledger-fabric.readthedocs.io/en/latest/commands/peersnapshot.html
    • Operations guide: https://hyperledger-fabric.readthedocs.io/en/latest/peer_ledger_snapshot.html
  • Samples status - Chris
• Linux Foundation Marketing Campaign Update - David Boswell
• International languages(standing topic)
  • Remind translators that if they are maintainers that after they approve a PR they can user the `doc-merge` label on a PR to merge it.
    
    • Malayalam translation update - Annena
    • Japanese translation update - Tsujita-san
    • Brazilian Portuguese translation update - Renato
    • French Translation update - Oumar
    • Spanish translations update - Claudio/Maria
    • Russian Language update - Arseny
      
    • Tamil Translation - Ravi
• Channel Participation API doc
• Orderer Deployment Guide doc
• Getting Started

Discussion

Minutes:

1. Linux Foundation Marketing Campaign Update
   1. David - Investigating to see if we can get a video person.
   2. We have 5 interested parties representing Japan, China and India (Malayalam)
   3. Meeting on 11/10 for next steps
2. Channel Particpation API doc - Pam walked through doc in current state
   1. Recommendation to not break out the tutorial on a separate page
   2. Under How this process differs from the legacy process: where we talk about how we used to create a channel, also remind people what command was used then.
   3. Questions about the tech debt we are creating by referencing the System channel here when we ultimately have to remove it. Agreed it is required to include it in some form to differentiate the new process.
   4. If mutual TLS is enabled then the --clientAuth flag is also required on the commands
   5. Would the illustrations from the Contributor's call be helpful? Maybe one in step one and and second in step 2 showing the follower.
   6. Does the new Admin.ListenAddress include the host and port? Do we also need to mention the ListenAddress TLS flags when TLS is enabled?
   7. Talk to Joe about the suggestion to put the steps to remove the system channel from the existing ordering nodes/serve in the Upgrade documentation. When you upgrade to Fabric v2.3.0 if you want to take advantage of the channel
      participation API...
3. Getting Started - Rob walked through the Getting started topics PR: https://github.com/hyperledger/fabric/pull/1999
   
   1. Need clarity on whether we really want the cURL to point to the latest (is this master? content) branch instead of the latest stable branch. Rob to check with Dave.
   2. Suggestion - On the layers page, maybe show the steps with a layered architecture diagram?
   3. Refactor links to the existing Writing your First Application tutorial since we are changing the title
   4. After these updates, Rob plans to take off the WIP flag and squash the commits.

Quarterly reports

Upcoming reports

Backlog