git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-bug: Distributed bug tracker embedded in git

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Aug 18, 2018, 05:43 UTC
Message-ID
<20180818054300.GB241538@aiede.svl.corp.google.com>
In-Reply-To
<CACSZ0Pwzs2e7E5RUEPDcEUsa=inzCyBAptU7YaCUw+5=MutSsA@mail.gmail.com>
Hi,
Michael Muré wrote:
Show 6 quoted lines
> I released today git-bug, a distributed bug tracker that embeds in
> git. It use git's internal storage to store bugs information in a way
> that can be merged without conflict. You can push/pull to the normal
> git remote you are already using to interact with other people. Normal
> code and bugs are completely separated and no files are added in the
> regular branches.

I am a bit unhappy about the namespace grab. Not for trademark reasons: the Git trademark rules are pretty clear about this kind of usage being okay. Instead, the unhappiness comes because a future Git command like "git bug" to produce a bug report with appropriate diagnostics for a bug in Git seems like a likely and useful thing to get added to Git some day. And now the name's taken.

Is it too late to ask if it's possible to come up with a less generic name?

Separately from that, I'm happy to see progress being made in the distributed bug tracker world; thanks for that!

Thanks, Jonathan

Previous: Tacitus AedifexNext: Ævar Arnfjörð Bjarmason
Message 3 of 18 in “git-bug: Distributed bug tracker embedded in git”
  1. Michael MuréAug 17, 2018
  2. Tacitus AedifexAug 17, 2018
  3. Jonathan NiederAug 18, 2018
  4. Ævar Arnfjörð BjarmasonAug 18, 2018
  5. Jonathan NiederAug 18, 2018
  6. Ævar Arnfjörð BjarmasonAug 18, 2018
  7. Jonathan NiederAug 18, 2018
  8. Ævar Arnfjörð BjarmasonAug 18, 2018
  9. Jonathan NiederAug 18, 2018
  10. Jeff KingAug 19, 2018
  11. Junio C HamanoAug 18, 2018
  12. Jonathan NiederAug 19, 2018
  13. Kyle MeyerAug 19, 2018
  14. Jonathan NiederAug 19, 2018
  15. Jonathan NiederAug 18, 2018
  16. Michael MuréAug 19, 2018
  17. Michael MuréAug 19, 2018
  18. Elijah NewrenAug 19, 2018

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.