This post originated from an RSS feed registered with Ruby Buzz
by James Britt.
Original Post: Next steps for Monkeybars + Rawr
Feed Title: James Britt: Ruby Development
Feed URL: http://feeds.feedburner.com/JamesBritt-Home
Feed Description: James Britt: Playing with better toys
As of today I am the admin for the Monkeybars and Rawr projects
I’m taking over from Logan Barnett who has, without a doubt, done a fantastic job with these projects. (And of course big props to David Koontz as well. David and Logan have been the magicians behind Monkeybars and Rawr.)
My immediate plans:
Get acquainted with the current project.
The means not just going through the code, but getting more familiar with Kenai
These are forks of rawr and Monkeybars, created to make it easier for me to pursue certain design, packaging, and business goals. It worked well for me, but it’s less useful overall to have multiple projects that are kinda sorta the same.
I don’t want to impulsively just merge in the features that distinguish my forks, but I know that at least some of them have good use cases and should be made regular features.
However, I hope to get some feedback from current rawr and Monkeybars users to see how best to go about things.
It is quite likely that I will move things off of Kenai. I’ve never really liked the site; the mailing list has wonky navigation, and I’d prefer to just use github for the repo. Bug tracking is another matter. Github’s issue tracking is OK, but not terribly robust. Pivotal Tracker may be a better choice.
But there may be features or options in Kenai that I’m unaware of, especially regarding the integration of tools, so I need to do a bit of homework.
If you are a user of Monkeybars or Rawr let me know your thoughts on the Kenai services.
Previous Topic
