That makes sense @davideaster. I think I was thrown off by the chimera-like relationship between the top-level Rakefile (actually running tasks) and the sub-directories being treated like modules. Should we move to refactor within this repo better since moving to separate repos seems like a more painful move?

It was really confusing to me that the top-level Rakefile is both aggregating and defining tasks and that you have to cd into specific directories to run certain tasks. And I'm familiar with rake. I'm sure those who are coming to it for the first time are really confused.

At the very least, could we expose more tasks to the top-level rake command, at least the ones that make sense? That way, `rake -T` at the top-level exposes ALL of the tasks that are available on the project instead of having to cd around everywhere to discover tasks. Or we could just move everything to the top-level Rakefile and use rake's namespaces.

Ideas? Thoughts?