[Mesa-dev] [Piglit] GitLab migration of Piglit

[Eric Engestrom]

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?

> 
> On Mon, Jun 4, 2018 at 3:29 PM, Eric Anholt <eric at anholt.net> wrote:
> 
> > Jason Ekstrand <jason at jlekstrand.net> writes:
> >
> > > 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.
> >
> > So far, having it be a separate group has just been a pain in getting
> > people to contribute to piglit, when we mistakenly forget to add mesa
> > devs to it.  I don't think we need it to be a separate committer group.
> >

> _______________________________________________
> Piglit mailing list
> Piglit at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/piglit