Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Project Health

Cactus continues to progress as a project.  We have added a new, major contributor (Enrique Garzas, from Accenture) and expect that he will be promoted to maintainer in the not too distant future.   We have been better about responding to communication tools in a timely manner as well.  So Cactus has become healthier over time, even if not by leaps and bounds.

We are in active talks about cross-project collaboration with the aim of sharing at least some of the code among the different interoperability projects/labs that are out there, our stated goal is to have a compounding effect instead of fragmentation.
There's a comparison blog post underway as well as multiple different proof of concepts aimed at exploring how to achieve the above with Weaver and Firefly and also in general about being able to have runtime dependencies of the Cactus API server that were written in a different programming language but are possible to be compiled down to WebAssembly.

Required Information

  1. Have you switched from master to main in all your repos? Yes.
  2. Have you implemented repolinter.json in all your repos? Not yet.

Questions/Issues for the TSC

...

We have recently released version versions v0.4.0, v0.5.0 and a hot-fix to it as v0.4.1 (which was also a great test of our capability to rapidly issue releases when necessary). The changes in these releases are best described as moving towards a modular, efficient blockchain integration platform that can be used with both the Accenture and Fujitsu applications (as well as others). The precise changes in each release are much too long for this report, but thankfully Peter has done a wonderful job of documenting them here (https://github.com/hyperledger/cactus/releases). Please take a look if you'd like to see all of the release details.

...

Takuma Takeuchi – Fujitsu

In the not too distant future, Jonathan Hamilton is planning on retiring as a maintainer, and Enrique Garzas (also from Accenture) is planning on replacing him. We are more than open to adding additional maintainers outside of the core Accenture/Fujitsu group, and hopefully in the not too distant future.

...

...