2020 03 20 DWG Agenda
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
Release status:
Pam/Joe Dashboard: https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104
Contributor call recap.
Contributors topic for new languages
How to do a small doc change
End to end walk-through from Joe Alewine
HLF internals docs
Create channel tutorial
BFT update
LTS RFC update
Fabric CA Deployment updates
Including Considerations when using Kubernetes and Docker
use of -M in place of FABRIC_CA_CLIENT_MSPDIR env var https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/clientcli.html
added `--enrollment.profile tls` when enrolling with the TLS ca
Discussion
Release status: Pam, Joe
Config transaction library - create some higher level transactions for updating channels etc
Hadera hashgraph also discussed on contributors call
BFT work proceeding
Deployment guide progress
Test network progress
CA doc in good shape
Google doc being created for checkpoint/archive. RFC soon
Go smart contracts already in
Go SDK doing well
Contributors topic for new languages
Need ability for other users to show how to do this
Need help from Rich Zhao
Keep as aide memoir here
Small doc change video tutorial from Jo
HLF documentation
Quick review. Very valuable
How to maintain, how is it kept current
PPT is not ideal
Live in markdown, and keep it current
Great content
if it were in markdown, much easier to maintain
Sit in 1.4 repo, and go through changes at right time as it evolved
Architecture reference material for peers and chaincode container is excellent
What are key concepts below in the docs
Architecture reference material
Developer related information
Who is the target personae for this content
This looks like great low level design document
Would use it for debugging – for developing fabric content, but could some of it be relevant for end user developers
Look at repo for design docs
It uses old lifecycle, rather then new lifecycle – needs to be update for 2.0
Could write a tool to say how close doc code was to actual code
really great material – who is the consumer, not relevant for chaincode developer
needs to be shaped for the right auidence
How much needs to be in the docs
Get feedback from the community on progress
full stack developers right now
this is useful for most developers in the real world
DWG interested in content even as-is
Need to have information out there
It's very low level
First few slides, drop too low for customer
Other topics deferred to next week
Video of this week's session at: Recordings