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

  1. Release status: Pam/Joe: Dashboard: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104
    1. Fabric 2.2 release: GA planned for July 8:

      1. TLS v1.3

      2. Automatically include CouchDB in v2.x upgrade step (Updating the Upgrade Instructions for this)

      3. Fabric dependency updates (use Go modules, update go dependencies, update Alpine)

      4. Code refactoring for easier maintenance (bccsp, ledger)

      5. Improvements (e.g. improved error messages) and fixes

      6. Removal of BYFN from docs and Samples (keep page there for now but add text and link them to Test network and deployment guide)
  2. Update to Style Guide (Joe)
  3. Contributors topic for new languages(standing topic)
  4. Translation Governance:
    1. What is the minimum translated content required to publish in the ReadTheDocs?
    2. Who are the maintainers for each language?
    3. Currency - what is the process for keeping content up to date?
    4. How to track and incorporate changes from English content into translated content?
    5. In general, should translation start with the LTS version of the docs?

Discussion

Eastern hemisphere call

  1. Introductions
    1. Welcome to Kondo-san, Tsujita-san and Nishijima-san from Japanese translation working group
    2. Welcome to Annena Alexander from Malayalam working group
  2. Reviewed wiki structure with emphasis on language workgroups
    1. Japanese WG - Japanese Documentation Working Group
    2. Malayalam WG - Malayalam Documentation Working Group
    3. New quarter starts next week
  3. Release minutes
    1. Schedule
      1. Friday June 26 end of development
      2. Wed July 8 - Release 2.2
    2. Proposed Contents

      1. TLS v1.3 - will not affect users as will negotiate down

      2. Automatically include CouchDB in v2.x upgrade step – database drop now done automatically

      3. Fabric dependency updates (use Go modules, update go dependencies, update Alpine - all good hygene

      4. (Tentative) Configure all peers as leaders by default, always get blocks from ordering service (proposed FAB-16435) - note it's just the default that changes

      5. Code refactoring for easier maintenance (bccsp, ledger)

      6. Improvements (e.g. improved error messages) and fixes

      7. Removal of BYFN from docs and Samples (keep page there for now but add text and link them to Test network and deployment guide) - really important note that BYFN is now deprecated
        1. Chris G offer to scrub docs wrt First network removal
    3. Rocket chat/Samples reference
      1. Fabric samples channel: https://chat.hyperledger.org/channel/fabric-samples
    4. 2.2 release upgrade instructions
      1. Last 1.4 upgrade instructions
      2. Multiple instruction steps will be possible
  4. Tour of i18n
    1. ja_JP folder and contents
    2. ml_IN folder and contents
    3. CODEOWNERS has been set up to include contributions with a broad set of maintainers
      1. CODEOWNERS: https://github.com/hyperledger/fabric-docs-i18n/blob/master/CODEOWNERS
      2. https://github.com/orgs/hyperledger/teams/fabric-ja_jp-doc-maintainers
      3. https://github.com/orgs/hyperledger/teams/fabric-ml_in-doc-maintainers
    4. Allows for lots of contributions
  5. ja_JP translation
    1. Significant work being done by the team
    2. Fork of i18n
    3. RTD builds working
    4. Discussion on when to start populating i18n
    5. Agreed with Introduction, Contributing and Glossary as minimum topic set
    6. There is a lot to translate!
  6. ml_IN translation
    1. Complete first pass of docs
    2. Second pass almost done
    3. Expect to be ready to populate i18n next week
    4. Would like to see appear in public docs soon
    5. Excellent progress!
  7. Translation process
    1. How to keep languages up to date
    2. Consider 2 mechanisms (which can be combined)
      1. Use doc tags/labels to identify changes
      2. File delta using GitHub releases
    3. Option 1 is available today
      1. Both teams happy with this approach, would like to see incremental changes
  8. Recording uploaded


Western hemisphere call

  1. Welcome
    1. Welcome to Oumar
    2. Community leader for Senegal
    3. French speaker
    4. Hyperledger Africa informal group
      1. Meet once per month
      2. On-line meetings also being planned
      3. Includes English speaking part of West Africa
        1. Burkina Faso, Morocco involvement
    5. Keen to collaborate with wider French speaking teams
  2. Release status
    1. Fabric 2.2 release: GA planned for July 8:

    2. TLS v1.3

    3. Automatically include CouchDB in v2.x upgrade step (Updating the Upgrade Instructions for this)

    4. Fabric dependency updates (use Go modules, update go dependencies, update Alpine)

    5. Code refactoring for easier maintenance (bccsp, ledger)

    6. Improvements (e.g. improved error messages) and fixes

    7. Removal of BYFN from docs and Samples (keep page there for now but add text and link them to Test network and deployment guide)
    8. Gossip unlikely to be release
    9. 2.3 likely for snapshot/checkpoint
    10. GO SDK will be available
    11. Channel participation API
      1. Could be significant operational change
      2. Business and technical implications
      3. What is a network?
      4. Unlikely for 2.2? Likely 3.0 given changes
      5. Will role of system channel change
  3. Network deployment guide new PR for CA update
    1. Close to being merged
    2. Deploying a peer topic next
    3. Then orderer topic
    4. BYFN removal depends on these
  4. Updates to the style guide
    1. Use of language changes
    2. Style guide to reflect these
    3. Pretty good compliance already, so minor changes
  5. Pt_BR language updates
    1. Lots of progress on translation
      1. Key concepts almost finished
      2. Brett to fix RTD documentation
        1. Still has small issue
    2. Latin America Chapter meeting
      1. Promote workgroup to Spanish
      2. Thank you Renato
      3. Next week may join the call
      4. Lots of chapters, Chile, Mexico...
        1. Renato will support Spanish team in LA and Spain
        2. Pam follow-up with IBM Brazil will follow up
        3. Anthony will connect
  6. Eastern hemisphere update on ML and JA
    1. New Rocket chat channel for Japanese team, and ML will do the same
  7. Translation governance
    1. Need to make decisions on how to govern
    2. Contributors call on Wednesday
    3. We will say minimum
      1. Next topics should consider are
      2. Recommend Key Concepts as first!
      3. Add a recommended set afterwards
        1. Build this from Renato's order of translation
    4. Could Google analytics help?
      1. Consideration from David Boswell
      2. Runtime stats on this as suggestion
        1. Available for every group doing translations
        2. Discussion item for next week
      3. This can inform order of translations
      4. Add to agenda for next week
    5. Architects/Student may be looking to different content to developers
    6. GitHub edit change
      1. Will this work?
      2. People will try to do this?
      3. CN goes to HL Labs
      4. Should be address
    7. New translations start with LTS
      1. Is this right?
      2. What is good guidance here
      3. Shouldn't translate from master:pick a published release
    8. Really important to tag as docs
  8. BYFN update
    1. Suggestion from Chris to link back to BYFN 2.1 so that easy navigation is possible
      1. FAB18015 to cover this
  9. July4 reminder for next week – no Western hemisphere meeting next week!
  10. Video uploaded


Video of this week's session at: Recordings

Quarterly reports

Upcoming reports

Backlog



  • No labels