<div class="gmail_quote">Hello,<br>
<br>
I've been using RabbitMQ for 2 months now and I figured I would share my<br>
experiences.<br>
<br>
== Background ==<br>
<br>
I'm using RabbitMQ because Celery recommends it. �If Celery recommended<br>
something else, I would have used that. �I'm just pointing that out because<br>
sometimes core services forget that people often use them because a<br>
particular library favors that implementation. �It's important to take care<br>
of the downstream libraries, especially when you're using an open protocol<br>
like AMQP.<br>
<br>
== Comments so Far ==<br>
<br>
I think RabbitMQ is awesome and has done really well so far for me. �It's<br>
been very fast (only marginally important for me) and very stable (much,<br>
much more important for me). �Here's my constructive criticism (i.e. things<br>
that can be addressed easily IMHO).<br>
<br>
�* This newsgroup format is terrible. �Please move to Google Groups.<br>
�* The code is very difficult to get at. �Please move to Github (or<br>
BitBucket). �I see that you're using Mercurial already, so BitBucket is the<br>
obvious choice. �I think GitHub is way more feature rich but if you're not<br>
willing to move to Git, that won't work of course.<br>
�* The documentation is not version-specific. �This has caused me enormous<br>
problems (specifically with set-permissions, which is why I'm in the mode to<br>
write this message at all). �Please move to a platform that supports<br>
versioned documentation better. �I don't know the best solution to this<br>
exactly - maybe Sphinx or just a wiki with a url structure that supports<br>
multiple versions?<br>
�* Where are the open tickets? �It appears that all bugs are going through<br>
the mailing list - it's really hard on the users to not have an<br>
easy-to-search ticket system. �Launchpad could work or BitBucket's issue<br>
system, or Redmine, or Trac?<br>
�* The site itself needs a fresh look. �I know MongoDB is funded, but<br>
there's an example of a great site for this type of thing:<br>
<a href="http://www.mongodb.org/" target="_blank">http://www.mongodb.org/</a> .<br>
�* Outdated stuff should be taken down or have a disclaimer on it. �For<br>
instance the ec2 page: <a href="http://www.rabbitmq.com/ec2.html" target="_blank">http://www.rabbitmq.com/ec2.html</a> has images for<br>
Karmic Koala. �While that was great last year, it's really time to have a<br>
Lucid ec2 images available - or nothing at all. �A Lucid image, because it<br>
is long term, could be up for a year or two and it would be ok.<br>
�* Please don't tell Mac users to use MacPorts:<br>
<a href="http://www.rabbitmq.com/macports.html" target="_blank">http://www.rabbitmq.com/macports.html</a> It's time to move them to HomeBrew at<br>
<a href="http://github.com/mxcl/homebrew" target="_blank">http://github.com/mxcl/homebrew</a><br>
�* Please be more descriptive about how to set up an environment with tools<br>
like Alice and Wonderland. �These appear to be great assets to RabbitMQ, but<br>
are hidden in the dense 'Getting Started' page:<br>
<a href="http://www.rabbitmq.com/how.html" target="_blank">http://www.rabbitmq.com/how.html</a> . �All the links from a Getting Started<br>
page should take no longer than 1 hour to read. �Check out Django's one hour<br>
intro here: <a href="http://docs.djangoproject.com/en/dev/intro/tutorial01/" target="_blank">http://docs.djangoproject.com/en/dev/intro/tutorial01/</a> �. �The<br>
first link on RabbitMQ's Getting Started page goes to this Alexis Richardson<br>
talk -<br>
<a href="http://skillsmatter.com/podcast/erlang/alexis-richardson-introduction-to-rabbitmq" target="_blank">http://skillsmatter.com/podcast/erlang/alexis-richardson-introduction-to-rabbitmq</a><br>
. �While the content is great, it's geared towards the intermediate user,<br>
not a beginner just getting started. �Also, having dynamic delicious<br>
searches is fine for an appendix maybe, but not the first page for people<br>
getting started.<br>
<br>
In fine, I really think the product is tremendous, it's just a matter of<br>
fixing up the experience for users of the software. �The core issues are<br>
documentation (plenty of it is there, almost too much, but not tightly<br>
curated, updated or kept versioned), code access (archaic tools around this<br>
- although using Mercurial is a huge plus over cvs or svn), and issue<br>
tracking.<br>
<br>
Thanks,<br>
Adam<br>
<br>
<br>
--<br>
View this message in context: <a href="http://old.nabble.com/Thoughts-from-a-new-user-tp29742723p29742723.html" target="_blank">http://old.nabble.com/Thoughts-from-a-new-user-tp29742723p29742723.html</a><br>
Sent from the RabbitMQ mailing list archive at Nabble.com.<br>
<br>
<br></div><br><br clear="all"><br>-- <br>Adam<br>