You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm currently writing a master's thesis on CouchDB and benchmarking. I plan to update the YCSB CouchDB bindings, and I am wondering what's the best way to proceed with these upcoming updates - as YCSB-CouchDB bindings that work with CouchDB 2.0 and a recent version of YCSB might be useful for a lot of other people as well.
Is this GitHub repo still actively maintained? Given the fact that the binding is outdated, there hasn't been any active development for quite some time, and PRs are not getting merged, it doesn't make that impression, to be frank.
Are there any ambitions to get development going again, to accept contributions and keep the code up-to-date with recent versions of CouchDB and YCSB?
Would the maintainer be willing to handle pull requests on that behalf, or might transfering ownership of this project be an option for them?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
I'm currently writing a master's thesis on CouchDB and benchmarking. I plan to update the YCSB CouchDB bindings, and I am wondering what's the best way to proceed with these upcoming updates - as YCSB-CouchDB bindings that work with CouchDB 2.0 and a recent version of YCSB might be useful for a lot of other people as well.
Is this GitHub repo still actively maintained? Given the fact that the binding is outdated, there hasn't been any active development for quite some time, and PRs are not getting merged, it doesn't make that impression, to be frank.
Are there any ambitions to get development going again, to accept contributions and keep the code up-to-date with recent versions of CouchDB and YCSB?
Would the maintainer be willing to handle pull requests on that behalf, or might transfering ownership of this project be an option for them?
Thanks!
The text was updated successfully, but these errors were encountered: