Next Gen Infrastructure
The project has 4 servers:
- mocha (not used anymore, and we don't have access to it)
All servers are hosted at the Namur University in Belgium. Our contacts there are Didier and Pollux
All Xfce related services are hosted on these servers:
- Websites (www, wiki, blog etc)
- DNS master
- Mailing Lists
- Release manager and archive master
- DNS slave
We have very old hardware (Sun Fire, Sun V20z etc.), and little or no hardware spares.
Even if we don't update our workflow, we need to get rid of our old servers. We can thank UNamur 100000x for their free hosting for the last decade, but I think we need to find a new sponsor. Maybe Gandi (with m8t) can be a solution.
This can be some cloud services or dedicated servers or something else. We don't need unlimited resources, only 2 or 3 instances with enough ram / cpu / disk and good stability.
On the DNS side, maybe outsource this to a provider.
What do we need : 2 instances (VM are ok), per instances:
- 6GB Ram
- ~ 50GB Disk
And a backup server. As we can keep our servers at namur, they can serve as a backup site.
Proof of Concept
We need a VM (Debian) for testing the self-hosted alternatives and the migration workflow. Current POC of Gitea is here: https://gitea.xfce.alteroot.org/xfce
Projects and users
- Each Xfce project should be placed under specific category — “organization” in terms of gitea. The following organizations should be created: Xfce Core, Xfce Applications, Panel Plugins, Thunar Plugins, Bindings, WWW, Archive. ✔
- Allow to register for everybody in order to create issues and pull requests ✔
- Users with higher level of privileges can create their own user repositories (is it possible to do with gitea?) ⇒ Everybody can create a “fork” or a repository by default. We can set MAX_CREATION_LIMIT = 0 to only allow Forks (note: need to handle the “user repo” thing) ✔
- Users can be added as project collaborators in order to commit to the repo directly (multiple project maintainers): One “owner” team per organization (full admin, by default), one “core” dev team per organization (with write access) + individual dev write access to individual projects (for example panel plugins). ✔
- Some git hooks/configs are required: deny force push to git master, deny deleting master repo, deny deleting projects from organizations (official categories, see above), (what else?) : Only on “official” repo (not forks), enable “branch protection” + Add denyNonFastforwards = true with a script (not possible via gitea itself) ✔
- git post-receive hook : use a “hack” by using git template (in ~/.gitconfig ) + symbolic links based on https://discuss.gogs.io/t/global-git-hook-support/777 : ✔
- Enable github oauth ?
Migration from Cgit
- All git repos, project descriptions and hooks should be migrated to gitea
- Cgit could remain in order to provide old GUI. It should work with gitea repos (gitolite will be dropped) so it requires some patches to display user repos properly
- Keep a git-daemon for the git:/ protocol
Style and GUI
- Gitea's color scheme should be adapted to Xfce web scheme
- Integrate the Xfce website header somehow
- Starting page should redirect to list of organizations unless user is signed in
Migration from Bugzilla
- Issues link should redirect to bugzilla initially: Done with “External Tracker” option ✔
- Transifex translation commits can be (optionally) hidden from gitea web gui
Migration from Bugzilla
- Migrate all issues from bugzilla to gitea
- New “Bugzilla Migration” user should be created as owner of all migrated comments from bugzilla
- Product categories should be replaced with gitea issue tags (they should be created for each repo)
- Bug statuses such as duplicate/wontfix/etc should be migrated as default gitea-level tags
- Bug statuses such as open/closed bugs should be migrated as open/closed issue statuses
- All attachments (even patches) should be migrated as attachments
- Write a simple web server which will redirect from old bugzilla pages to new gitea issue pages (there should be a small db with (“bugzilla bug id” <> “repo name”, “repo bug id”) association)