Taiga VS Gitea

View on GitHub

GitHub: Taiga GitHub Repository

I'll also check out plane.so and taiga.io. I have not checked those out.

My team at work uses taiga

taiga.io — Project management platform for startups and agile developers, free for Open Source

The folks being Penpot also make a kanban management tool, kind of like Trello, called Taiga: http://taiga.io/ And it's also OSS.

I'm rooting for both of these, and now that they have some funding I hope they'll dedicate effort on polishing the rough edges (and do something about gratuitous amount of white space that permeates all of their web presence, and maybe reconsider their color pallete). They're very close, so I think and hope we'll some wonderful results very soon.

Taiga - Storage limitation

taiga.io has been good in my experience

^ This installs docker first (not sure if needed, but I'm trying to figure out how to set up taiga.io on my k3s cluster and they seem to want docker?

As I mentioned in a previous post - you can use "git" without Github by hosting an instance of the open-source Gitea service.

https://github.com/go-gitea/gitea

As mentioned in the last post, I keep my notes in git repositories. I originally used Obsidian for years as my note-taking application of choice after migrating away from Google Keep, using the vast library of community plugins (namely obsidian-livesync and obsidian-git) to back up and sync my notes on an interval to my 3 remotes; GitHub, my private Gitea instance for my private "second brain" type notes, and my Otterwiki instance (a wiki that runs on a git server of markdown files).

The solution to this is to use fake e-mails.

I can't say what Forgejo has over Gitea, but I can tell you Forgejo is missing everything from the 888 merged PRs in Gitea 1.23: https://github.com/go-gitea/gitea/releases/tag/v1.23.0-rc0

Repo license support, integrated Arch package repository, automatic issue suggestions, and the new review+homepage UIs would be notable ones for me.

See this issue: https://github.com/go-gitea/gitea/issues/1029

For years, "self-hosting" Gitea wasn't done because it was missing a bunch of useful collaboration features. Now, it looks like that gap has been closed. All of the specific features mentioned in that issue seem to have been fixed, and the big remaining task is figuring out below to actually migrate all the existing data out of GitHub -- which doesn't seem to be super high on the priority list.

We're not, and they're still in the process of discussion. It seems a bit early to fork and witch-hunt [0]:

> So clarification here: you asked me about that, but I haven’t been able to respond to you due to my illnesses and I’m just getting back on my feet now. So it’s not that it hasn’t been well received, it’s that I’ve been physically unable to respond to you.

[0]: https://github.com/go-gitea/gitea/pull/24257#issuecomment-23...

Yeah, I'm actually doing that with Gitea: https://about.gitea.com/

Some people went with the forgejo fork: https://forgejo.org/ though Gitea itself was a fork of Gogs, if I remember correctly: https://gogs.io/

I also ran GitLab in the past: https://about.gitlab.com/ but keeping it updated and giving it enough resources for it to be happy was troublesome.

There's also GitBucket: https://gitbucket.github.io/ and some other platforms, though those tend to be a little bit more niche.

Either way, there's lots of nice options out there, albeit I'd still have to admit that just using GitHub or cloud GitLab version would be easier for most folks. Convenience and all.

Create a system service. Download the file and save it to /etc/systemd/system/ or view the raw file in a browser and replace the URL with the version of Gitea you installed. You can find the list on https://github.com/go-gitea/gitea/blob/release/v1.22/contrib/systemd/gitea.service:

Same [1]. Zoom being outsourced to the implementing platform is one major pain-point. That example from us has grown in size.

We are clearly using the wrong tool for a diagram of this complexity, but the practicality of seeing commit changes in the diff, what property was changed by whom and instantly having the visual feedback in the Pull Request is just way too useful to use a "proper" tool.

[1] https://github.com/go-gitea/gitea/issues/25803