lets all create pointless multiple docker-<random_string> repositories in our accounts now. will serve them right :P
Using #docker in #Github repo names is forbidden.
We made you popular, you can sue us?!
Fair use? Asshole company,pic.twitter.com/uEISLFWIH2
-
-
-
thinking about renaming my repos to fuck-you-docker-<project-name> which would be allowed
-
New conversation -
-
-
IMHO I do not think that TM is applicable to the repos name
-
possibly…time to poke and edge these companies behaving like assholes against their own community :-)
End of conversation
New conversation -
-
-
is the last comment regarding Docker, or GitHub?
-
talking of docker only
End of conversation
New conversation -
-
-
@purpleidea i guess it's coming for me, too -
well,
#Docker Inc is corrupted by their $$$$$$ venture capital, one of these too-fast grown asshole startups
End of conversation
New conversation -
-
-
Even if project owner explicitly mention there is no partnership, or sponsorhip?
-
don’t ask me, ask legal@docker.com
End of conversation
New conversation -
-
-
-
would be also interesting whether this "rule" is only applies to GitHub repos. What's about Maven central ? npmjs ? CPAN ? Gems ?
-
ask legal@docker.com, ask them for _clear_ guidelines
-
already did :) now waiting for an answer ....
End of conversation
New conversation -
-
-
I read something about how use tha name herehttps://www.docker.com/trademark-guidelines …
-
…which is clearly cited in the posting :)
-
sorry I copied the bad link :) https://www.docker.com/brand-guidelines … search with "Use the word Docker as the first"
End of conversation
New conversation -
-
-
they need a clear trademark rule section. Like we have at
@TheASF http://www.apache.org/foundation/marks/ … -
of course they have guidelines https://www.docker.com/trademark-guidelines … The question is appropriate and fair-use.
-
I personally strongly believe that "docker-maven-plugin" falls under 'nominative use' and is thus fine to use.
-
I will ask
@docker tomorrow, too. imo 'docker-maven-plugin' doesn't dilute the brand at all. In contrary. But let's see. -
If there is a case, I will also warn the other 15 or so docker-maven-plugins. Not that they get into trouble.
-
Probably a good time to start unifying and moving the plugin under the umbrella of either the maven or docker community?
-
Could be a solution, but there are 4 active competing plugins, so not easy which to choose. Renaming is probably better.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.