February 07, 2019 (7:00am - 8:00am PT)
- Arnaud Le Hors
- Baohua Yang
- Binh Nguyen
- Christopher Ferris
- Dan Middleton
- Hart Montgomery
- Kelly Olson
- Mark Wagner
- Mic Bowman
- Nathan George
- Silas Davis
- Still looking for mentors for the summer internship program.
- Intern applications will happen next month.
- Propose a new internship project here.
- Quilt architecture regroup process started yesterday.
- Quilt meetings are on the calendar.
- Tracy Kuhrt is leaving us. Her last day is the 12th.
- She's staying on as a Labs steward.
- Lots of thanks Tracy!!
- 2019 Q1 Hyperledger Fabric Update
- First long-term support (LTS), version 1.4 was released in early January.
- Coming soon: 1.41, fixes for the LTS.
- Coming soon: 2.0, new features.
- Overall health:
- Still very popular
- Contributors numbers are stable
- Recent presentation at Univ. of Waterloo
- Started with 3.5k tx/sec and with optimizations increased that to 20k tx/sec.
- Open source works well. Despite all of the work so far, a researcher came in and drastically improved performance.
- One issue is that non-regular-contributors submit PRs but they are having difficulty getting them reviewed.
- Maintainers and contributors have had discussions about it.
- There's a RocketChat channel #fabric-pr-review is for asking for reviews.
- Automating PR review nagging of maintainers.
- Any PR's that don't get responses from the submitters will be archived.
- Any PR's tied to a JIRA will not close JIRA ticket if PR gets archived.
- Brian suggests
- In a move from 1.x to 2.x we are tolerant of backwards compatibility
- Fabric should make some moves to interop more.
- Fabric project is looking forward to Ursa and to Burrow integration.
- Fabric and Burrow integration resulted in mutual bug discoveries and fixes.
- 2019 Q1 Hyperledger Indy Update
- Lots of growth.
- Two new use cases are live on Sovrin mainnet.
- 2M credentials in production.
- Agent side of codebase is growing most.
- Lots of standards work around edge protocols and specifications.
- Sovrin Provo, UT Office is hosting agent connect-a-thon February 19-22.
- Organizations from all over the world coming together to test agent-to-agent communications.
- Lots of stability changes in main ledger.
- Lots of changes in SDK.
- Next release is 1.8.
- Release of 2.0 will have new wallet features and will use Hyperledger Ursa.
- Expected before next quarterly report.
- The new design work for 2.0 is already underway.
- Indy is moving over to Hyperledger Ursa for crypto abstraction.
- Have not completed all of the CII badge requirements.
- However all of the changes have been merged, but infrastructure issues are slowing things down.
- Project Health
- One maintainer has shifted away, however new contributors and maintainers have joined to fill in.
- Indy Catalyst has moved towards the main codebase.
- Reaching out to Streetcred group to coordinate agent work with their .Net implementations.
- Proposing a new wallet codebase as new project that will lead to cross-ledger compatibility.
- Project proposal is being drafted now.
- Expected after release of Indy based on Ursa.
- Been moving build infrastructure out of Evernym.
- Some trouble moving to Hyperledger infrastructure is difficult, especially with Android and iOS build support.
- Hyperledger Ursa CI/CD fixes should help with Hyperledger Indy migration.
- Working with Sawtooth team to coordinate cooperation so that interop can increase.
- What are the greatest challenges that the Indy team is facing that the HL staff could help fix?
- The build infrastructure seems very focused on Fabric.
- The Ursa build work is shifting that somewhat.
- There are a lot of client build requirements which presents a challenge.
- Thank you Tracy and Ry working with the Indy team getting them through issues.
- Turn-around time is slow while working out mismatches in requirements.
- Done a good job at bringing in outside contributors. How much time does the Indy team spend on recruiting additional contributors?
- Is it worth it? Yes, spending time recruiting has yielded success.
- The team has also experienced PRs from new contributors stalling, like Fabric.
- Spending time on getting new contributors introduced and plugged in seems to help.
- Nathan estimates that he spends about 20% of time recruiting.
- Sovrin developers focus on building developers moreso than building code.
- Maintainers spending 20-30% of time recruiting new contributors seems like the minimum. –Brian
- Does Indy/Sovrin host a user-focused call around users of the platform?
- Have had a call in the past.
- It has shifted to be more offline recently.
- Several companies in consulting ecosystem are doing consulting.
- Working to resurrect user-facing support and educational materials and training opportunities in healthcare/financial/government verticals.
- Is the user-facing coordination happening through Sovrin?
- A lot of it is.
- Hyperledger also serves as an important platform for doing the coordination.
Items of discussion