tag:help.rubygems.org,2010-01-19:/discussions/problems/393-gem-violating-existing-gem-nameRubyGems.org: Discussion 2011-04-07T20:59:34Ztag:help.rubygems.org,2010-01-19:Comment/36592422010-11-16T01:17:07Z2010-11-16T01:17:07ZGem violating existing gem name.<div><p>Sorry about the delay here, rubyconf and the normal post-rubyconf sickness has delayed me.</p>
<p>Usually we work this out with the owner of the gem, if it's the same project... In most cases it's just going to be easier for you to rename it, especially for branding/marketing your own project.</p>
<p>I don't think we have any say in who gets "copyright" or "ownership", plenty of other open source projects exist under the same name that do different things (think Google's Go vs Go, which was around for many years beforehand...not to mention the billion Go games online)</p>
<p>My recommendation here, especially if you're just starting out, would be to rename it. We had to rename Gemcutter a few times as well (wiki page from back in the day... <a href="https://github.com/rubygems/gemcutter/wiki/Brainstorming">https://github.com/rubygems/gemcutter/wiki/Brainstorming</a>).</p>
<p>Overall, the name doesn't matter IMO, if your code rocks, people will use it.</p></div>Nick Quaranto