Hi everyone, Here’s a brief summary of our weekly *Apache ResilientDB (Incubating)* community meeting held on *November 24, 2025* for those who couldn’t attend:
Attendees: Bismanpal Anand, Chenyi Zhou, Dakai Kang, Devang Borkar, Harish Krishnakumar, Henry Chou, Junchao Chen, Mohammad Sadoghi, Shaokang Xie, Zehong Ruan Brief Summary: This week’s discussion focused on repository deprecations and migration to the monorepo structure, progress on the ResCanvas deployment, and the planning of the new *ResAI* project integrating multiple AI tools and agents. The team also discussed improving the navigation and visibility of Res AI tools, addressing production deployment issues, and formalizing PMC nominations and repository management processes. Action Items: - Update deprecation notices in older repositories for greater visibility and clarity as per Mohammad’s feedback; send or coordinate an email to the Apache mailing list announcing repository deprecations and the migration to the monorepo. - Add cross-links or navigation options for other tools (Nexus, Contract Forge, Beacon) on the Res AI Hub website; lead development of the ResAI prototype MVP by mid-December or early January; emphasize measurable performance and programmability benefits within the prototype. *Monorepo Migration and Repository Management* The team reviewed the status of repository migrations and deprecations as part of the ongoing consolidation into the ResilientDB monorepo. Bismanpal explained the addition of deprecation notices in older repositories to direct contributors to the new structure, and Mohammad suggested making the notices more visually prominent for improved clarity. The team agreed that a formal deprecation notice should also be shared via the dev@ mailing list to maintain transparency across the community. *2. ResCanvas and ResAI Development* Harish provided updates on ResCanvas, reporting that while the production server is active, the “get” and “set” APIs fail after the first request. Harish then outlined the roadmap for *ResAI*, a new prototype integrating multiple AI agents and MCP servers into a unified interface. The goal is to combine deployment, observability, and documentation tools to make ResilientDB’s advanced capabilities more accessible and interactive. The team aims to have an MVP by mid-December or early January. *3. ResAI Tools Organization and Accessibility* The team discussed enhancements to the ResAI Hub, which now houses all ResilientDB AI tools under one interface. Mohammad suggested improving navigation by adding dropdown menus or direct links to Nexus, Contract Forge, and Beacon. Harish agreed to incorporate these updates. The discussion also highlighted the need to emphasize the novel and measurable benefits of Res AI tools, such as improved performance, debugging efficiency, and programmability in the upcoming demo paper and prototype presentation. *4. Ongoing Administrative and Project Updates* Zehong provided updates on Res Social, including dependency fixes and continued API design work. The team also discussed account and repository ownership transfers, with Zehong managing the transition of PyPI/Expo access. Finally, Harish and Mohammad reviewed next steps for PMC nominations, particularly for Henry, and reaffirmed the importance of regular progress tracking through weekly reports and transparent mailing list communication. Ending Note:The meeting underscored the team’s focus on streamlining repository management, improving tool integration, and accelerating development toward the upcoming ResAI prototype. With strengthened collaboration and transparent communication practices, ResilientDB (Incubating) continues to advance both technically and organizationally on its path toward Apache graduation. - Best, Bismanpal Singh Anand PPMC, ResilientDB (Incubating) -- Bismanpal Singh Anand
