2019 08 08 TSC Minutes

(7:00am - 8:00am PT)

via Zoom

Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: Hyperledger Code of Conduct

TSC Members

Present?

• Arnaud Le Hors
• Baohua Yang
• Binh Nguyen
• Christopher Ferris
• Dan Middleton
• Hart Montgomery
• Kelly Olson
• Mark Wagner
• Mic Bowman
• Nathan George
• Silas Davis
  

Resources:

• Chat: chat.hyperledger.org ( use your LFID to login )

• Github: www.github.com/hyperledger

• Wiki: wiki.hyperledger.org /

• Public lists: lists.hyperledger.org

• Meetings: wiki.hyperledger.org/community/calendar-public-meetings

Announcements

• TSC election nomination phase
  • Contributors can be automatically pulled from the code repos. 
  • WG Chairs need to submit contributor lists to Ry Jones
  • Ry is gathering the master list of contributors.

Items of discussion

• TSC Election
  • Tracy described how the TSC election went last year.
  • Chris reminded us how the original TSC was set up and asked what people think of expanding the TSC membership now that Hyperledger has grown.
    • General support for this idea exists but there are concerns about growing the TSC too big.
    • Chris pointed out that the board is up to 21 and that we're up to 14 projects and a few more about to come in and the TSC is still just 11 people.
    • Ry suggested adjusting to add a rolling quorum too to deal with needing more people to be present for quorum.
    • Brian shared an idea of adding 6 more appointed people to the TSC that would be appointed by the elected TSC each year.
    • Dan suggested to defer this to the mailing list and to be taken up by the new TSC to take to the board if they decide.
• Project Lifecycle Task Force - (Arnaud J LE HORS)
  • Vote on three resolutions.
  • Issue 1: When do we know that a project is "done"? What are the end-of-life criteria?
    • Should we rename end-of-life to archived? EOL is not a new state and is in the existing lifecycle document.
    • The proposal is to adopt both 1.1 and 1.2 resolutions.
    • Vote: unanimously in favor, zero opposed, zero abstained.

  • Issue 7: How/when does a project get officially names?

    • The hope is that a proposal comes with a name that is acceptable at first and the marketing committee will weigh in on the rename. 
    • Vote: unanimously in favor, zero opposed, Silas abstained (because he was late tot he conversation).

  • Issue 8: How do we deal with a new project coming in that is already a shipping product for a company?

    • Vote: unanimously in favor, zero opposed, zero abstained.
  • Two major issues left to be dealt with in a future TSC meeting.
    • Issue 2: What ar
    •    e the criteria for a "First Major Release"?
    • Issue 6: Should we have subprojects (and fewer toplevel projects)?
• Housekeeping
  • CI/CD Committee
    
    • https://lf-hyperledger.atlassian.net/x/5BD5
  • Working Groups Committee
• New Project Proposals - are we ready to vote and/or archive?
  • Justitia
  • Gardener

Quarterly updates

• 2019 Q3 Hyperledger Burrow
  • Ask is for people to run through the documentation to see what works and what doesn't.
  • Suggestion was to connect with people at the Brazil bootcamp that did a great demo of Burrow.
• 2019 Q3 Hyperledger Indy
  • Working on the split of code from the Indy code base to the Aries code base. Progress is being made but there is some coordination going on between the Decentralized Identity Foundation and the Aries project on the standards around the wallet layer.

Upcoming items

Backlog

• Github/Jira/Confluence integration to enable Open Planning and Ambassador program (Silona - TBD)
• Working Group Structure (Mic Bowman - Date TBD)
• Project Lifecycle Committee Report (Arnaud J LE HORS - Date TBD)
• Project Pipeline Direction
• Smart Contracts Diagram submitted by sterzi
• Centralized decision record

Recordings

• dummyfile.txt
• dummyfile.txt