4 ms·
To add to that: one of the great consequences of this change is that a large amount of RethinkDB source code that was previously unavailable as open-source code
by mglukhovsky 10y ago
To add to that: one of the great consequences of this change is that a large amount of RethinkDB source code that was previously unavailable as open-source code (including some unreleased features for RethinkDB, copious amounts of artwork and content, and build / performance scripts) will now also be steadily open-sourced.
We felt that it was too important to let the work we created have a life of its own and establish its own life in the open-source community. It's wonderful to see this finally happen.
- pmontra 10y agoWhy that code couldn't be made available under the AGPL, maybe different and incompatible licenses?
- mglukhovsky 10y agoSome of the code and content was heavily used internally, but we never invested time to properly package it for public consumption. We also briefly had a closed-source version of RethinkDB that has a few useful features for larger teams: we're excited to be able to merge these back into the project.