2018 03 08 TSC Meeting
Hyperledger Project
Technical Steering Committee (TSC) Meeting
March 8, 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
- Wiki:Â https://lf-hyperledger.atlassian.net
- Public lists:Â lists.hyperledger.org
- Meetings:Â wiki.hyperledger.org/community/calendar-public-meetings
2018 Hackfest Planning
- Dubai - go/no-go?
- Agreement to not hold the event in April.
- Try to hold a Hackfest in Asia prior to the June Hackfest in Amsterdam?
- Needs further discussion.
- A suggestion was made to also consider a 1-day Hackfest after Consensus in NY.
- Hackfest format discussion
- Some in favor of having a roadshow to get regional folks up the learning curve vs. and entirely separate event focused on cross-project collaboration and hacking (some in favor of keeping them piggy-backed -- more time at fewer, longer events... less time traveling to many shorter events)
- Agreement that much more agenda structure and objectives planning needs to be completed in advance of the actual Hackfest, not in unconference format on the first morning.
- June 27-29 | Amsterdam (registration | draft agenda)
Hyperledger Internship Program
- Now accepting applications (please help promote)
- Deadline for students to apply is March 23rd
- Blog here
- Click to tweet: https://ctt.ec/b69P1
Quarterly WG updates
- None this week
- Next week:Â Requirements WG update
Quarterly project updates
1.0 before leaving incubation
- Thread
- No current policy in place that Active status is required before a 1.0 release -- but, should this be added?
- Concern that some of the smaller projects with smaller communities would be disadvantaged by requiring active status, even if they have a mature code base.
- Comment that if code maturity is not required to exit incubation, then why is project maturity a requirement for 1.0 (they seem to be independent).
- Concern that if an incubation project goes 1.0, it does send a signal to users that it will continue to exist, even if maintainers leave (so, maturity of the project community, process, etc. is important)
- Comment that 1.0 triggers a lot of work from Marketing, security audit & license scanning, etc. and also gives some level of endorsement from Hyperledger (community maturity and active status is more desired)
- Continue discussion via mailing list and rocket.chat -- will finalize in TSC call next week