- The core code-base continues getting cleaner and more modular. The goal is to make many of the internal features behave like plugins, following a general schema. Based on this approach, contributors can easily add new features in a well-defined, localized manner, without being familiar with the entire code-base.
- The documentation pages are also being improved to provide a top-down introduction into Caliper's architecture and further technical details. Hopefully, a quick overview of the important parts of a Caliper project will help users navigate the available examples easier.
- Caliper is now continuously published to NPM and DockerHub upon every merged PR, providing immediate access to experimental features in the same manner as a stable release does.
- Community relations mainly happen on Rocket.Chat, and the questions are answered in detail, and on time. Furthermore, there is an increasing contributor/user interest related to the supported DLTs (Besu, Fabric v2).
Questions/Issues for the TSC
There are no issues at this time.
- v0.3.0 was released on the 4th of March, 2020 (GitHub release notes). Fun fact: the "release button" was pressed live during Nick Lincoln's Global Forum presentation on Caliper.
- v0.3.1 patch is coming soon with Fabric v2 support.
Overall Activity in the Past Quarter
- Project stats (since the last report)
- Issues closed: 33
- PRs merged: 58
- MQTT-based messaging was added for the master and worker processes to support truly distributed Caliper deployments, i.e. horizontal scaling.
- Enhanced the Caliper CLI and the Docker image to make the distributed usage easier.
- Continuous delivery was implemented to provide unstable releases upon every merged PR.
- The previously deprecated Hyperledger Composer support has now been removed.
- The introductory pages of the documentation have been restructured and improved.
After the v0.3.1 patch for Fabric v2 support, v0.4.0 will address the followings:
- Identify the parts of the code-base that fit the description of a "plugin" (like performance and resource monitors in the master process, TX monitors in the worker processes).
- Make such plugins as object-oriented as possible, following strict interfaces and life-cycle management.
- Streamline data flow in/between the Caliper processes, thus simplifying the code-base and improving performance and robustness.
Subsequent releases will target the improvement of platform supports, starting with the existing adapters.
The list of maintainers remained unchanged since the last report.
There are currently 32 contributors to the repository, 17 of them with more than one commit. To the best of our knowledge, contributors are from various companies/organizations, such as Huawei, IBM, Intel, Soramitsu, Budapest University of Technology and Economics, Monax and the University of Oregon. The maintainers are also keeping in touch with other companies who are mainly interested in expanding the platform support of Caliper (e.g., with Corda).