this post was submitted on 02 Oct 2023
46 points (92.6% liked)

Linux

45756 readers
984 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
AgreeableLandscape@lemmy.ml
nooter692@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
46
Issue Tracking System for Linux (feddit.uk)
submitted 9 months ago by addie@feddit.uk to c/linux@lemmy.ml
9 comments fedilink hide all child comments
 

Hey gang! Looking for some recommendations on issue tracking software that I can run on Linux. Partly so that I can keep track of my hobby dev projects, partly so that I've got a bit more to talk about in interviews. My current workplace uses Jira, Trello and Asana for various different projects, which, eh, mostly serve their purposes. But I'm not going to be running those at home.

The ArchWiki has Bugzilla, Flyspray, Mantis, Redmine and Trac, for instance. Any of those an improvement over pen and paper? Any of those likely to impress an employer?

top 9 comments
sorted by: hot top controversial new old
[–] CapillaryUpgrade@lemmy.sdf.org 16 points 9 months ago (2 children)

Forgejo/Gitea are probably the most common "low-resource" (read: doesn't use a couple of GB RAM, like Gitlab supposedly does) code forges.

Do you want to impress future employers by running an enterprise-grade bugtracker or by showing that you can document your work with meaningful bug reports/etc.?

If it's the first option, consider Gitlab, if it's the second option, what ever you like.

[–] netchami@sh.itjust.works 7 points 9 months ago

Forgejo + ForgeFed is the perfect solution

[–] addie@feddit.uk 3 points 9 months ago (1 children)

Cool, will have a look at those, thanks! More looking to impress with my knowledge of using a variety of bugtrackers; have got plenty of evidence to show that there's a couple I know how to use.

[–] CapillaryUpgrade@lemmy.sdf.org 7 points 9 months ago

Then use Bugzilla. That will show you are ready to flail yourself for the good of the company /s

Sorry, but i find that platform so painful to use.

On a more serious note, i think some of the "github-style" (Gitlab/Gitea/Forgejo) can migrate between each other.

Check out if that's true and if so, try them all!

[–] sxan@midwest.social 6 points 9 months ago (2 children)

Put your FIXME:s in the source code, and use a tool like legume or ditz to manage them. (Here's an LWN "state of affairs" article from 2013 with several).

IMO web based bug trackers are overkill for personal projects. A workflow based ticketing system with an external interface adds a lot of unnecessary overhead unless you want users to be able to submit bugs, and even then, email works pretty well.

[–] ReversalHatchery@beehaw.org 2 points 9 months ago (1 children)

IMO web based bug trackers are overkill for personal projects.

I don't think so. This fixme-in-the-file wouldn't suit me well for example, because a lot of my projects are not file-based, and also because I regularly find myself writing lengthy comments under my gitea tickets to preserve how did I do something, or when something doesn't work to record the symptoms and what I tried to fix it, etc.

Gitea is probably not the best tool either for this, but it's quite good, and to me objectively better: all notes (issues and their comments) are timestamped and those can't be modified by mistake, tag support, several other aspects for categorization..

[–] sxan@midwest.social 2 points 9 months ago

If you're not working with files, then sure. For coders, putting tickets in the sourcecode enforces locality, and it also preserves history... because most people use a VCS.

But it sounds like you're using it as a journalling system, and that has different needs.

[–] pinchcramp@lemmy.dbzer0.com 2 points 9 months ago

Oh, this sounds interesting. I'll have to give this a try.

[–] cmeerw@programming.dev 2 points 9 months ago

There is also Roundup Issue Tracker