tag:help.rubygems.org,2010-01-19:/discussions/problems/17847-namesquattingRubyGems.org: Discussion 2018-10-18T19:51:21Ztag:help.rubygems.org,2010-01-19:Comment/332035392014-05-30T17:57:14Z2014-05-30T17:57:16ZNamesquatting<div><p><a href=
"https://rubygems.org/gems/dawn">https://rubygems.org/gems/dawn</a></p>
<p>I'd like to use the above gem name.</p></div>Blaž Hrastniktag:help.rubygems.org,2010-01-19:Comment/332035392014-06-07T01:57:49Z2014-06-07T01:57:49ZNamesquatting<div><p>Hi, it's been almost a week. Any input?</p></div>Blaž Hrastniktag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T02:45:49Z2014-06-16T02:45:49ZNamesquatting<div><p>Added <code>thesp0nge@gmail.com</code> to this thread, who's the
owner of that gem. Let's try to resolve this nicely first before
resorting to a hostile takeover.</p>
<p>It does seem like you have an awful lot of gems squatted on. Any
chance of releasing <code>dawn</code>?</p>
<p>Also, rubygems.org is 100% volunteer run. Please be patient with
us. :)</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T06:46:47Z2014-06-16T06:46:48ZNamesquatting<div><p>Hi there... i read "hostile takeover" and I found myself
puzzled.</p>
<p>I maintain codesake-dawn and the dawn gem is the placeholder
since it's<br>
already planned a namespace migration.<br>
Can you please list me "awful lot of gems squatted on"?</p></div>Paolo Peregotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T06:53:20Z2014-06-16T06:53:20ZNamesquatting<div><p>And I'll make a further bit... codesake-dawn started before<br>
<a href=
"https://github.com/dawn/dawn">https://github.com/dawn/dawn</a>
it's really disappointing you talk to me about<br>
"hostile takeover".</p></div>Paolo Peregotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T13:04:52Z2014-06-16T13:04:54ZNamesquatting<div><p>I ended up using <code>dawn-cli</code>. I reported the gem
because it seemed the place to do so, based on <a href=
"http://help.rubygems.org/discussions/problems/1566-namesquatting">http://help.rubygems.org/discussions/problems/1566-namesquatting</a></p>
<p>I just didn't think it seemed fair to take ahold of a name like
that (I don't know what rubygems' policies about namesquatting are
though). Back in the end of 2013 I checked rubygems and I picked
the project name because I saw that the gem name has not been
taken. I could easily have done the same, and pushed a placeholder
that would be sitting in the index for the last 9 months, waiting
for me to finally release code.</p></div>Blaž Hrastniktag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T13:08:02Z2014-06-16T13:08:02ZNamesquatting<div><p>Blaz, sorry to disappoint you but I started codesake-dawn with
dawn as<br>
binary script name in April 2013. So please don't accuse me about
name<br>
squatting.</p>
<p>Thank you<br>
Paolo</p></div>Paolo Peregotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T13:28:53Z2014-06-16T13:28:53ZNamesquatting<div><p>Sounds like the other name should be used then. I didn't mean to
imply a takeover would occur, we rarely if ever give gems over to
someone else without the authors permission.</p>
<p>Sent from my iPad</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T13:40:38Z2014-06-16T13:40:39ZNamesquatting<div><p>Guys... the thing that is disappointing me is that I release a
placeholder<br>
gem "dawn" in December 2013, yanked and then in January 2014. More
or less<br>
in the same period Blaz was working on his tool. Talking about<br>
"namesquatting" do imply that I publish dawn because I want to
cause a damage to Blaz and his project and this is not true.</p>
<p>So please let's make very clear that I was wondering about
resolving<br>
codesake (my saas not yet started) namespace clash for the static
analysis<br>
tool.<br>
I was not even aware for the Blaz dawn project, that uses the same
binary<br>
name as well... so am I expected to tell something about his script
name?<br>
I don't think so.</p>
<p>I will migrate gracefully. Putting a note in the gem post
installation<br>
message.<br>
Paolo</p></div>Paolo Peregotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T13:46:14Z2014-06-16T13:46:15ZNamesquatting<div><p>Another point I want to clarify Nick. You said "It does seem
like you have<br>
an awful lot of gems squatted on".<br>
Can you please clarify your point?</p>
<p>Apart from dawn and dusk (that is a security dynamic tool
placeholder from<br>
codesake-dusk), can you tell me which are the gems I released that
are<br>
"squat"? I see only, maybe useless, but real code.</p></div>Paolo Peregotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T13:53:27Z2014-06-16T13:53:28ZNamesquatting<div><p>I am not disputing that you started this in April '13, I am just
stating that I think it's wrong that <code>dawn</code> has been
sitting in the registry with nothing else but a module declaration
since January. It should either be put to use, or released for
others to use, anything else I consider namesquatting.</p>
<p>That said, I've settled on using <code>dawn-cli</code>, so this
issue can be marked as resolved.</p></div>Blaž Hrastniktag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T13:56:39Z2014-06-16T13:56:40ZNamesquatting<div><p>You consider this way. I consider not.<br>
It's a matter of opinions.</p>
<p>Following your way of thing you're a namesquatter too since your
gem binary<br>
name is dawn as mine...</p></div>Paolo Peregotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T14:48:03Z2014-06-16T14:48:03ZNamesquatting<div><p>It sounds like this is resolved since Blaž is going to use
a different gem name. Sorry to cause trouble here.</p></div>Nick Quarantotag:help.rubygems.org,2010-01-19:Comment/332035392014-06-16T15:15:45Z2014-06-16T15:15:45ZNamesquatting<div><p>For the future, I can suggest a friendly email to gem owner
instead to<br>
publicly accuse a person.<br>
Anyway, glad that we solve.</p></div>Paolo Perego