Namesquatting

Blaž Hrastnik's Avatar

Blaž Hrastnik

30 May, 2014 05:57 PM

https://rubygems.org/gems/dawn

I'd like to use the above gem name.

  1. 1 Posted by Blaž Hrastnik on 07 Jun, 2014 01:57 AM

    Blaž Hrastnik's Avatar

    Hi, it's been almost a week. Any input?

  2. Support Staff 2 Posted by Nick Quaranto on 16 Jun, 2014 02:45 AM

    Nick Quaranto's Avatar

    Added [email blocked] to this thread, who's the owner of that gem. Let's try to resolve this nicely first before resorting to a hostile takeover.

    It does seem like you have an awful lot of gems squatted on. Any chance of releasing dawn?

    Also, rubygems.org is 100% volunteer run. Please be patient with us. :)

  3. 3 Posted by Paolo Perego on 16 Jun, 2014 06:46 AM

    Paolo Perego's Avatar

    Hi there... i read "hostile takeover" and I found myself puzzled.

    I maintain codesake-dawn and the dawn gem is the placeholder since it's
    already planned a namespace migration.
    Can you please list me "awful lot of gems squatted on"?

  4. 4 Posted by Paolo Perego on 16 Jun, 2014 06:53 AM

    Paolo Perego's Avatar

    And I'll make a further bit... codesake-dawn started before
    https://github.com/dawn/dawn it's really disappointing you talk to me about
    "hostile takeover".

  5. 5 Posted by Blaž Hrastnik on 16 Jun, 2014 01:04 PM

    Blaž Hrastnik's Avatar

    I ended up using dawn-cli. I reported the gem because it seemed the place to do so, based on http://help.rubygems.org/discussions/problems/1566-namesquatting

    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.

  6. 6 Posted by Paolo Perego on 16 Jun, 2014 01:08 PM

    Paolo Perego's Avatar

    Blaz, sorry to disappoint you but I started codesake-dawn with dawn as
    binary script name in April 2013. So please don't accuse me about name
    squatting.

    Thank you
    Paolo

  7. Support Staff 7 Posted by Nick Quaranto on 16 Jun, 2014 01:28 PM

    Nick Quaranto's Avatar

    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.

    Sent from my iPad

  8. 8 Posted by Paolo Perego on 16 Jun, 2014 01:40 PM

    Paolo Perego's Avatar

    Guys... the thing that is disappointing me is that I release a placeholder
    gem "dawn" in December 2013, yanked and then in January 2014. More or less
    in the same period Blaz was working on his tool. Talking about
    "namesquatting" do imply that I publish dawn because I want to cause a
    damage to Blaz and his project and this is not true.

    So please let's make very clear that I was wondering about resolving
    codesake (my saas not yet started) namespace clash for the static analysis
    tool.
    I was not even aware for the Blaz dawn project, that uses the same binary
    name as well... so am I expected to tell something about his script name?
    I don't think so.

    I will migrate gracefully. Putting a note in the gem post installation
    message.
    Paolo

  9. 9 Posted by Paolo Perego on 16 Jun, 2014 01:46 PM

    Paolo Perego's Avatar

    Another point I want to clarify Nick. You said "It does seem like you have
    an awful lot of gems squatted on".
    Can you please clarify your point?

    Apart from dawn and dusk (that is a security dynamic tool placeholder from
    codesake-dusk), can you tell me which are the gems I released that are
    "squat"?
    I see only, maybe useless, but real code.

  10. 10 Posted by Blaž Hrastnik on 16 Jun, 2014 01:53 PM

    Blaž Hrastnik's Avatar

    I am not disputing that you started this in April '13, I am just stating that I think it's wrong that dawn 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.

    That said, I've settled on using dawn-cli, so this issue can be marked as resolved.

  11. 11 Posted by Paolo Perego on 16 Jun, 2014 01:56 PM

    Paolo Perego's Avatar

    You consider this way. I consider not.
    It's a matter of opinions.

    Following your way of thing you're a namesquatter too since your gem binary
    name is dawn as mine...

  12. Support Staff 12 Posted by Nick Quaranto on 16 Jun, 2014 02:48 PM

    Nick Quaranto's Avatar

    It sounds like this is resolved since Blaž is going to use a different gem name. Sorry to cause trouble here.

  13. Nick Quaranto closed this discussion on 16 Jun, 2014 02:48 PM.

  14. Paolo Perego re-opened this discussion on 16 Jun, 2014 03:15 PM

  15. 13 Posted by Paolo Perego on 16 Jun, 2014 03:15 PM

    Paolo Perego's Avatar

    For the future, I can suggest a friendly email to gem owner instead to
    publicly accuse a person.
    Anyway, glad that we solve.

  16. Nick Quaranto closed this discussion on 18 Jun, 2014 12:28 AM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac