README.markdown in zk-1.8.0 vs README.markdown in zk-1.9.0
- old
+ new
@@ -1,8 +1,8 @@
# ZK #
-[![Build Status (master)](https://secure.travis-ci.org/slyphon/zk.png?branch=master)](http://travis-ci.org/slyphon/zk)
+[![Build Status (master)](https://secure.travis-ci.org/zk-ruby/zk.png?branch=master)](http://travis-ci.org/zk-ruby/zk)
ZK is an application programmer's interface to the Apache [ZooKeeper][] server. It is based on the [zookeeper gem][] which is a multi-Ruby low-level driver. Currently MRI 1.8.7, 1.9.2, 1.9.3, REE, and JRuby are supported. Rubinius 2.0.testing is supported-ish (it's expected to work, but upstream is unstable, so YMMV).
ZK is licensed under the [MIT][] license.
@@ -14,14 +14,14 @@
Development is sponsored by [Snapfish][] and has been generously released to the Open Source community by HPDC, L.P.
[ZK::Client::Base]: http://rubydoc.info/gems/zk/ZK/Client/Base
[ZooKeeper]: http://zookeeper.apache.org/ "Apache ZooKeeper"
-[zookeeper gem]: https://github.com/slyphon/zookeeper "slyphon-zookeeper gem"
+[zookeeper gem]: https://github.com/zk-ruby/zookeeper "zookeeper gem"
[MIT]: http://www.gnu.org/licenses/license-list.html#Expat "MIT (Expat) License"
[Snapfish]: http://www.snapfish.com/ "Snapfish"
-[RELEASES]: https://github.com/slyphon/zk/blob/master/RELEASES.markdown
+[RELEASES]: https://github.com/zk-ruby/zk/blob/master/RELEASES.markdown
## What is ZooKeeper? ##
ZooKeeper is a multi-purpose tool that is designed to allow you to write code that coordinates many nodes in a cluster. It can be used as a directory service, a configuration database, and can provide cross-cluster [locking][], [leader election][], and [group membership][] (to name a few). It presents to the user what looks like a distributed file system, with a few important differences: every node can have children _and_ data, and there is a 1MB limit on data size for any given node. ZooKeeper provides atomic semantics and a simple API for manipulating data in the heirarchy.
@@ -36,11 +36,11 @@
[watches]: http://zookeeper.apache.org/doc/current/zookeeperProgrammers.html#ch_zkWatches
[locking]: http://zookeeper.apache.org/doc/current/recipes.html#sc_recipes_Locks
[leader election]: http://zookeeper.apache.org/doc/current/recipes.html#sc_leaderElection
[group membership]: http://zookeeper.apache.org/doc/current/recipes.html#sc_outOfTheBox
[ha-config]: http://zookeeper.apache.org/doc/current/zookeeperAdmin.html#sc_CrossMachineRequirements "HA config"
-[groups]: https://github.com/slyphon/zk-group
+[groups]: https://github.com/zk-ruby/zk-group
[locks]: http://rubydoc.info/gems/zk/ZK/Locker
## What does ZK do that the zookeeper gem doesn't?
@@ -60,11 +60,11 @@
In addition to all of that, I would like to think that the public API the ZK::Client provides is more convenient to use for the common (synchronous) case. For use with [EventMachine][] there is [zk-eventmachine][] which provides a convenient API for writing evented code that uses the ZooKeeper server.
[recipes]: http://zookeeper.apache.org/doc/current/recipes.html
[Mongoid]: http://mongoid.org/
[EventMachine]: https://github.com/eventmachine/eventmachine
-[zk-eventmachine]: https://github.com/slyphon/zk-eventmachine
+[zk-eventmachine]: https://github.com/zk-ruby/zk-eventmachine
## Release info / Changelog
See the [RELEASES][] page for more info on features and bugfixes in each release.
@@ -83,11 +83,11 @@
* _ACLS: HOW DO THEY WORK?!_ ACL support is mainly faith-based now. I have not had a need for ACLs, and the authors of the upstream [twitter/zookeeper][] code also don't seem to have much experience with them/use for them (purely my opinion, no offense intended). If you are using ACLs and you find bugs or have suggestions, I would much appreciate feedback or examples of how they *should* work so that support and tests can be added.
* ZK::Client supports asynchronous calls of all basic methods (get, set, delete, etc.) however these versions are kind of inconvenient to use. For a fully evented stack, try [zk-eventmachine][], which is designed to be compatible and convenient to use in event-driven code.
[twitter/zookeeper]: https://github.com/twitter/zookeeper
-[async-branch]: https://github.com/slyphon/zk/tree/dev%2Fasync-conveniences
+[async-branch]: https://github.com/zk-ruby/zk/tree/dev%2Fasync-conveniences
[chroot]: http://zookeeper.apache.org/doc/current/zookeeperProgrammers.html#ch_zkSessions
[YARD]: http://yardoc.org/
[sessions]: http://zookeeper.apache.org/doc/current/zookeeperProgrammers.html#ch_zkSessions
[watches]: http://zookeeper.apache.org/doc/r3.3.5/zookeeperProgrammers.html#ch_zkWatches
@@ -98,22 +98,21 @@
* [DCell](https://github.com/celluloid/dcell): Distributed ruby objects, built on top of the super cool [Celluloid](https://github.com/celluloid/celluloid) framework.
## Dependencies
-* The [slyphon-zookeeper gem][szk-gem] ([repo][szk-repo]).
+* The [zookeeper gem][szk-gem] ([repo][szk-repo]).
* For JRuby, the [slyphon-zookeeper\_jar gem][szk-jar-gem] ([repo][szk-jar-repo]), which just wraps the upstream zookeeper driver jar in a gem for easy installation
-[szk-gem]: https://rubygems.org/gems/slyphon-zookeeper
-[szk-repo]: https://github.com/slyphon/zookeeper
-[szk-repo-bundler]: https://github.com/slyphon/zookeeper/tree/dev/gemfile/
+[szk-gem]: https://rubygems.org/gems/zookeeper
+[szk-repo]: https://github.com/zk-ruby/zookeeper
+[szk-repo-bundler]: https://github.com/zk-ruby/zookeeper/tree/dev/gemfile/
[szk-jar-gem]: https://rubygems.org/gems/slyphon-zookeeper_jar
-[szk-jar-repo]: https://github.com/slyphon/zookeeper_jar
+[szk-jar-repo]: https://github.com/zk-ruby/zookeeper_jar
## Contacting the author
-* I'm usually hanging out in IRC on freenode.net in the BRAND NEW #zk-gem channel.
* if you really want to, you can also reach me via twitter [@slyphon][]
[@slyphon]: https://twitter.com/#!/slyphon