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 for this week:
- V2.0 release status: Pam/Joe
- Fabric 2.0 GA:
- Dave will create a release-2.0 fabric branch end of this week, to start the v2.0 close down and open up v2.x dev in master. We are targeting Jan 29th for final v2.0 release
- Nik has updated CouchDB (merged), Private Data Tutorial, Add an Org tutorial (draft) to new Test Network
- Fabric 2.0 GA:
- Ledger API (Matthew White)
- Commercial Paper Tutorial doc updates (Nik)
- BYFN Replacement/New Deployment Guide status (Nik/Joe/Pam)
- MSP Key Concept status (Pam) - Draft tag has been removed. See it here: https://github.com/hyperledger/fabric/pull/307
Discussion
- Release status
- Starting to shut down 2.0 content
- Nothing new being proposed
- Nik working on updating tutorials to use test network
- CouchDB, PDC, AddOrg tutorials
- Subsequent add channel and deploy smart contract
- New deployment guide also being worked as part of V2 continuation
- Post on mailing list about documentation maintainers group
- no comments, objections, feedback etc. Working with Brett in parallel to implement.
- Up and live target date is near-term, Feb 2020.
- SDKs will be released simultaneouly.
- Ledger API
- See video recording.
- Topic charts as follows
- Why a ledger API?
- Conceptual architecture
- An example ledger
- Jim Mason: logical and physical models can help. Emphasize this as a logical model.
- Ledger relationships
- Logical model
- fabric-ledger-API
- Chris Gabriel:
- Scalable for enterprise
- Interoperable
- Present business reason for adoption
- Ledger API is about a strong programming model to store business objects
- Chris Gabriel:
Video of this week's session at: Recordings