2019 Q3 Hyperledger Quilt
Created by David Fuelling, last modified by Mark Wagner on Sep 26, 2019
Project health over Q1/Q2 of 2019 has been poor, although I (David Fuelling) would like this to improve in Q3 2019 and beyond. Some things that have changed over the past month that are important to note:
1) The TSC decided that the Quilt project should be limited to Interledger (ILP) Java, which is its current charter (i.e., the “reboot” will not proceed ). While I supported the reboot and at the time was unable to assume leadership of the Quilt project, I am now in a position to actively maintain the project, especially since it will be limited to an Interledger Java focus.
2.) There has been renewed interest in Interledger Java, even over the past month. First, organizational support is expanding around ILP Java, so I expect there to be at least 3 full-time engineers (myself included) with bandwidth to focus on Quilt and Java software built around Quilt by the end of Q3 2019. Additionally, the project has recently had a new unaffiliated contributor who has begun submitting PRs , so by the end of Q3, I expect project health to be improved as compared to H1 2019.
Given the various potential changes discussed in Q1/Q2 2019 in the Quilt project, there is confusion around the focus of the project, who will lead it and maintain it, and what its future will be. I am interested in revitalizing the Quilt project and begin shipping ILP code around it. However, if the TSC feels that this effort is too late, or the charter of the project doesn’t align with the broader focus of Hyperledger, then this is potentially something to clarify.
To this end, I sometimes find it difficult to know what is expected by the TSC in terms of tasks or reports that project maintainers should be delivering. This is likely just because I have never filled this role before (prior to the reboot these tasks were performed by a maintainer who is no longer able to contribute), but I was unaware of this page , as an example. Are there other TSC reporting requirements of the project lead other than these reports?
Quilt has had only SNAPSHOT releases thus far. However, we are targeting a 1.0 release of Quilt Core (see remaining tasks here ) by the end of Q3. Follow-on deliverables will be identified after this release.
Overall Activity in the Past Quarter
Activity over the past quarter started off light. However, in late August/early-september, activity picked-up ( 5 PRs were merged). From mid Sept to the end of the month, participation and activity has been very robust , with many tasks completed towards providing Interledger STREAM support in the Quilt library (this will allow Quilt clients to interact with Interledger Connectors for the first time!).
We are currently planning to release v1.0 of Quilt by Sept 30th,
- This will include core libraries to support ILP sender & receiver functionality, including support for the STREAM protocol, which will be a large enabler for applications built on top of Quilt libraries. Th”at said, today’s Quilt is currently limited to core-libraries underpinning ILP (IL-DCP, BTP, Core packets, OER serialization, etc). Over the coming month we will be discussing potential additional contributions to the project, including an ILP Sender, ILP Receiver, and possibly an ILP Connector/Router as well.
Two new maintainers have been added in Q3: ( https://github.com/nhartner ) and ( https://github.com/theotherian ). Including myself, there are now three maintainers. While our technical diversity is strong, we are all funded by the same company, so from this perspective diversity is low.
Currently contributions are coming from developers at Ripple/Xpring and the University of Washington (e.g., https://github.com/sudheesh001 ), with some less regular contributions coming from developers at Coil .
Not at this time.
- ✅ Arnaud Le Hors
- 🔲 Baohua Yang
- ✅ Binh Nguyen
- ✅ Christopher Ferris
- ✅ Dan Middleton
- ✅ Hart Montgomery
- ✅ Kelly Olson
- ✅ Mark Wagner
- ✅ Mic Bowman
- ✅ Nathan George
- ✅ Silas Davis
Thanks for the update, David. Probably a good idea to subscribe to the tsc and maintainers lists.
If you aren't sure about a maintainer process you can ask on the community architects channel on chat or email:
Posted by email@example.com at Aug 13, 2019 11:41
I don't think anybody has an interest in killing this project if it can live. So, I encourage you to take the time to try and make progress and see what comes out of it.
To answer your question about what is expected from the TSC I would say that we primarily want to make sure the project still has a heartbeat.
Posted by lehors at Sep 23, 2019 13:06