Why and how does an organization provide managed Gitea instances? #5
Labels
No labels
Analysis
Interviews
Question
Report
Use Cases and Personae
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Hostea/user-research#5
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This focuses on the experience of the Sysadmin personae rather than the Gitea admin or Gitea user.
Question: why and how does an organization provide managed Gitea instances?
Rationale: The Sysadmin works within an organization that provides services to clients, including managed hosting. They occasionally setup a Gitea instance for their client and although it does not happen very often. There are less than ten Gitea instances in an organization that has less than 20 employees.
Assumptions: They preferred Gitea over GitLab, maybe because it uses less resources, maybe for other reasons. Since there are only a handful of them installed, it was done manually as well as the upgrades. The installation and upgrade process was documented internally and involves connecting with the existing backup/recovery system, firewall, intrusion detection and monitoring.
It is useful to understand what drives the choices of these Sysadmins, what is their experience with installation and maintenance, to better understand how Z could be an attractive proposition for them. What would make them choose Z over manually managed Gitea?
dachary referenced this issue2022-03-19 14:00:07 +05:30