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
So, I've been maintaining a fork of twitter/zookeeper for about the past year. I've been doing regular releases, bugfixes, and code maintenance to keep Zookeeper running, and to support my higher-level Zookeeper wrapper ZK, which is now (I'm proud to say) powering redis_failover and is incorporated in dcell.
I wanted to ask: would twitter consider transferring this repository to me?
I've been stalling for months, hemming and hawing about filing a pull request. There are major changes I'd like to make (that would break the API, or at least the heirarchy), and I don't feel comforatable doing that unless I actually own the project. You can see from what the pull request would look like, it's a massive number of fixes. I've added proper chroot support, code generation tools to allow the C extension to do proper GIL release in 1.9.x (while maintaining 1.8.7 compatibility), more reliable eventmachine support, etc.
One advantage is that it'd be be more obvious to people where to file bugs (as my gem is starting to get more use), and I could more easily service the needs of users of the code.
So @wickman, @neilconway, @jmhodges: I care deeply about this codebase and have spent many many hours working on it. Would you consider allowing me to adopt this code?
The text was updated successfully, but these errors were encountered:
So, I've been maintaining a fork of twitter/zookeeper for about the past year. I've been doing regular releases, bugfixes, and code maintenance to keep Zookeeper running, and to support my higher-level Zookeeper wrapper ZK, which is now (I'm proud to say) powering redis_failover and is incorporated in dcell.
I wanted to ask: would twitter consider transferring this repository to me?
I've been stalling for months, hemming and hawing about filing a pull request. There are major changes I'd like to make (that would break the API, or at least the heirarchy), and I don't feel comforatable doing that unless I actually own the project. You can see from what the pull request would look like, it's a massive number of fixes. I've added proper chroot support, code generation tools to allow the C extension to do proper GIL release in 1.9.x (while maintaining 1.8.7 compatibility), more reliable eventmachine support, etc.
One advantage is that it'd be be more obvious to people where to file bugs (as my gem is starting to get more use), and I could more easily service the needs of users of the code.
So @wickman, @neilconway, @jmhodges: I care deeply about this codebase and have spent many many hours working on it. Would you consider allowing me to adopt this code?
The text was updated successfully, but these errors were encountered: