There's been an interesting thread on the Ruby mailing list, sparked by Simon Cozen's article regarding taxonomy and modules. It seems what Perl has taken for granted with module naming conventions is still an issue for the Ruby and Python communities.
Mostly the issue boils down to namespaces. One big difference, however, is that a module like Toast::Buttered in Perl refers to a file Buttered.pm under the directory "Toast". In Ruby, Toast is a module that can contain its own data and Buttered would be a class within that module. It has nothing to do with directory structure per se.
Personally, I don't care that much about the issue. A cruddy module name might annoy me be it won't stop me from using it. I'm much more concerned with the atrocious lack of documentation for some Ruby modules that look like they would be very useful. The openssl extension comes to mind...
