freedesktop issueshttps://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues2024-03-14T08:43:22Zhttps://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/69Migrate DRM repositories to gitlab2024-03-14T08:43:22ZDaniel VetterMigrate DRM repositories to gitlabNote, this is a very WIP migration plan, we will fill out details as we go.
## Checklist
Probably need this checklist for each part of the migration ...
- [x] Project contacts filled by by requestor
- [x] CoC section filled by request...Note, this is a very WIP migration plan, we will fill out details as we go.
## Checklist
Probably need this checklist for each part of the migration ...
- [x] Project contacts filled by by requestor
- [x] CoC section filled by requestor
- [x] Git repo information filled by requestor (or N/A)
- [x] Bugzilla information filled by requestor (or N/A)
- [x] Mailman information filled by requestor (or N/A)
- [x] Web hosting information filled by requestor (or N/A)
- [x] Migration request acked & scheduled by admin
- [ ] Migration in progress
## Project contacts
**Primary project admin** (GitLab username): seanpaul, danvet
There will be additional owners for each of the projects we're migrating underneath the overall drm umbrealla. Sean&Me will do the initial migration hearding for DRM overall.
-Daniel
## Code of Conduct
- [x] Our projects agree to the Code of Conduct
- [x] Where reasonable, we have placed links to the CoC within our project
**CoC contacts**: Listed in CONTRIBUTING or similar docs in each project, with fd.o as escalation points.
## Git repository migration
All currently under `cgit.freedesktop.org/drm` is in scope. We need to figure out details, so this is just the overview.
- [x] New project: `gitlab.fd.o/drm/maintainer-tools`, will be filled with the maintainer-tools branch from `cgit.fd.o/drm/drm-tip`, but reduced committer/owner list.
- [x] Update logic in dim to switch to the new maintainer-tools branch
- [x] Need to disable the intel-gfx-ci job to build maintainer-tools docs <- @ivyl
- [x] Need a web redirect from `dri.fd.o/docs/dim` to `drm.pages.fd.o/maintainer-tools`
- [x] Migrate: `cgit.fd.o/drm/igt-gpu-tools` -> `gitlab.fd.o/drm/igt-gpu-tools` with same group.
- [x] RFC discussion on `igt-dev@lists.fd.o`
- [x] Migrate all the accounts in the igt group
- [x] After one week to let everyone activate their accounts: Migrate the actual repo
- [x] Make @ivyl and @adrinael maintainers
- [x] Delete the igt gitlab group at https://gitlab.freedesktop.org/igt
- [x] Move?: `cgit.fd.o/drm_hwcomposer` -> `gitlab.fd.o/drm-hwcomposer/drm-hwcomposer`
- [x] Migrate: `cgit.fd.o/drm/drm-firmware` -> `gitlab.fd.o/drm/firmware`
- [ ] Would be nice to link to `gitlab.fd.o/mesa/drm` from the drm group.
The kernel repos must all move together, and only after we've prepared it all in the maintainer-tools scripts. drm-tip needs some ACL magic to allow any committer to the other drm kernel repos to also push to drm-tip.
- [x] Prepare maintainer-tools to allow auto-migration of existing setups
- [ ] Migrate: `cgit.fd.o/drm/drm` -> `gitlab.fd.o/drm/kernel`
- [x] Create the DRM Group
- [x] Add all maintainers to the Group
- [x] Create the DRM Repository
- [x] Push the current branches in the `cgit.fd.o/drm/drm` Repository
- [x] Update `rerere` nightly.conf
- [x] Update `MAINTAINERS`
- [x] Update Documentation
- [x] Send an email to let dri-devel know about the new URL
- [x] Let linux-next and sfr know about the new URL
- [x] Setup the git hook to prevent someone from pushing without dim
- [x] Setup the old repo as a mirror of the new one
- [x] Sync all the drm-* and topic/* tags
- [ ] Remove the old repo after a while
- [ ] Migrate: `cgit.fd.o/drm/drm-tip` -> `gitlab.fd.o/drm/tip`
- [x] Create the new repo
- [x] Give access to the repo to the following groups:
- [x] intel
- [x] misc
- [x] xe
- [x] Prefill the repo with the old repo content
- [x] Mark the cgit repo read-only
- [x] Update `rerere` nightly.conf
- [x] Update documentation
- [x] Setup the git hook to prevent someone from pushing without dim
- [x] Setup the old repo as a mirror of the new one
- [ ] Remove `cgit.fd.o/drm-tip` after a while
- [ ] Remove `cgit.fd.o/drm/drm-tip` after a while
- [ ] Migrate: `cgit.fd.o/drm/drm-misc` -> `gitlab.fd.o/drm/misc/kernel`
- [x] Create the drm-misc Group
- [x] Add all members of the drm-misc ldap group to the Gitlab group
- [x] Make sure all drm-misc maintainers are setup as owners
- [x] Create the drm-misc Repository
- [x] Mark the cgit repo read-only
- [x] Push the current branches in the `cgit.fd.o/drm/misc/kernel` Repository
- [x] Update `rerere` nightly.conf
- [x] Update `MAINTAINERS`
- [x] Update Documentation
- [x] Send an email to let dri-devel know about the new URL
- [x] Let linux-next and sfr know about the new URL
- [x] Setup the git hook to prevent someone from pushing without dim
- [x] Setup the old repo as a mirror of the new one
- [x] Sync all the drm-misc-* and topic/* tags
- [ ] Remove the old repo after a while
- [ ] Migrate: `cgit.fd.o/drm/drm-intel` -> `gitlab.fd.o/drm/i915/kernel`
- [x] Create `drm/i915` group
- [x] Add all members of the drm-intel ldap group to the Gitlab group
- [x] Make sure all drm-intel maintainers are setup as owners
- [ ] Find an acceptable way to store the issue templates
- [ ] Move `drm/intel` repo to `drm/i915/kernel`
- [ ] Mark the cgit repo read-only
- [ ] Push the current branches in the `gitlab.fd.o/drm/i915/kernel` Repository
- [ ] Update `rerere` nightly.conf
- [ ] Update `MAINTAINERS`
- [ ] Update Documentation
- [ ] Send an email to let dri-devel know about the new URL
- [ ] Let linux-next and sfr know about the new URL
- [ ] Setup the git hook to prevent someone from pushing without dim
- [ ] Setup the old repo as a mirror of the new one
- [ ] Sync all the drm-intel-* and topic/* tags
- [ ] Remove the old repo after a while
- [ ] Migrate: `cgit.fd.o/drm/drm-amd` -> `gitlab.fd.o/drm/*/kernel`
- [ ] Figure out a group name that doesn't conflict with the current `gitlab.fd.o/drm/amd` issues repo
- [ ] Create `drm/?` group
- [ ] Add all members of the ldap group to the Gitlab group
- [ ] Make sure all maintainers are setup as owners
- [ ] Find an acceptable way to store the issue templates
- [ ] Move `drm/amd` repo to `drm/?/kernel`
- [ ] Mark the cgit repo read-only
- [ ] Push the current branches in the `gitlab.fd.o/drm/?/kernel` Repository
- [ ] Update `rerere` nightly.conf
- [ ] Update `MAINTAINERS`
- [ ] Update Documentation
- [ ] Send an email to let dri-devel know about the new URL
- [ ] Let linux-next and sfr know about the new URL
- [ ] Setup the git hook to prevent someone from pushing without dim
- [ ] Setup the old repo as a mirror of the new one
- [ ] Sync all the drm-amd-* and topic/* tags
- [ ] Remove the old repo after a while
- [ ] Fixup fork network so all kernel repos are forks of `gitlab.fd.o/drm/drm`, see https://docs.gitlab.com/ee/api/projects.html#create-a-forked-fromto-relation-between-existing-projects
- [ ] `drm/amd`
- [x] `drm/intel`
- [x] `drm/misc/kernel`
- [ ] `drm/msm`
- [ ] `drm/nouveau`
- [ ] `drm/tegra`
- [x] `drm/tip`
- [ ] `drm/xe/kernel`
- [x] Delete cgit.fd.o/drm/drm-xe
- [x] Mark cgit.fd.o/drm/drm-firmware as read-only
NOTE: Large scale kernel repo migration is blocked on making gitlab.fd.o scale more: #138
## Bugzilla
ATM no bug migration planned. We'll disable gitlab issues until we're ready to start using them.
## Merge Request Flow
ATM not planned to be used. We'll disable gitlab MR until we're ready to start using them.
## Mailman
Lists releavant to different parts of DRM:
- maintainer-tools: `dim-tools@lists.fd.o`
- igt: `igt-dev@lists.fd.o`
- drm-intel: `intel-gfx@lists.fd.o`
- drm-amd: `amd-gfx@lists.fd.o`
- Everything else: `dri-devel@lists.fd.o`
## Web hosting
Definitely not first priority, but would be nice to migrate a few things (including putting them into gitlab autobuilders):
- [ ] igt docs: atm hosted on Intel's 01.org, needs something like `https://dri.freedesktop.org/docs/igt`
- [ ] drm docs: `https://dri.freedesktop.org/docs/drm/`
- [x] maintainer-tools docs: `https://dri.freedesktop.org/docs/dim/`Maxime Ripardmripard@kernel.orgMaxime Ripardmripard@kernel.orghttps://gitlab.freedesktop.org/freedesktop/freedesktop/-/issues/28Migrate XDG specifications to GitLab2020-01-16T18:40:12ZDaniel Stonedaniel@fooishbar.orgMigrate XDG specifications to GitLabIt would be nice if we could migrate the Git hosting for all the XDG specifications to GitLab. Once that is done, we can start looking at using GitLab CI pipelines through Pages to automatically generate https://specifications.freedeskto...It would be nice if we could migrate the Git hosting for all the XDG specifications to GitLab. Once that is done, we can start looking at using GitLab CI pipelines through Pages to automatically generate https://specifications.freedesktop.org from its component repositories.
Here are the repositories we currently have. All of these will need some kind of responsible owners designated:
* [x] dapi-dbus (archived as inactive)
* [x] dapi (archived as inactive)
* [x] default-icon-theme (@alexl)
* [x] icon-naming-spec
* [x] icon-theme-spec
* [x] desktop-file-utils (@faure / @mclasen)
* [x] libxdg-vfs (archived as inactive)
* [x] mpris-spec (#83)
* [x] pyxdg
* [x] shared-mime-info (@hadess / #27)
* [ ] xdg-specs
* [ ] autostart-spec (@faure)
* [ ] basedir-spec (@lennart)
* [ ] clipboard-extensions-spec (no maintainer)
* [ ] clipboards-spec (no maintainer)
* [ ] desktop-entry-spec (@otaylor / @faure / @smcv)
* [ ] help-system-spec (not on the site? @shaunm)
* [ ] idle-inhibit-spec (@hadess)
* [ ] menu-spec (@faure)
* [ ] mime-apps-spec (@faure)
* [ ] recent-file-spec (no maintainer)
* [ ] secret-service (@stefw)
* [ ] systemtray-spec (no maintainer)
* [ ] thumbnail-spec (no maintainer)
* [ ] trash-spec (@faure / @alexl)
* [ ] wm-spec (@otaylor?)
* [ ] xembed-spec (@otaylor)
* [ ] xsettings-spec (@otaylor)
* [x] xdg-user-dirs (@alexl)
* [x] xdg-utils
* [x] xdgmime (@hadess / #27)
Additionally, on the site we have:
* [ ] dbus introspection (generated from dbus source)
* [ ] freedesktop-platform-specs (@daniels / should just be deleted)
* [x] startup-notification-spec (separate repo)
I haven't looked into these at all yet to see who's responsible, or even necessarily where the specs have come from. But it would be good to clear that up as we go.