Re: [Piglit] [Mesa-dev] GitLab migration of Piglit
Given the discussion below, I think we'll make piglit a sub-project of mesa. Those who need commit access to piglit but not mesa can be added directly to the piglit project. Hi list. Since piglit was also moved to the gitlab, same with mesa, our team is interested in process workflow for contributing to it. Before (again, same with mesa) we created mailing threads and after reviewing test was pushed to master by somebody with access. Now mesa got a new possibility for reviewing - merge requests, which doesn't exist in piglit. Also, according to Jason's conclusion, anybody can request commit access to piglit. But in this case how the review process will be done? Thank you in advance. On 6/7/18 10:18 AM, Daniel Stone wrote: Hi Emil, On 5 June 2018 at 18:21, Emil Velikov wrote: On 5 June 2018 at 18:02, Daniel Stone wrote: drm-gralloc.git Empty - please nuke, alongside bugzilla & other infra. Done. drm.git Out of curiosity - this and others (say igt) projects are accessible as mesa/$foo and drm/$foo. I'd image the same approach will be adopted in gitlab? Unfortunately not, it provides a single canonical URL rather than aliasing. But both old anongit URLs will continue to work. llvm.git Empty - nuke? Done. mesa-test.git Plain copy/paste just like xserver-test. There were no extra branches/patches wrt the usual repos. Nuke? Done. libwsbm.git linux-agp-compat.git vmwgfx.git Might want to check with the VMware people about these. I'm suspecting that the developers are not keeping a close eye on mesa-dev@ I'm going to follow up with them separately about vmwgfx.git. Cheers, Daniel ___ mesa-dev mailing list mesa-...@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ Piglit mailing list Piglit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/piglit
Re: [Piglit] [Mesa-dev] GitLab migration of Piglit
Hi Dan, Sharing a couple of small ideas. On 5 June 2018 at 18:02, Daniel Stone wrote: >>> drm-gralloc.git Empty - please nuke, alongside bugzilla & other infra. >>> drm.git Out of curiosity - this and others (say igt) projects are accessible as mesa/$foo and drm/$foo. I'd image the same approach will be adopted in gitlab? >>> llvm.git Empty - nuke? >>> mesa-test.git Plain copy/paste just like xserver-test. There were no extra branches/patches wrt the usual repos. Nuke? >>> libwsbm.git >>> linux-agp-compat.git >>> vmwgfx.git Might want to check with the VMware people about these. I'm suspecting that the developers are not keeping a close eye on mesa-dev@ HTH Emil ___ Piglit mailing list Piglit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/piglit
Re: [Piglit] [Mesa-dev] GitLab migration of Piglit
On Tuesday, 2018-06-05 17:52:17 +0100, Daniel Stone wrote: > Hi Eric, > > On 5 June 2018 at 17:49, Eric Engestrom wrote: > > On Tuesday, 2018-06-05 09:11:58 -0700, Jason Ekstrand wrote: > >> Given the discussion below, I think we'll make piglit a sub-project of > >> mesa. Those who need commit access to piglit but not mesa can be added > >> directly to the piglit project. > >> > >> Unless someone objects strongly, I'll plan to migrate piglit on Thursday > >> along with all the other mesa repos. > > > > "all the other mesa repos" > > -> could we get a list? :) > > > > I assume that's now mesa, libdrm, piglit, shader-db, crucible, kmscube, > > mesa-demos; what about igt? Anything else? > > We currently have under /git/mesa: > clover.git > crucible.git > demos.git > drm-gralloc.git > drm.git > glu.git > glut.git > glw.git > kmscube.git > libwsbm.git > linux-agp-compat.git > llvm.git > mesa-test.git > mesa.git > r600_demo.git > rbug-gui > shader-db.git > tasks.git > vkpipeline-db.git > vmwgfx.git This might just be my outsider impression, but aren't most of those dead/no longer maintained? > > Of those, kmscube and crucible have already been migrated. > > Cheers, > Daniel ___ Piglit mailing list Piglit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/piglit
Re: [Piglit] [Mesa-dev] GitLab migration of Piglit
I would say it's a sub-project of Mesa. Marek On Mon, Jun 4, 2018 at 11:48 AM, Jason Ekstrand wrote: > All, > > Sorry for the mess of GitLab e-mails but there are a lot of questions to > ask as this process moves forward. Today, we're discussing piglit. I've > included both the mesa and piglit list in the hopes that people will > actually see this e-mail. > > Honestly, I expect the migration of piglit to have much less impact on > most people's daily lives than moving the mesa repo. > > The biggest question I have is whether we actually want to continue to > have a separate "piglit" group. With GitLab, we can already give someone > developer access to piglit without giving them developer access to mesa. > Mostly, this is a question of whether we consider piglit to be it's own > project on freedesktop or a sub-project of mesa. I don't know the answer > to that question. > > Thoughts? > > --Jason Ekstrand > > ___ > mesa-dev mailing list > mesa-...@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev > > ___ Piglit mailing list Piglit@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/piglit
