5 ms·

Hello HN , sorry for the early leak. I posted as I've discovered on github after looking around rethinkdb progress. RethinkDB as a product is not dead.The com

by v3ss0n 10y ago

Hello HN , sorry for the early leak. I posted as I've discovered on github after looking around rethinkdb progress. RethinkDB as a product is not dead.The community and one of ex RethinkDB senior developer are still maintaining it. Since it is fully Opensourced , we are welcoming contributors , lets make RethinkDB great , together! https://github.com/rethinkdb/rethinkdb https://github.com/rethinkdb/rethinkdb Here are current rehtinkdb plans : https://docs.google.com/document/d/1f8qODp7voKIqwioQ3si69q3-ruc7h3ncfH0KoHYv_4k/ https://docs.google.com/document/d/1f8qODp7voKIqwioQ3si69q3-... Most of ex RethinkDB developers are going to keep contributing rethinkdb, after things got settled down a bit. https://docs.google.com/document/d/1c27S3Ij2WLB_JiUmpIGkbwJOgVL8T7nW0sPz7OJZjro https://docs.google.com/document/d/1c27S3Ij2WLB_JiUmpIGkbwJO... Please try out rethinkdb , and if there any questions we are activly answering at : https://rethinkdb.slack.com/messages/general/ https://rethinkdb.slack.com/messages/general/ Please join https://rethinkdb.slack.com/messages/open-rethinkdb https://rethinkdb.slack.com/messages/open-rethinkdb for OpenRethinkDB updates. Thank you very much , rethinkdb is an excellent Database. I see a lot of New users at RethinkDB slack. Before RethinkDB slack was quite empty but now it have lot more active user after RethinkDB Shutdown. @coffeemug , those who've tried rethinkdb are staying with rethinkdb. The product is not a failure and the actual users values the standards you have set! Many of us are going to stay with RethinkDB .

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
neoeldex 10y ago
Haven't tried recently, but the only way to install RethinkDB on my machine (ubuntu) was running the docker image. Is it currently fixed again?
- v3ss0n 10y ago
  it can be easily installed on Ubuntu: source /etc/lsb-release && echo "deb http://download.rethinkdb.com/apt http://download.rethinkdb.com/apt $DISTRIB_CODENAME main" | sudo tee /etc/apt/sources.list.d/rethinkdb.list wget -qO- https://download.rethinkdb.com/apt/pubkey.gpg https://download.rethinkdb.com/apt/pubkey.gpg | sudo apt-key add - sudo apt-get update sudo apt-get install rethinkdb
- dkersten 10y ago
  That's strange. I've ran it on ubuntu (using the .deb, I believe) since 2014.
deleted 10y ago
[deleted]

by v3ss0n 10y ago

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

neoeldex 10y ago

Haven't tried recently, but the only way to install RethinkDB on my machine (ubuntu) was running the docker image. Is it currently fixed again?

v3ss0n 10y ago
it can be easily installed on Ubuntu: source /etc/lsb-release && echo "deb http://download.rethinkdb.com/apt http://download.rethinkdb.com/apt $DISTRIB_CODENAME main" | sudo tee /etc/apt/sources.list.d/rethinkdb.list wget -qO- https://download.rethinkdb.com/apt/pubkey.gpg https://download.rethinkdb.com/apt/pubkey.gpg | sudo apt-key add - sudo apt-get update sudo apt-get install rethinkdb
dkersten 10y ago
That's strange. I've ran it on ubuntu (using the .deb, I believe) since 2014.

deleted 10y ago

[deleted]