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
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
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
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
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
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
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
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
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
