2020 10 16 DWG Agenda

Owned by Pam Andrejko (Deactivated)
Last updated: Oct 16, 2020
3 min read

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
    • Channel participation API - soft launch on target for v2.3
    • Ledger snapshot - doc work started - v2.3 GA
    • Deployment Guide - Peer published, started orderer deployment work on-going
    • Samples status - Chris
  • Banner temporarily removed from older release topics.
  • 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 - Maria
      • Russian Language update - Arseny
      • Tamil Translation - Ravi
  • Promoting translated docs and translation groups
    • French and Malayalam versions of Hyperledger home page are now live
    • All home page translations should work on the 'Resources in your language' section to link to translated docs, translations work groups and any other resources available in that language
    • Discussion of next steps with a contribution campaign
  • Ledger snapshot
  • Channel Participation API Doc Strategy
  • Orderer deployment guide
  • Getting Started

Discussion

Minutes:


  1. Internationalization
    1. Renato: continued progress. Still working alone and could use help. David can potentially broadcast the need.
    2. Claudio:next week Spanish wg meetup, adding more people from Madras meetup.
  2. David Boswell: more visible we can become around translations
    1. If we want to be a little more structured - Resources in your language good place to add a link to your languages https://fr.hyperledger.org/
    2. German coming soon
    3. Contribution campaign planned for January/February timeline - video or some other assets - need content to be ready early next year
  3. Ledger snapshot
    1. Google doc started
    2. Operations guide instead of a tutorial
      1. Not really appropriate for test network - due to interactions between different organizations.
      2. Take a snapshot of all the blocks, hash, transmit out of band,
      3. orgs can compare their state db's to see if any fork or corruptions
      4. other org can point to snapshot.
  4. Channel participation API - way to create a channel without a system channel
    1. Stategy
    2. Trying to agree upon terminoloigy/What to call this
    3. More of the burden is now on the peer orgs
    4. Creating a new create a channel tutorial 
  5. Orderer deployment guide
    1. New planning topic - similar to peer
      1. This process describes the process for using a system channel. Update after 2.3 GA when channel participation API is available
      2. We need will need to add a production profile in configtx.yaml
      3. sizing - nodes are on multiple channels, will be having ledgers on every channel - alot of blocks
      4. Cluster considerations - how many nodes are practical to have on a particular ordering service? Increased message traffic as # channels grow.
    2. Checklist
      1. Again similar to peer and CA deployment guides we will highlight the most important settings for a production env
      2. Currently in the process of scoping the list of settings to highlight.
      3. Chris demo
      4. Troubleshooting topics will be included
  6. Getting started
    1. Rob perspective: I like to look at code to understand what is going on. so I need to be able to see the code too. So that's why I've included everything here.
    2. Pam: don't want it make it hard for existing users to find the cURL command
    3. Jim: different types of users - some people just want a demo model (to try out tutorials or samples), kick something up quickly. vs. I am new developer.

Quarterly reports

Upcoming reports

Backlog