2016 03 10 TSC Minutes

Hyperledger Project

Technical Steering Committee (TSC) Meeting

March 10, 2016 (7:00am - 8:30am PT)

via GoToMeeting

TSC Members

Resources:

Agenda

Technical F2F

CF: Building out set of stories that we need to be driving. Hope that Tamas and team will be doing the same. Session for requirements and use cases. Session for project lifecycle and proposals. Session for code of conduct.
Q: Can anyone bring use cases?

Yes. This will come through the WG run by Patrick to build consensus… and then this would go to TSC.

In general -- requirements and use cases for what hyperledger is doing in general.

Requirements Committee

Current volunteers (Tamas, Benedickt, Igor, Primrose, Judy, Stefan, Emmanuel, Nikilesh)
Email patrick.holmes@intel.com if you want to participate
Started collecting use cases, will create a repository for these
Need to determine the scope of use cases (can be part of the Technical F2F)

White Paper

DAH/IBM

IBM put code into incubator repo, DAH to push code soon.
https://github.com/hyperledger-incubator
CF: from IBM perspective, working on some of the aspects of the proposal.
Binh: Look at OBC repo at this point, number of issues created to work toward that and prepare for F2F. Specifically, looking at ability to integrate an interpreter. Picked up interpreter from Bitcoin. Tried to call that from chain code. Prototype ability to pass in a Bitcoin transaction through OBC system, to the interpreter, to be able to turn around and update the transaction log. Hope to show at F2F.
Shaul: done a lot of work on binding to bitcoin interpreter. Feel free to ping DAH on any help needed.
Binh: Couldn’t find DAH interpreter, so went with Bitcoin interpreter. Though, this would be an easy switch if needed. Shaul can point to this.

Code of Conduct

Project Proposal Template

Proposal Template for a Hyperledger Improvement Project (HIP).pdf
Vipin: Reworked document from previous suggestions suggestions (i.e. licensing and trademark has been added). Tried to make it function more as a template, with the sections in bold and also removed any strong language about using this particular format to handle the solutions. If the solution does not require this certain section to be handled, left it open in that sense. Goes through list of various possible sections you should address in solution.
Q: what is definition of a team champion?

The person who is driving project proposal (will update to make plural so that multiple people can drive the proposal for continuity, in case someone were to leave the project)
Comment: need to know who the initial maintainers are, don’t necessarily need “project champion”

Vipin: “how to” was meant to address that. But, could include what you just said as well.

Note: Once approved, does not preclude changes down road.
CF: this is getting very close. Please review doc and add any comments or suggestions. Try to close on this next week.

Project Lifecycle Proposal