Re: Hyperledger Cactus Name Change Proposal
Hi Rama, All,
I accept the name change and am also very happy that we'll be working together! This is a huge milestone for the project, and I am very excited about the future!
I'd like to thank all the maintainers and contributors for all your efforts and help in the past, present and future! We are just getting started! 😉
Copying the mailing list as well to keep everyone in the loop and to open it up for comments from the community. With that said, I do consider the decision final at this point given the unanimous agreement by the maintainers.
Accenture Products & Platforms (APP)
Office: +1 (415) 537-5541
Mobile: +1 (650) 488-1741
From: Venkatraman Ramakrishna <vramakr2@...>
Sent: Monday, September 5, 2022 10:49 AM
To: sato.izuru@... <sato.izuru@...>; Somogyvari, Peter <peter.somogyvari@...>; takeuchi.takuma@... <takeuchi.takuma@...>; Sandeep Nishad1 <Sandeep.Nishad1@...>; Krishnasuri Narayanam <knaraya3@...>; Dhinakaran Vinayagamurthy <dvinaya1@...>; Sasan, Jagpreet Singh <jagpreet.singh.sasan@...>; shingo_fujimoto@... <shingo_fujimoto@...>
Cc: Hart Montgomery <hmontgomery@...>; Arnaud Le Hors <lehors@...>; Kuhrt, Tracy A. <tracy.a.kuhrt@...>; Vinayaka D Pandit <pvinayak@...>
Subject: [External] RE: Hyperledger Cactus Name Change Proposal
Thanks a lot, Izuru and the Fujitsu team!
From: sato.izuru@... <sato.izuru@...>
Dear Weaver and Cactus maintainers, Thank you for proposing the name. Fujitsu is happily accepting the proposed project name “Cacti” for the merger of Cactus and Weaver projects. We are looking forward to smooth transition process to retain
Dear Weaver and Cactus maintainers,
Thank you for proposing the name.
Fujitsu is happily accepting the proposed project name “Cacti” for the merger of Cactus and Weaver projects.
We are looking forward to smooth transition process to retain user bases of both projects.
From: Venkatraman Ramakrishna <vramakr2@...>
Dear Cactus and Weaver Maintainers,
I'd like to propose that we adopt the name “Cacti” for the Hyperledger project that results from a merger of the Cactus and Weaver systems (architecture as well as code bases). This name was suggested by the Hyperledger management and came up in one of our earlier discussions.
The name "Cacti" simultaneously conveys several things:
- Given the similarity with "Cactus", it indicates continuity for the Cactus project, telling existing contributors and users that the project lives and thrives, albeit in a new avatar.
- The change from singular to plural indicates that the new project contains a multitude of approaches and features for solving the kinds of interoperabilty problems that drew existing users (and clients) to our respective projects in the first place. But the fact that these approaches are offered through a common platform tells users that there is a common core to the interoperability system, and a common design philosophy and objectives, offered by Hyperledger Cacti.
- It indicates that the Weaver project is not dead but lives on under a new banner. Existing Weaver users need not worry about the shelf life of the system they are currently using or experimenting with, nor about Cacti maintaining backward compatibility for their networks and applications.
- Related to the above point, it indicates that the new project is a merger of two projects rather than one project getting subsumed into another. The new project preserves the cutting-edge technical features and spectra of use cases provided by both without eliminating anything.
From a Weaver maintainer's perspective, I'd like to emphasize that we have been working on the platform code and use cases as well as publishing on the topic since the latter part of 2019. Even though we open sourced the code only in 2021 as a Lab, it has garnered a significant amount of interest as well as active use. It is therefore important that we don't lose or confuse the Weaver community but bring both the Cactus and Weaver communities together.
Therefore, I really hope that the Cactus maintainers will be willing to consider and accept this name change. Please indicate your preference by replying to this email thread.
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.