2018 02 01 TSC Meeting
Hyperledger Project
Technical Steering Committee (TSC) Meeting
February 1, 2018 (7:00am - 8:00am PT) via GoToMeeting
TSC Members
Arnaud Le Hors | Yes |
Baohua Yang | Yes |
Binh Nguyen | Yes |
Christopher Ferris | Yes |
Dan Middleton | Yes |
Greg Haskins | Yes |
Hart Montgomery | Yes |
Jonathan Levi | Yes |
Kelly Olson | Yes |
Mic Bowman | Yes |
Nathan George | Yes |
Resources:
Rocket.Chat: chat.hyperledger.org (you can use your LFID to login)
Github: www.github.com/hyperledger
Public lists: lists.hyperledger.org
Meetings: wiki.hyperledger.org/community/calendar-public-meetings
Congrats to Hyperledger Sawtooth team on 1.0 release!
2018 Hackfest Planning
February 20-22 | Los Angeles (registration | draft agenda)
April 29 - May 1 | Dubai (tentative -- more details soon)
*registration now open* June 27-29 | Amsterdam (registration | draft agenda)
2018 Hyperledger Internship Program
Project reporting
ACTION: Composer Maintainers to complete Hyperledger Composer update
Quarterly WG updates
Tracy merged all edits from the previous TSC call
VOTE: unanimously approved
ACTION: Tracy to update wiki and move reporting schedule to start a bit earlier.
Confidential security bug handling for all Hyperledger projects
Dave Huseby provided a recap of the his thread
In the process of finding a consultant to modify Jira to modify processes in place.
Hope that projects move away from GitHub issues to Jira. Not _required_ to use this, this is just for security issues.
Connect with Dave if you want to participate.
How many projects using Github issues? Composer, Quilt, Iroha, and Burrow
FYI that Iroha uses non-Hyperledger Jira + GitHub issues, they need to move over.
DH: should a project decide NOT to use Hyperledger Jira, they will need to post very publicly “if you are reporting a security issue, email security@hyperledger.org or report it through Jira so that is is properly handled.”