Hi everyone, Here’s a brief summary of our *weekly Apache ResilientDB (Incubating)* community meeting held on *October 13, 2025* for those who couldn’t attend:
Attendees: Bismanpal Anand, Chenyi Zhou, Dakai Kang, Devang Borkar, Divyanshu Malik, Harish Krishnakumar, Henry Chou, Junchao Chen, Mohammad Sadoghi, Kenny Sun, Ketki Kulkarni, Shaokang Xie, Zehong Ruan This meeting convened key contributors to the ResilientDB project, with the primary objective of coordinating ongoing development efforts, advancing the Apache Incubation process, and fostering community growth. Participants reviewed recent achievements, discussed upcoming technical milestones, and emphasized the importance of collaborative action, transparent documentation, and active engagement from both core members and new contributors. The agenda was structured to facilitate constructive dialogue on project releases, critical features, deployment automation, and strategic plans for graduation, ensuring that everyone remained aligned and informed as the project moves forward. *Action Items: * - Review the Apache Incubator graduation checklist and work on completing the remaining items. - Dakai - Raise an issue for the Hot Stuff recovery mechanism and share it with Bismanpal and Harish to include in the university outreach project ideas. - Work on incorporating the Thunderbolt concurrency improvement technique in the next release. - Engage with the volunteers to involve them in developing new features and tools for the next ResilientDB release. - Research and ideate the gas fee and token system for the ResilientDB ecosystem. - Integrate the ResilientDB AI tools (Res Canvas, Res Chat, Res Share) into the monorepo. *Graduation Process and Community Growth:* The meeting addressed the Apache Incubation graduation process for ResilientDB, with Junchao reviewing progress on essential checklist items such as code readiness, licensing, documentation, and the need for comprehensive public release guides. The team agreed on collaboratively tackling remaining tasks, including outreach to other contributors and underscored the importance of regular announcements and transparent documentation for ongoing progress. Emphasizing community growth, Mohammad Sadoghi advocated for actively involving new developers, not only to contribute code and features but also to expand the pool of committers and core contributors, ultimately strengthening the project’s sustainability and fostering a vibrant, participatory community. *Next Release Planning and Feature Discussions:* Mohammad Sadoghi emphasized maintaining a healthy release cycle and invited input on potential features, with Junchao suggesting the checkpointing subsystem as a key addition and tying it to graduation goals. They also discussed improving execution performance through Thunderbolt and RDMA-based distributed connections. Dakai proposed enhancing the recovery mechanism for HotStuff and exploring extensions to other protocols in the HotStuff family. *Indexing Mechanism and Gas Fee Implementation:* Harish proposed implementing an indexing mechanism for ResilientDB, which would include get/set APIs for composite keys and JSON objects, thereby enabling more flexible and application-specific schema management. He suggested this feature would be beneficial for both developers and students, and discussed benchmarking key-value store performance. In parallel, Bisman and Harish addressed the introduction of a gas fee system and a token model to support a transition from an open blockchain architecture to one where tokens could be loaded and managed via smart contracts within the existing key-value infrastructure. Both emphasized the importance of collaboration between core contributors and student groups, aiming to avoid duplicated efforts and ensure coherence in further development. *Application Stack and Deployment Tools:* The team discussed the current status of the application stack, with Bisman providing updates on projects like Beacon and Nexus, highlighting that applications such as Beacon, Nexus, and Contract Forge are nearly ready for release, pending licensing updates. The conversation also recognized the valuable contributions of new volunteers and students to various ResilientDB applications. Addressing deployment, Harish emphasized the need for improved and more automated deployment tools—suggesting workflow automation and infrastructure as code (e.g., using CircleCI or Vercel) to enable students to deploy independently without direct maintainer involvement, thus reducing bottlenecks and streamlining the development and release process. *Ending Note :* In summary, the meeting concluded with a clear direction for the next steps across technical development, community engagement, and project milestones. The team reaffirmed the importance of collaboration among core members and students, setting actionable tasks to drive forward new releases, streamline deployment, and fulfill graduation requirements. Participants expressed a commitment to supporting one another, encouraging active communication, and continuing to build momentum in both research and community growth. The meeting ended on a forward-looking note, with a collective focus on consolidating efforts, enhancing documentation, and ensuring ResilientDB’s progress toward its long-term goals. Feel free to share any follow-up thoughts or continue the discussion here on the list. -- Best, Bismanpal Singh Anand PPMC, ResilientDB (Incubating)
