This is a pretty big step for us. It removes a lot of unsafe and
complex cases from the code, which is a key point of difference for our
Would love to see your comments and review! As usual it passes the test
suite (except test_remdb_cursor_modify which is a known issue).
Hey guys, finally able to start working on the project again!
I have cloned the latest commit and tried to compile using make.
when I compiled I got 4 errors in the remdb_stat.c specifically on line 1234
reguarding the mdb_dbi_open function.
I am assuming that the remdb_stat.c file hasn't yet been updated for the
Rather than having the source under my namespace (Firstyear/remdb) I've
created a group in gitlab, and moved the project there.
You may need to update your git URL's to match, but this will make it
better in a number of ways:
* easier to request reviews (you can nominate the group)
* we aren't "my project", we are a community
* we have a better looking url (all about the style points)
* we can properly fork/branch/merge, and have protected branches
Sorry to have done this without consulting everyone first, but I'm
assuming everyone is happy with me doing this (or will forgive me!)
Just a notification to review MR6, relicensing our derived works.
An important point is, should we be notifiying this list for reviews?
Or are we happy for gitlab to notify us directly (Does gitlab notify
you to conduct reviews?)
Welcome to the ReMDB development mailing list.
We are a key-value database project focused on "correct, simple, fast".
We follow the rules of the Django code of conduct, and I take pride in
the high standards for behaviour of the community that we want to
At this time the source code is still private, but we will open this to
the public soon.
In the near future important project administrative details will need
to be worked out like team membership, conduct enforcement processes,
and release management.
Thanks, and I look forward to working with you all!