<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> </head> <body text="#000000" bgcolor="#FFFFFF"> On 9/25/19 11:05 AM, <a class="moz-txt-link-abbreviated" href="mailto:daniels@collabora.com">daniels@collabora.com</a> wrote: <blockquote type="cite" cite="mid:2e358062-1d8c-4f9b-9434-2c4ae6695f89@email.android.com"> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"> <div dir="auto">Sorry for mangled phone formatting, but go to <a class="moz-txt-link-freetext" href="https://gitlab.freedesktop.org">https://gitlab.freedesktop.org</a>, follow the + menu to create a new project, select 'import' and then GitHub.</div> <div class="gmail_extra"> <div class="gmail_quote">On 25 Sep 2019 5:56 pm, Kyle Brenneman <a class="moz-txt-link-rfc2396E" href="mailto:kbrenneman@nvidia.com"><kbrenneman@nvidia.com></a> wrote: <blockquote class="quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> On 9/24/19 11:40 PM, Matt Turner wrote: > On Wed, Sep 11, 2019 at 9:14 PM Kyle Brenneman <a class="moz-txt-link-rfc2396E" href="mailto:kbrenneman@nvidia.com"><kbrenneman@nvidia.com></a> wrote: >> On 9/9/19 12:07 PM, Adam Jackson wrote: >>> On Wed, 2019-09-04 at 14:27 -0600, Kyle Brenneman wrote: >>>> On 9/4/19 8:44 AM, Daniel Stone wrote: >>>>> Hi, >>>>> >>>>> On Wed, 4 Sep 2019 at 15:12, Chuck Atkins <a class="moz-txt-link-rfc2396E" href="mailto:chuck.atkins@kitware.com"><chuck.atkins@kitware.com></a> wrote: >>>>>> Can we use Gitlab's GitHub import feature? >>>>>> >>>>>> <a class="moz-txt-link-freetext" href="https://gitlab.freedesktop.org/help/user/project/import/github.md">https://gitlab.freedesktop.org/help/user/project/import/github.md</a> >>>>>> >>>>>> I haven't used it before but it looks like it will migrate everything, i.e. repo, issues, prs, etc. >>>>> Yeah, we definitely can. We can create a new namespace for GLVND and >>>>> import the project into there. >>>>> >>>>> Who else should I add to the group? >>>> I'm not very familiar with the administrative side of GitLab -- does >>>> adding to the group just control who can check in new commits? >>> It's fairly fine-grained, for details see: >>> >>> <a class="moz-txt-link-freetext" href="https://docs.gitlab.com/ee/user/permissions.html">https://docs.gitlab.com/ee/user/permissions.html</a> >>> >>> - ajax >>> >> In that case, in addition to myself and the other NVIDIA engineers, Adam >> Jackson would probably make sense to add for push/merge permission. Not >> sure who else. >> >> Is there anything that's needed from me to get the GitHub repo ready to >> import? >> >> -Kyle > Okay, everyone is in agreement. Great! > > Mesa 19.2.0 is going to be released tomorrow and has been prepared for > libglvnd finally having pkgconfig files after many years of waiting, > but there's no libglvnd release for distros to ship. Is there > something we're waiting on? > > Can we make a release, transition to FDO Gitlab, etc? Daniel says that > only someone with permissions on the GitHub repo (Kyle, I suppose) can > do the transition. > > Can we please make this happen tomorrow? I just updated the libglvnd package version to 1.2.0, and tagged it as a new release. As for migrating the repository, what do I need to do to do that? -Kyle </blockquote> </div> </div> </blockquote> Okay, I've imported the Github repository here: <a class="moz-txt-link-freetext" href="https://gitlab.freedesktop.org/glvnd/libglvnd">https://gitlab.freedesktop.org/glvnd/libglvnd</a> It looks like the code, bug reports, and pull requests all came in cleanly. The release tarballs didn't, though. I guess the next step is to figure out what to do with the Github repository. I've seen Github repos that are explicitly labeled as being a mirror of another repo, but I'll have to go figure out how to configure that. There's also some still-active discussions on the Github bug reports that we'll need to migrate over. -Kyle </body> </html>