Page tree
Skip to end of metadata
Go to start of metadata

Project Health

Project health is unchanged from the previous quarter (I would mark it as neutral-to-unhealthy). Contributors have dropped to just one (me, David Fuelling, the primary maintainer) due to changing priorities at the companies that have historically funded development of Interledger and Quilt. Contributions to the project over Q1 were also neutral: there were only two commits to the project, although one introduced substantial new functionality in the form of ILP-Pay (a port of the JS client application of the same name) allowing for more robust micro-payment sending using the STREAM protocol.

That said, my own ability to contribute to Quilt will likely be reduced during Q2 and Q3, so while no major bugs have been identified in Quilt, adding new features is not currently a high priority because there are no external customers or developers seeking to deploy Quilt or the Java ILP Connector, at the moment. Until this changes, I will likely focus my priorities elsewhere.

On the bright side, however, there are a number of developer-grant programs spinning-up that will focus on Interledger (e.g., Coil/Mozilla's Grant for the Web) and crypto in-general, so it will be interesting to see how developer and/or corporate interest in Interledger evolves over 2021. If this increases, it's likely that I will have more cycles to contribute, and also likely others who have historically contribute to the project would also have cycles to contribute to Quilt.

That said, if project health continues in this direction, we should consider moving Quilt into a dormant/maintenance state potentially, or become more comfortable with few contributions (at least over the short term 1 or 2 quarters)

Required Information

  1. Have you switched from master to main in all your repos? Not yet, but there is an issue filed to perform this change (see here).
  2. Have you implemented repolinter.json in all your repos? Not fully, but see this issue that is half-complete.

Questions/Issues for the TSC

What happens to a project when it goes through a "lull" in contributions, such as what Quilt is experiencing now? There was some discussion awhile back by the TSC around "project states", but I haven't been tracking the TSC closely enough to know the current state of these discussions, or current HL process. Any pointers would be helpful.

Releases

No new releases. Most recent release was August, 2020.

Overall Activity in the Past Quarter

Outside of the primary contributor, there is no developer activity (e.g., no new issues filed in Q1, no external participants via email or community call).

Current Plans

See the "Project Health" section above. Quilt development will likely be paused for some months.

Maintainer Diversity

No new maintainers. David Fuelling is the primary maintainer, though technically these people are the core maintainer group and can address bugs. However, nobody has new functionality planned.

Contributor Diversity

Contributor diversity is low, and unchanged.

Additional Information

None at this time.

Reviewed By


2 Comments

  1. Any idea how many people are actually using Quilt?

    1. Don't know. Maybe maintainers/Hyperledger staff can get it. But we could think of introducing a `dormant` state for project. I see a request here not to go to end of life but rather stack the current release for a while until an external force to do so is available.