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:
  • Asia Pacific Study Circle
  • 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
  • Recognizing contributors - David
    • We had discussed having a Translator badge (among other possible badges) and it sounds like that may be too specific.  I wanted to check back in about what type of badge would work better?
      • One option would be to have a Fabric Documentation badge that could be issued to people making a range of documentation related contributions
      • Another option would be to have a Fabric Contributor badge that could be issued to people making documentation contributions or other Fabric related contributions
    • Example of pages from other open source projects:https://make.wordpress.org/meta/handbook/documentation/profile-badges/
      • "contributor badges are generally assigned to anyone who has contributed to a particular team"
      • There is a documentation badge
  • Samples status - Chris
  • New process for local builds: See https://hyperledger-fabric.readthedocs.io/en/latest/docs_guide.html#building-locally
  • Retiring Fabric docs versions 1.1/1.2/1.3 - Banner not working in RTD.
  • Peer deployment guide update https://github.com/hyperledger/fabric/pull/1803
    • new this week: peer deployment tutorial
  • Google Analytics update - Joe/Pam

Discussion

Eastern hemisphere call

  1. Blockchain Fundamentals program
    1. Kick started last Monday
    2. August 24-August 29
    3. AICTE All India Counctil for Technical Education
    4. LInk: http:// fdp.saintgits.org and http://fdp.saintgits.org/blockchainfundamentals/

    5. Short term training program
      1. Blockchain Program first – 6 day program
      2. October, Blockchain Applications
    6. Invite to program
  2. Asia Pacific Study Circle
    1. Completed after 6 weeks
    2. Overview on Hyperledger
    3. Good participation from Aus, Japan...
    4. Feedback to start session on Hyperledger Fabric study circle
    5. Sourcing speakers for this
  3. Women in Blockchain Event
    1. Lots of positive feedback
    2. Wide mix of panelists
  4. Malayalam translations
    1. Version 2.2 focus
    2. Formatting, aligning, translations
    3. Want to complete before Fabric study circle
    4. Kerela holiday coming soon
    5. What is status of public website
    6. Could be ready to do test publication
    7. Need to work with Brett on this.
  5. Broader homepage translation
    1. David has contacted Aneena and Tsujita-san for main Hyperledger translations
    2. minor issues being translation
  6. Blog and Community spotlight video
    1. Needs to be moved forward in Sept
  7. Japanese translation update
    1. Translating contributing page
    2. Key Concepts being translated
      1. Lots of work to do this
    3. Kaban board to see progress
      1. Allows checking of progress
    4. Note that new languages are appearing on website, but not yet connected to release 2.2. and build
      1. Need to check status with Brett
  8. Recording

Western hemisphere call

  1. Release status
    1. Not many new updates
    2. Listen to contributors call for detail
    3. MirBFT starting to make progress
    4. Channel participation API
      1. Will impact documentation
      2. Could be new default long term
    5. Config txn library
      1. Add org tutorial being updated
    6.  Deployment guide
      1. Peer deployment docs now released as PR
      2. Lots of content to review
      3. Chris providing excellent feedback
    7. Backup/restore
      1. Playback 2 weeks ago
      2. recorded
    8. SDK update
      1. All available
  2. Samples update
    1. Writing your first chaincode
    2. Based on asset transfer basic sample
      1. reviewed and merged
    3. Constructed with single main package
    4. Will next focus on private data tutorial
      1. See fabric-samples channel in rocket chat
    5. Work item plan in Google docs
    6. Token discussion might be soon-to-be work item
  3. Updates on Study circles
    1. Western study circle
    2. How to best support people on community on these skills?
      1. Please connect with David
  4. See Eastern hemi notes above
    1. Doc-merge label on PRs
  5. No updates on other languages
    1. Renato next week
  6. Recognizing contributors
    1. New opportunity - badging infrastructure could be piloted in this workgroup
    2. Less granular than docs
    3. See link to wordpress
    4. Different options are available – Fabric Documentation and Contributor
    5. Suggestions
      1. Joining calls
      2. First commit/contribution
      3. "Recognized" level = 10 (say) commits. Can apply for this – commits are public
      4. Currency is important, e.g. 2020, 2021 badges
      5. Should have LF ID and handle
      6. Nominations are important idea here too
      7. Where does badge show up?
        1. 3rd party badge provider
        2. LF profile page
        3. LinkedIn integration possible
      8. Automatic recognition helps
        1. RocketChat, Commit history
        2. Keep overhead low - ability to scale
        3. Can also self-nominate, e.g. blog writers
      9. Doc badge seems like good idea
    6. Recognitiion not just badges, going forward
  7. Local build process
    1. https://hyperledger-fabric.readthedocs.io/en/latest/docs_guide.html#building-locally
    2. Containerized local builds!
      1. Much easier - helps with Python pre-reqs etc
    3. Standardized and recommended process
  8. Retiring Fabric docs versions
    1. 1.1/1.2/1.3 still being used by readers
    2. 1.4.3 EOS in 2021
    3. 2 step approach to encourage
      1. A
        1. Banner on every page - to remind people not latest content, with link to latest content
        2. Nice RTD mechanism to do this. A few challenges, but now working
        3. See example: https://hyperledger-fabric.readthedocs.io/en/release-2.2/
          1. Only on landing page – a bit or work to do
      2. B
        1. Archive old content and configure re-direct
        2. Deactivate and redirect: https://github.com/readthedocs/readthedocs.org/issues/6891
    4. Will bring up on contributors call
      1. Raise awareness of this issue
    5. Started with broken links discussion
      1. AWS and Azure impacts
      2. Might be good reason to keep around
    6. Different meaning to deprecate and remove service
    7. Discussion on docs remaining
  9. Share peer deployment guide on contributors call next week
    1. Good place to get review



Video of this week's session at: Recordings

Quarterly reports

Upcoming reports

Backlog



  • No labels