Page History

...

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
- https://lnkd.in/ggMJqKk
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.
- RTD instructions https://docs.readthedocs.io/en/stable/versions.html#version-warning
- Deactivate and redirect: https://github.com/readthedocs/readthedocs.org/issues/6891
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

<minutes>

Western hemisphere call

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
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
Women in Blockchain Event
1. Lots of positive feedback
2. Wide mix of panelists
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.
Broader homepage translation
1. David has contacted Aneena and Tsujita-san for main Hyperledger translations
2. minor issues being translation
Blog and Community spotlight video
1. Needs to be moved forward in Sept
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
Recording

Western hemisphere call

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
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
Updates on Study circles
1. Western study circle
2. How to best support people on community on these skills?
  1. Please connect with David
See Eastern hemi notes above
1. Doc-merge label on PRs
No updates on other languages
1. Renato next week
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
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
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
Share peer deployment guide on contributors call next week
1. Good place to get review
Chris G blog on private data: https://www.linkedin.com/posts/chris-gabriel_hyperledger-on-twitter-activity-6701441156414287872-XI9e
Chris local build process update:
1. When you clone Fabric, to your local drive, and you setup your sphinx build, and follow instructions to Build locally:
  1. You need to run: `pip3 install sphinx-rtd-theme`.
  2. Then you can run `pipenv shell`.
  3. Then run make html in the fabric/docs folder.
1. Samples update
  1. Tutorials - Refactoring chaincode4developers was turned into Writing your first chaincode in 2.2 and Master branch.
    1. New: Added content about the high level contract API
    2. Patterned the tutorial after the new basic asset transfer sample
    3. details on each function call.
  2. So all the tutorials have been updated now: Using Fabric test network, Deploying a smart contract, Writing your first Application, and Writing your first chaincode
Peer deployment guide: Draft PR created https://github.com/hyperledger/fabric/pull/1789
1. Updated Deploying a Production network.
  1. Embeded toc links to detail instructions inside each step
2. New Planning for a Peer topic. Decisions you need to make before you deploy a peer.
3. New Peer planning checklist doc.
4. Next: Peer deployment guide.
5. Chris Need section on alternative syntax when you do an override of the environment variables. If you are putting it k8s or docker compose file - how to build out the environment variables. You can infer how to build them.
6. Peer sampleconfig.yaml does not include all the parameters. Look at the core.yaml in the peer binary config folder instead.
7. Nik: What are the challenges with deploying fabric in K8s? HA, running multiple replica sets on different VMs, What happens when there is node failure - you can configure this in K8s. A big challenge is the sequence in which you do things. Prioritizing deployment of CA, creating certs, configuring Node OUs.. Coordinating with other organizations.
Promoting translations - David
1. How to make translated docs discoverable? Publish on HL social media channel, also landing page when Language is ready to publish
How to recognize contributors to the DWG:
1. Pilot process... group level (Documentation, translation) vs. Project (Fabric).
2. Translation badge is too specific.
3. Fabric documentation badge issued to people making a rang eo fo documentation related contribution - group specific rather than task specific.
4. Fabric contributor badge -
5. Other open source projects: range - depends on how many badge types/how granular. Set criteria and then monitor.
6. Ideally this is an automated recognition.
7. Should this be brought up on contributors call -
8. David to present again next week and we provide feedback - Have a longer discusioon pr
9. Consider that people doing the translating are necessary the person making the commits -

Video of this week's session at: Recordings

Page tree

Versions Compared

Old Version 1

New Version Current

Key

Announcements

Discussion

Quarterly reports

Upcoming reports

Backlog