git-issue VS AnyTone-D868UV

Note that if you just want to provide a issue tracker within Git rather than relying on centralized web services like Github or Gitlab, there is

https://github.com/MichaelMure/git-bug

https://github.com/dspinellis/git-issue

https://sciit.gitlab.io/sciit/ (this one has a list of alternatives here https://sciit.gitlab.io/sciit/#other-distributed-issue-track...)

Overall it's very disappointing that Github didn't decide to embed issue tracking (and also PR discussions) inside the repository (in another branch perhaps). Issue discussion is part of documentation IMO, and not distributing it alongside the repository causes lock-in

A quick search for 'issue tracker stored in git repository' brings up this Stackoverflow post, which points to git-bug and git-issue. Those look closer to what you're asking for, thought I haven't used them.

I think he meant just the network effects of a social platform. Github has more people in them so there are more people interacting with repositories hosted on Github.

I wish that somehow people carried identity across Github / Gitlab / Gitea / other services. Like, a federated issue tracker. Or otherwise that the issues themselves were easily movable between platforms, with no lock-in. But the incumbent platforms rarely want something like this.

An alternative is to eschew platform issues entirely, and use decentralized issue comments hosted as Git repositories, like https://github.com/dspinellis/git-issue or https://github.com/neithernut/git-dit or https://github.com/MichaelMure/git-bug - I think that Gitlab should offer integration with one of them. I mean: both allowing to export issues and PRs into a Git branch, and allowing people to comment on issues and PRs by pushing to a Git branch.

git-bug, the one mentioned in the article here, has some documentation on its README of how well its importer/exporter tools support Github, Gitlab, Jira, and Launchpad: https://github.com/MichaelMure/git-bug

Most of the other such tools I've seen barely have the resources to import/export a single such API. git-issue only has Github import it looks like. https://github.com/dspinellis/git-issue

There's perceval which is designed to be a generic archival tool and supports lots of APIs, but only dumps them to source-specific formats and would still need a lot of work if you tried to use issues from different APIs together: https://github.com/chaoss/grimoirelab-perceval

My most starred repo has no code in it too!

A few years ago I bought an AnyTone AT-D868UV ham radio. As with any software-managed device, there were a few issues. I wanted a place to keep track of these problems for my own purposes. So I thought "GitHub Issues!"

https://github.com/geary/AnyTone-D868UV

I added a couple dozen of the problems I'd run into. And then it took a life of its own. Some people thought it was an official AnyTone support channel (despite my disclaimer). That's bound to happen.

The fun part was when people started an issue on how to upgrade a D868UV to a D878UV.

https://github.com/geary/AnyTone-D868UV/issues/59

Of course this was kind of an insane project unless you look at it from the point of a ham operator: radio hacking is fun!

Now about the gloves and chili.

Around 1974 I decided to stir fry a very hot dish of chiles and eggplant.

I didn't use any gloves, nor the fume hood that would have been wise.

Midway through the stir fry I noticed my forehead was burning.

But I ate the dish and it was delicious.

The next morning I woke up and my fingers were numb!

I went into survival mode and quickly realized that what I needed to do was eat a lot of yogurt, right then and there.

And it worked. I still have my fingers!

I am embarrassed to admit that my most popular GitHub repo is an issues-only tracker for something I didn't even create: a popular handheld ham radio, the AnyTone AT-D868UV/AT-D878UV.

After I bought my radio, I found a few firmware issues and looked for a way to communicate them to the manufacturer. No luck on that. There was an active Facebook group, but it is a weird place run by a radio dealer who would ban you for discussing anything he thought might interfere with his business.

So I made a repo and started adding issues for the things I'd noticed. People found it and it took on a life of its own. The most popular issue is a lengthy collaboration among several hams who worked out a way to update the firmware on the D868UV to convert it to a D878UV.

This was one of the topics that would get you banned on that Facebook group, as the group owner would rather sell you a new radio. The funny part about that is the upgrade involves buying a special programming board and considerable time and effort, plus the risk of ruining your radio. So it was really just a labor of love for a few hams who had a blast working out how to do the upgrade.

Hams may not build our own radios as much as we used to, but we can still hack the firmware!

https://github.com/geary/AnyTone-D868UV

thanks yea. it's been a while, but according to another recent comment on the github