Hyperledger Project

Technical Steering Committee (TSC) Meeting

Hyperledger Project - Technical Steering Committee (TSC) 04.27.17.mp4

April 27, 2017 (7:00am - 8:00am PT) via GoToMeeting

TSC Members

Arnaud Le Hors


Binh Nguyen


Christopher Ferris


Dan Middleton

Greg Haskins


Hart Montgomery


Mic Bowman


Murali Krishna Katipalli


Richard Brown

Sheehan Anderson

Tamas Blummer



Hackfest/Hackathon Planning

  • DC Hackfest recap
    • 65 participants -- great mix of familiar faces and new faces
    • Activity that transpired at the Hackfest
  • Beijing, June 17-20
    • June 17-18 Hackathon
    • June 19 Hyperledger track (sessions just finalized, will be announced soon)
    • June 19-20 Hackfest
    • No objections.

Top-level project vs. sub-project discussion

  • Hart had proposed establishing a dependency graph amongst the various projects for when a project is presented for incubation (rather than projects vs. sub-projects) and that the TSC establish certain interdependencies amongst projects and if a dependency exists, the maintainers of that depended on project would weigh in on the proposal and its merits as an input to the TSC decision making process.
  • At the Hackfest there was support for the idea that when marketing projects, the list of projects does not need to represent the TSC organizational view (i.e. SDKs), instead present a “product” view.  This would slim down existing projects when publicly facing. 
  • Suggest a regular reporting structure (once per month for report outs)
  • Q:  As an example, Fabric SDKs would be part of Fabric report?
    • Brian:  The marketing of projects would be that Fabric SDKs would be part of Fabric pages.  From TSC and organizational view it would be an independent project reporting separately to TSC.
  • Hart:  There are two mostly separate issues here: project governance (through dependencies) and project proposal changes. It seems like there was wide consensus to maintain the flat project structure on email, so that should probably stay as is. The consensus for the project proposal changes seems that we should require project proposals to include sign-offs from experts so the TSC can be confident in the project merits.
  • Suggestion to add expert review or endorsements to project template.
  • ACTION:  rework draft proposal and bring back to TSC for vote on May 4th TSC meeting.

Performance and Scalability Working Group

  • Mark Wagner gave an overview of the proposal, which was also discussed during the Hackfest
  • A suggestion was made to benchmark different configurations, as opposed to different projects.
  • A suggestion was made to detail out associated terminology/definitions so that everyone is clear.
  • VOTE:  Unanimous.  APPROVED.

Actions + On-going

  • Hackfest/Hackathon planning (Beijing, June 17-20)
  • No labels