Re: [DISCUSS] Incubating Proposal of ResilientDB
It would be great if we could move to the [vote] thread, now that the "broader contributing members" were also removed. --- Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis ExpoLab: https://expolab.org/ ResilientDB: https://resilientdb.com/ Phone: 914-319-7937 On Sat, Oct 14, 2023 at 2:06 PM Christian Grobmeier wrote: > Hello, > > I removed the "broader contributing members" as suggested: > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > Let's move ahead with the [vote] thread. > > Kind regards, > Christian > > > On Sat, Oct 14, 2023, at 12:37, Christian Grobmeier wrote: > > On Fri, Oct 13, 2023, at 20:22, Atri Sharma wrote: > >> Unfortunately , I am locked out of my Apache account. While I reset > that, I > >> would request one of the mentors to make the changes. > >> > >> Post that, I will start the vote thread > > > > If not another mentor is faster than me, I am going to look at it later > today > > > >> > >> On Fri, 13 Oct 2023 at 10:47 PM, Mohammad Sadoghi < > mo.sado...@expolab.org> > >> wrote: > >> > >>> Dear all, > >>> > >>> Could we move the [VOTE] phase after removing the broad contributors > (as it > >>> was suggested)? > >>> > >>> The last [Discuss] thread was sent 10 days ago with +8(binding). > >>> > >>> --- > >>> Best Regards, > >>> Mohammad Sadoghi, PhD > >>> Associate Professor > >>> Exploratory Systems Lab (ExpoLab) > >>> Department of Computer Science > >>> University of California, Davis > >>> > >>> ExpoLab: https://expolab.org/ > >>> ResilientDB: https://resilientdb.com/ > >>> Phone: 914-319-7937 > >>> > >>> > >>> On Thu, Oct 12, 2023 at 12:03 AM Mohammad Sadoghi < > mo.sado...@expolab.org> > >>> wrote: > >>> > >>> > Sure, please remove them [I do not have write access to the wiki]. > Thank > >>> > you kindly. > >>> > > >>> > --- > >>> > Best Regards, > >>> > Mohammad Sadoghi, PhD > >>> > Associate Professor > >>> > Exploratory Systems Lab (ExpoLab) > >>> > Department of Computer Science > >>> > University of California, Davis > >>> > > >>> > ExpoLab: https://expolab.org/ > >>> > ResilientDB: https://resilientdb.com/ > >>> > Phone: 914-319-7937 > >>> > > >>> > > >>> > On Thu, Oct 12, 2023 at 12:02 AM Atri Sharma > wrote: > >>> > > >>> >> I suggest removing them since it is leading to confusion. > >>> >> > >>> >> On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi > >>> >> wrote: > >>> >> > > >>> >> > Dear all, > >>> >> > > >>> >> > As for the question of the “Broader Contributing Members”, they > do not > >>> >> > qualify as initial committers as they have provided feedback / > >>> >> contributed > >>> >> > on the broader scope of ResilientDB, so we suggest either removing > >>> them > >>> >> or > >>> >> > keeping them in a separate category. I prefer keeping them as a > >>> separate > >>> >> > category, but of course, we will follow the ASF recommendation.We > are > >>> in > >>> >> > the process of improving and upgrading our website, and we will > add > >>> all > >>> >> the > >>> >> > initial committers to the website. Currently, from our website, we > >>> have > >>> >> > also linked to our Apache proposal, which includes the complete > list > >>> of > >>> >> > initial committers.With regards to the question of forked repo vs. > >>> >> branch, > >>> >> > we are fine with either option. We have made our development > public > >>> (no > >>> >> > longer private), and we can work on the either public repo (main > vs. > >>> >> > forked), whichever mode is preferred by ASF.With regards to PR, > moving > >>> >> > forward, we will ensure PR reviews and issue discussions are all > done > >>> on > >>> >> > the public repo with complete visibility. > >>> >> > > >>> >> > --- > >>> >> > Best Regards, > >>> >> > Mohammad Sadoghi, PhD > >>> >> > Associate Professor > >>> >> > Exploratory Systems Lab (ExpoLab) > >>> >> > Department of Computer Science > >>> >> > University of California, Davis > >>> >> > > >>> >> > ExpoLab: https://expolab.org/ > >>> >> > ResilientDB: https://resilientdb.com/ > >>> >> > Phone: 914-319-7937 > >>> >> > > >>> >> > > >>> >> > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang < > willem.ji...@gmail.com> > >>> >> wrote: > >>> >> > > >>> >> > > Unlike the Linux kernel, we use the dev or main branch from the > >>> >> > > official upstream repo to accept the PRs from the developer; we > do > >>> the > >>> >> > > release work on the other branch in the same repo. We don't use > >>> >> > > another forked repo to keep those changes first. It will > confuse > >>> the > >>> >> > > contributor in finding the right developing branch on the > project > >>> repo > >>> >> > > to work on. > >>> >> > > > >>> >> > > I barely find the repo's PR reviews and issue discussions[1]. > >>> Without > >>> >> > > sharing these development contexts, it is hard for the new > >>> contributor > >>> >> > > to know the story behind the code change. We can improve the
Re: [DISCUSS] Incubating Proposal of ResilientDB
Hello, I removed the "broader contributing members" as suggested: https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal Let's move ahead with the [vote] thread. Kind regards, Christian On Sat, Oct 14, 2023, at 12:37, Christian Grobmeier wrote: > On Fri, Oct 13, 2023, at 20:22, Atri Sharma wrote: >> Unfortunately , I am locked out of my Apache account. While I reset that, I >> would request one of the mentors to make the changes. >> >> Post that, I will start the vote thread > > If not another mentor is faster than me, I am going to look at it later today > >> >> On Fri, 13 Oct 2023 at 10:47 PM, Mohammad Sadoghi >> wrote: >> >>> Dear all, >>> >>> Could we move the [VOTE] phase after removing the broad contributors (as it >>> was suggested)? >>> >>> The last [Discuss] thread was sent 10 days ago with +8(binding). >>> >>> --- >>> Best Regards, >>> Mohammad Sadoghi, PhD >>> Associate Professor >>> Exploratory Systems Lab (ExpoLab) >>> Department of Computer Science >>> University of California, Davis >>> >>> ExpoLab: https://expolab.org/ >>> ResilientDB: https://resilientdb.com/ >>> Phone: 914-319-7937 >>> >>> >>> On Thu, Oct 12, 2023 at 12:03 AM Mohammad Sadoghi >>> wrote: >>> >>> > Sure, please remove them [I do not have write access to the wiki]. Thank >>> > you kindly. >>> > >>> > --- >>> > Best Regards, >>> > Mohammad Sadoghi, PhD >>> > Associate Professor >>> > Exploratory Systems Lab (ExpoLab) >>> > Department of Computer Science >>> > University of California, Davis >>> > >>> > ExpoLab: https://expolab.org/ >>> > ResilientDB: https://resilientdb.com/ >>> > Phone: 914-319-7937 >>> > >>> > >>> > On Thu, Oct 12, 2023 at 12:02 AM Atri Sharma wrote: >>> > >>> >> I suggest removing them since it is leading to confusion. >>> >> >>> >> On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi >>> >> wrote: >>> >> > >>> >> > Dear all, >>> >> > >>> >> > As for the question of the “Broader Contributing Members”, they do not >>> >> > qualify as initial committers as they have provided feedback / >>> >> contributed >>> >> > on the broader scope of ResilientDB, so we suggest either removing >>> them >>> >> or >>> >> > keeping them in a separate category. I prefer keeping them as a >>> separate >>> >> > category, but of course, we will follow the ASF recommendation.We are >>> in >>> >> > the process of improving and upgrading our website, and we will add >>> all >>> >> the >>> >> > initial committers to the website. Currently, from our website, we >>> have >>> >> > also linked to our Apache proposal, which includes the complete list >>> of >>> >> > initial committers.With regards to the question of forked repo vs. >>> >> branch, >>> >> > we are fine with either option. We have made our development public >>> (no >>> >> > longer private), and we can work on the either public repo (main vs. >>> >> > forked), whichever mode is preferred by ASF.With regards to PR, moving >>> >> > forward, we will ensure PR reviews and issue discussions are all done >>> on >>> >> > the public repo with complete visibility. >>> >> > >>> >> > --- >>> >> > Best Regards, >>> >> > Mohammad Sadoghi, PhD >>> >> > Associate Professor >>> >> > Exploratory Systems Lab (ExpoLab) >>> >> > Department of Computer Science >>> >> > University of California, Davis >>> >> > >>> >> > ExpoLab: https://expolab.org/ >>> >> > ResilientDB: https://resilientdb.com/ >>> >> > Phone: 914-319-7937 >>> >> > >>> >> > >>> >> > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang >>> >> wrote: >>> >> > >>> >> > > Unlike the Linux kernel, we use the dev or main branch from the >>> >> > > official upstream repo to accept the PRs from the developer; we do >>> the >>> >> > > release work on the other branch in the same repo. We don't use >>> >> > > another forked repo to keep those changes first. It will confuse >>> the >>> >> > > contributor in finding the right developing branch on the project >>> repo >>> >> > > to work on. >>> >> > > >>> >> > > I barely find the repo's PR reviews and issue discussions[1]. >>> Without >>> >> > > sharing these development contexts, it is hard for the new >>> contributor >>> >> > > to know the story behind the code change. We can improve the >>> >> > > situation during the incubation process. You can take the issue and >>> >> > > PRs of OpenDaL[2] as a polling example. >>> >> > > >>> >> > > BTW, the license header on the source code[3] is not the ASL >>> >> > > request[4]. We can address this kind of problem during the code >>> >> > > transfer. >>> >> > > >>> >> > > [1]https://github.com/resilientdb/resilientdb >>> >> > > [2]https://github.com/apache/incubator-opendal/ >>> >> > > [3] >>> >> > > >>> >> >>> https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 >>> >> > > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 >>> >> > > >>> >> > > Willem Jiang >>> >> > > >>> >> > > Twitter: willemjiang >>> >> > > Weibo: 姜宁willem >>> >> > > >>> >> > > On Tue, Oct 10, 2023 at
Re: [DISCUSS] Incubating Proposal of ResilientDB
On Fri, Oct 13, 2023, at 20:22, Atri Sharma wrote: > Unfortunately , I am locked out of my Apache account. While I reset that, I > would request one of the mentors to make the changes. > > Post that, I will start the vote thread If not another mentor is faster than me, I am going to look at it later today > > On Fri, 13 Oct 2023 at 10:47 PM, Mohammad Sadoghi > wrote: > >> Dear all, >> >> Could we move the [VOTE] phase after removing the broad contributors (as it >> was suggested)? >> >> The last [Discuss] thread was sent 10 days ago with +8(binding). >> >> --- >> Best Regards, >> Mohammad Sadoghi, PhD >> Associate Professor >> Exploratory Systems Lab (ExpoLab) >> Department of Computer Science >> University of California, Davis >> >> ExpoLab: https://expolab.org/ >> ResilientDB: https://resilientdb.com/ >> Phone: 914-319-7937 >> >> >> On Thu, Oct 12, 2023 at 12:03 AM Mohammad Sadoghi >> wrote: >> >> > Sure, please remove them [I do not have write access to the wiki]. Thank >> > you kindly. >> > >> > --- >> > Best Regards, >> > Mohammad Sadoghi, PhD >> > Associate Professor >> > Exploratory Systems Lab (ExpoLab) >> > Department of Computer Science >> > University of California, Davis >> > >> > ExpoLab: https://expolab.org/ >> > ResilientDB: https://resilientdb.com/ >> > Phone: 914-319-7937 >> > >> > >> > On Thu, Oct 12, 2023 at 12:02 AM Atri Sharma wrote: >> > >> >> I suggest removing them since it is leading to confusion. >> >> >> >> On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi >> >> wrote: >> >> > >> >> > Dear all, >> >> > >> >> > As for the question of the “Broader Contributing Members”, they do not >> >> > qualify as initial committers as they have provided feedback / >> >> contributed >> >> > on the broader scope of ResilientDB, so we suggest either removing >> them >> >> or >> >> > keeping them in a separate category. I prefer keeping them as a >> separate >> >> > category, but of course, we will follow the ASF recommendation.We are >> in >> >> > the process of improving and upgrading our website, and we will add >> all >> >> the >> >> > initial committers to the website. Currently, from our website, we >> have >> >> > also linked to our Apache proposal, which includes the complete list >> of >> >> > initial committers.With regards to the question of forked repo vs. >> >> branch, >> >> > we are fine with either option. We have made our development public >> (no >> >> > longer private), and we can work on the either public repo (main vs. >> >> > forked), whichever mode is preferred by ASF.With regards to PR, moving >> >> > forward, we will ensure PR reviews and issue discussions are all done >> on >> >> > the public repo with complete visibility. >> >> > >> >> > --- >> >> > Best Regards, >> >> > Mohammad Sadoghi, PhD >> >> > Associate Professor >> >> > Exploratory Systems Lab (ExpoLab) >> >> > Department of Computer Science >> >> > University of California, Davis >> >> > >> >> > ExpoLab: https://expolab.org/ >> >> > ResilientDB: https://resilientdb.com/ >> >> > Phone: 914-319-7937 >> >> > >> >> > >> >> > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang >> >> wrote: >> >> > >> >> > > Unlike the Linux kernel, we use the dev or main branch from the >> >> > > official upstream repo to accept the PRs from the developer; we do >> the >> >> > > release work on the other branch in the same repo. We don't use >> >> > > another forked repo to keep those changes first. It will confuse >> the >> >> > > contributor in finding the right developing branch on the project >> repo >> >> > > to work on. >> >> > > >> >> > > I barely find the repo's PR reviews and issue discussions[1]. >> Without >> >> > > sharing these development contexts, it is hard for the new >> contributor >> >> > > to know the story behind the code change. We can improve the >> >> > > situation during the incubation process. You can take the issue and >> >> > > PRs of OpenDaL[2] as a polling example. >> >> > > >> >> > > BTW, the license header on the source code[3] is not the ASL >> >> > > request[4]. We can address this kind of problem during the code >> >> > > transfer. >> >> > > >> >> > > [1]https://github.com/resilientdb/resilientdb >> >> > > [2]https://github.com/apache/incubator-opendal/ >> >> > > [3] >> >> > > >> >> >> https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 >> >> > > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 >> >> > > >> >> > > Willem Jiang >> >> > > >> >> > > Twitter: willemjiang >> >> > > Weibo: 姜宁willem >> >> > > >> >> > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi >> >> > > wrote: >> >> > > > >> >> > > > Dear all, >> >> > > > >> >> > > > *Question on Initial Committers:* >> >> > > > As was mentioned earlier. The criteria that I used was to credit >> >> anyone >> >> > > who >> >> > > > has worked on the ResilientDB project since 2018, acknowledging >> >> their >> >> > > > contributions. Below is the detailed breakdown of our >>
Re: [DISCUSS] Incubating Proposal of ResilientDB
Unfortunately , I am locked out of my Apache account. While I reset that, I would request one of the mentors to make the changes. Post that, I will start the vote thread On Fri, 13 Oct 2023 at 10:47 PM, Mohammad Sadoghi wrote: > Dear all, > > Could we move the [VOTE] phase after removing the broad contributors (as it > was suggested)? > > The last [Discuss] thread was sent 10 days ago with +8(binding). > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Thu, Oct 12, 2023 at 12:03 AM Mohammad Sadoghi > wrote: > > > Sure, please remove them [I do not have write access to the wiki]. Thank > > you kindly. > > > > --- > > Best Regards, > > Mohammad Sadoghi, PhD > > Associate Professor > > Exploratory Systems Lab (ExpoLab) > > Department of Computer Science > > University of California, Davis > > > > ExpoLab: https://expolab.org/ > > ResilientDB: https://resilientdb.com/ > > Phone: 914-319-7937 > > > > > > On Thu, Oct 12, 2023 at 12:02 AM Atri Sharma wrote: > > > >> I suggest removing them since it is leading to confusion. > >> > >> On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi > >> wrote: > >> > > >> > Dear all, > >> > > >> > As for the question of the “Broader Contributing Members”, they do not > >> > qualify as initial committers as they have provided feedback / > >> contributed > >> > on the broader scope of ResilientDB, so we suggest either removing > them > >> or > >> > keeping them in a separate category. I prefer keeping them as a > separate > >> > category, but of course, we will follow the ASF recommendation.We are > in > >> > the process of improving and upgrading our website, and we will add > all > >> the > >> > initial committers to the website. Currently, from our website, we > have > >> > also linked to our Apache proposal, which includes the complete list > of > >> > initial committers.With regards to the question of forked repo vs. > >> branch, > >> > we are fine with either option. We have made our development public > (no > >> > longer private), and we can work on the either public repo (main vs. > >> > forked), whichever mode is preferred by ASF.With regards to PR, moving > >> > forward, we will ensure PR reviews and issue discussions are all done > on > >> > the public repo with complete visibility. > >> > > >> > --- > >> > Best Regards, > >> > Mohammad Sadoghi, PhD > >> > Associate Professor > >> > Exploratory Systems Lab (ExpoLab) > >> > Department of Computer Science > >> > University of California, Davis > >> > > >> > ExpoLab: https://expolab.org/ > >> > ResilientDB: https://resilientdb.com/ > >> > Phone: 914-319-7937 > >> > > >> > > >> > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang > >> wrote: > >> > > >> > > Unlike the Linux kernel, we use the dev or main branch from the > >> > > official upstream repo to accept the PRs from the developer; we do > the > >> > > release work on the other branch in the same repo. We don't use > >> > > another forked repo to keep those changes first. It will confuse > the > >> > > contributor in finding the right developing branch on the project > repo > >> > > to work on. > >> > > > >> > > I barely find the repo's PR reviews and issue discussions[1]. > Without > >> > > sharing these development contexts, it is hard for the new > contributor > >> > > to know the story behind the code change. We can improve the > >> > > situation during the incubation process. You can take the issue and > >> > > PRs of OpenDaL[2] as a polling example. > >> > > > >> > > BTW, the license header on the source code[3] is not the ASL > >> > > request[4]. We can address this kind of problem during the code > >> > > transfer. > >> > > > >> > > [1]https://github.com/resilientdb/resilientdb > >> > > [2]https://github.com/apache/incubator-opendal/ > >> > > [3] > >> > > > >> > https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 > >> > > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 > >> > > > >> > > Willem Jiang > >> > > > >> > > Twitter: willemjiang > >> > > Weibo: 姜宁willem > >> > > > >> > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi > >> > > wrote: > >> > > > > >> > > > Dear all, > >> > > > > >> > > > *Question on Initial Committers:* > >> > > > As was mentioned earlier. The criteria that I used was to credit > >> anyone > >> > > who > >> > > > has worked on the ResilientDB project since 2018, acknowledging > >> their > >> > > > contributions. Below is the detailed breakdown of our > contributors. > >> So we > >> > > > can reduce the list as needed in accordance with ASF guidelines. > As > >> for > >> > > the > >> > > > broader contributors, these are the folks who have supported > >> ResilientDB, > >> > > > e.g., formalization of the research ideas, discussion of how to >
Re: [DISCUSS] Incubating Proposal of ResilientDB
Dear all, Could we move the [VOTE] phase after removing the broad contributors (as it was suggested)? The last [Discuss] thread was sent 10 days ago with +8(binding). --- Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis ExpoLab: https://expolab.org/ ResilientDB: https://resilientdb.com/ Phone: 914-319-7937 On Thu, Oct 12, 2023 at 12:03 AM Mohammad Sadoghi wrote: > Sure, please remove them [I do not have write access to the wiki]. Thank > you kindly. > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Thu, Oct 12, 2023 at 12:02 AM Atri Sharma wrote: > >> I suggest removing them since it is leading to confusion. >> >> On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi >> wrote: >> > >> > Dear all, >> > >> > As for the question of the “Broader Contributing Members”, they do not >> > qualify as initial committers as they have provided feedback / >> contributed >> > on the broader scope of ResilientDB, so we suggest either removing them >> or >> > keeping them in a separate category. I prefer keeping them as a separate >> > category, but of course, we will follow the ASF recommendation.We are in >> > the process of improving and upgrading our website, and we will add all >> the >> > initial committers to the website. Currently, from our website, we have >> > also linked to our Apache proposal, which includes the complete list of >> > initial committers.With regards to the question of forked repo vs. >> branch, >> > we are fine with either option. We have made our development public (no >> > longer private), and we can work on the either public repo (main vs. >> > forked), whichever mode is preferred by ASF.With regards to PR, moving >> > forward, we will ensure PR reviews and issue discussions are all done on >> > the public repo with complete visibility. >> > >> > --- >> > Best Regards, >> > Mohammad Sadoghi, PhD >> > Associate Professor >> > Exploratory Systems Lab (ExpoLab) >> > Department of Computer Science >> > University of California, Davis >> > >> > ExpoLab: https://expolab.org/ >> > ResilientDB: https://resilientdb.com/ >> > Phone: 914-319-7937 >> > >> > >> > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang >> wrote: >> > >> > > Unlike the Linux kernel, we use the dev or main branch from the >> > > official upstream repo to accept the PRs from the developer; we do the >> > > release work on the other branch in the same repo. We don't use >> > > another forked repo to keep those changes first. It will confuse the >> > > contributor in finding the right developing branch on the project repo >> > > to work on. >> > > >> > > I barely find the repo's PR reviews and issue discussions[1]. Without >> > > sharing these development contexts, it is hard for the new contributor >> > > to know the story behind the code change. We can improve the >> > > situation during the incubation process. You can take the issue and >> > > PRs of OpenDaL[2] as a polling example. >> > > >> > > BTW, the license header on the source code[3] is not the ASL >> > > request[4]. We can address this kind of problem during the code >> > > transfer. >> > > >> > > [1]https://github.com/resilientdb/resilientdb >> > > [2]https://github.com/apache/incubator-opendal/ >> > > [3] >> > > >> https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 >> > > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 >> > > >> > > Willem Jiang >> > > >> > > Twitter: willemjiang >> > > Weibo: 姜宁willem >> > > >> > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi >> > > wrote: >> > > > >> > > > Dear all, >> > > > >> > > > *Question on Initial Committers:* >> > > > As was mentioned earlier. The criteria that I used was to credit >> anyone >> > > who >> > > > has worked on the ResilientDB project since 2018, acknowledging >> their >> > > > contributions. Below is the detailed breakdown of our contributors. >> So we >> > > > can reduce the list as needed in accordance with ASF guidelines. As >> for >> > > the >> > > > broader contributors, these are the folks who have supported >> ResilientDB, >> > > > e.g., formalization of the research ideas, discussion of how to >> tackle a >> > > > particular algorithm or its implementation, testing, and analysis. >> > > However, >> > > > these broader members have not contributed to the codebase. So this >> is >> > > why >> > > > they were tagged differently.*ResilientDB Core *[all have signed >> ICLA] >> > > > Mohammad Sadoghi >> > > > Junchao Chen >> > > > Dakai Kang >> > > > Suyash Gupta [Now at UC Berkeley] >> > > > Sajjad Rahnama [Now at Oracle] >> > > > Wayne Wang [Now at Hesai Technology] >> > > > Julieta Duarte >> > > >
Re: [DISCUSS] Incubating Proposal of ResilientDB
Sure, please remove them [I do not have write access to the wiki]. Thank you kindly. --- Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis ExpoLab: https://expolab.org/ ResilientDB: https://resilientdb.com/ Phone: 914-319-7937 On Thu, Oct 12, 2023 at 12:02 AM Atri Sharma wrote: > I suggest removing them since it is leading to confusion. > > On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi > wrote: > > > > Dear all, > > > > As for the question of the “Broader Contributing Members”, they do not > > qualify as initial committers as they have provided feedback / > contributed > > on the broader scope of ResilientDB, so we suggest either removing them > or > > keeping them in a separate category. I prefer keeping them as a separate > > category, but of course, we will follow the ASF recommendation.We are in > > the process of improving and upgrading our website, and we will add all > the > > initial committers to the website. Currently, from our website, we have > > also linked to our Apache proposal, which includes the complete list of > > initial committers.With regards to the question of forked repo vs. > branch, > > we are fine with either option. We have made our development public (no > > longer private), and we can work on the either public repo (main vs. > > forked), whichever mode is preferred by ASF.With regards to PR, moving > > forward, we will ensure PR reviews and issue discussions are all done on > > the public repo with complete visibility. > > > > --- > > Best Regards, > > Mohammad Sadoghi, PhD > > Associate Professor > > Exploratory Systems Lab (ExpoLab) > > Department of Computer Science > > University of California, Davis > > > > ExpoLab: https://expolab.org/ > > ResilientDB: https://resilientdb.com/ > > Phone: 914-319-7937 > > > > > > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang > wrote: > > > > > Unlike the Linux kernel, we use the dev or main branch from the > > > official upstream repo to accept the PRs from the developer; we do the > > > release work on the other branch in the same repo. We don't use > > > another forked repo to keep those changes first. It will confuse the > > > contributor in finding the right developing branch on the project repo > > > to work on. > > > > > > I barely find the repo's PR reviews and issue discussions[1]. Without > > > sharing these development contexts, it is hard for the new contributor > > > to know the story behind the code change. We can improve the > > > situation during the incubation process. You can take the issue and > > > PRs of OpenDaL[2] as a polling example. > > > > > > BTW, the license header on the source code[3] is not the ASL > > > request[4]. We can address this kind of problem during the code > > > transfer. > > > > > > [1]https://github.com/resilientdb/resilientdb > > > [2]https://github.com/apache/incubator-opendal/ > > > [3] > > > > https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 > > > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi > > > wrote: > > > > > > > > Dear all, > > > > > > > > *Question on Initial Committers:* > > > > As was mentioned earlier. The criteria that I used was to credit > anyone > > > who > > > > has worked on the ResilientDB project since 2018, acknowledging their > > > > contributions. Below is the detailed breakdown of our contributors. > So we > > > > can reduce the list as needed in accordance with ASF guidelines. As > for > > > the > > > > broader contributors, these are the folks who have supported > ResilientDB, > > > > e.g., formalization of the research ideas, discussion of how to > tackle a > > > > particular algorithm or its implementation, testing, and analysis. > > > However, > > > > these broader members have not contributed to the codebase. So this > is > > > why > > > > they were tagged differently.*ResilientDB Core *[all have signed > ICLA] > > > > Mohammad Sadoghi > > > > Junchao Chen > > > > Dakai Kang > > > > Suyash Gupta [Now at UC Berkeley] > > > > Sajjad Rahnama [Now at Oracle] > > > > Wayne Wang [Now at Hesai Technology] > > > > Julieta Duarte > > > > Glenn Chen > > > > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > > > > Thamir Qadah [Umm Al-Qura University] > > > > Jinxiao Yu [Now at Amazon AWS] > > > > Arindaam Roy [Now at Square] > > > > Divjeet Singh Jas > > > > Apratim Shukla > > > > Priyal Soni [Now at Amazon AWS] > > > > Rohan Sogani [Now at Oracle] > > > > Kaustubh Shete > > > > Gopal Nambiar > > > > Saipranav Kotamreddy > > > > Haskell Lark Macaraig > > > > > > > > *Deprecated/Obsolete Features *[have been rewritten or removed] > > > > Jelle Hellings [Now at McMaster > > > University] > > > > Shesha Vishnu Prasad [Now at
Re: [DISCUSS] Incubating Proposal of ResilientDB
I suggest removing them since it is leading to confusion. On Thu, Oct 12, 2023 at 12:27 PM Mohammad Sadoghi wrote: > > Dear all, > > As for the question of the “Broader Contributing Members”, they do not > qualify as initial committers as they have provided feedback / contributed > on the broader scope of ResilientDB, so we suggest either removing them or > keeping them in a separate category. I prefer keeping them as a separate > category, but of course, we will follow the ASF recommendation.We are in > the process of improving and upgrading our website, and we will add all the > initial committers to the website. Currently, from our website, we have > also linked to our Apache proposal, which includes the complete list of > initial committers.With regards to the question of forked repo vs. branch, > we are fine with either option. We have made our development public (no > longer private), and we can work on the either public repo (main vs. > forked), whichever mode is preferred by ASF.With regards to PR, moving > forward, we will ensure PR reviews and issue discussions are all done on > the public repo with complete visibility. > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang wrote: > > > Unlike the Linux kernel, we use the dev or main branch from the > > official upstream repo to accept the PRs from the developer; we do the > > release work on the other branch in the same repo. We don't use > > another forked repo to keep those changes first. It will confuse the > > contributor in finding the right developing branch on the project repo > > to work on. > > > > I barely find the repo's PR reviews and issue discussions[1]. Without > > sharing these development contexts, it is hard for the new contributor > > to know the story behind the code change. We can improve the > > situation during the incubation process. You can take the issue and > > PRs of OpenDaL[2] as a polling example. > > > > BTW, the license header on the source code[3] is not the ASL > > request[4]. We can address this kind of problem during the code > > transfer. > > > > [1]https://github.com/resilientdb/resilientdb > > [2]https://github.com/apache/incubator-opendal/ > > [3] > > https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 > > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi > > wrote: > > > > > > Dear all, > > > > > > *Question on Initial Committers:* > > > As was mentioned earlier. The criteria that I used was to credit anyone > > who > > > has worked on the ResilientDB project since 2018, acknowledging their > > > contributions. Below is the detailed breakdown of our contributors. So we > > > can reduce the list as needed in accordance with ASF guidelines. As for > > the > > > broader contributors, these are the folks who have supported ResilientDB, > > > e.g., formalization of the research ideas, discussion of how to tackle a > > > particular algorithm or its implementation, testing, and analysis. > > However, > > > these broader members have not contributed to the codebase. So this is > > why > > > they were tagged differently.*ResilientDB Core *[all have signed ICLA] > > > Mohammad Sadoghi > > > Junchao Chen > > > Dakai Kang > > > Suyash Gupta [Now at UC Berkeley] > > > Sajjad Rahnama [Now at Oracle] > > > Wayne Wang [Now at Hesai Technology] > > > Julieta Duarte > > > Glenn Chen > > > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > > > Thamir Qadah [Umm Al-Qura University] > > > Jinxiao Yu [Now at Amazon AWS] > > > Arindaam Roy [Now at Square] > > > Divjeet Singh Jas > > > Apratim Shukla > > > Priyal Soni [Now at Amazon AWS] > > > Rohan Sogani [Now at Oracle] > > > Kaustubh Shete > > > Gopal Nambiar > > > Saipranav Kotamreddy > > > Haskell Lark Macaraig > > > > > > *Deprecated/Obsolete Features *[have been rewritten or removed] > > > Jelle Hellings [Now at McMaster > > University] > > > Shesha Vishnu Prasad [Now at Path] > > > Dhruv Krishnan [Now at Amazon AWS] > > > Shubham Pandey [Now at Cisco] > > > Steve Chen > > > Priya Holani [Now at Amazon AWS] > > > Haojun (Howard) Zhu > > > Robert HE [Now at Amazon AWS] > > > Shreenath Iyer [Now at Amazon AWS] > > > Domenic Cianfichi [Now at Amazon AWS] > > > Erik Linsenmayer [Now at General > > Atomics] > > > Shreyan Mohanty [Now at General Atomics] > > > Xinyuan Sun [Now at CertiK] > > > Patrick Liao [Now at Juniper Networks] > > > Tim Huang > > > Jared Givens > > > Aditya Bej > > > Seongwoo Choi > > > > > > *Question on Private Development:* > > > As per request, we have
Re: [DISCUSS] Incubating Proposal of ResilientDB
Dear all, As for the question of the “Broader Contributing Members”, they do not qualify as initial committers as they have provided feedback / contributed on the broader scope of ResilientDB, so we suggest either removing them or keeping them in a separate category. I prefer keeping them as a separate category, but of course, we will follow the ASF recommendation.We are in the process of improving and upgrading our website, and we will add all the initial committers to the website. Currently, from our website, we have also linked to our Apache proposal, which includes the complete list of initial committers.With regards to the question of forked repo vs. branch, we are fine with either option. We have made our development public (no longer private), and we can work on the either public repo (main vs. forked), whichever mode is preferred by ASF.With regards to PR, moving forward, we will ensure PR reviews and issue discussions are all done on the public repo with complete visibility. --- Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis ExpoLab: https://expolab.org/ ResilientDB: https://resilientdb.com/ Phone: 914-319-7937 On Wed, Oct 11, 2023 at 7:49 PM Willem Jiang wrote: > Unlike the Linux kernel, we use the dev or main branch from the > official upstream repo to accept the PRs from the developer; we do the > release work on the other branch in the same repo. We don't use > another forked repo to keep those changes first. It will confuse the > contributor in finding the right developing branch on the project repo > to work on. > > I barely find the repo's PR reviews and issue discussions[1]. Without > sharing these development contexts, it is hard for the new contributor > to know the story behind the code change. We can improve the > situation during the incubation process. You can take the issue and > PRs of OpenDaL[2] as a polling example. > > BTW, the license header on the source code[3] is not the ASL > request[4]. We can address this kind of problem during the code > transfer. > > [1]https://github.com/resilientdb/resilientdb > [2]https://github.com/apache/incubator-opendal/ > [3] > https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 > [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi > wrote: > > > > Dear all, > > > > *Question on Initial Committers:* > > As was mentioned earlier. The criteria that I used was to credit anyone > who > > has worked on the ResilientDB project since 2018, acknowledging their > > contributions. Below is the detailed breakdown of our contributors. So we > > can reduce the list as needed in accordance with ASF guidelines. As for > the > > broader contributors, these are the folks who have supported ResilientDB, > > e.g., formalization of the research ideas, discussion of how to tackle a > > particular algorithm or its implementation, testing, and analysis. > However, > > these broader members have not contributed to the codebase. So this is > why > > they were tagged differently.*ResilientDB Core *[all have signed ICLA] > > Mohammad Sadoghi > > Junchao Chen > > Dakai Kang > > Suyash Gupta [Now at UC Berkeley] > > Sajjad Rahnama [Now at Oracle] > > Wayne Wang [Now at Hesai Technology] > > Julieta Duarte > > Glenn Chen > > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > > Thamir Qadah [Umm Al-Qura University] > > Jinxiao Yu [Now at Amazon AWS] > > Arindaam Roy [Now at Square] > > Divjeet Singh Jas > > Apratim Shukla > > Priyal Soni [Now at Amazon AWS] > > Rohan Sogani [Now at Oracle] > > Kaustubh Shete > > Gopal Nambiar > > Saipranav Kotamreddy > > Haskell Lark Macaraig > > > > *Deprecated/Obsolete Features *[have been rewritten or removed] > > Jelle Hellings [Now at McMaster > University] > > Shesha Vishnu Prasad [Now at Path] > > Dhruv Krishnan [Now at Amazon AWS] > > Shubham Pandey [Now at Cisco] > > Steve Chen > > Priya Holani [Now at Amazon AWS] > > Haojun (Howard) Zhu > > Robert HE [Now at Amazon AWS] > > Shreenath Iyer [Now at Amazon AWS] > > Domenic Cianfichi [Now at Amazon AWS] > > Erik Linsenmayer [Now at General > Atomics] > > Shreyan Mohanty [Now at General Atomics] > > Xinyuan Sun [Now at CertiK] > > Patrick Liao [Now at Juniper Networks] > > Tim Huang > > Jared Givens > > Aditya Bej > > Seongwoo Choi > > > > *Question on Private Development:* > > As per request, we have transitioned away from local/private development. > > We have forked our public ResilientDB, and we began the process of moving > > all experimental features into this repo. All these ongoing features are > > available in this repo but are still under development and not yet ready > to > > be released to the main repository.*Our New Development Repo: * > >
Re: [DISCUSS] Incubating Proposal of ResilientDB
Unlike the Linux kernel, we use the dev or main branch from the official upstream repo to accept the PRs from the developer; we do the release work on the other branch in the same repo. We don't use another forked repo to keep those changes first. It will confuse the contributor in finding the right developing branch on the project repo to work on. I barely find the repo's PR reviews and issue discussions[1]. Without sharing these development contexts, it is hard for the new contributor to know the story behind the code change. We can improve the situation during the incubation process. You can take the issue and PRs of OpenDaL[2] as a polling example. BTW, the license header on the source code[3] is not the ASL request[4]. We can address this kind of problem during the code transfer. [1]https://github.com/resilientdb/resilientdb [2]https://github.com/apache/incubator-opendal/ [3]https://github.com/resilientdb/resilientdb/blob/master/executor/common/transaction_manager.cpp#L1 [4]https://github.com/msadoghi/resilientdb/blob/hs/LICENSE#L189 Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Oct 10, 2023 at 11:50 AM Mohammad Sadoghi wrote: > > Dear all, > > *Question on Initial Committers:* > As was mentioned earlier. The criteria that I used was to credit anyone who > has worked on the ResilientDB project since 2018, acknowledging their > contributions. Below is the detailed breakdown of our contributors. So we > can reduce the list as needed in accordance with ASF guidelines. As for the > broader contributors, these are the folks who have supported ResilientDB, > e.g., formalization of the research ideas, discussion of how to tackle a > particular algorithm or its implementation, testing, and analysis. However, > these broader members have not contributed to the codebase. So this is why > they were tagged differently.*ResilientDB Core *[all have signed ICLA] > Mohammad Sadoghi > Junchao Chen > Dakai Kang > Suyash Gupta [Now at UC Berkeley] > Sajjad Rahnama [Now at Oracle] > Wayne Wang [Now at Hesai Technology] > Julieta Duarte > Glenn Chen > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > Thamir Qadah [Umm Al-Qura University] > Jinxiao Yu [Now at Amazon AWS] > Arindaam Roy [Now at Square] > Divjeet Singh Jas > Apratim Shukla > Priyal Soni [Now at Amazon AWS] > Rohan Sogani [Now at Oracle] > Kaustubh Shete > Gopal Nambiar > Saipranav Kotamreddy > Haskell Lark Macaraig > > *Deprecated/Obsolete Features *[have been rewritten or removed] > Jelle Hellings [Now at McMaster University] > Shesha Vishnu Prasad [Now at Path] > Dhruv Krishnan [Now at Amazon AWS] > Shubham Pandey [Now at Cisco] > Steve Chen > Priya Holani [Now at Amazon AWS] > Haojun (Howard) Zhu > Robert HE [Now at Amazon AWS] > Shreenath Iyer [Now at Amazon AWS] > Domenic Cianfichi [Now at Amazon AWS] > Erik Linsenmayer [Now at General Atomics] > Shreyan Mohanty [Now at General Atomics] > Xinyuan Sun [Now at CertiK] > Patrick Liao [Now at Juniper Networks] > Tim Huang > Jared Givens > Aditya Bej > Seongwoo Choi > > *Question on Private Development:* > As per request, we have transitioned away from local/private development. > We have forked our public ResilientDB, and we began the process of moving > all experimental features into this repo. All these ongoing features are > available in this repo but are still under development and not yet ready to > be released to the main repository.*Our New Development Repo: * > https://github.com/msadoghi/resilientdb/*Notable Branches (Active Projects)* > Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe > Rotating Leader (lightweight recovery): > https://github.com/msadoghi/resilientdb/tree/hs > Queue-Oriented Concurrency Control (concurrent execution): > https://github.com/msadoghi/resilientdb/tree/QueccBranch > Smart Contract Concurrency: > https://github.com/msadoghi/resilientdb/tree/smartcontract_cc > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Mon, Oct 9, 2023 at 6:18 PM Dave Fisher wrote: > > > > > > > Sent from my iPhone > > > > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > > > > > wrote: > > > > > > Hello All > > > > > > Let me try to add to Mohammad's response. We defined an initial committer > > > list of 40+ members as we wanted to give credit to everyone who has > > > collaborated with us on projects/papers that were built around > > ResilientDB. > > > But, the 20 contributors visible on github are the ones who worked on the > > > actual codebase, which we are trying to bring to ASF. The projects that > > > other folks worked on are independent from the ResilientDB codebase and > > > have no correlation with this release. > > > > > > So, following ASF guidelines, we are fine with
Re: [DISCUSS] Incubating Proposal of ResilientDB
I still have a question for the “Broader Contributing Members”: do we treat them as initial committers? It makes sense that we keep track of all the contributors on the project website so that no one will be surprised by the long list of initial committers. An extensive initial committer list doesn't mean we have a healthy, diverse community. It is incredibly challenging to bring those graduated students back to the project from my experience with IoTDB. When we consider the community-building work during the polling graduation evaluation, we just track the new committers we have during the incubation process. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Tue, Oct 10, 2023 at 7:43 PM 俊平堵 wrote: > > Agree with Roman and Dave that we can keep the original list. > I think Willem is just curious on the mismatch between commits and > committers, and the explanation here make sense to me. > > Thanks, > > JP > > Mohammad Sadoghi 于2023年10月10日周二 11:50写道： > > > Dear all, > > > > *Question on Initial Committers:* > > As was mentioned earlier. The criteria that I used was to credit anyone who > > has worked on the ResilientDB project since 2018, acknowledging their > > contributions. Below is the detailed breakdown of our contributors. So we > > can reduce the list as needed in accordance with ASF guidelines. As for the > > broader contributors, these are the folks who have supported ResilientDB, > > e.g., formalization of the research ideas, discussion of how to tackle a > > particular algorithm or its implementation, testing, and analysis. However, > > these broader members have not contributed to the codebase. So this is why > > they were tagged differently.*ResilientDB Core *[all have signed ICLA] > > Mohammad Sadoghi > > Junchao Chen > > Dakai Kang > > Suyash Gupta [Now at UC Berkeley] > > Sajjad Rahnama [Now at Oracle] > > Wayne Wang [Now at Hesai Technology] > > Julieta Duarte > > Glenn Chen > > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > > Thamir Qadah [Umm Al-Qura University] > > Jinxiao Yu [Now at Amazon AWS] > > Arindaam Roy [Now at Square] > > Divjeet Singh Jas > > Apratim Shukla > > Priyal Soni [Now at Amazon AWS] > > Rohan Sogani [Now at Oracle] > > Kaustubh Shete > > Gopal Nambiar > > Saipranav Kotamreddy > > Haskell Lark Macaraig > > > > *Deprecated/Obsolete Features *[have been rewritten or removed] > > Jelle Hellings [Now at McMaster University] > > Shesha Vishnu Prasad [Now at Path] > > Dhruv Krishnan [Now at Amazon AWS] > > Shubham Pandey [Now at Cisco] > > Steve Chen > > Priya Holani [Now at Amazon AWS] > > Haojun (Howard) Zhu > > Robert HE [Now at Amazon AWS] > > Shreenath Iyer [Now at Amazon AWS] > > Domenic Cianfichi [Now at Amazon AWS] > > Erik Linsenmayer [Now at General > > Atomics] > > Shreyan Mohanty [Now at General Atomics] > > Xinyuan Sun [Now at CertiK] > > Patrick Liao [Now at Juniper Networks] > > Tim Huang > > Jared Givens > > Aditya Bej > > Seongwoo Choi > > > > *Question on Private Development:* > > As per request, we have transitioned away from local/private development. > > We have forked our public ResilientDB, and we began the process of moving > > all experimental features into this repo. All these ongoing features are > > available in this repo but are still under development and not yet ready to > > be released to the main repository.*Our New Development Repo: * > > https://github.com/msadoghi/resilientdb/*Notable Branches (Active > > Projects)* > > Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe > > Rotating Leader (lightweight recovery): > > https://github.com/msadoghi/resilientdb/tree/hs > > Queue-Oriented Concurrency Control (concurrent execution): > > https://github.com/msadoghi/resilientdb/tree/QueccBranch > > Smart Contract Concurrency: > > https://github.com/msadoghi/resilientdb/tree/smartcontract_cc > > > > --- > > Best Regards, > > Mohammad Sadoghi, PhD > > Associate Professor > > Exploratory Systems Lab (ExpoLab) > > Department of Computer Science > > University of California, Davis > > > > ExpoLab: https://expolab.org/ > > ResilientDB: https://resilientdb.com/ > > Phone: 914-319-7937 > > > > > > On Mon, Oct 9, 2023 at 6:18 PM Dave Fisher wrote: > > > > > > > > > > > Sent from my iPhone > > > > > > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > .invalid> > > > wrote: > > > > > > > > Hello All > > > > > > > > Let me try to add to Mohammad's response. We defined an initial > > committer > > > > list of 40+ members as we wanted to give credit to everyone who has > > > > collaborated with us on projects/papers that were built around > > > ResilientDB. > > > > But, the 20 contributors visible on github are the ones who worked on > > the > > > > actual codebase, which we are trying to bring to ASF. The projects that > > > > other folks worked on are independent from the ResilientDB codebase and > > > > have no correlation with this release. > > > > > > > > So, following ASF
Re: [DISCUSS] Incubating Proposal of ResilientDB
On Tue, Oct 10, 2023, at 20:49, Atri Sharma wrote: > If no further concerns, I wish to start the vote thread tomorrow. > Awesome. Since you have allowed plenty of "complain time," it's safe to go by tomorrow. Thanks for taking care of this! > On Wed, 11 Oct 2023 at 12:16 AM, Christian Grobmeier > wrote: > >> I agree too. >> >> However, I am also concerned the titel is [DISCUSS] - shouldn't this be a >> vote already? >> >> >> On Tue, Oct 10, 2023, at 13:42, 俊平堵 wrote: >> > Agree with Roman and Dave that we can keep the original list. >> > I think Willem is just curious on the mismatch between commits and >> > committers, and the explanation here make sense to me. >> > >> > Thanks, >> > >> > JP >> > >> > Mohammad Sadoghi 于2023年10月10日周二 11:50写道： >> > >> >> Dear all, >> >> >> >> *Question on Initial Committers:* >> >> As was mentioned earlier. The criteria that I used was to credit anyone >> who >> >> has worked on the ResilientDB project since 2018, acknowledging their >> >> contributions. Below is the detailed breakdown of our contributors. So >> we >> >> can reduce the list as needed in accordance with ASF guidelines. As for >> the >> >> broader contributors, these are the folks who have supported >> ResilientDB, >> >> e.g., formalization of the research ideas, discussion of how to tackle a >> >> particular algorithm or its implementation, testing, and analysis. >> However, >> >> these broader members have not contributed to the codebase. So this is >> why >> >> they were tagged differently.*ResilientDB Core *[all have signed ICLA] >> >> Mohammad Sadoghi >> >> Junchao Chen >> >> Dakai Kang >> >> Suyash Gupta [Now at UC Berkeley] >> >> Sajjad Rahnama [Now at Oracle] >> >> Wayne Wang [Now at Hesai Technology] >> >> Julieta Duarte >> >> Glenn Chen >> >> *Tooling/SDK/Wallet/Applications *[all have signed ICLA] >> >> Thamir Qadah [Umm Al-Qura University] >> >> Jinxiao Yu [Now at Amazon AWS] >> >> Arindaam Roy [Now at Square] >> >> Divjeet Singh Jas >> >> Apratim Shukla >> >> Priyal Soni [Now at Amazon AWS] >> >> Rohan Sogani [Now at Oracle] >> >> Kaustubh Shete >> >> Gopal Nambiar >> >> Saipranav Kotamreddy >> >> Haskell Lark Macaraig >> >> >> >> *Deprecated/Obsolete Features *[have been rewritten or removed] >> >> Jelle Hellings [Now at McMaster >> University] >> >> Shesha Vishnu Prasad [Now at Path] >> >> Dhruv Krishnan [Now at Amazon AWS] >> >> Shubham Pandey [Now at Cisco] >> >> Steve Chen >> >> Priya Holani [Now at Amazon AWS] >> >> Haojun (Howard) Zhu >> >> Robert HE [Now at Amazon AWS] >> >> Shreenath Iyer [Now at Amazon AWS] >> >> Domenic Cianfichi [Now at Amazon AWS] >> >> Erik Linsenmayer [Now at General >> >> Atomics] >> >> Shreyan Mohanty [Now at General Atomics] >> >> Xinyuan Sun [Now at CertiK] >> >> Patrick Liao [Now at Juniper Networks] >> >> Tim Huang >> >> Jared Givens >> >> Aditya Bej >> >> Seongwoo Choi >> >> >> >> *Question on Private Development:* >> >> As per request, we have transitioned away from local/private >> development. >> >> We have forked our public ResilientDB, and we began the process of >> moving >> >> all experimental features into this repo. All these ongoing features are >> >> available in this repo but are still under development and not yet >> ready to >> >> be released to the main repository.*Our New Development Repo: * >> >> https://github.com/msadoghi/resilientdb/*Notable Branches (Active >> >> Projects)* >> >> Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe >> >> Rotating Leader (lightweight recovery): >> >> https://github.com/msadoghi/resilientdb/tree/hs >> >> Queue-Oriented Concurrency Control (concurrent execution): >> >> https://github.com/msadoghi/resilientdb/tree/QueccBranch >> >> Smart Contract Concurrency: >> >> https://github.com/msadoghi/resilientdb/tree/smartcontract_cc >> >> >> >> --- >> >> Best Regards, >> >> Mohammad Sadoghi, PhD >> >> Associate Professor >> >> Exploratory Systems Lab (ExpoLab) >> >> Department of Computer Science >> >> University of California, Davis >> >> >> >> ExpoLab: https://expolab.org/ >> >> ResilientDB: https://resilientdb.com/ >> >> Phone: 914-319-7937 >> >> >> >> >> >> On Mon, Oct 9, 2023 at 6:18 PM Dave Fisher >> wrote: >> >> >> >> > >> >> > >> >> > Sent from my iPhone >> >> > >> >> > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > >> .invalid> >> >> > wrote: >> >> > > >> >> > > Hello All >> >> > > >> >> > > Let me try to add to Mohammad's response. We defined an initial >> >> committer >> >> > > list of 40+ members as we wanted to give credit to everyone who has >> >> > > collaborated with us on projects/papers that were built around >> >> > ResilientDB. >> >> > > But, the 20 contributors visible on github are the ones who worked >> on >> >> the >> >> > > actual codebase, which we are trying to bring to ASF. The projects >> that >> >> > > other folks worked on are independent from the ResilientDB codebase >> and >> >> > > have no correlation with this
Re: [DISCUSS] Incubating Proposal of ResilientDB
If no further concerns, I wish to start the vote thread tomorrow. On Wed, 11 Oct 2023 at 12:16 AM, Christian Grobmeier wrote: > I agree too. > > However, I am also concerned the titel is [DISCUSS] - shouldn't this be a > vote already? > > > On Tue, Oct 10, 2023, at 13:42, 俊平堵 wrote: > > Agree with Roman and Dave that we can keep the original list. > > I think Willem is just curious on the mismatch between commits and > > committers, and the explanation here make sense to me. > > > > Thanks, > > > > JP > > > > Mohammad Sadoghi 于2023年10月10日周二 11:50写道： > > > >> Dear all, > >> > >> *Question on Initial Committers:* > >> As was mentioned earlier. The criteria that I used was to credit anyone > who > >> has worked on the ResilientDB project since 2018, acknowledging their > >> contributions. Below is the detailed breakdown of our contributors. So > we > >> can reduce the list as needed in accordance with ASF guidelines. As for > the > >> broader contributors, these are the folks who have supported > ResilientDB, > >> e.g., formalization of the research ideas, discussion of how to tackle a > >> particular algorithm or its implementation, testing, and analysis. > However, > >> these broader members have not contributed to the codebase. So this is > why > >> they were tagged differently.*ResilientDB Core *[all have signed ICLA] > >> Mohammad Sadoghi > >> Junchao Chen > >> Dakai Kang > >> Suyash Gupta [Now at UC Berkeley] > >> Sajjad Rahnama [Now at Oracle] > >> Wayne Wang [Now at Hesai Technology] > >> Julieta Duarte > >> Glenn Chen > >> *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > >> Thamir Qadah [Umm Al-Qura University] > >> Jinxiao Yu [Now at Amazon AWS] > >> Arindaam Roy [Now at Square] > >> Divjeet Singh Jas > >> Apratim Shukla > >> Priyal Soni [Now at Amazon AWS] > >> Rohan Sogani [Now at Oracle] > >> Kaustubh Shete > >> Gopal Nambiar > >> Saipranav Kotamreddy > >> Haskell Lark Macaraig > >> > >> *Deprecated/Obsolete Features *[have been rewritten or removed] > >> Jelle Hellings [Now at McMaster > University] > >> Shesha Vishnu Prasad [Now at Path] > >> Dhruv Krishnan [Now at Amazon AWS] > >> Shubham Pandey [Now at Cisco] > >> Steve Chen > >> Priya Holani [Now at Amazon AWS] > >> Haojun (Howard) Zhu > >> Robert HE [Now at Amazon AWS] > >> Shreenath Iyer [Now at Amazon AWS] > >> Domenic Cianfichi [Now at Amazon AWS] > >> Erik Linsenmayer [Now at General > >> Atomics] > >> Shreyan Mohanty [Now at General Atomics] > >> Xinyuan Sun [Now at CertiK] > >> Patrick Liao [Now at Juniper Networks] > >> Tim Huang > >> Jared Givens > >> Aditya Bej > >> Seongwoo Choi > >> > >> *Question on Private Development:* > >> As per request, we have transitioned away from local/private > development. > >> We have forked our public ResilientDB, and we began the process of > moving > >> all experimental features into this repo. All these ongoing features are > >> available in this repo but are still under development and not yet > ready to > >> be released to the main repository.*Our New Development Repo: * > >> https://github.com/msadoghi/resilientdb/*Notable Branches (Active > >> Projects)* > >> Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe > >> Rotating Leader (lightweight recovery): > >> https://github.com/msadoghi/resilientdb/tree/hs > >> Queue-Oriented Concurrency Control (concurrent execution): > >> https://github.com/msadoghi/resilientdb/tree/QueccBranch > >> Smart Contract Concurrency: > >> https://github.com/msadoghi/resilientdb/tree/smartcontract_cc > >> > >> --- > >> Best Regards, > >> Mohammad Sadoghi, PhD > >> Associate Professor > >> Exploratory Systems Lab (ExpoLab) > >> Department of Computer Science > >> University of California, Davis > >> > >> ExpoLab: https://expolab.org/ > >> ResilientDB: https://resilientdb.com/ > >> Phone: 914-319-7937 > >> > >> > >> On Mon, Oct 9, 2023 at 6:18 PM Dave Fisher > wrote: > >> > >> > > >> > > >> > Sent from my iPhone > >> > > >> > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta >> .invalid> > >> > wrote: > >> > > > >> > > Hello All > >> > > > >> > > Let me try to add to Mohammad's response. We defined an initial > >> committer > >> > > list of 40+ members as we wanted to give credit to everyone who has > >> > > collaborated with us on projects/papers that were built around > >> > ResilientDB. > >> > > But, the 20 contributors visible on github are the ones who worked > on > >> the > >> > > actual codebase, which we are trying to bring to ASF. The projects > that > >> > > other folks worked on are independent from the ResilientDB codebase > and > >> > > have no correlation with this release. > >> > > > >> > > So, following ASF guidelines, we are fine with reducing the initial > >> > > committer list to the 20 members. Please let us know your thoughts. > >> > > >> > One way to consider is that initial committers should be those who > plan > >> to > >> > participate in the Apache ResilientDB community. ASF
Re: [DISCUSS] Incubating Proposal of ResilientDB
I agree too. However, I am also concerned the titel is [DISCUSS] - shouldn't this be a vote already? On Tue, Oct 10, 2023, at 13:42, 俊平堵 wrote: > Agree with Roman and Dave that we can keep the original list. > I think Willem is just curious on the mismatch between commits and > committers, and the explanation here make sense to me. > > Thanks, > > JP > > Mohammad Sadoghi 于2023年10月10日周二 11:50写道： > >> Dear all, >> >> *Question on Initial Committers:* >> As was mentioned earlier. The criteria that I used was to credit anyone who >> has worked on the ResilientDB project since 2018, acknowledging their >> contributions. Below is the detailed breakdown of our contributors. So we >> can reduce the list as needed in accordance with ASF guidelines. As for the >> broader contributors, these are the folks who have supported ResilientDB, >> e.g., formalization of the research ideas, discussion of how to tackle a >> particular algorithm or its implementation, testing, and analysis. However, >> these broader members have not contributed to the codebase. So this is why >> they were tagged differently.*ResilientDB Core *[all have signed ICLA] >> Mohammad Sadoghi >> Junchao Chen >> Dakai Kang >> Suyash Gupta [Now at UC Berkeley] >> Sajjad Rahnama [Now at Oracle] >> Wayne Wang [Now at Hesai Technology] >> Julieta Duarte >> Glenn Chen >> *Tooling/SDK/Wallet/Applications *[all have signed ICLA] >> Thamir Qadah [Umm Al-Qura University] >> Jinxiao Yu [Now at Amazon AWS] >> Arindaam Roy [Now at Square] >> Divjeet Singh Jas >> Apratim Shukla >> Priyal Soni [Now at Amazon AWS] >> Rohan Sogani [Now at Oracle] >> Kaustubh Shete >> Gopal Nambiar >> Saipranav Kotamreddy >> Haskell Lark Macaraig >> >> *Deprecated/Obsolete Features *[have been rewritten or removed] >> Jelle Hellings [Now at McMaster University] >> Shesha Vishnu Prasad [Now at Path] >> Dhruv Krishnan [Now at Amazon AWS] >> Shubham Pandey [Now at Cisco] >> Steve Chen >> Priya Holani [Now at Amazon AWS] >> Haojun (Howard) Zhu >> Robert HE [Now at Amazon AWS] >> Shreenath Iyer [Now at Amazon AWS] >> Domenic Cianfichi [Now at Amazon AWS] >> Erik Linsenmayer [Now at General >> Atomics] >> Shreyan Mohanty [Now at General Atomics] >> Xinyuan Sun [Now at CertiK] >> Patrick Liao [Now at Juniper Networks] >> Tim Huang >> Jared Givens >> Aditya Bej >> Seongwoo Choi >> >> *Question on Private Development:* >> As per request, we have transitioned away from local/private development. >> We have forked our public ResilientDB, and we began the process of moving >> all experimental features into this repo. All these ongoing features are >> available in this repo but are still under development and not yet ready to >> be released to the main repository.*Our New Development Repo: * >> https://github.com/msadoghi/resilientdb/*Notable Branches (Active >> Projects)* >> Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe >> Rotating Leader (lightweight recovery): >> https://github.com/msadoghi/resilientdb/tree/hs >> Queue-Oriented Concurrency Control (concurrent execution): >> https://github.com/msadoghi/resilientdb/tree/QueccBranch >> Smart Contract Concurrency: >> https://github.com/msadoghi/resilientdb/tree/smartcontract_cc >> >> --- >> Best Regards, >> Mohammad Sadoghi, PhD >> Associate Professor >> Exploratory Systems Lab (ExpoLab) >> Department of Computer Science >> University of California, Davis >> >> ExpoLab: https://expolab.org/ >> ResilientDB: https://resilientdb.com/ >> Phone: 914-319-7937 >> >> >> On Mon, Oct 9, 2023 at 6:18 PM Dave Fisher wrote: >> >> > >> > >> > Sent from my iPhone >> > >> > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > .invalid> >> > wrote: >> > > >> > > Hello All >> > > >> > > Let me try to add to Mohammad's response. We defined an initial >> committer >> > > list of 40+ members as we wanted to give credit to everyone who has >> > > collaborated with us on projects/papers that were built around >> > ResilientDB. >> > > But, the 20 contributors visible on github are the ones who worked on >> the >> > > actual codebase, which we are trying to bring to ASF. The projects that >> > > other folks worked on are independent from the ResilientDB codebase and >> > > have no correlation with this release. >> > > >> > > So, following ASF guidelines, we are fine with reducing the initial >> > > committer list to the 20 members. Please let us know your thoughts. >> > >> > One way to consider is that initial committers should be those who plan >> to >> > participate in the Apache ResilientDB community. ASF committers need to >> > sign an ICLA and that will determine how many committers. Nothing >> prevents >> > any of those who don’t sign from contributing. >> > >> > Early in incubation you will need to create a website and you can discuss >> > the history of the project and if they agree those contributors you wish >> to >> > honor. >> > >> > Best wishes, >> > Dave >> > >> > > >> > > >> > >> On Sun, Oct 8,
Re: [DISCUSS] Incubating Proposal of ResilientDB
Agree with Roman and Dave that we can keep the original list. I think Willem is just curious on the mismatch between commits and committers, and the explanation here make sense to me. Thanks, JP Mohammad Sadoghi 于2023年10月10日周二 11:50写道： > Dear all, > > *Question on Initial Committers:* > As was mentioned earlier. The criteria that I used was to credit anyone who > has worked on the ResilientDB project since 2018, acknowledging their > contributions. Below is the detailed breakdown of our contributors. So we > can reduce the list as needed in accordance with ASF guidelines. As for the > broader contributors, these are the folks who have supported ResilientDB, > e.g., formalization of the research ideas, discussion of how to tackle a > particular algorithm or its implementation, testing, and analysis. However, > these broader members have not contributed to the codebase. So this is why > they were tagged differently.*ResilientDB Core *[all have signed ICLA] > Mohammad Sadoghi > Junchao Chen > Dakai Kang > Suyash Gupta [Now at UC Berkeley] > Sajjad Rahnama [Now at Oracle] > Wayne Wang [Now at Hesai Technology] > Julieta Duarte > Glenn Chen > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > Thamir Qadah [Umm Al-Qura University] > Jinxiao Yu [Now at Amazon AWS] > Arindaam Roy [Now at Square] > Divjeet Singh Jas > Apratim Shukla > Priyal Soni [Now at Amazon AWS] > Rohan Sogani [Now at Oracle] > Kaustubh Shete > Gopal Nambiar > Saipranav Kotamreddy > Haskell Lark Macaraig > > *Deprecated/Obsolete Features *[have been rewritten or removed] > Jelle Hellings [Now at McMaster University] > Shesha Vishnu Prasad [Now at Path] > Dhruv Krishnan [Now at Amazon AWS] > Shubham Pandey [Now at Cisco] > Steve Chen > Priya Holani [Now at Amazon AWS] > Haojun (Howard) Zhu > Robert HE [Now at Amazon AWS] > Shreenath Iyer [Now at Amazon AWS] > Domenic Cianfichi [Now at Amazon AWS] > Erik Linsenmayer [Now at General > Atomics] > Shreyan Mohanty [Now at General Atomics] > Xinyuan Sun [Now at CertiK] > Patrick Liao [Now at Juniper Networks] > Tim Huang > Jared Givens > Aditya Bej > Seongwoo Choi > > *Question on Private Development:* > As per request, we have transitioned away from local/private development. > We have forked our public ResilientDB, and we began the process of moving > all experimental features into this repo. All these ongoing features are > available in this repo but are still under development and not yet ready to > be released to the main repository.*Our New Development Repo: * > https://github.com/msadoghi/resilientdb/*Notable Branches (Active > Projects)* > Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe > Rotating Leader (lightweight recovery): > https://github.com/msadoghi/resilientdb/tree/hs > Queue-Oriented Concurrency Control (concurrent execution): > https://github.com/msadoghi/resilientdb/tree/QueccBranch > Smart Contract Concurrency: > https://github.com/msadoghi/resilientdb/tree/smartcontract_cc > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Mon, Oct 9, 2023 at 6:18 PM Dave Fisher wrote: > > > > > > > Sent from my iPhone > > > > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta .invalid> > > wrote: > > > > > > Hello All > > > > > > Let me try to add to Mohammad's response. We defined an initial > committer > > > list of 40+ members as we wanted to give credit to everyone who has > > > collaborated with us on projects/papers that were built around > > ResilientDB. > > > But, the 20 contributors visible on github are the ones who worked on > the > > > actual codebase, which we are trying to bring to ASF. The projects that > > > other folks worked on are independent from the ResilientDB codebase and > > > have no correlation with this release. > > > > > > So, following ASF guidelines, we are fine with reducing the initial > > > committer list to the 20 members. Please let us know your thoughts. > > > > One way to consider is that initial committers should be those who plan > to > > participate in the Apache ResilientDB community. ASF committers need to > > sign an ICLA and that will determine how many committers. Nothing > prevents > > any of those who don’t sign from contributing. > > > > Early in incubation you will need to create a website and you can discuss > > the history of the project and if they agree those contributors you wish > to > > honor. > > > > Best wishes, > > Dave > > > > > > > > > > >> On Sun, Oct 8, 2023 at 9:47 AM Mohammad Sadoghi < > mo.sado...@expolab.org > > > > > >> wrote: > > >> > > >> Everything we have done including research/papers and outcome of > > >> development have been open for years. We simply wanted to keep the > > public > > >> repo cleaner and we only released when we
Re: [DISCUSS] Incubating Proposal of ResilientDB
On Tue, Oct 10, 2023 at 6:50 AM Mohammad Sadoghi wrote: > > Dear all, > > *Question on Initial Committers:* > As was mentioned earlier. The criteria that I used was to credit anyone who > has worked on the ResilientDB project since 2018, acknowledging their > contributions. Below is the detailed breakdown of our contributors. So we > can reduce the list as needed in accordance with ASF guidelines. I suggest you don't. In all of the projects that I helped with Incubation I always encouraged the initial committer list to include everybody (even legacy committers -- people who are clearly no longer participating) and then pare it down at a graduation time. Give everybody a chance to re-engage! What's the worst that can happen? You may actually re-incentivize people to start contributing again! Yay! Thanks, Roman. > As for the > broader contributors, these are the folks who have supported ResilientDB, > e.g., formalization of the research ideas, discussion of how to tackle a > particular algorithm or its implementation, testing, and analysis. However, > these broader members have not contributed to the codebase. So this is why > they were tagged differently.*ResilientDB Core *[all have signed ICLA] > Mohammad Sadoghi > Junchao Chen > Dakai Kang > Suyash Gupta [Now at UC Berkeley] > Sajjad Rahnama [Now at Oracle] > Wayne Wang [Now at Hesai Technology] > Julieta Duarte > Glenn Chen > *Tooling/SDK/Wallet/Applications *[all have signed ICLA] > Thamir Qadah [Umm Al-Qura University] > Jinxiao Yu [Now at Amazon AWS] > Arindaam Roy [Now at Square] > Divjeet Singh Jas > Apratim Shukla > Priyal Soni [Now at Amazon AWS] > Rohan Sogani [Now at Oracle] > Kaustubh Shete > Gopal Nambiar > Saipranav Kotamreddy > Haskell Lark Macaraig > > *Deprecated/Obsolete Features *[have been rewritten or removed] > Jelle Hellings [Now at McMaster University] > Shesha Vishnu Prasad [Now at Path] > Dhruv Krishnan [Now at Amazon AWS] > Shubham Pandey [Now at Cisco] > Steve Chen > Priya Holani [Now at Amazon AWS] > Haojun (Howard) Zhu > Robert HE [Now at Amazon AWS] > Shreenath Iyer [Now at Amazon AWS] > Domenic Cianfichi [Now at Amazon AWS] > Erik Linsenmayer [Now at General Atomics] > Shreyan Mohanty [Now at General Atomics] > Xinyuan Sun [Now at CertiK] > Patrick Liao [Now at Juniper Networks] > Tim Huang > Jared Givens > Aditya Bej > Seongwoo Choi > > *Question on Private Development:* > As per request, we have transitioned away from local/private development. > We have forked our public ResilientDB, and we began the process of moving > all experimental features into this repo. All these ongoing features are > available in this repo but are still under development and not yet ready to > be released to the main repository.*Our New Development Repo: * > https://github.com/msadoghi/resilientdb/*Notable Branches (Active Projects)* > Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe > Rotating Leader (lightweight recovery): > https://github.com/msadoghi/resilientdb/tree/hs > Queue-Oriented Concurrency Control (concurrent execution): > https://github.com/msadoghi/resilientdb/tree/QueccBranch > Smart Contract Concurrency: > https://github.com/msadoghi/resilientdb/tree/smartcontract_cc > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Mon, Oct 9, 2023 at 6:18 PM Dave Fisher wrote: > > > > > > > Sent from my iPhone > > > > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > > > > > wrote: > > > > > > Hello All > > > > > > Let me try to add to Mohammad's response. We defined an initial committer > > > list of 40+ members as we wanted to give credit to everyone who has > > > collaborated with us on projects/papers that were built around > > ResilientDB. > > > But, the 20 contributors visible on github are the ones who worked on the > > > actual codebase, which we are trying to bring to ASF. The projects that > > > other folks worked on are independent from the ResilientDB codebase and > > > have no correlation with this release. > > > > > > So, following ASF guidelines, we are fine with reducing the initial > > > committer list to the 20 members. Please let us know your thoughts. > > > > One way to consider is that initial committers should be those who plan to > > participate in the Apache ResilientDB community. ASF committers need to > > sign an ICLA and that will determine how many committers. Nothing prevents > > any of those who don’t sign from contributing. > > > > Early in incubation you will need to create a website and you can discuss > > the history of the project and if they agree those contributors you wish to > > honor. > > > > Best wishes, > > Dave > > > > > > > > > > >> On Sun, Oct 8, 2023 at 9:47 AM Mohammad Sadoghi > > > > >> wrote: > > >> > > >>
Re: [DISCUSS] Incubating Proposal of ResilientDB
Dear all, *Question on Initial Committers:* As was mentioned earlier. The criteria that I used was to credit anyone who has worked on the ResilientDB project since 2018, acknowledging their contributions. Below is the detailed breakdown of our contributors. So we can reduce the list as needed in accordance with ASF guidelines. As for the broader contributors, these are the folks who have supported ResilientDB, e.g., formalization of the research ideas, discussion of how to tackle a particular algorithm or its implementation, testing, and analysis. However, these broader members have not contributed to the codebase. So this is why they were tagged differently.*ResilientDB Core *[all have signed ICLA] Mohammad Sadoghi Junchao Chen Dakai Kang Suyash Gupta [Now at UC Berkeley] Sajjad Rahnama [Now at Oracle] Wayne Wang [Now at Hesai Technology] Julieta Duarte Glenn Chen *Tooling/SDK/Wallet/Applications *[all have signed ICLA] Thamir Qadah [Umm Al-Qura University] Jinxiao Yu [Now at Amazon AWS] Arindaam Roy [Now at Square] Divjeet Singh Jas Apratim Shukla Priyal Soni [Now at Amazon AWS] Rohan Sogani [Now at Oracle] Kaustubh Shete Gopal Nambiar Saipranav Kotamreddy Haskell Lark Macaraig *Deprecated/Obsolete Features *[have been rewritten or removed] Jelle Hellings [Now at McMaster University] Shesha Vishnu Prasad [Now at Path] Dhruv Krishnan [Now at Amazon AWS] Shubham Pandey [Now at Cisco] Steve Chen Priya Holani [Now at Amazon AWS] Haojun (Howard) Zhu Robert HE [Now at Amazon AWS] Shreenath Iyer [Now at Amazon AWS] Domenic Cianfichi [Now at Amazon AWS] Erik Linsenmayer [Now at General Atomics] Shreyan Mohanty [Now at General Atomics] Xinyuan Sun [Now at CertiK] Patrick Liao [Now at Juniper Networks] Tim Huang Jared Givens Aditya Bej Seongwoo Choi *Question on Private Development:* As per request, we have transitioned away from local/private development. We have forked our public ResilientDB, and we began the process of moving all experimental features into this repo. All these ongoing features are available in this repo but are still under development and not yet ready to be released to the main repository.*Our New Development Repo: * https://github.com/msadoghi/resilientdb/*Notable Branches (Active Projects)* Speculative Consensus: https://github.com/msadoghi/resilientdb/tree/poe Rotating Leader (lightweight recovery): https://github.com/msadoghi/resilientdb/tree/hs Queue-Oriented Concurrency Control (concurrent execution): https://github.com/msadoghi/resilientdb/tree/QueccBranch Smart Contract Concurrency: https://github.com/msadoghi/resilientdb/tree/smartcontract_cc --- Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis ExpoLab: https://expolab.org/ ResilientDB: https://resilientdb.com/ Phone: 914-319-7937 On Mon, Oct 9, 2023 at 6:18 PM Dave Fisher wrote: > > > Sent from my iPhone > > > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > wrote: > > > > Hello All > > > > Let me try to add to Mohammad's response. We defined an initial committer > > list of 40+ members as we wanted to give credit to everyone who has > > collaborated with us on projects/papers that were built around > ResilientDB. > > But, the 20 contributors visible on github are the ones who worked on the > > actual codebase, which we are trying to bring to ASF. The projects that > > other folks worked on are independent from the ResilientDB codebase and > > have no correlation with this release. > > > > So, following ASF guidelines, we are fine with reducing the initial > > committer list to the 20 members. Please let us know your thoughts. > > One way to consider is that initial committers should be those who plan to > participate in the Apache ResilientDB community. ASF committers need to > sign an ICLA and that will determine how many committers. Nothing prevents > any of those who don’t sign from contributing. > > Early in incubation you will need to create a website and you can discuss > the history of the project and if they agree those contributors you wish to > honor. > > Best wishes, > Dave > > > > > > >> On Sun, Oct 8, 2023 at 9:47 AM Mohammad Sadoghi > > >> wrote: > >> > >> Everything we have done including research/papers and outcome of > >> development have been open for years. We simply wanted to keep the > public > >> repo cleaner and we only released when we were certain that the new > feature > >> is well tested and stable. > >> > >> We will switch our development completely to our public repo effective > >> immediately. That is not issue at all. > >> > >> Best Regards, > >> Mohammad Sadoghi, PhD > >> Associate Professor > >> Exploratory Systems Lab (ExpoLab) > >> Department of Computer Science > >> University of California, Davis > >> > >> > >> On Sun, Oct 8, 2023 at 3:08 AM Willem Jiang > >> wrote: > >> > >>> I just checked the GitHub issue and PRs of ResilientDB. There is > >>>
Re: [DISCUSS] Incubating Proposal of ResilientDB
Sent from my iPhone > On Oct 9, 2023, at 7:51 PM, Suyash Gupta > wrote: > > Hello All > > Let me try to add to Mohammad's response. We defined an initial committer > list of 40+ members as we wanted to give credit to everyone who has > collaborated with us on projects/papers that were built around ResilientDB. > But, the 20 contributors visible on github are the ones who worked on the > actual codebase, which we are trying to bring to ASF. The projects that > other folks worked on are independent from the ResilientDB codebase and > have no correlation with this release. > > So, following ASF guidelines, we are fine with reducing the initial > committer list to the 20 members. Please let us know your thoughts. One way to consider is that initial committers should be those who plan to participate in the Apache ResilientDB community. ASF committers need to sign an ICLA and that will determine how many committers. Nothing prevents any of those who don’t sign from contributing. Early in incubation you will need to create a website and you can discuss the history of the project and if they agree those contributors you wish to honor. Best wishes, Dave > > >> On Sun, Oct 8, 2023 at 9:47 AM Mohammad Sadoghi >> wrote: >> >> Everything we have done including research/papers and outcome of >> development have been open for years. We simply wanted to keep the public >> repo cleaner and we only released when we were certain that the new feature >> is well tested and stable. >> >> We will switch our development completely to our public repo effective >> immediately. That is not issue at all. >> >> Best Regards, >> Mohammad Sadoghi, PhD >> Associate Professor >> Exploratory Systems Lab (ExpoLab) >> Department of Computer Science >> University of California, Davis >> >> >> On Sun, Oct 8, 2023 at 3:08 AM Willem Jiang >> wrote: >> >>> I just checked the GitHub issue and PRs of ResilientDB. There is >>> little discussion on the GitHub issue and review comments on GitHub >>> PRs. >>> Please keep Open Communications[1] in mind. We value transparency in >>> the ASF way. Internal development could block the contributions >>> outside of the organization and cause us some trouble in building the >>> community. >>> >>> Once the development switches to the public repo, the project could be >>> ready to enter the incubation process. >>> >>> [1] >>> >> https://www.apache.org/theapacheway/#what-makes-the-apache-way-so-hard-to-define >>> >>> >>> Willem Jiang >>> >>> Twitter: willemjiang >>> Weibo: 姜宁willem >>> >>> On Sun, Oct 8, 2023 at 3:33 PM Mohammad Sadoghi >>> wrote: Thank you for your question. With regards to the initial committers, over the years we had much >> larger set of contributors who worked on the private repo of ResilientDB which derives the research. Only when features are stable and well tested >> over time, they have been advanced and promoted to our public repo. Our >>> private repo has many more experimental features that as part of our roadmap >> will be released once they reach the same level of maturity. Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis On Sun, Oct 8, 2023 at 12:23 AM Willem Jiang >>> wrote: > Hi, > > I have a quick question about the initial committers. > There are about 40+ initial committers, but I can only find about 20 > contributors in the GitHub group[1] contributor list. > Could you explain the initial committer criteria? > There is a section of "Broader Contributing Members" in the > proposal[2] after the initial committer, if we treat them as initial > committers, why do we need to separate them with the initial > committer? > > Thanks, > > [1]https://github.com/resilientdb > [2] > >>> >> https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sun, Oct 8, 2023 at 1:38 PM 俊平堵 wrote: >> >> +1. >> btw, I assume we will have an official vote thread (start with >>> [VOTE]) >> later? >> >> Thanks, >> >> JP >> >> Atri Sharma 于2023年10月3日周二 19:24写道： >> >>> We want to propose ResilientDB as a new Apache Incubator project. >>> >>> ResilientDB[1] is a distributed blockchain framework that is >>> written >>> in C++ and integrates with Byzantine Fault-Tolerant (BFT) and >> Crash >>> Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. >>> >>> Key features: >>> >>> Provides a scalable client-server architecture. Each developer >> can >>> use >>> the ResilientDB framework to deploy a replicated service acting >> as >>> a >>> service. The developer can choose the desired
Re: [DISCUSS] Incubating Proposal of ResilientDB
Hello All Let me try to add to Mohammad's response. We defined an initial committer list of 40+ members as we wanted to give credit to everyone who has collaborated with us on projects/papers that were built around ResilientDB. But, the 20 contributors visible on github are the ones who worked on the actual codebase, which we are trying to bring to ASF. The projects that other folks worked on are independent from the ResilientDB codebase and have no correlation with this release. So, following ASF guidelines, we are fine with reducing the initial committer list to the 20 members. Please let us know your thoughts. On Sun, Oct 8, 2023 at 9:47 AM Mohammad Sadoghi wrote: > Everything we have done including research/papers and outcome of > development have been open for years. We simply wanted to keep the public > repo cleaner and we only released when we were certain that the new feature > is well tested and stable. > > We will switch our development completely to our public repo effective > immediately. That is not issue at all. > > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > > On Sun, Oct 8, 2023 at 3:08 AM Willem Jiang > wrote: > > > I just checked the GitHub issue and PRs of ResilientDB. There is > > little discussion on the GitHub issue and review comments on GitHub > > PRs. > > Please keep Open Communications[1] in mind. We value transparency in > > the ASF way. Internal development could block the contributions > > outside of the organization and cause us some trouble in building the > > community. > > > > Once the development switches to the public repo, the project could be > > ready to enter the incubation process. > > > > [1] > > > https://www.apache.org/theapacheway/#what-makes-the-apache-way-so-hard-to-define > > > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Sun, Oct 8, 2023 at 3:33 PM Mohammad Sadoghi > > wrote: > > > > > > Thank you for your question. > > > > > > With regards to the initial committers, over the years we had much > larger > > > set of contributors who worked on the private repo of ResilientDB which > > > derives the research. Only when features are stable and well tested > over > > > time, they have been advanced and promoted to our public repo. Our > > private > > > repo has many more experimental features that as part of our roadmap > will > > > be released once they reach the same level of maturity. > > > > > > Best Regards, > > > Mohammad Sadoghi, PhD > > > Associate Professor > > > Exploratory Systems Lab (ExpoLab) > > > Department of Computer Science > > > University of California, Davis > > > > > > > > > On Sun, Oct 8, 2023 at 12:23 AM Willem Jiang > > wrote: > > > > > > > Hi, > > > > > > > > I have a quick question about the initial committers. > > > > There are about 40+ initial committers, but I can only find about 20 > > > > contributors in the GitHub group[1] contributor list. > > > > Could you explain the initial committer criteria? > > > > There is a section of "Broader Contributing Members" in the > > > > proposal[2] after the initial committer, if we treat them as initial > > > > committers, why do we need to separate them with the initial > > > > committer? > > > > > > > > Thanks, > > > > > > > > [1]https://github.com/resilientdb > > > > [2] > > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > > > > > > > Willem Jiang > > > > > > > > Twitter: willemjiang > > > > Weibo: 姜宁willem > > > > > > > > On Sun, Oct 8, 2023 at 1:38 PM 俊平堵 wrote: > > > > > > > > > > +1. > > > > > btw, I assume we will have an official vote thread (start with > > [VOTE]) > > > > > later? > > > > > > > > > > Thanks, > > > > > > > > > > JP > > > > > > > > > > Atri Sharma 于2023年10月3日周二 19:24写道： > > > > > > > > > > > We want to propose ResilientDB as a new Apache Incubator project. > > > > > > > > > > > > ResilientDB[1] is a distributed blockchain framework that is > > written > > > > > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and > Crash > > > > > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > > > > > > > > > Key features: > > > > > > > > > > > > Provides a scalable client-server architecture. Each developer > can > > use > > > > > > the ResilientDB framework to deploy a replicated service acting > as > > a > > > > > > service. The developer can choose the desired number of replicas > > and > > > > > > the number of clients its system should tolerate. > > > > > > > > > > > > Provides native integration with PBFT consensus protocol – > arguably > > > > > > the most popular BFT consensus protocol. PBFT helps replicas > reach > > an > > > > > > agreement for ordering the client's requests. > > > > > > > > > > > > Provides a mechanism to simulate the failure of different > replicas > > > > > > (including the leader). > > > > > > > > > > > >
Re: [DISCUSS] Incubating Proposal of ResilientDB
Everything we have done including research/papers and outcome of development have been open for years. We simply wanted to keep the public repo cleaner and we only released when we were certain that the new feature is well tested and stable. We will switch our development completely to our public repo effective immediately. That is not issue at all. Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis On Sun, Oct 8, 2023 at 3:08 AM Willem Jiang wrote: > I just checked the GitHub issue and PRs of ResilientDB. There is > little discussion on the GitHub issue and review comments on GitHub > PRs. > Please keep Open Communications[1] in mind. We value transparency in > the ASF way. Internal development could block the contributions > outside of the organization and cause us some trouble in building the > community. > > Once the development switches to the public repo, the project could be > ready to enter the incubation process. > > [1] > https://www.apache.org/theapacheway/#what-makes-the-apache-way-so-hard-to-define > > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sun, Oct 8, 2023 at 3:33 PM Mohammad Sadoghi > wrote: > > > > Thank you for your question. > > > > With regards to the initial committers, over the years we had much larger > > set of contributors who worked on the private repo of ResilientDB which > > derives the research. Only when features are stable and well tested over > > time, they have been advanced and promoted to our public repo. Our > private > > repo has many more experimental features that as part of our roadmap will > > be released once they reach the same level of maturity. > > > > Best Regards, > > Mohammad Sadoghi, PhD > > Associate Professor > > Exploratory Systems Lab (ExpoLab) > > Department of Computer Science > > University of California, Davis > > > > > > On Sun, Oct 8, 2023 at 12:23 AM Willem Jiang > wrote: > > > > > Hi, > > > > > > I have a quick question about the initial committers. > > > There are about 40+ initial committers, but I can only find about 20 > > > contributors in the GitHub group[1] contributor list. > > > Could you explain the initial committer criteria? > > > There is a section of "Broader Contributing Members" in the > > > proposal[2] after the initial committer, if we treat them as initial > > > committers, why do we need to separate them with the initial > > > committer? > > > > > > Thanks, > > > > > > [1]https://github.com/resilientdb > > > [2] > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > > > > > Willem Jiang > > > > > > Twitter: willemjiang > > > Weibo: 姜宁willem > > > > > > On Sun, Oct 8, 2023 at 1:38 PM 俊平堵 wrote: > > > > > > > > +1. > > > > btw, I assume we will have an official vote thread (start with > [VOTE]) > > > > later? > > > > > > > > Thanks, > > > > > > > > JP > > > > > > > > Atri Sharma 于2023年10月3日周二 19:24写道： > > > > > > > > > We want to propose ResilientDB as a new Apache Incubator project. > > > > > > > > > > ResilientDB[1] is a distributed blockchain framework that is > written > > > > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > > > > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > > > > > > > Key features: > > > > > > > > > > Provides a scalable client-server architecture. Each developer can > use > > > > > the ResilientDB framework to deploy a replicated service acting as > a > > > > > service. The developer can choose the desired number of replicas > and > > > > > the number of clients its system should tolerate. > > > > > > > > > > Provides native integration with PBFT consensus protocol – arguably > > > > > the most popular BFT consensus protocol. PBFT helps replicas reach > an > > > > > agreement for ordering the client's requests. > > > > > > > > > > Provides a mechanism to simulate the failure of different replicas > > > > > (including the leader). > > > > > > > > > > Provides a correct implementation of the view-change protocol that > > > > > replaces a faulty (or malicious) leader and moves all replicas to > the > > > > > new view. > > > > > > > > > > Provides checkpoint and recovery protocols to facilitate garbage > > > > > collection, recovery of failed replicas, and durably logging of the > > > > > blockchain state. > > > > > > > > > > Eases development and testing of newer and optimized BFT and CFT > > > > > consensus protocols. > > > > > Provides clients with support for three different application > > > interfaces: > > > > > > > > > > Key-Value Stores - where client transactions include key-value > pairs. > > > > > > > > > > Smart Contracts - where clients issue smart contracts in Solidity > for > > > > > processing. > > > > > > > > > > UTXO - where clients issue unspent transactions similar to ones in > > > Bitcoin. > > > > > > > > > > Facilitates benchmarking system/protocol performance with the
Re: [DISCUSS] Incubating Proposal of ResilientDB
I just checked the GitHub issue and PRs of ResilientDB. There is little discussion on the GitHub issue and review comments on GitHub PRs. Please keep Open Communications[1] in mind. We value transparency in the ASF way. Internal development could block the contributions outside of the organization and cause us some trouble in building the community. Once the development switches to the public repo, the project could be ready to enter the incubation process. [1]https://www.apache.org/theapacheway/#what-makes-the-apache-way-so-hard-to-define Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Oct 8, 2023 at 3:33 PM Mohammad Sadoghi wrote: > > Thank you for your question. > > With regards to the initial committers, over the years we had much larger > set of contributors who worked on the private repo of ResilientDB which > derives the research. Only when features are stable and well tested over > time, they have been advanced and promoted to our public repo. Our private > repo has many more experimental features that as part of our roadmap will > be released once they reach the same level of maturity. > > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > > On Sun, Oct 8, 2023 at 12:23 AM Willem Jiang wrote: > > > Hi, > > > > I have a quick question about the initial committers. > > There are about 40+ initial committers, but I can only find about 20 > > contributors in the GitHub group[1] contributor list. > > Could you explain the initial committer criteria? > > There is a section of "Broader Contributing Members" in the > > proposal[2] after the initial committer, if we treat them as initial > > committers, why do we need to separate them with the initial > > committer? > > > > Thanks, > > > > [1]https://github.com/resilientdb > > [2] > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > > > Willem Jiang > > > > Twitter: willemjiang > > Weibo: 姜宁willem > > > > On Sun, Oct 8, 2023 at 1:38 PM 俊平堵 wrote: > > > > > > +1. > > > btw, I assume we will have an official vote thread (start with [VOTE]) > > > later? > > > > > > Thanks, > > > > > > JP > > > > > > Atri Sharma 于2023年10月3日周二 19:24写道： > > > > > > > We want to propose ResilientDB as a new Apache Incubator project. > > > > > > > > ResilientDB[1] is a distributed blockchain framework that is written > > > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > > > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > > > > > Key features: > > > > > > > > Provides a scalable client-server architecture. Each developer can use > > > > the ResilientDB framework to deploy a replicated service acting as a > > > > service. The developer can choose the desired number of replicas and > > > > the number of clients its system should tolerate. > > > > > > > > Provides native integration with PBFT consensus protocol – arguably > > > > the most popular BFT consensus protocol. PBFT helps replicas reach an > > > > agreement for ordering the client's requests. > > > > > > > > Provides a mechanism to simulate the failure of different replicas > > > > (including the leader). > > > > > > > > Provides a correct implementation of the view-change protocol that > > > > replaces a faulty (or malicious) leader and moves all replicas to the > > > > new view. > > > > > > > > Provides checkpoint and recovery protocols to facilitate garbage > > > > collection, recovery of failed replicas, and durably logging of the > > > > blockchain state. > > > > > > > > Eases development and testing of newer and optimized BFT and CFT > > > > consensus protocols. > > > > Provides clients with support for three different application > > interfaces: > > > > > > > > Key-Value Stores - where client transactions include key-value pairs. > > > > > > > > Smart Contracts - where clients issue smart contracts in Solidity for > > > > processing. > > > > > > > > UTXO - where clients issue unspent transactions similar to ones in > > Bitcoin. > > > > > > > > Facilitates benchmarking system/protocol performance with the help of > > > > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > > > > > > > Stores non-volatile ledger (blockchain) in memory and for further > > > > durability, provides APIs to store both client data and blockchain in > > > > LevelDB and RocksDB. > > > > > > > > > > > > The serving mentors would be: > > > > > > > > Junping Du > > > > > > > > Calvin Kirs > > > > > > > > Kevin Ratnasekera > > > > > > > > Roman Shaposhnik > > > > > > > > Christian Grobmeier > > > > > > > > and I shall be serving as the Champion. > > > > > > > > We have not done a trademark check yet for the name but that can be > > > > pursued independently. > > > > > > > > [1] > > > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > > > [2]
Re: [DISCUSS] Incubating Proposal of ResilientDB
Thank you for your question. With regards to the initial committers, over the years we had much larger set of contributors who worked on the private repo of ResilientDB which derives the research. Only when features are stable and well tested over time, they have been advanced and promoted to our public repo. Our private repo has many more experimental features that as part of our roadmap will be released once they reach the same level of maturity. Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis On Sun, Oct 8, 2023 at 12:23 AM Willem Jiang wrote: > Hi, > > I have a quick question about the initial committers. > There are about 40+ initial committers, but I can only find about 20 > contributors in the GitHub group[1] contributor list. > Could you explain the initial committer criteria? > There is a section of "Broader Contributing Members" in the > proposal[2] after the initial committer, if we treat them as initial > committers, why do we need to separate them with the initial > committer? > > Thanks, > > [1]https://github.com/resilientdb > [2] > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Sun, Oct 8, 2023 at 1:38 PM 俊平堵 wrote: > > > > +1. > > btw, I assume we will have an official vote thread (start with [VOTE]) > > later? > > > > Thanks, > > > > JP > > > > Atri Sharma 于2023年10月3日周二 19:24写道： > > > > > We want to propose ResilientDB as a new Apache Incubator project. > > > > > > ResilientDB[1] is a distributed blockchain framework that is written > > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > > > Key features: > > > > > > Provides a scalable client-server architecture. Each developer can use > > > the ResilientDB framework to deploy a replicated service acting as a > > > service. The developer can choose the desired number of replicas and > > > the number of clients its system should tolerate. > > > > > > Provides native integration with PBFT consensus protocol – arguably > > > the most popular BFT consensus protocol. PBFT helps replicas reach an > > > agreement for ordering the client's requests. > > > > > > Provides a mechanism to simulate the failure of different replicas > > > (including the leader). > > > > > > Provides a correct implementation of the view-change protocol that > > > replaces a faulty (or malicious) leader and moves all replicas to the > > > new view. > > > > > > Provides checkpoint and recovery protocols to facilitate garbage > > > collection, recovery of failed replicas, and durably logging of the > > > blockchain state. > > > > > > Eases development and testing of newer and optimized BFT and CFT > > > consensus protocols. > > > Provides clients with support for three different application > interfaces: > > > > > > Key-Value Stores - where client transactions include key-value pairs. > > > > > > Smart Contracts - where clients issue smart contracts in Solidity for > > > processing. > > > > > > UTXO - where clients issue unspent transactions similar to ones in > Bitcoin. > > > > > > Facilitates benchmarking system/protocol performance with the help of > > > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > > > > > Stores non-volatile ledger (blockchain) in memory and for further > > > durability, provides APIs to store both client data and blockchain in > > > LevelDB and RocksDB. > > > > > > > > > The serving mentors would be: > > > > > > Junping Du > > > > > > Calvin Kirs > > > > > > Kevin Ratnasekera > > > > > > Roman Shaposhnik > > > > > > Christian Grobmeier > > > > > > and I shall be serving as the Champion. > > > > > > We have not done a trademark check yet for the name but that can be > > > pursued independently. > > > > > > [1] > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > > [2] https://github.com/resilientdb/resilientdb > > > > > > Atri > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Incubating Proposal of ResilientDB
Hi, I have a quick question about the initial committers. There are about 40+ initial committers, but I can only find about 20 contributors in the GitHub group[1] contributor list. Could you explain the initial committer criteria? There is a section of "Broader Contributing Members" in the proposal[2] after the initial committer, if we treat them as initial committers, why do we need to separate them with the initial committer? Thanks, [1]https://github.com/resilientdb [2]https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Sun, Oct 8, 2023 at 1:38 PM 俊平堵 wrote: > > +1. > btw, I assume we will have an official vote thread (start with [VOTE]) > later? > > Thanks, > > JP > > Atri Sharma 于2023年10月3日周二 19:24写道： > > > We want to propose ResilientDB as a new Apache Incubator project. > > > > ResilientDB[1] is a distributed blockchain framework that is written > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > Key features: > > > > Provides a scalable client-server architecture. Each developer can use > > the ResilientDB framework to deploy a replicated service acting as a > > service. The developer can choose the desired number of replicas and > > the number of clients its system should tolerate. > > > > Provides native integration with PBFT consensus protocol – arguably > > the most popular BFT consensus protocol. PBFT helps replicas reach an > > agreement for ordering the client's requests. > > > > Provides a mechanism to simulate the failure of different replicas > > (including the leader). > > > > Provides a correct implementation of the view-change protocol that > > replaces a faulty (or malicious) leader and moves all replicas to the > > new view. > > > > Provides checkpoint and recovery protocols to facilitate garbage > > collection, recovery of failed replicas, and durably logging of the > > blockchain state. > > > > Eases development and testing of newer and optimized BFT and CFT > > consensus protocols. > > Provides clients with support for three different application interfaces: > > > > Key-Value Stores - where client transactions include key-value pairs. > > > > Smart Contracts - where clients issue smart contracts in Solidity for > > processing. > > > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > > > Facilitates benchmarking system/protocol performance with the help of > > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > > > Stores non-volatile ledger (blockchain) in memory and for further > > durability, provides APIs to store both client data and blockchain in > > LevelDB and RocksDB. > > > > > > The serving mentors would be: > > > > Junping Du > > > > Calvin Kirs > > > > Kevin Ratnasekera > > > > Roman Shaposhnik > > > > Christian Grobmeier > > > > and I shall be serving as the Champion. > > > > We have not done a trademark check yet for the name but that can be > > pursued independently. > > > > [1] > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > [2] https://github.com/resilientdb/resilientdb > > > > Atri > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of ResilientDB
+1. btw, I assume we will have an official vote thread (start with [VOTE]) later? Thanks, JP Atri Sharma 于2023年10月3日周二 19:24写道： > We want to propose ResilientDB as a new Apache Incubator project. > > ResilientDB[1] is a distributed blockchain framework that is written > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > Key features: > > Provides a scalable client-server architecture. Each developer can use > the ResilientDB framework to deploy a replicated service acting as a > service. The developer can choose the desired number of replicas and > the number of clients its system should tolerate. > > Provides native integration with PBFT consensus protocol – arguably > the most popular BFT consensus protocol. PBFT helps replicas reach an > agreement for ordering the client's requests. > > Provides a mechanism to simulate the failure of different replicas > (including the leader). > > Provides a correct implementation of the view-change protocol that > replaces a faulty (or malicious) leader and moves all replicas to the > new view. > > Provides checkpoint and recovery protocols to facilitate garbage > collection, recovery of failed replicas, and durably logging of the > blockchain state. > > Eases development and testing of newer and optimized BFT and CFT > consensus protocols. > Provides clients with support for three different application interfaces: > > Key-Value Stores - where client transactions include key-value pairs. > > Smart Contracts - where clients issue smart contracts in Solidity for > processing. > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > Facilitates benchmarking system/protocol performance with the help of > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > Stores non-volatile ledger (blockchain) in memory and for further > durability, provides APIs to store both client data and blockchain in > LevelDB and RocksDB. > > > The serving mentors would be: > > Junping Du > > Calvin Kirs > > Kevin Ratnasekera > > Roman Shaposhnik > > Christian Grobmeier > > and I shall be serving as the Champion. > > We have not done a trademark check yet for the name but that can be > pursued independently. > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > [2] https://github.com/resilientdb/resilientdb > > Atri > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Incubating Proposal of ResilientDB
+1 (binding) Regards JB Le mar. 3 oct. 2023 à 13:23, Atri Sharma a écrit : > We want to propose ResilientDB as a new Apache Incubator project. > > ResilientDB[1] is a distributed blockchain framework that is written > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > Key features: > > Provides a scalable client-server architecture. Each developer can use > the ResilientDB framework to deploy a replicated service acting as a > service. The developer can choose the desired number of replicas and > the number of clients its system should tolerate. > > Provides native integration with PBFT consensus protocol – arguably > the most popular BFT consensus protocol. PBFT helps replicas reach an > agreement for ordering the client's requests. > > Provides a mechanism to simulate the failure of different replicas > (including the leader). > > Provides a correct implementation of the view-change protocol that > replaces a faulty (or malicious) leader and moves all replicas to the > new view. > > Provides checkpoint and recovery protocols to facilitate garbage > collection, recovery of failed replicas, and durably logging of the > blockchain state. > > Eases development and testing of newer and optimized BFT and CFT > consensus protocols. > Provides clients with support for three different application interfaces: > > Key-Value Stores - where client transactions include key-value pairs. > > Smart Contracts - where clients issue smart contracts in Solidity for > processing. > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > Facilitates benchmarking system/protocol performance with the help of > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > Stores non-volatile ledger (blockchain) in memory and for further > durability, provides APIs to store both client data and blockchain in > LevelDB and RocksDB. > > > The serving mentors would be: > > Junping Du > > Calvin Kirs > > Kevin Ratnasekera > > Roman Shaposhnik > > Christian Grobmeier > > and I shall be serving as the Champion. > > We have not done a trademark check yet for the name but that can be > pursued independently. > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > [2] https://github.com/resilientdb/resilientdb > > Atri > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Incubating Proposal of ResilientDB
On Tue, Oct 3, 2023 at 2:24 PM Atri Sharma wrote: > > We want to propose ResilientDB as a new Apache Incubator project. > > ResilientDB[1] is a distributed blockchain framework that is written > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > Key features: > > Provides a scalable client-server architecture. Each developer can use > the ResilientDB framework to deploy a replicated service acting as a > service. The developer can choose the desired number of replicas and > the number of clients its system should tolerate. > > Provides native integration with PBFT consensus protocol – arguably > the most popular BFT consensus protocol. PBFT helps replicas reach an > agreement for ordering the client's requests. > > Provides a mechanism to simulate the failure of different replicas > (including the leader). > > Provides a correct implementation of the view-change protocol that > replaces a faulty (or malicious) leader and moves all replicas to the > new view. > > Provides checkpoint and recovery protocols to facilitate garbage > collection, recovery of failed replicas, and durably logging of the > blockchain state. > > Eases development and testing of newer and optimized BFT and CFT > consensus protocols. > Provides clients with support for three different application interfaces: > > Key-Value Stores - where client transactions include key-value pairs. > > Smart Contracts - where clients issue smart contracts in Solidity for > processing. > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > Facilitates benchmarking system/protocol performance with the help of > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > Stores non-volatile ledger (blockchain) in memory and for further > durability, provides APIs to store both client data and blockchain in > LevelDB and RocksDB. > > > The serving mentors would be: > > Junping Du > > Calvin Kirs > > Kevin Ratnasekera > > Roman Shaposhnik > > Christian Grobmeier > > and I shall be serving as the Champion. > > We have not done a trademark check yet for the name but that can be > pursued independently. > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > [2] https://github.com/resilientdb/resilientdb +1 (binding) Thanks, Roman. - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of ResilientDB
+1 (binding) On Thu, Oct 5, 2023 at 6:03 AM Uma Maheswara Rao Gangumalla wrote: > > +1 (binding) > > Regards, > Uma > > On Tue, Oct 3, 2023 at 4:23 AM Atri Sharma wrote: > > > We want to propose ResilientDB as a new Apache Incubator project. > > > > ResilientDB[1] is a distributed blockchain framework that is written > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > Key features: > > > > Provides a scalable client-server architecture. Each developer can use > > the ResilientDB framework to deploy a replicated service acting as a > > service. The developer can choose the desired number of replicas and > > the number of clients its system should tolerate. > > > > Provides native integration with PBFT consensus protocol – arguably > > the most popular BFT consensus protocol. PBFT helps replicas reach an > > agreement for ordering the client's requests. > > > > Provides a mechanism to simulate the failure of different replicas > > (including the leader). > > > > Provides a correct implementation of the view-change protocol that > > replaces a faulty (or malicious) leader and moves all replicas to the > > new view. > > > > Provides checkpoint and recovery protocols to facilitate garbage > > collection, recovery of failed replicas, and durably logging of the > > blockchain state. > > > > Eases development and testing of newer and optimized BFT and CFT > > consensus protocols. > > Provides clients with support for three different application interfaces: > > > > Key-Value Stores - where client transactions include key-value pairs. > > > > Smart Contracts - where clients issue smart contracts in Solidity for > > processing. > > > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > > > Facilitates benchmarking system/protocol performance with the help of > > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > > > Stores non-volatile ledger (blockchain) in memory and for further > > durability, provides APIs to store both client data and blockchain in > > LevelDB and RocksDB. > > > > > > The serving mentors would be: > > > > Junping Du > > > > Calvin Kirs > > > > Kevin Ratnasekera > > > > Roman Shaposhnik > > > > Christian Grobmeier > > > > and I shall be serving as the Champion. > > > > We have not done a trademark check yet for the name but that can be > > pursued independently. > > > > [1] > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > [2] https://github.com/resilientdb/resilientdb > > > > Atri > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > -- Best wishes！ CalvinKirs - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of ResilientDB
+1 (binding) Regards, Uma On Tue, Oct 3, 2023 at 4:23 AM Atri Sharma wrote: > We want to propose ResilientDB as a new Apache Incubator project. > > ResilientDB[1] is a distributed blockchain framework that is written > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > Key features: > > Provides a scalable client-server architecture. Each developer can use > the ResilientDB framework to deploy a replicated service acting as a > service. The developer can choose the desired number of replicas and > the number of clients its system should tolerate. > > Provides native integration with PBFT consensus protocol – arguably > the most popular BFT consensus protocol. PBFT helps replicas reach an > agreement for ordering the client's requests. > > Provides a mechanism to simulate the failure of different replicas > (including the leader). > > Provides a correct implementation of the view-change protocol that > replaces a faulty (or malicious) leader and moves all replicas to the > new view. > > Provides checkpoint and recovery protocols to facilitate garbage > collection, recovery of failed replicas, and durably logging of the > blockchain state. > > Eases development and testing of newer and optimized BFT and CFT > consensus protocols. > Provides clients with support for three different application interfaces: > > Key-Value Stores - where client transactions include key-value pairs. > > Smart Contracts - where clients issue smart contracts in Solidity for > processing. > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > Facilitates benchmarking system/protocol performance with the help of > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > Stores non-volatile ledger (blockchain) in memory and for further > durability, provides APIs to store both client data and blockchain in > LevelDB and RocksDB. > > > The serving mentors would be: > > Junping Du > > Calvin Kirs > > Kevin Ratnasekera > > Roman Shaposhnik > > Christian Grobmeier > > and I shall be serving as the Champion. > > We have not done a trademark check yet for the name but that can be > pursued independently. > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > [2] https://github.com/resilientdb/resilientdb > > Atri > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Incubating Proposal of ResilientDB
+1 (Binding) -Ayush On Wed, 4 Oct 2023 at 23:57, Christian Grobmeier wrote: > > +1 (binding) > The proposal looks solid > > > -- > The Apache Software Foundation > V.P., Data Privacy > > On Tue, Oct 3, 2023, at 13:23, Atri Sharma wrote: > > We want to propose ResilientDB as a new Apache Incubator project. > > > > ResilientDB[1] is a distributed blockchain framework that is written > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > Key features: > > > > Provides a scalable client-server architecture. Each developer can use > > the ResilientDB framework to deploy a replicated service acting as a > > service. The developer can choose the desired number of replicas and > > the number of clients its system should tolerate. > > > > Provides native integration with PBFT consensus protocol – arguably > > the most popular BFT consensus protocol. PBFT helps replicas reach an > > agreement for ordering the client's requests. > > > > Provides a mechanism to simulate the failure of different replicas > > (including the leader). > > > > Provides a correct implementation of the view-change protocol that > > replaces a faulty (or malicious) leader and moves all replicas to the > > new view. > > > > Provides checkpoint and recovery protocols to facilitate garbage > > collection, recovery of failed replicas, and durably logging of the > > blockchain state. > > > > Eases development and testing of newer and optimized BFT and CFT > > consensus protocols. > > Provides clients with support for three different application interfaces: > > > > Key-Value Stores - where client transactions include key-value pairs. > > > > Smart Contracts - where clients issue smart contracts in Solidity for > > processing. > > > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > > > Facilitates benchmarking system/protocol performance with the help of > > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > > > Stores non-volatile ledger (blockchain) in memory and for further > > durability, provides APIs to store both client data and blockchain in > > LevelDB and RocksDB. > > > > > > The serving mentors would be: > > > > Junping Du > > > > Calvin Kirs > > > > Kevin Ratnasekera > > > > Roman Shaposhnik > > > > Christian Grobmeier > > > > and I shall be serving as the Champion. > > > > We have not done a trademark check yet for the name but that can be > > pursued independently. > > > > [1] > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > [2] https://github.com/resilientdb/resilientdb > > > > Atri > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of ResilientDB
+1 (binding) The proposal looks solid -- The Apache Software Foundation V.P., Data Privacy On Tue, Oct 3, 2023, at 13:23, Atri Sharma wrote: > We want to propose ResilientDB as a new Apache Incubator project. > > ResilientDB[1] is a distributed blockchain framework that is written > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > Key features: > > Provides a scalable client-server architecture. Each developer can use > the ResilientDB framework to deploy a replicated service acting as a > service. The developer can choose the desired number of replicas and > the number of clients its system should tolerate. > > Provides native integration with PBFT consensus protocol – arguably > the most popular BFT consensus protocol. PBFT helps replicas reach an > agreement for ordering the client's requests. > > Provides a mechanism to simulate the failure of different replicas > (including the leader). > > Provides a correct implementation of the view-change protocol that > replaces a faulty (or malicious) leader and moves all replicas to the > new view. > > Provides checkpoint and recovery protocols to facilitate garbage > collection, recovery of failed replicas, and durably logging of the > blockchain state. > > Eases development and testing of newer and optimized BFT and CFT > consensus protocols. > Provides clients with support for three different application interfaces: > > Key-Value Stores - where client transactions include key-value pairs. > > Smart Contracts - where clients issue smart contracts in Solidity for > processing. > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > Facilitates benchmarking system/protocol performance with the help of > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > Stores non-volatile ledger (blockchain) in memory and for further > durability, provides APIs to store both client data and blockchain in > LevelDB and RocksDB. > > > The serving mentors would be: > > Junping Du > > Calvin Kirs > > Kevin Ratnasekera > > Roman Shaposhnik > > Christian Grobmeier > > and I shall be serving as the Champion. > > We have not done a trademark check yet for the name but that can be > pursued independently. > > [1] https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > [2] https://github.com/resilientdb/resilientdb > > Atri > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of ResilientDB
+1 (binding) On Wed, Oct 4, 2023 at 7:08 PM PJ Fanning wrote: > +1 (binding) > > The project looks to have a big enough community and the proposal > looks good. Best of luck. > > On Wed, 4 Oct 2023 at 17:52, Mohammad Sadoghi > wrote: > > > > Dear all, > > > > On August 28, Calvin had done "a quick check of the project name and > there > > are no potential trademark issues." We have all the necessary ICLAs > > prepared and signed. I own the domain name ResilientDB.com and Git repo, > > which I can transfer the ownership to Apache. There are no registered > > trademarks on ResilientDB. > > > > --- > > Best Regards, > > Mohammad Sadoghi, PhD > > Associate Professor > > Exploratory Systems Lab (ExpoLab) > > Department of Computer Science > > University of California, Davis > > > > ExpoLab: https://expolab.org/ > > ResilientDB: https://resilientdb.com/ > > Phone: 914-319-7937 > > > > > > On Tue, Oct 3, 2023 at 4:23 AM Atri Sharma wrote: > > > > > We want to propose ResilientDB as a new Apache Incubator project. > > > > > > ResilientDB[1] is a distributed blockchain framework that is written > > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > > > Key features: > > > > > > Provides a scalable client-server architecture. Each developer can use > > > the ResilientDB framework to deploy a replicated service acting as a > > > service. The developer can choose the desired number of replicas and > > > the number of clients its system should tolerate. > > > > > > Provides native integration with PBFT consensus protocol – arguably > > > the most popular BFT consensus protocol. PBFT helps replicas reach an > > > agreement for ordering the client's requests. > > > > > > Provides a mechanism to simulate the failure of different replicas > > > (including the leader). > > > > > > Provides a correct implementation of the view-change protocol that > > > replaces a faulty (or malicious) leader and moves all replicas to the > > > new view. > > > > > > Provides checkpoint and recovery protocols to facilitate garbage > > > collection, recovery of failed replicas, and durably logging of the > > > blockchain state. > > > > > > Eases development and testing of newer and optimized BFT and CFT > > > consensus protocols. > > > Provides clients with support for three different application > interfaces: > > > > > > Key-Value Stores - where client transactions include key-value pairs. > > > > > > Smart Contracts - where clients issue smart contracts in Solidity for > > > processing. > > > > > > UTXO - where clients issue unspent transactions similar to ones in > Bitcoin. > > > > > > Facilitates benchmarking system/protocol performance with the help of > > > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > > > > > Stores non-volatile ledger (blockchain) in memory and for further > > > durability, provides APIs to store both client data and blockchain in > > > LevelDB and RocksDB. > > > > > > > > > The serving mentors would be: > > > > > > Junping Du > > > > > > Calvin Kirs > > > > > > Kevin Ratnasekera > > > > > > Roman Shaposhnik > > > > > > Christian Grobmeier > > > > > > and I shall be serving as the Champion. > > > > > > We have not done a trademark check yet for the name but that can be > > > pursued independently. > > > > > > [1] > > > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > > [2] https://github.com/resilientdb/resilientdb > > > > > > Atri > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
Re: [DISCUSS] Incubating Proposal of ResilientDB
+1 (binding) The project looks to have a big enough community and the proposal looks good. Best of luck. On Wed, 4 Oct 2023 at 17:52, Mohammad Sadoghi wrote: > > Dear all, > > On August 28, Calvin had done "a quick check of the project name and there > are no potential trademark issues." We have all the necessary ICLAs > prepared and signed. I own the domain name ResilientDB.com and Git repo, > which I can transfer the ownership to Apache. There are no registered > trademarks on ResilientDB. > > --- > Best Regards, > Mohammad Sadoghi, PhD > Associate Professor > Exploratory Systems Lab (ExpoLab) > Department of Computer Science > University of California, Davis > > ExpoLab: https://expolab.org/ > ResilientDB: https://resilientdb.com/ > Phone: 914-319-7937 > > > On Tue, Oct 3, 2023 at 4:23 AM Atri Sharma wrote: > > > We want to propose ResilientDB as a new Apache Incubator project. > > > > ResilientDB[1] is a distributed blockchain framework that is written > > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > > > Key features: > > > > Provides a scalable client-server architecture. Each developer can use > > the ResilientDB framework to deploy a replicated service acting as a > > service. The developer can choose the desired number of replicas and > > the number of clients its system should tolerate. > > > > Provides native integration with PBFT consensus protocol – arguably > > the most popular BFT consensus protocol. PBFT helps replicas reach an > > agreement for ordering the client's requests. > > > > Provides a mechanism to simulate the failure of different replicas > > (including the leader). > > > > Provides a correct implementation of the view-change protocol that > > replaces a faulty (or malicious) leader and moves all replicas to the > > new view. > > > > Provides checkpoint and recovery protocols to facilitate garbage > > collection, recovery of failed replicas, and durably logging of the > > blockchain state. > > > > Eases development and testing of newer and optimized BFT and CFT > > consensus protocols. > > Provides clients with support for three different application interfaces: > > > > Key-Value Stores - where client transactions include key-value pairs. > > > > Smart Contracts - where clients issue smart contracts in Solidity for > > processing. > > > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > > > Facilitates benchmarking system/protocol performance with the help of > > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > > > Stores non-volatile ledger (blockchain) in memory and for further > > durability, provides APIs to store both client data and blockchain in > > LevelDB and RocksDB. > > > > > > The serving mentors would be: > > > > Junping Du > > > > Calvin Kirs > > > > Kevin Ratnasekera > > > > Roman Shaposhnik > > > > Christian Grobmeier > > > > and I shall be serving as the Champion. > > > > We have not done a trademark check yet for the name but that can be > > pursued independently. > > > > [1] > > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > > [2] https://github.com/resilientdb/resilientdb > > > > Atri > > > > - > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [DISCUSS] Incubating Proposal of ResilientDB
Dear all, On August 28, Calvin had done "a quick check of the project name and there are no potential trademark issues." We have all the necessary ICLAs prepared and signed. I own the domain name ResilientDB.com and Git repo, which I can transfer the ownership to Apache. There are no registered trademarks on ResilientDB. --- Best Regards, Mohammad Sadoghi, PhD Associate Professor Exploratory Systems Lab (ExpoLab) Department of Computer Science University of California, Davis ExpoLab: https://expolab.org/ ResilientDB: https://resilientdb.com/ Phone: 914-319-7937 On Tue, Oct 3, 2023 at 4:23 AM Atri Sharma wrote: > We want to propose ResilientDB as a new Apache Incubator project. > > ResilientDB[1] is a distributed blockchain framework that is written > in C++ and integrates with Byzantine Fault-Tolerant (BFT) and Crash > Fault-Tolerant (CFT) consensus protocols. Code is present at [2]. > > Key features: > > Provides a scalable client-server architecture. Each developer can use > the ResilientDB framework to deploy a replicated service acting as a > service. The developer can choose the desired number of replicas and > the number of clients its system should tolerate. > > Provides native integration with PBFT consensus protocol – arguably > the most popular BFT consensus protocol. PBFT helps replicas reach an > agreement for ordering the client's requests. > > Provides a mechanism to simulate the failure of different replicas > (including the leader). > > Provides a correct implementation of the view-change protocol that > replaces a faulty (or malicious) leader and moves all replicas to the > new view. > > Provides checkpoint and recovery protocols to facilitate garbage > collection, recovery of failed replicas, and durably logging of the > blockchain state. > > Eases development and testing of newer and optimized BFT and CFT > consensus protocols. > Provides clients with support for three different application interfaces: > > Key-Value Stores - where client transactions include key-value pairs. > > Smart Contracts - where clients issue smart contracts in Solidity for > processing. > > UTXO - where clients issue unspent transactions similar to ones in Bitcoin. > > Facilitates benchmarking system/protocol performance with the help of > existing benchmarks, such as YCSB [SoCC’10] and Diablo [EuroSys’23]. > > Stores non-volatile ledger (blockchain) in memory and for further > durability, provides APIs to store both client data and blockchain in > LevelDB and RocksDB. > > > The serving mentors would be: > > Junping Du > > Calvin Kirs > > Kevin Ratnasekera > > Roman Shaposhnik > > Christian Grobmeier > > and I shall be serving as the Champion. > > We have not done a trademark check yet for the name but that can be > pursued independently. > > [1] > https://cwiki.apache.org/confluence/display/INCUBATOR/ResilientDBProposal > [2] https://github.com/resilientdb/resilientdb > > Atri > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
