gitlab migration

[Michel Dänzer]

On 2018-06-08 08:08 PM, Adam Jackson wrote:
> I'd like us to start moving repos and bug tracking into gitlab.
> Hopefully everyone's aware that gitlab exists and why fdo projects are
> migrating to it. If not, the thread about Mesa's migration provides
> some useful background:
> 
> https://lists.x.org/archives/mesa-dev/2018-May/195634.html
> 
> This should be mostly mechanical, except for moving some of the older
> junk into the archive and deciding which drivers _not_ to move yet (I
> imagine intel has some of its processes hooked up to bz, for example).

As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating
these to GitLab for Git and patch review.

However, I'm not sure what to do about bugs/issues. My first thought was
to allow creating new issues in GitLab and disable creating new reports
in Bugzilla, but not to migrate existing reports from Bugzilla. However,
it still happens fairly often that a report is initially filed against
the Xorg drivers, even though it's actually an issue in the X server,
Mesa or the kernel (old habits die hard...). Therefore, I'm inclined to
stick to Bugzilla until at least the X server and Mesa have moved to
GitLab for issue tracking, to hopefully allow moving such misfiled issues.


Adding the amd-gfx list, in cases somebody there has concerns or other
feedback.


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer