Migrate DRM repositories to gitlab
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 ...
-
Project contacts filled by by requestor -
CoC section filled by requestor -
Git repo information filled by requestor (or N/A) -
Bugzilla information filled by requestor (or N/A) -
Mailman information filled by requestor (or N/A) -
Web hosting information filled by requestor (or N/A) -
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
-
Our projects agree to the Code of Conduct -
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.
-
New project: gitlab.fd.o/drm/maintainer-tools
, will be filled with the maintainer-tools branch fromcgit.fd.o/drm/drm-tip
, but reduced committer/owner list.-
Update logic in dim to switch to the new maintainer-tools branch -
Need to disable the intel-gfx-ci job to build maintainer-tools docs <- @ivyl -
Need a web redirect from dri.fd.o/docs/dim
todrm.pages.fd.o/maintainer-tools
-
-
Migrate: cgit.fd.o/drm/igt-gpu-tools
->gitlab.fd.o/drm/igt-gpu-tools
with same group.-
RFC discussion on igt-dev@lists.fd.o
-
Migrate all the accounts in the igt group -
After one week to let everyone activate their accounts: Migrate the actual repo -
Make @ivyl and @adrinael maintainers -
Delete the igt gitlab group at https://gitlab.freedesktop.org/igt
-
-
Move?: cgit.fd.o/drm_hwcomposer
->gitlab.fd.o/drm-hwcomposer/drm-hwcomposer
-
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.
-
Prepare maintainer-tools to allow auto-migration of existing setups -
Migrate: cgit.fd.o/drm/drm
->gitlab.fd.o/drm/kernel
-
Create the DRM Group -
Add all maintainers to the Group -
Create the DRM Repository -
Push the current branches in the cgit.fd.o/drm/drm
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-* and topic/* tags -
Remove the old repo after a while
-
-
Migrate: cgit.fd.o/drm/drm-tip
->gitlab.fd.o/drm/tip
-
Create the new repo -
Give access to the repo to the following groups: -
intel -
misc -
xe
-
-
Prefill the repo with the old repo content -
Mark the cgit repo read-only -
Update rerere
nightly.conf -
Update documentation -
Setup the git hook to prevent someone from pushing without dim -
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
-
Create the drm-misc Group -
Add all members of the drm-misc ldap group to the Gitlab group -
Make sure all drm-misc maintainers are setup as owners -
Create the drm-misc Repository -
Mark the cgit repo read-only -
Push the current branches in the cgit.fd.o/drm/misc/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-misc-* and topic/* tags -
Remove the old repo after a while
-
-
Migrate: cgit.fd.o/drm/drm-intel
->gitlab.fd.o/drm/i915/kernel
-
Create drm/i915
group -
Add all members of the drm-intel ldap group to the Gitlab group -
Make sure all drm-intel maintainers are setup as owners -
Find an acceptable way to store the issue templates -
Move drm/intel
repo todrm/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 todrm/?/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
-
drm/intel
-
drm/misc/kernel
-
drm/msm
-
drm/nouveau
-
drm/tegra
-
drm/tip
-
drm/xe/kernel
-
-
Delete cgit.fd.o/drm/drm-xe -
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/
-
maintainer-tools docs: https://dri.freedesktop.org/docs/dim/