Synthesis

Just wanted to mention our Rails Rumble project, RubyBrigade.org. Jason Perry, James Seaman and I worked through the weekend to build RubyBrigade.org – a geographically aware database of Ruby User groups.

Big thanks to James for the killer hand drawn illustrations and interface. Big thanks to Jason & Katie for letting us take over their house for the weekend.

Features:

• Google Maps Integration
• Sub-domains for each group
• Geocoding: either by the search box or by sub-domain!
• RSS and iCal feed parsing
• Display latest user groups
• Display upcoming events across all groups
• Display blog posts & upcoming events for individual groups
• ReCAPTCHA for spam prevention
• No authentication required

More Screenshots

View a Brigade

Edit a Brigade

Delete a Brigade

404 Message

If you like what you see, vote for us!

With the whole RailsForge survey thing, it’s also come out that a lot of people hate the current incarnation of RubyForge.

Some are suggesting to redesign RubyForge, which is a good idea. Re-think RubyForge and give it some 37signals-style, UI-first design love. I haven’t talked with any RubyForge maintainers yet, but I’d be interested in helping out.

By the way, I totally appreciate RubyForge, and I’m so thankful to the people who run it and donate their time and money to keep it going.

RubyForge pet peeves

What is it about RubyForge that’s so annoying? For me, when I arrive at a project page on RubyForge, I’m greeted with a plethora of “stuff” cluttering the page, that’s either un-used or not really telling me anything. I often leave more confused, and I’m an experienced developer. Imagine how a beginner feels! I then look elsewhere hoping someone has written a helpful tutorial on their blog.

RubyForge-specific complaints from the RailsForge survey responses:

• Most of the features go unused.
• Biggest problem is the UI.
• It’s very difficult to do the things the majority of people want – 1. learn about a project, 2. download and install it, 3. learn how to use it.
• 90% of the project page has nothing to do with any of this and it just adds clutter.

• Let project maintainers selectively turn on the features they want.
• 80% want to learn. 20% want to contribute. Refocus the UI to reflect this.

Asset Packager has been released! (Formerly known as MergeJS) New features include:

• support for css files
• versioning of individual packages
• use of more meaningful subversion revision numbers (if available) (thanks Chris Van Pelt!)
• namespaced rake tasks
• no more revision numbers in the yaml file
• lotsa refactoring
• unit tests
• more intuitive names for everything!

Go here to check it out: AssetPackager