2018 10 18 TSC Meeting
Hyperledger Project
Technical Steering Committee (TSC) Meeting
October 18, 2018 (7:00am - 8:00am PT) via Zoom
TSC Members
Arnaud Le Hors | Yes |
Baohua Yang | Yes |
Binh Nguyen | Yes |
Christopher Ferris | Yes |
Dan Middleton | Yes |
Hart Montgomery | Yes |
Kelly Olson | Yes |
Mark Wagner | Yes |
Mic Bowman | Yes |
Nathan George | Yes |
Silas Davis | Yes |
Resources:
Rocket.Chat: chat.hyperledger.org (you can use your LFID to login)
Github: www.github.com/hyperledger
Public lists: lists.hyperledger.org
Meetings: wiki.hyperledger.org/community/calendar-public-meetings
Event Reminders
APAC Hackfest -- week of March 4th (details coming soon)
Schedule announced for Hyperledger Global Forum, December 12-15 (Basel, Switzerland)
Supply Chain proposal
Dave Cecchi provided an overview of the proposal
Are there more details on generic components being built that could be more widely shared? Supply chain is a very general term that encompasses many thing -- what is your definition and specific set of capabilities?
The motivations are supply chain centric, but certainly components from this type of framework may have applicability to other market models. Typical use cases deal with logistics, track and trace, as well as multi-party distributed supply chain business enablement. Want to solve distributed supply chain problems.
Would it be useful for Hyperledger to define a transaction format that is generic enough to be used in a wide range of environments with similar commonalities (i.e. format with sender/receiver addresses with backpointers)
These problems have been solved outside of blockchain -- businesses have been transacting for a while. Looking for reusable components. As a platform, the components all need to work together.
What code currently exists? If this was put into incubation, what would land on Day 0? A lot seems to be centered around business process -- is supply chain as an umbrella project the best path?
Some code exists, but not production ready -- this is for incubation. Code from track and trace usage linked in proposal, as well.
Customer, counterparty/party, product or material -- reusable components that can be assembled into an application that would tie these primitives together.
Why wouldn’t existing standards for supply chain apply?
Yes, the standards exists… but, why aren’t they implemented and in open source (or Hyperledger implementation) yet.
Compare Hyperledger Composer with the scope of this proposal?
Composer is a tool to help people get ramped into blockchain and do code generation of business considerations.
For this supply chain project, not code generation, but to still facilitate coding business level concerns in delivering an application.
A suggestion was made to add this into the proposal.
A suggestion was made to create a non-generic name (not “supply chain”)
A suggestion was made to have some references to existing standards, and sequencing expectations on deliverables
Questions as to whether it is limited to this vertical or more broadly encompassing
Continue discussion via chat and mailing list
Quarterly project updates
Victor Hu provided the Hyperledger Caliper update
What is current level of communication between Caliper and PSWG?
For each PSWG meeting, one rep from Caliper will be there
Chris Ferris provided the Hyperledger Fabric update
Andi Gunderson provided the Hyperledger Sawtooth update
Is there a plan for testnet?
Loose plan was to get a starter testnet going where we raise nodes in different organizations, and do some basic integration testing across organizational boundaries -- then, look at more security-focused use of testnet
Are we still looking at testnet at a Hyperledger-level?
Dave Huseby is pulling together thoughts and a proposal for 2019 budget planning
ADD for TSC call next week
October 25th: Hyperledger Iroha update
Quarterly WG updates