Ahhhh! Ok, that can be fair although I'd probably consider that a technical requirement. Really, you'll find the same problem with Merb and Django. There are

Ahhhh! Ok, that can be fair although I'd probably consider that a technical requirement. Really, you'll find the same problem with Merb and Django. There are a bunch of people who have done small things (say, a todo list) in them that don't really know the framework. While the Django community doesn't tend to have the same attitude that some of the Rails community has, it's a really small community. Finding good Django programmers is hard. While some in the Django community would argue that it's just Python (vs. Rails' more DSL take on Ruby), it's more than simply Python. It's hard to hire programmers in general. Django and Merb are much smaller than Rails in terms of exposure and number of programmers. While you might not get as many pretenders or as many bad attitude people, there are simply less people. I wish I had something more helpful to say here. If you're looking to hire Django people, djangogigs.com and djangopeople.net are good places to post/look. I really think Merb would be the better choice as a lot of the code can be reused - you could completely reuse the models and templates which would probably save you a huge amount of development not to mention require no alteration to your database.