Hacker News Reader

GIT is non-proprietary and decentralized so it keeps that promise.

And having a built-in issue tracker

1. isn't related to those properties, and

2. isn't truly within the scope of a source code version control management solution.

That's the domain of project management.

Fossil has one. If its something you want use Fossil - which I think is a great alternative for small teams, on the other hand, this is probably not something large teams (which are a high priority for git) want.

For large projects like the Linux kernel as an example out of many, I would assume the built-in issue tracker would end up 100x the size of the code base in storage space. lol

If I ever get around to writing my git issue tracker, everything will be stored in a completely separate reponame-issues.git

Shouldn't the git native issue tracker be as simple as adding file pr/the_problem_i_am_having

Issues shouldn't really live in the same source tree, IMO. But AFAIK there are forges that keep the issues in the same repository, just not in the same tree of commits that the source tree has, git notes style.

Any user without commit permission should be able to create tickets and comment on them.

What's wrong with debbugs? :)