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

Hyperledger Cactus Quarterly Report

Project Health

As a brand new project, Hyperledger Cactus seems to be building momentum.  We have had a number of new people (outside of the core Accenture/Fujitsu group that founded Cactus) participate in our meetings and, in some cases, even contribute.  We have presented in the architecture and identity working groups, where we have also garnered a good amount of project interest.  Mostly, however, we are just thrilled to be done with the initial bureaucracy around getting a project approved and set up, and are very happy that we can finally spend most of our time on the architecture and code.

Questions/Issues for the TSC

We don't have any issues or questions for the TSC at this time.  As we roll out interfaces for different Hyperledger blockchains, though, we would appreciate reviews and comments from people affiliated with said blockchains.  So please expect contact from us in the future!

Releases

We have not had any notable releases of the combined Cactus codebase, although there are previous releases of the BIF and ConnectionChain.  We hope to have a full Cactus release in the not too distant future.

The releases will be pushed to npm and in a monorepo format but under the npm scope of @hyperledger meaning that the project name will not be the npm scope but rather just a prefix prior to the package name. This makes it much wordier for the package names, but the upside is that we are consistent with the global Hyperledger npm scope. So the package names will be like this for exmaple:

  • @hyperledger/cactus-cmd-api-sever,
  • @hpyerledger/cactus-common
  • @hyperledger/cactus-sdk,
  • etc.. 

It is not too late to change the package naming theme if the TSC would rather have us our own npm scope such as:

  • @cactus/cmd-api-server
  • @cactus/common
  • @cactus/sdk

Which is easier to read (less verbose), but may be confusing to users who expect all legit Hyperledger projects to publish under the same @hyperledger npm scope.

Overall Activity in the Past Quarter

The focus of the project at this point has mostly been getting all of the infrastructure set up and working on a modular, combined architecture.  There has been quite a bit of coding going into this as well, but the priorities have been focused on infrastructure.

Current Plans

Our plans are essentially the following:

  1. Finalize our plugin architecture, down to minute specifications needed for implementation.
  2. Merge all of the functionality from the Fujitsu and Accenture solutions into our plugin architecture.
  3. Add functionality for immediately needed use cases.
  4. Design future architectures for things that are needed to scale Cactus to bigger use cases, such as identity management.

Maintainer Diversity

We currently have four maintainers.  They are:

Shingo Fujimoto – Fujitsu

Jonathan Hamilton – Accenture

Peter Somogyvari – Accenture

Takuma Takeuchi – Fujitsu

We are more than open to adding additional maintainers outside of the core Accenture/Fujitsu group, and hopefully in the not too distant future.

Contributor Diversity

We recommend the following for detailed contributor information:  https://lfanalytics.io/projects/hyperledger%2Fcactus/dashboard.  Thanks Ry!

That being said, our contributors are (in lexicographical order) as follows:

Rafael Belchior – Technico Lisboa

Patrick Erichsen – Target

Shingo Fujimoto – Fujitsu

Jonathan Hamilton – Accenture

Tracy Kuhrt – Accenture

Hart Montgomery – Fujitsu

Sownak Roy – Accenture

Peter Somogyvari – Accenture

Takuma Takeuchi – Fujitsu

程阳 – Aliyun

Additional Information

Thanks for reading this!  

Reviewed by


  • No labels