[Mesa-dev] GitLab migration of Piglit

[Dylan Baker]

As we discussed offline, I think it should be part of the mesa project. As I
understand your explanation: if piglit becomes a mesa group project then anyone
in the mesa group would automatically get piglit write access, but we can still
give specific people write access to the piglit repo (without mesa, libdrm, etc
access). That seems like the right solution to me.

Dylan

Quoting Jason Ekstrand (2018-06-04 08:48:53)
> 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: signature
URL: <https://lists.freedesktop.org/archives/mesa-dev/attachments/20180604/65fdff0d/attachment-0001.sig>