2020 05 29 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
- Fabric 2.1.1 release this week. 2.2.0 (LTS) is early July
- Contributors topic for new languages(standing topic)
- Proposal to move all languages under Fabric Repo by Arnaud LeHors. See RocketChat.
- Local build issue on Ubuntu with native HTML.
- Continuation of discussion from last week around "organizational resources folder structure".
Discussion
Eastern hemisphere call
- Review of release status: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104
- Covered all major discussion points from last week's call
- Aneena on ML progress
- Local builds working well
- Local forks now building in RTD.
- See example build: https://fabric-docs-ml.readthedocs.io/en/latest/
- Aneena resolved some PDF Latex build issues during the week
- Addresses with custom RTD build file
- Allows anyone to do ML build
- Review of Git book: https://git-scm.com/
- Agreed importance of understanding concepts for new contributors
- Great for students to learn git concepts and practice
- Git working practice example walkthrough
- Explained upstream, origin and local clone
- Working with branches
- Working as contributor demo
- Working as a maintainer demo
- Resync-ing with the upstream
- Building new branch with RTD
- Recording uploaded.
Western hemisphere call
- Release Status
- Preparation for 2.2. LTS release, July slated
- 2.1.1 bug fix stablization release
- 2.2 slated early July
- Config transaction library slated for 2.2.
- Deployment guide
- Snapshot/checkpoint in preparation for next LTS
- SDK GO for 2.2
- EOL 1.4 discussion started
- Contributor meeting
- Need clarity on this
- In favour of bringing translations into Fabric repo
- Discussion on WASM discussion
- Renato on Pt_BR support
- Pipenv specifics
- Building docs nicely now
- Translated Introduction
- Looking very promising
- Working with Chapter in Brazil to build a community in effort
- Focussed on having something real
- create and interest
- Looking to Renato for guidance and suggestions on how to work
- What will be the process on update to contents
- How do English language propogations
- The process is important
- Demonstrating a repeatable process
- Worksheet for other teams to get started
- Spanish, Italian and Greek.
- A single page would be sufficient
- Renato and Aneena can help too
- Quick update on ML progress
- As per above
- Arnaud asking about timing for multiple translated content to live alongside English documentation
- Historically done for POC, prototype reasons
- Concern about extra PRs and issue tracking noise
- The process for translation is importance
- Awareness
- Refactoring
- To keep translations fresh
- Validate or address quality of translations
- this is repo-independent
- We are at inflection point
- What would facilitate good translations
- In general maintainers seem keen to have doc with code
- logistical point
- Maintainers for per language
- All very doable
- Maybe a different repository structure would approve
- This could help the process
- Maybe a separate languages repository
- This can help the process
- Soft launch
- HL Labs
- Anthony to doc during the week
- Invite Arnaud to this call next week
- Local build issue on Ubuntu with native HTML.
- resolved by Renato
- Maybe carry over to main repo
- Continuation of discussion from last week around "organizational resources folder structure".
- Conceptual structure now focusses on the organization
- Incorporated comments
- improved images
- "Decide on structure of folders and certificates" vs certificate pathing
- Draft PR being reviewed by CA owners
- Lots of opportunity to review
- Will move on to peer and ordering service deployment
- Uploaded recording
Video of this week's session at: Recordings