Versions Compared

Old Version 1

changes.mady.by.user 竹内琢磨

Saved on

compared with

New Version Current

changes.mady.by.user Danno Ferrin

Saved on

Key

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

Project Health

  • Cactus and Weaver were merged to one project "Cacti." Now we are preparing for moving codes and making the new Cacti repository.
  • On the original Cactus repository, we released Cactus v1.1.0 that resolved the issues from the comprehensive security audit of Cactus v1.
  • Cacti new architecture diagram is now discussed among the maintainers and this will be determined soon.

Required Information

  1. Have you switched from master to main in all your repos? Yes
  2. Have you implemented the Common Repository Structure in all your repos? Yes
  3. Has your project implemented these inclusive language changes listed below to your repo? You can optionally use the DCI Lint tool to make this a recurring action on your repo. Yes, we use DCI-Lint as part of our CI
    1. master → main
    2. slave → replicas
    3. blacklist → denylist
    4. whitelist → allowlist
  4. Have you added an Inclusive Language Statement to your project's documentation and/or Wiki pages? Yes

...

  1. We achieved the project merging of Cactus and Weaver. We are preparing the initial repository including Cactus and Weaver codes.
  2. We aim to bring as much Hyperledger interoperability work efforts together as possible to make the total output greater than the individual sums (code reuse enablement, shared testing infrastructure expertise, benchmarks, release management, etc.)
  3. The plan is to leverage our mono-repo project structure in order to make the above plans as painless/as low overhead as possible since we want to actively prevent bogging down everybody involved with administrative changes/refactorings/breaking changes required in the name of collaboration
  4. We continue to put effort into academic research (namely a research group within Hyperledger; several Hyperledger Summer Internships with a research component have been proposed and accepted).

Current Plans

  1. Currently there are some unstable behaviors of our CI scripts and our pull-requests are stopped to be merged, but we already made a counter measure and the problem will be fixed soon. => https://github.com/hyperledger/cactus/pull/2096

  2. After the above problem are fixed, we plan to finish the security audit of the 1.0.0 release and issue patch releases as necessary based on the findings (1.0.1, 1.0.2 etc.)The maintainers are planning the Cacti new architecture that is combined with the strengths of Cactus and Weaver. They will determine the Cacti v2 release plan and largely refactor the codes as the architecture.

  3. They are also planning about some supporting tools such as ledger explorer interface of Cacti.

Maintainer Diversity