Todd Benzies <tbenzies@...>
Technical Steering Committee (TSC) Meeting
May 26, 2016 (7:00am - 8:30am PT)
Deutsche Boerse Group
Richard G. Brown
Action Item Review
TSC representation policy draft (Chris Ferris)
Whitepaper review (Dave Voell)
June (virtual) Hackathon (Todd Benzies)
July Hackathon (west coast) (Todd Benzies)
Exit criteria summary (Chris Ferris)
TSC Representation Policy
HIP: IBM-DTCC Joint Proposal for Java Chaincode Support (Murali, Pardha, Sheehan, Muralidharan)
Requirements WG (Oleg Abdrashitov)
Working on financial use cases… swaps, interest rate, etc.
Different trading scenarios (OTC, exchanges, etc.)
Need help from different members to validate use cases
DIscussion on how much of implementation of workflow detail to include in the use cases (only user stories? ...or propose how they can get implemented to solve something?)
Equity contracts and fixed income
Trying to complete financial use cases as first milestone
Architecture WG (Ram Jagadeesan)
Met yesterday -- good progress on understanding consensus module and smart contract business logic layer and how the two interact
Previously decided to use slack -- yesterday, decided to setup a mailing list for deeper discussions w/ appropriate contract
Would like to have use cases and requirements baked before more detailed discussions on architecture -- but, while we wait, decided to pick up more obvious topics with understanding of requirements. Picked functionality and interaction consensus module and smart contract business logic layer.
2 approaches -- one is more closely aligned with bitcoin style mechanisms and STL… other is fabric folks developing and documentation for requirements of confidential transactions (meet confidentiality requirements). Trying to determine, can we align on one approach?
Whitepaper WG (Dave Voell)
RGB: feedback sent via email to technical-discuss.
Lots of unsupported assertions throughout paper, primarily about value of blockchain technology -- need these to be justified. Stuff is not yet deployed, we don’t know for sure.
A lot of assumed knowledge in paper -- terms used without being introduced or defined. We know that these terms are evolving in their interpretation. Benefit from defining terms or providing a glossary so that there isn’t misinterpretation.
Vision -- reader is left at end wondering what vision is. Closest we got was vision is that lots of different blockchains need to be built from the same underlying architecture. Not particularly inspiring and it may or may not be true. Could make argument that modularity is desirable based on things like Linux…. But, this is not entirely clear or justified.
Quality of prose needs to be raised -- this may come out in editing at end. Just needs some general fixing.
Section labeled requirements… but it doesn’t really have any requirements. Should say “must” “should” “may”.... as opposed to a sales pitch.
Paper does not yet adequately establish vision of HLP as a whole…. i.e. architecture onwards is mainly focused on OBC… didn’t focus on the high-level project with projects in incubation under that… also doesn’t seem to be any focus on STL.
DV: Great feedback! We’ll take all these points in consideration. Requirements, for example, this is not meant to be requirements doc. Just wanted to provide some examples that would be illustrative of features we’d like to do. Did receive other feedback from form that there were more examples of use cases, requirements, and want to have those ideas transferred over the Requirements WG. Remainder of comments are really excellent.
Whitepaper Draft v0.1 (published May 19, 2016)
Please provide feedback to the Whitepaper working group through our Feedback Form
Request for everyone, especially TSC members, to read through and add edits prior to this draft going to the Governing Board
DV: Group met yesterday. Confirmed that strategy is to publish a new draft every other week. Process is to review feedback and discuss, assign people to do updates (or live on call), following week would incorporate input and push out a new draft version.
Brian -- consider posting incorporated feedback to announcement list…. But, try to have as few channels for feedback as possible. This is a foundational document -- people will be rallying around this. Most common watering hole is the technical-discuss list. Once you are ready for broader input… try to focus comments on technical-discuss and on google doc (add comments) so people can build on each others comments.
Identity WG (Christopher Allen)
Did not meet this week (only bi-weekly).
Next Wednesday should have IBM membership services team present a deeper dive into architecture and a bit about cryptography and confidentiality support that membership services feature of fabric demonstrates. Have not yet received confirmation, but hopeful.
CI WG (Chris Ferris)
Jenkins up and running -- getting it to spin out slaves onto alternate platforms
Need to do some work to integrate with slack/email
Gerrit is stood up… but only actively using for CI pipeline right now… and spinning up Jenkins jobs
Eventually want to transition other things as well
ACTION: Todd to schedule an overview training session “immersion into using Gerrit” (or maybe during TSC call).
Please jump on CI pipeline channel on Slack.
Would love to see process of STL transitioned over. Tamas -- for Fabric API buildout, if there is something we can do to help transfer over build processes to LF Jenkins, that would be great.
Finalize June (virtual) Hackathon (Todd)
Finalize July Hackathon (west coast) (Todd)
Schedule an overview training session “Immersion into using Gerrit” (or maybe during TSC call) (Todd)
Exit Criteria Summary (Chris Ferris)
Senior Program Manager
The Linux Foundation
+1 (415) 412-0310 (m)