Let us know how we are doing
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
This week's agenda:
- Administrivia: New meeting calendar entries: Anthony
- Active from Jan meeting 10 2020
- You can subscribe to events (tagged with #cal-notice)
- Automated email sent 1 day before event. Will also send more personalized note.
- DWG meetings for 2019/2020
- Next week – Dec 20 – will be last meeting of 2019
- DWG meetings will restart Friday Jan 10 2020
- V2.0 release status: Pam/Joe
- New External chaincode builder and launcher documentation merged: https://hyperledger-fabric.readthedocs.io/en/latest/cc_launcher.html
- New External chaincode as a service documentation: https://hyperledger-fabric.readthedocs.io/en/latest/cc_service.html
- Fabric 2.0 Upgrade process docs: https://github.com/hyperledger/fabric/pull/299 Joe
- MSP Key Concept updates: https://github.com/hyperledger/fabric/pull/307 Pam
- WRT to using GitHub instead of Gerritt, Joe talked about the need to squash commits and that line lengths can now be > 80. In fact that is recommended for easier reviewing in Github.
- Chris asked about the Fabric broken links Jira - FAB-17235Getting issue details... STATUS . One thing to be aware of is that the new Azure pipeline build process for the docs is not checking for broken links. The gerritt pipeline did include some tooling for that, but it never really seemed to fully work.
- Reviewed new Fabric beta docs (links are listed above ^). Start with What's new and release notes for a list of what is deprecated.
- Nik showed the new Test network tutorial that is published under Getting Started.
- Pam showed the latest updates to the MSP key concepts topic.
- General agreement around duplicating the Identity classification content here even though it is also in the Ops Guide.
- Chris pointed out that we need to describe the relationship between the MSP and the CSR in the Fabric CA server and client – probably need to add this to the MSP topic in the Operations Guide. There was acknowledgement that Ops Guide MSP topic also needs to be revisited.
- Also a good discussion from Chris around how there is NO documentation in Fabric on how to configure an Intermediate CA. This is a barrier to adopting Fabric. Suggestion was made to open a Jira and lets get some help from the right minds on this.
- Joe showed the new Hyperledger Fabric v2.0 Beta Release documentation
- What's new https://hyperledger-fabric.readthedocs.io/en/latest/whatsnew.html
- Release notes: https://github.com/hyperledger/fabric/releases/tag/v2.0.0-beta
- New test network now available in Fabric samples!!! https://hyperledger-fabric.readthedocs.io/en/latest/test_network.html
- Upgrade instructions now available off the main toc https://hyperledger-fabric.readthedocs.io/en/latest/upgrade.html
- Chaincode External builder and launcher https://hyperledger-fabric.readthedocs.io/en/latest/cc_launcher.html
- Chaincode as an external service: https://hyperledger-fabric.readthedocs.io/en/latest/cc_service.html
- Pam showed the latest updates for the MSP key concept topic: https://github.com/hyperledger/fabric/pull/307
- requested that workgroup review again and see if it helps
- OK to duplicate the section on Identity classification here although it is also in the Operations Guide? General agreement this is useful.
- Chris Gabriel pointed out that there is more information needed about the config.yaml file - likely in the MSP Operations topic - which explains the importance of and the relationship between the Fabric CA Server and Client and the CSR.
- General agreement that we need to update the MSP Operations Guide topic as well. Next task once we settle on the MSP Key Concept topic.
- Chris pointed out the lack of Fabric documentation around how to configure an Intermediate CA with a Fabric Root CA and pointed to the questions in the RocjetChat #fabric-crypto channel around this. He demonstrated how he reverse engineers some of that process using the logs in the VSCode extension. Suggestion was that he start a Jira requesting that this information be added to the Fabric CA Operations Guide and we start the discussion there to get the right people involved. He said this is truly a barrier to adopting Fabric.
Video of this week's session at: Recordings