From: Richard Conroy <richard.conroy@...>
Date: 2010-08-06T00:51:34+09:00
Subject: Re: Project name ownership and conflict

--0003255590ae2ca024048d1586d3
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Aug 5, 2010 at 4:13 PM, Roger Pack <rogerpack2005@gmail.com> wrote:

>
> > What is the community view of project name 'ownership'? Was my fellow
> > Rubyist right to publish his Gem without checking Google, GitHub or
> > RubyForge for existing projects under his intended name? Or am I right
> > to expect Ruby Gem authors to perform at least a minimal search for
> > existing projects prior to publication?
>
> Yeah typically all we check if "can I push this gem?" before grabbing
> the namespace.  Unfortunately.
> Hopefully you can work it out civilly :)
> One option would be to keep with your original github gem name
> username-gemname, since apparently that was good enough at one point?


Is this issue growing in significance? I have heard of cases of gemname
'squatting'
going on.

Is there even some kind of community ad-hoc guide for naming gems?

While 'first to publish claims the name' sounds harsh, in practice I don't
see any other
reliable way for enforcement.

-- 
http://richardconroy.blogspot.com

--0003255590ae2ca024048d1586d3--