From: Trans <transfire@...>
Date: 2007-02-04T02:43:21+09:00
Subject: Gem Namespaces

Hi--

I know I will probably be lambasted by the usual lambasting sort,
nonetheless I think its worth suggesting that all gems have a project
namespace. As things stand a project on Rubyforge can create gems with
any name at all --which can readily conflict with gems in another
project. A few projects in particular suck up lots of name real-
estate, in just 3 projects alone one can find 59 gems, some with names
as simple as "traits".

I realize the community has done pretty well in working together to
avoid conflicts. But as RubyForge grows this becomes increasingly more
difficult -- not to mention annoying.

So I'm thinking perhaps gems should be referenced with a namspece
attached. For example instead of

  gem install traits

do:

  gem install codeforpeople:traits

Perhaps we could still use the former too, but if there is conflict
the gem app can ask us which project is intended. Or something to that
effect. Has anyone else considered remedies for this?

Thanks,
T.