Thinky Maintainers

[grantcarthew]

Hi Thinky users.

After @neumino published in #609 that he was not going to be involved in Thinky as much anymore, the call went out for maintainers. After some discussion there are now four that I know:

• @neumino <= Original author minimal repo administration.
• @grantcarthew <= That's me however I don't have the time to do much.
• @wookoouk <= Good activity on github. Great things expected :)
• @cur3n4 <= Actively working on current pull requests.

There may be more however I don't have full access to this repo so I can't see the settings. If anyone else is a maintainer, please comment here.

If anyone else is interested in being a maintainer such as @lirantal, please request here.

I am still heavily using Think in my own projects as are many people. Rest assured that bugs will get fixed and the project will continue on, all be it at a slower cadence.

[lirantal]

Hi Guys,

We're using RethinkDB across a few projects, some of us use thinky indeed. We're also using rethinkdb-migrate and have contributed to it so we're all in for helping the community if there's anything specific. I don't think we have any case with thinky specifically so I'd probably not be very active in taking on PRs.

[iamclaytonray]

Hey, I'd be down to contribute as often as I could. I can't commit to collab status but I could probably shoot a PR or two per week. (If you guys are still looking for people)

[grantcarthew]

Hi @iamclaytonray. Thinky has lots of PRs. We need people to view them, create/check tests, merge them. Can you reconsider the collaborative status?

[iamclaytonray]

Hmmm. I could probably commit in like 2 - 3 weeks. I'm pretty busy until then, but things should be dying down for me

[iamclaytonray]

Not the ideal scenario but it's the best I have 😄

[grantcarthew]

@neumino Time is precious and @iamclaytonray is happy to give Thinky some.

[valclark1]

Hey guys so what is the status of this project. Do you recommend reverting back to the ReQL driver? It looks like this project is about to be unmaintained.

[grantcarthew]

OK, I'm going to be honest here. I have been watching the RethinkDB repository over the years and the activity on the server has dropped significantly. Lots of green with very little red or purple. Green is new issue, pull request, or unresolved issues. Red is a closed issue or pull request and purple is a merged pull request.

If you checkout the RethinkDB pulse you will see in a month there have only been three contributors (as of 2017-11-30). No doubt they are working hard, however there is a significant amount of open issues (1496 as of 2017-11-30).

Even just to read near 1500 issues is going to take a lot of time let alone understanding and coding solutions. For a database that is ranked 54th we can assume there are a lot of users with very little number of coders. An assumption here is that the issues will continue to rise.

I did this analysis myself a few months ago and have decided to migrate my projects to PostgreSQL using Sequelize. This was a sad choice I had to make because I spent a lot of time making a job queue based on RethingDB called rethinkdb-job-queue. I am going to continue to maintain the job queue for fixes however I will not be coding new features for it.

You never know. The situation can always change however I would rather use a data store that has lots of activity moving forward with plenty of support.

I never had time to become intimate with Thinky so my move away is not going to affect this project.