Re: [Mesa-dev] GitLab Migration: Users and Groups

As a quick update, I was wrong about what I said below. Masters cannot add/remove users, only Owners can. I've made everyone in the Masters list below an Owner. It also means that you can do all sorts of dangerous things like delete the entire mesa group. Please be careful. :-) --Jason On Wed

Re: [Mesa-dev] GitLab migration update

On Thu, 2018-06-07 at 08:25 +0100, Daniel Stone wrote: > The following dormant repos were _not_ migrated, but can be migrated > (perhaps to an archive/ section?) if they are still useful: > clover glw libwsbm linux-agp-compat r600_demo rbug-gui Eek. glw has a bugfix in it from me I don't even r

Re: [Mesa-dev] GitLab migration update

On 7 June 2018 at 10:43, Rob Clark wrote: > On Thu, Jun 7, 2018 at 3:25 AM, Daniel Stone wrote: >> Hi, >> >> On 2 June 2018 at 16:45, Jason Ekstrand wrote: >>> When the migration happens, there will be a very brief (less than 30 >>> minutes?) period during which no one will be able to push to ei

Re: [Mesa-dev] GitLab migration update

On Thu, Jun 7, 2018 at 3:25 AM, Daniel Stone wrote: > Hi, > > On 2 June 2018 at 16:45, Jason Ekstrand wrote: >> When the migration happens, there will be a very brief (less than 30 >> minutes?) period during which no one will be able to push to either repo. >> I'll fire off an e-mail as well as m

Re: [Mesa-dev] GitLab migration update

On Thu, Jun 7, 2018 at 9:25 AM, Daniel Stone wrote: > Hi, > > On 2 June 2018 at 16:45, Jason Ekstrand wrote: >> When the migration happens, there will be a very brief (less than 30 >> minutes?) period during which no one will be able to push to either repo. >> I'll fire off an e-mail as well as m

Re: [Mesa-dev] GitLab migration update

Hi, On 2 June 2018 at 16:45, Jason Ekstrand wrote: > When the migration happens, there will be a very brief (less than 30 > minutes?) period during which no one will be able to push to either repo. > I'll fire off an e-mail as well as messages in #dri-devel and #intel-3d > shortly before we actua

Re: [Mesa-dev] GitLab migration of Piglit

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

Re: [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 pigli

[Mesa-dev] GitLab migration of Piglit

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

Re: [Mesa-dev] GitLab migration update

Hi, On 2 June 2018 at 16:45, Jason Ekstrand wrote: > My current plan (if Daniel is amenable) is to due the migration late next > week. I'm tentatively thinking Thursday morning pacific but that may change > depending on Daniel's schedule. That works for me. > When the migration happens, there

[Mesa-dev] GitLab migration update

All, I just wanted to give a quick status update and planned timeline for the GitLab move. In case you missed the original e-mail (and lively discussion), you can find it here: https://lists.freedesktop.org/archives/mesa-dev/2018-May/195634.html If you have not yet set up your gitlab SSH keys,

Re: [Mesa-dev] GitLab Migration: Users and Groups

Jason Ekstrand writes: > All, > > As part of the move to GitLab, we have a few decisions to make regarding > users and groups. FWIW, I like your resolutions to both questions. signature.asc Description: PGP signature ___ mesa-dev mailing list mesa-de

Re: [Mesa-dev] GitLab Migration: Users and Groups

We're moving to not force pushing stable branches anymore. The plan now is that maintainers use some kind of "proposed" or "wip" branch that does have force pushes, but that the (for example) 18.1 branch is *not* force pushed, and anything that lands there but needs to be removed is reverted with a

Re: [Mesa-dev] GitLab Migration: Users and Groups

On Wed, May 30, 2018 at 5:14 PM, Stuart Young wrote: > On 31 May 2018 at 02:15, Jason Ekstrand wrote: > >> Gitlab divides users into three categories per-project: Guests, >> Developers, and Masters. In general, developers and masters will have push >> access. Masters have the ability to add de

Re: [Mesa-dev] GitLab Migration: Users and Groups

On 31 May 2018 at 02:15, Jason Ekstrand wrote: > Gitlab divides users into three categories per-project: Guests, > Developers, and Masters. In general, developers and masters will have push > access. Masters have the ability to add developers to the project. > Masters will also have the ability

Re: [Mesa-dev] GitLab Migration: Users and Groups

Hey, On 30 May 2018 at 21:40, Ilia Mirkin wrote: > Given that not everyone will be a master by default, it would be good > to also set out criteria for adding and removing masters. I'm not > proposing anything heavy -- perhaps by a majority vote of the existing > masters to either add or remove s

Re: [Mesa-dev] GitLab Migration: Users and Groups

On Wed, May 30, 2018 at 12:15 PM, Jason Ekstrand wrote: > All, > > As part of the move to GitLab, we have a few decisions to make regarding > users and groups. > > Question 1: Who should be masters? > > Gitlab divides users into three categories per-project: Guests, Developers, > and Masters. In

Re: [Mesa-dev] GitLab Migration: Users and Groups

On Wed, May 30, 2018 at 1:40 PM, Ilia Mirkin wrote: > On Wed, May 30, 2018 at 12:15 PM, Jason Ekstrand > wrote: > > All, > > > > As part of the move to GitLab, we have a few decisions to make regarding > > users and groups. > > > > Question 1: Who should be masters? > > > > Gitlab divides users

Re: [Mesa-dev] Gitlab migration

Jason Ekstrand writes: > Mesa developers, > > tl;dr. Please go to gitlab.freedesktop.org, create your account, and > upload your SSH keys. Instructions are the bottom of this e-mail. > > The freedesktop.org admins are trying to move as many projects and services > as possible over to gitlab and

[Mesa-dev] GitLab Migration: Users and Groups

All, As part of the move to GitLab, we have a few decisions to make regarding users and groups. Question 1: Who should be masters? Gitlab divides users into three categories per-project: Guests, Developers, and Masters. In general, developers and masters will have push access. Masters have the

Re: [Mesa-dev] Gitlab migration

Daniel Stone writes: > On 26 May 2018 at 00:47, Mark Janes wrote: > >> I am eager to make Intel CI results more visible. Can I push our >> artifacts to an fd.o directory, and have GitLab display them to users as >> if the build ran on fd.o? A typical build produces ~500MB of junit test >> outp

Re: [Mesa-dev] Gitlab migration

Hey, On 27 May 2018 at 16:35, Rob Clark wrote: > On Sun, May 27, 2018 at 10:47 AM, Jason Ekstrand wrote: >> Given the number of people who have said they still like the mailing list, >> that's probably a discussion for another email thread. > > It would be kinda clever if gitlab could automagica

Re: [Mesa-dev] Gitlab migration

Hi, On 26 May 2018 at 07:42, Marek Olšák wrote: > On Thu, May 24, 2018 at 6:46 AM, Daniel Stone wrote: >> cgit and anongit will not be orphaned: they remain as push mirrors so >> are updated simultaneously with GItLab pushes, as will the GitHub >> mirrors. Realistically, we can't deprecate anong

Re: [Mesa-dev] Gitlab migration

Hi Mark, On 26 May 2018 at 00:47, Mark Janes wrote: > Daniel Stone writes: >> We had a go at using Jenkins for some of this: Intel's been really >> quite successful at doing it internally, but our community efforts >> have been a miserable failure. After a few years I've concluded that >> it's n

Re: [Mesa-dev] Gitlab migration

On 27.05.2018 18:03, Marek Olšák wrote: On Sun, May 27, 2018 at 10:47 AM, Jason Ekstrand > wrote: On May 26, 2018 21:03:39 Marek Olšák mailto:mar...@gmail.com>> wrote: On Sat, May 26, 2018 at 11:13 AM, Jason Ekstrand mailto:ja...@jlekstrand.net>> wrote:

Re: [Mesa-dev] Gitlab migration

On Sun, May 27, 2018 at 9:03 AM, Marek Olšák wrote: > On Sun, May 27, 2018 at 10:47 AM, Jason Ekstrand > wrote: >> >> On May 26, 2018 21:03:39 Marek Olšák wrote: >>> >>> On Sat, May 26, 2018 at 11:13 AM, Jason Ekstrand >>> wrote: On May 25, 2018 23:43:33 Marek Olšák wrote: >

Re: [Mesa-dev] Gitlab migration

On Sun, May 27, 2018 at 10:47 AM, Jason Ekstrand wrote: > On May 26, 2018 21:03:39 Marek Olšák wrote: > >> On Sat, May 26, 2018 at 11:13 AM, Jason Ekstrand >> wrote: >> >>> On May 25, 2018 23:43:33 Marek Olšák wrote: >>> On Thu, May 24, 2018 at 6:46 AM, Daniel Stone wrote:

Re: [Mesa-dev] Gitlab migration

On Sun, May 27, 2018 at 10:47 AM, Jason Ekstrand wrote: > On May 26, 2018 21:03:39 Marek Olšák wrote: >> >> On Sat, May 26, 2018 at 11:13 AM, Jason Ekstrand >> wrote: >>> >>> On May 25, 2018 23:43:33 Marek Olšák wrote: On Thu, May 24, 2018 at 6:46 AM, Daniel Stone wrote: > >

Re: [Mesa-dev] Gitlab migration

On May 26, 2018 21:03:39 Marek Olšák wrote: On Sat, May 26, 2018 at 11:13 AM, Jason Ekstrand wrote: On May 25, 2018 23:43:33 Marek Olšák wrote: On Thu, May 24, 2018 at 6:46 AM, Daniel Stone wrote: Hi all, I'm going to attempt to interleave a bunch of replies here. On 23 May 2018 at 20:34,

Re: [Mesa-dev] Gitlab migration

On Sat, May 26, 2018 at 11:13 AM, Jason Ekstrand wrote: > On May 25, 2018 23:43:33 Marek Olšák wrote: > >> On Thu, May 24, 2018 at 6:46 AM, Daniel Stone >> wrote: >> >>> Hi all, >>> I'm going to attempt to interleave a bunch of replies here. >>> >>> On 23 May 2018 at 20:34, Jason Ekstrand wrot

Re: [Mesa-dev] Gitlab migration

On May 25, 2018 23:43:33 Marek Olšák wrote: On Thu, May 24, 2018 at 6:46 AM, Daniel Stone wrote: Hi all, I'm going to attempt to interleave a bunch of replies here. On 23 May 2018 at 20:34, Jason Ekstrand wrote: The freedesktop.org admins are trying to move as many projects and services as p

Re: [Mesa-dev] Gitlab migration

On Thu, May 24, 2018 at 6:46 AM, Daniel Stone wrote: > Hi all, > I'm going to attempt to interleave a bunch of replies here. > > On 23 May 2018 at 20:34, Jason Ekstrand wrote: > > The freedesktop.org admins are trying to move as many projects and > services > > as possible over to gitlab and som

Re: [Mesa-dev] Gitlab migration

On Fri, May 25, 2018 at 4:47 PM, Mark Janes wrote: > Daniel Stone writes: > > GitLab CI fixes all of these things. Pipelines are strongly and > > directly correlated with commits in repositories, though you can also > > trigger them manually or on a schedule. Permissions are that of the > > repo

Re: [Mesa-dev] Gitlab migration

Daniel Stone writes: > We had a go at using Jenkins for some of this: Intel's been really > quite successful at doing it internally, but our community efforts > have been a miserable failure. After a few years I've concluded that > it's not going to change - even with Jenkins 2.0. > > Firstly, Jen

Re: [Mesa-dev] Gitlab migration

On Thu, May 24, 2018 at 3:23 PM, Daniel Stone wrote: > Hi, > > On 24 May 2018 at 02:23, Jason Ekstrand wrote: >> On Wed, May 23, 2018 at 5:49 PM, Jordan Justen >> wrote: >>> Another project I'm involved with had a contingency that swore >>> github's "issues" were completely inadequate compared t

Re: [Mesa-dev] Gitlab migration

Hi, On 24 May 2018 at 02:23, Jason Ekstrand wrote: > On Wed, May 23, 2018 at 5:49 PM, Jordan Justen > wrote: >> Another project I'm involved with had a contingency that swore >> github's "issues" were completely inadequate compared to bugzilla, >> which is to say that I don't think there is cons

Re: [Mesa-dev] Gitlab migration

On Thu, May 24, 2018 at 3:23 AM, Jason Ekstrand wrote: > On Wed, May 23, 2018 at 5:49 PM, Jordan Justen > wrote: >> >> On 2018-05-23 15:16:58, wrote: >> > On Wed, May 23, 2018 at 5:48 PM, Jordan Justen >> > wrote: >> >> > And I'm not strongly tied to bugzilla vs gitlab's issue tracking. >> >> A

Re: [Mesa-dev] Gitlab migration

On Thu, May 24, 2018 at 8:18 AM, Kenneth Graunke wrote: > On Wednesday, May 23, 2018 1:58:14 PM PDT Nicolai Hähnle wrote: >> Hi Jason, >> >> On 23.05.2018 21:34, Jason Ekstrand wrote: >> > Mesa developers, >> > >> > tl;dr. Please go to gitlab.freedesktop.org >> > ,

Re: [Mesa-dev] Gitlab migration

Hi, On 24 May 2018 at 11:46, Daniel Stone wrote: > It _is_ possible to bend Jenkins to your will - Mark's excellent and > super-helpful work with Intel's CI is testament to that - and in some > environments it's fine, but after a few years of trying, I just don't > think it's suitable to run on f

Re: [Mesa-dev] Gitlab migration

Hi all, I'm going to attempt to interleave a bunch of replies here. On 23 May 2018 at 20:34, Jason Ekstrand wrote: > The freedesktop.org admins are trying to move as many projects and services > as possible over to gitlab and somehow I got hoodwinked into spear-heading > it for mesa. There are a

Re: [Mesa-dev] Gitlab migration

On 24.05.2018 08:46, Tapani Pälli wrote: * [Optional] Merge-request workflow.  With the rise of github, there are many developers out there who are used to the merge-request workflow and switching to that may lower the barrier to entry for new contributors. I admit that it's been a while sinc

Re: [Mesa-dev] Gitlab migration

On 05/24/2018 09:31 AM, Jason Ekstrand wrote: On May 23, 2018 23:18:08 Kenneth Graunke wrote: On Wednesday, May 23, 2018 1:58:14 PM PDT Nicolai Hähnle wrote: Hi Jason, On 23.05.2018 21:34, Jason Ekstrand wrote: Mesa developers, tl;dr.  Please go to gitlab.freedesktop.org

Re: [Mesa-dev] Gitlab migration

On May 23, 2018 23:18:08 Kenneth Graunke wrote: On Wednesday, May 23, 2018 1:58:14 PM PDT Nicolai Hähnle wrote: Hi Jason, On 23.05.2018 21:34, Jason Ekstrand wrote: Mesa developers, tl;dr. Please go to gitlab.freedesktop.org , create your account, and upload

Re: [Mesa-dev] Gitlab migration

On Wednesday, May 23, 2018 6:23:14 PM PDT Jason Ekstrand wrote: > Agreed. The gitlab/github issue system has some scaling problems. The > tagging system isn't as good as bugzilla's categorization. Also, the > ability to move bugs back and forth between mesa and kernel is a pretty > killer featur

Re: [Mesa-dev] Gitlab migration

On Wednesday, May 23, 2018 1:58:14 PM PDT Nicolai Hähnle wrote: > Hi Jason, > > On 23.05.2018 21:34, Jason Ekstrand wrote: > > Mesa developers, > > > > tl;dr. Please go to gitlab.freedesktop.org > > , create your account, and upload your > > SSH keys. Instructio

Re: [Mesa-dev] Gitlab migration

On Wed, May 23, 2018 at 5:49 PM, Jordan Justen wrote: > On 2018-05-23 15:16:58, wrote: > > On Wed, May 23, 2018 at 5:48 PM, Jordan Justen > > wrote: > > > Why can this only be done with gitlab? > > > > I'm not directly involved w/ decision to move things to gitlab, but that > said, > > > > http

Re: [Mesa-dev] Gitlab migration

On Wed, May 23, 2018 at 4:41 PM, Jordan Justen wrote: > On 2018-05-23 16:00:53, Jason Ekstrand wrote: > > On Wed, May 23, 2018 at 2:48 PM, Jordan Justen < > jordan.l.jus...@intel.com> > > wrote: > > > > > On 2018-05-23 12:34:11, Jason Ekstrand wrote: > > > > Mesa developers, > > > > > > > > tl;dr

Re: [Mesa-dev] Gitlab migration

On 2018-05-23 15:16:58, wrote: > On Wed, May 23, 2018 at 5:48 PM, Jordan Justen > wrote: > > Why can this only be done with gitlab? > > I'm not directly involved w/ decision to move things to gitlab, but that said, > > https://gitlab.freedesktop.org/freedesktop/freedesktop/wikis/home > > does

Re: [Mesa-dev] Gitlab migration

On 2018-05-23 16:00:53, Jason Ekstrand wrote: > On Wed, May 23, 2018 at 2:48 PM, Jordan Justen > wrote: > > > On 2018-05-23 12:34:11, Jason Ekstrand wrote: > > > Mesa developers, > > > > > > tl;dr. Please go to gitlab.freedesktop.org, create your account, and > > > upload your SSH keys. Instruc

Re: [Mesa-dev] Gitlab migration

On Wed, May 23, 2018 at 2:48 PM, Jordan Justen wrote: > On 2018-05-23 12:34:11, Jason Ekstrand wrote: > > Mesa developers, > > > > tl;dr. Please go to gitlab.freedesktop.org, create your account, and > > upload your SSH keys. Instructions are the bottom of this e-mail. > > > > The freedesktop.o

Re: [Mesa-dev] Gitlab migration

On Wed, May 23, 2018 at 5:48 PM, Jordan Justen wrote: > On 2018-05-23 12:34:11, Jason Ekstrand wrote: >> Mesa developers, >> >> tl;dr. Please go to gitlab.freedesktop.org, create your account, and >> upload your SSH keys. Instructions are the bottom of this e-mail. >> >> The freedesktop.org admi

Re: [Mesa-dev] Gitlab migration

On 2018-05-23 12:34:11, Jason Ekstrand wrote: > Mesa developers, > > tl;dr. Please go to gitlab.freedesktop.org, create your account, and > upload your SSH keys. Instructions are the bottom of this e-mail. > > The freedesktop.org admins are trying to move as many projects and services > as poss

Re: [Mesa-dev] Gitlab migration

Hi Jason, On 23.05.2018 21:34, Jason Ekstrand wrote: Mesa developers, tl;dr.  Please go to gitlab.freedesktop.org , create your account, and upload your SSH keys.  Instructions are the bottom of this e-mail. The freedesktop.org admins

Re: [Mesa-dev] Gitlab migration

On Wed, May 23, 2018 at 3:34 PM, Jason Ekstrand wrote: > > 1. Go to gitlab.freedesktop.org > 2. Click "Sign In / Register" in the upper left-hand corner > 3. You already have an account. Click "Forgot your password?", type in > your fd.o-associated e-mail, and click "Reset Password". Follow t

Re: [Mesa-dev] Gitlab migration

On Wednesday, May 23, 2018 12:34:11 PM PDT Jason Ekstrand wrote: > 1. Go to gitlab.freedesktop.org > 2. Click "Sign In / Register" in the upper left-hand corner > 3. You already have an account. Click "Forgot your password?", type > in your fd.o-associated e-mail, and click "Reset Password"

[Mesa-dev] Gitlab migration

Mesa developers, tl;dr. Please go to gitlab.freedesktop.org, create your account, and upload your SSH keys. Instructions are the bottom of this e-mail. The freedesktop.org admins are trying to move as many projects and services as possible over to gitlab and somehow I got hoodwinked into spear-