2018 09 27 TSC Meeting

Owned by Ry Jones
Oct 01, 2019

Hyperledger Project

Technical Steering Committee (TSC) Meeting

dummyfile.txt

September 27, 2018 (7:00am - 8:00am PT) via Zoom

TSC Members

Arnaud Le Hors


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:


Event Reminders


Quarterly project update

  • Hyperledger Caliper update

    • Concerns raised:

      • Project update not complete and no one on call to provide update.

      • PSWG has not heard back from Caliper when they have pinged them.

      • Suggestion made to email the project mailing list (as opposed to maintainers) for updates, as well as ensure that maintainers are subscribed to TSC list.

  • October 11th: Hyperledger Fabric update


Quarterly WG update

  • None this week

  • October 11th: Healthcare WG update


Bug Bounty

  • Dave Huseby provided an overview of the recent discussion

  • VOTE:  drop down to email support and rely on security team for triage.  Unanimously approved.


Social Impact WG

  • Marta Piekarska provided an overview of the discussion

    • Suggestion for work products to identify gaps in technology needed for this area.

    • Is social good a standalone domain?  What do we gain from this umbrella?

      • Good lead in regarding several WGs that are sector specific WGs  that could potentially be called a SIG. A lot of interest in these groups come from business stakeholders (have discussions and explore space).  This is different from an implementation PoV. As we look at profusion of SIGs, do we want to codify this as a slightly different structure than a technical WG.

    • Does it make sense to have groups like this have deliverables in the same way the technical groups have deliverables?

      • Brian noted that it helps them feel more guided and focused on outcomes, whereas if it was just a talk shop, it would feel unguided.

    • Maybe recruitment effort be more unfettered get enthusiasm going without heavy process

    • Maybe have a structure so that when there are exceptional things to discussion, TSC is available to facilitate; but, not lose our DNA on development.

    • VOTE:  get Social Impact WG started, then figure out governance structure in terms of deliverables and outputs, to make sure they are syncing with technical community well (i.e. WG or SIG, etc.)

      • Approved.

      • ACTION -- Community Architects to set up mailing lists and chat channels and email co-Chairs.


Healthcare WG / Chair update


Hyperledger Community Health WG discussion

  • Has been some discussion in Marketing Committee to make sure we are messaging well

  • All Projects/WGs should know about Code of Conduct

  • Needs further discussion on this initiative