5 ms·

You may want to review https://www.git-scm.com/about/trademark https://www.git-scm.com/about/trademark They have been stingy about projects with git in the nam

You may want to review https://www.git-scm.com/about/trademark https://www.git-scm.com/about/trademark They have been stingy about projects with git in the name.

HighlandSpring 4y ago
tig-bug would be fun
- Jenk 4y ago
  Quite fond of buggit :)
  - evanb 4y ago
    crickgit, mosgito, gnit, ...
fishbacon 4y ago
It also locks the scope to just git in the mind of the reader. Even if the scope broadens down the road. A less specific name might benefit the project? The part after the colon will explain the actual purpose.
M4v3R 4y ago
Have they? GitKraken & GitLens are pretty popular, commercial offerings, and they have been on the market for years. [0] https://www.gitkraken.com https://www.gitkraken.com
- sebmellen 4y ago
  Not to mention GitHub and GitLab either!
  - zeckalpha 4y ago
    Those all came before the crackdown
- deleted 4y ago
  [deleted]
michaelmure 4y ago
They have been quite ok[1] about the trademark aspect, but they do have a point about the namespace grab. I'm actually at a point where I do consider opting out of the git integration[2], as the introduction of new entities (project board, pr ...) do make things confusing (or even conflicting) as a series of git sub-commands. I haven't came up with a really satisfying solution though. [1]: https://marc.info/?l=git&m=153457109619678&w=2 https://marc.info/?l=git&m=153457109619678&w=2 [2]: https://github.com/MichaelMure/git-bug/issues/530 https://github.com/MichaelMure/git-bug/issues/530
xyzzy_plugh 4y ago
This is a bit weird to me. It's Git's own convention to add subcommands by placing a binary on the $PATH with the prefix `git-`. In this case, the subcommands becomes `git bug ...`. How would one name this differently? I tend to think this is more about commercial projects.
Klasiaster 4y ago
Git plugins must have binaries that start with "git-" because that's how they become subcommands. If the binary is called "git-something" for that reason, and it's about the project git anyway, it kind of makes sense to use this as project name.

You may want to review https://www.git-scm.com/about/trademark https://www.git-scm.com/about/trademark They have been stingy about projects with git in the name.

HighlandSpring 4y ago

tig-bug would be fun

Jenk 4y ago
Quite fond of buggit :)
- evanb 4y ago
  crickgit, mosgito, gnit, ...

fishbacon 4y ago

It also locks the scope to just git in the mind of the reader. Even if the scope broadens down the road. A less specific name might benefit the project? The part after the colon will explain the actual purpose.

M4v3R 4y ago

Have they? GitKraken & GitLens are pretty popular, commercial offerings, and they have been on the market for years. [0] https://www.gitkraken.com https://www.gitkraken.com

sebmellen 4y ago
Not to mention GitHub and GitLab either!
- zeckalpha 4y ago
  Those all came before the crackdown
deleted 4y ago
[deleted]

michaelmure 4y ago

They have been quite ok[1] about the trademark aspect, but they do have a point about the namespace grab. I'm actually at a point where I do consider opting out of the git integration[2], as the introduction of new entities (project board, pr ...) do make things confusing (or even conflicting) as a series of git sub-commands. I haven't came up with a really satisfying solution though. [1]: https://marc.info/?l=git&m=153457109619678&w=2 https://marc.info/?l=git&m=153457109619678&w=2 [2]: https://github.com/MichaelMure/git-bug/issues/530 https://github.com/MichaelMure/git-bug/issues/530

xyzzy_plugh 4y ago

This is a bit weird to me. It's Git's own convention to add subcommands by placing a binary on the $PATH with the prefix `git-`. In this case, the subcommands becomes `git bug ...`. How would one name this differently? I tend to think this is more about commercial projects.

Klasiaster 4y ago

Git plugins must have binaries that start with "git-" because that's how they become subcommands. If the binary is called "git-something" for that reason, and it's about the project git anyway, it kind of makes sense to use this as project name.