Sorry, but I’ll try to keep it brief.
We’ve started working with Gitea.
(Powered by Gitea Version: 1.25.4 Page: 1ms Template:1ms)
Working with repositories is generally great.
We tried working with scheduling,
but there are some inconsistencies – organizing scheduling is essentially impossible.
I read the forum – old posts:
- Basic concept of Organisation, Repository, Milestone, Project - #7 by mrall
- Can you explain to me the principle of organization, package and project within gitea
So, the problem exists and hasn’t been solved.
Individual scenarios are commendable, but they don’t solve the conceptual problem.
At a minimum, I’d like a template like this:
- Project (with a description of the goal and objectives)
(and this isn’t the same project that currently exists in Gitea) - Milestones (with the ability to assign responsibilities)
(milestones for the project, not for the repo or Kanban board) - Kanban board (or similar)
- Issue
- Repositories (multiple) (and they can have different participants)
Currently, Gitea’s current architecture confuses all concepts,
assuming that the repository is the primary entity.
This is, of course, incorrect.
The real question is: is there any work being done on planning?
Should we expect significant changes in this area?
P.S.: Repository management will remain a work in progress –
everything there is practically “The Best.”
The shot remark about Gitlab - it has deteriorated – it’s become a sluggish,
buggy monster with daily updates – this is unacceptable – fired.
Thank you for your patience – I hope my translation is readable enough.
And yes, Gitea is a good product. ‘Go’ is the right choice.