You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@resilientdb.apache.org by Bismanpal Singh Anand <bi...@gmail.com> on 2026/04/03 23:03:00 UTC
Weekly Community Meeting – Monday, March 9 at 4 PM PDT
Hi everyone,
Our *weekly Apache ResilientDB (Incubating) community meeting* will be held
on *Monday**, April 6 at 4 PM PST* via *Zoom*. These meetings are open to
all contributors and community members interested in ongoing development,
research, and incubation progress.
*When:* Monday, April 6 at 4 PM PST
*Where:*
https://ucdavis.zoom.us/j/95534430002?pwd=pLKg4fgf58lI7bZ6Ai17nP4u5YRM5Z.1
*Agenda for This Week:*
-
Review progress on cleanup pull requests and configuration updates
-
Status on Apache ResilientDB Release Candidate 1.12.0-rc3
-
Updates on Smart-Contract execution and RoK implementation
-
Open floor for community updates and questions
Meeting notes will be shared on this list afterward for those who can’t
attend.
-
Best,
*Bismanpal Singh Anand*PPMC, ResilientDB (Incubating)
Re: Weekly Community Meeting – Monday, March 9 at 4 PM PDT
Posted by Mohammad Sadoghi <ms...@expolab.org>.
Dear all,
I request that we move our meeting to Wednesday at 3 pm, if possible, for
this week only.
---
Best Regards,
Mohammad Sadoghi, PhD
Associate Professor, Chancellor's Fellow
Exploratory Systems Lab (ExpoLab)
Department of Computer Science
University of California, Davis
ExpoLab: https://expolab.org/
Apache ResilientDB (Incubating): https://resilientdb.com/
The Problems of Consensus: SpringerBriefs in Philosophy
<https://link.springer.com/book/10.1007/978-3-032-07282-5> [Interview
<https://cs.ucdavis.edu/news/computer-scientists-new-book-explores-philosophy-ethics-age-ai>
]
Phone: 914-319-7937
On Fri, Apr 3, 2026 at 4:03 PM Bismanpal Singh Anand <bi...@gmail.com>
wrote:
> Hi everyone,
>
> Our *weekly Apache ResilientDB (Incubating) community meeting* will be held
> on *Monday**, April 6 at 4 PM PST* via *Zoom*. These meetings are open to
> all contributors and community members interested in ongoing development,
> research, and incubation progress.
>
> *When:* Monday, April 6 at 4 PM PST
> *Where:*
> https://ucdavis.zoom.us/j/95534430002?pwd=pLKg4fgf58lI7bZ6Ai17nP4u5YRM5Z.1
>
>
> *Agenda for This Week:*
>
> -
>
> Review progress on cleanup pull requests and configuration updates
> -
>
> Status on Apache ResilientDB Release Candidate 1.12.0-rc3
> -
>
> Updates on Smart-Contract execution and RoK implementation
> -
>
> Open floor for community updates and questions
>
> Meeting notes will be shared on this list afterward for those who can’t
> attend.
> -
> Best,
>
> *Bismanpal Singh Anand*PPMC, ResilientDB (Incubating)
>
Re: Weekly Community Meeting – Monday, March 9 at 4 PM PDT
Posted by Bismanpal Singh Anand <bi...@gmail.com>.
Hi everyone,
Here’s a brief summary of our weekly *Apache ResilientDB (Incubating)*
community
meeting held on *April 8, 2026* for those who couldn’t attend:
Attendees: Bismanpal Anand, Dakai Kang, Devang Borkar, Josh Hutton, Junchao
Chen, Mohammad Sadoghi, Shaokang Xie, Zehong Ruan
Brief Summary
The meeting focused on the Apache ResilientDB project's release and
graduation process. The team discussed adding four new committers to the
project, with some accounts still pending creation. Bismanpal reported
progress on Contract Forge, including fixing API issues and adding chat
history preservation features, while also working on Resilient token
implementation. The team reviewed ongoing pull requests from Devang and
Josh, with discussions about using the development branch for future
contributions. Mohammad announced that we would start the graduation
process soon, which would elevate the project to top-level status within
Apache. The meeting also covered technical discussions about checkpointing
implementation and the potential involvement of Joshua's CryptoGo
improvements.
*Action Items:*
- Devang, Chris, and others awaiting committer accounts: Send follow-up
email with your email address and chosen account name to finalize account
creation.
- Update the architecture diagram on the website.
- Clean up old and unused branches in the repository (e.g., temporary
branches no longer needed).
- Josh: Update raft implementation pull request to the latest master
branch and continue work on checkpointing/snapshotting.
- Continue work on smart contract account creation enhancements
- Review and merge the pull requests ready and complete.
Committer Account Setup Discussion
The team discussed the status of committer accounts for several team
members, including Chris, Devang, and Kenny. It was determined that these
accounts had not yet been created, and Mohammad instructed the team to send
follow-up emails to ensure their accounts are set up properly. The group
also discussed the graduation process, with Junchao confirming that JB
would start the process this week, and they agreed to wait for JB's
guidance while ensuring the current committers are properly added to the
system.
ContractForge Progress Update
Bismanpal reported progress on Contract Forge, including fixing issues,
adding features to preserve chat history, and addressing concerns about API
key exposure. He created a contributing guide and delegated independent
feature enhancements to Ahan and Omar while resuming work on the Resilient
token implementation. Mohammad suggested exploring Joshua's improvements to
the CryptoGo mobile wallet as a potential addition to their ecosystem, with
the possibility of Joshua becoming a committee member.
ResilientDB Data Storage Progress Update
Josh reported that he has made progress on a pull request related to data
storage and recovery in ResilientDB, with most of the work on storing data
in stable storage before responding to RPCs completed. He noted that
checkpointing or snapshotting still needs to be implemented. When asked
about working on a branch versus a fork, Josh indicated that either
approach would work for him, and Mohammad informed him about the existing
development branch in the main repository. The discussion ended with
Mohammad inquiring about a release branch implementation, which is still a
pending task.
Checkpoint Manager and Project Updates
The team discussed the existing checkpoint manager implementation and its
relationship to Raft's log compaction. Junchao clarified that checkpointing
is part of the consensus layer and suggested that Josh consult with Dakai
for more details. Mohammad announced that the project is approaching its
10-year milestone since its inception in 2017-2018, with graduation to
top-level Apache project status expected soon. The team also discussed
adding new members, Haseeb and Varun, to future meetings, and Zehong
received guidance on how to properly submit his vote through the
appropriate email channels.
-
Best,
*Bismanpal Singh Anand*PPMC, ResilientDB (Incubating)
--
Bismanpal Singh Anand