Is gitarena intended to be a better Fossil?

[ckaran]

I'm trying to get a feel for what the intent of this project is. I can't tell if it is intended to be 100% distributed like fossil, or if it is just intended to be another Github/Gitlab.

The reason I ask is because I would love to see something like fossil, but for git, so that I can share not only my code but all of my issues, discussions, kanban board, etc., etc., etc. I just can't tell if that's the direction you're trying to go with it.

[mellowagain]

It's intended to be just like GitHub and GitLab, but with a primary focus on self hosting instead of being a hosted instance. I may add distributed system support in the future as the primary Git library I use, gitoxide, has had a discussion for something similiar so implementing it wouldn't be all too far fetched.

I will keep this issue open as a tracking issue regarding this.

[ckaran]

Good, I'm glad you're looking into it. If you do go down this route, you may also wish to look into CRDTs, or at least understand how they could be useful. Git-bug's model discusses them in relation to Git-bug, but the ideas are generally useful. When and where possible, they should be applied to your data models as they will make distributed operations FAR less painful for the end user.

[ckaran]

OK, I just had a chance to mess around with dolt. It looks pretty good so far. Most importantly, it has support for storing and managing its database from within git (see git-dolt). This means that you have a drop in MySQL replacement that can be managed within git, so gitarena could in theory be fully distributed.

[milahu]

see Fossil Versus Git for a detailed comparison

summary:

• git is better for collaboration between many random strangers ("bazaar", internet)
• fossil is better for collaboration in small teams ("cathedral", intranet)

so i guess the question should be rephrased to:
should gitarena provide a webinterface to git-bug?

gitea issue: go-gitea/gitea#6519

[ckaran]

I'm completely open to an interface to git-bug; I'm just after something that tracks issues and keeps them inside of the repo so I can remember them if I'm not connected to the internet.