34 ms·

First of all: this is great, thank you so much! Secondly, and with the risk of hijacking the OP: I think it would be a good thing if you could put a status upd

by smhg 10y ago

First of all: this is great, thank you so much! Secondly, and with the risk of hijacking the OP: I think it would be a good thing if you could put a status update either on rethinkdb.com or ~the first paragraph of the readme on GitHub about what you are trying to accomplish related to the name/rights/ownership/license/... I check those about once a month to see if something has changed. As a current user and someone evaluating future usage, this is causing the most uncertainty. I don't know how these things happen (it is probably complex). But I want to commit. Even if progress is slow. Bugfixes are important, but secondary if the project might somehow be significantly damaged trying to "escape" its current ownership. As an example: you are trying to transfer ownership of the build tools? I understand that might take a while, but what if that somehow can't happen? Is recreating them realistic? Basically a list of threats/risks would be nice to have! :) EDIT: this is also relevant for contributors/donations/... any type of investment. Thanks again!

v3ss0n 10y ago
I am just one of RethinkDB community. i am waiting to contribute donations to RethhinkDB when it have foundation up and running. I don't think Rethinkdb.com is under control of the Current Leadership Team . But it would be very good idea to put the status updates in ReadMe. I will submit a PR on it. Development is still continuing , but slowly. It is close to release 2.4, @atnnn and @srh is working on it. > Bugfixes are important, but secondary if the project might somehow be significantly damaged trying to "escape" its current ownership. > As an example: you are trying to transfer ownership of the build tools? I understand that might take a while, but what if that somehow can't happen? Is recreating them realistic? @atnnn is building and running own build tool server and its almost perfect , he will need help there: https://github.com/AtnNn/rethinkdb-nix https://github.com/AtnNn/rethinkdb-nix https://thanos.atnnn.com/jobset/rethinkdb/next#tabs-evaluations https://thanos.atnnn.com/jobset/rethinkdb/next#tabs-evaluati...
- v3ss0n 10y ago
  also join us on https://rethinkdb.slack.com/messages/open-rethinkdb/ https://rethinkdb.slack.com/messages/open-rethinkdb/ for more updated info

by smhg 10y ago

v3ss0n 10y ago

I am just one of RethinkDB community. i am waiting to contribute donations to RethhinkDB when it have foundation up and running. I don't think Rethinkdb.com is under control of the Current Leadership Team . But it would be very good idea to put the status updates in ReadMe. I will submit a PR on it. Development is still continuing , but slowly. It is close to release 2.4, @atnnn and @srh is working on it. > Bugfixes are important, but secondary if the project might somehow be significantly damaged trying to "escape" its current ownership. > As an example: you are trying to transfer ownership of the build tools? I understand that might take a while, but what if that somehow can't happen? Is recreating them realistic? @atnnn is building and running own build tool server and its almost perfect , he will need help there: https://github.com/AtnNn/rethinkdb-nix https://github.com/AtnNn/rethinkdb-nix https://thanos.atnnn.com/jobset/rethinkdb/next#tabs-evaluations https://thanos.atnnn.com/jobset/rethinkdb/next#tabs-evaluati...

v3ss0n 10y ago
also join us on https://rethinkdb.slack.com/messages/open-rethinkdb/ https://rethinkdb.slack.com/messages/open-rethinkdb/ for more updated info