bug
Distributed bug tracking with the filesystem and hg or git (by driusan)
PoormanIssueTracker
A simple format for using the file system as an issue tracker (by driusan)
bug | PoormanIssueTracker | |
---|---|---|
2 | 1 | |
204 | 27 | |
- | - | |
0.0 | 0.0 | |
about 5 years ago | over 7 years ago | |
Go | ||
GNU General Public License v3.0 only | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bug
Posts with mentions or reviews of bug.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-02.
-
Let's Make Sure Github Doesn't Become the only Option
For example, there's a bunch like bug, where the issues just get stored as plaintext files in your repo. This makes intuitive sense -- it's like storing your docs as Markdown files in your repo. You can use all the same tools to branch and merge and such, and you can include some code that fixes an issue, mark the issue as fixed, and update the docs all in the same commit, without needing any special tooling to synchronize those things. If you want to find out which branches (or releases, etc) have the fix, you can just look at the state of the bug inside those branches.
-
What does a sysadmin use for keeping track of Tasks and/or To-Do Lists?
https://github.com/driusan/bug is a similar system written in Go. The goal is to use the filesystem in a human readable way, similar to how an organized person without any bug tracking software might, by keeping track of bugs in an issues/ directory, one (descriptive) subdirectory per issue.
PoormanIssueTracker
Posts with mentions or reviews of PoormanIssueTracker.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-01-18.
-
What does a sysadmin use for keeping track of Tasks and/or To-Do Lists?
If you're comfortable with git and are willing to use the simplest thing that would work, have a look here: https://github.com/driusan/PoormanIssueTracker
What are some alternatives?
When comparing bug and PoormanIssueTracker you can also consider the following projects:
critic - Critic code review system.