Re: [eclipse.org-planning-council] Fwd: [cross-project-issues-dev] disab

[Mélanie Bats <melanie.bats@xxxxxxx>]

+1

--
Mélanie Bats
CTO
+33 7 87 69 42 84
+33 5 34 57 16 29
@melaniebats

*Obeo*
25 Boulevard Victor Hugo - Colomiers - France
http://www.obeo.fr

Le 26/06/2018 à 13:04, Frederic Gurr a écrit :
> Hi,
>
> I really like Jonah's idea (see below) to disable direct push access to
> master for org.eclipse.simrel.build.
>
> Simrel releng engineer and maybe a few others should keep push
> permissions to refs/heads/*.
>
> Here is how the permissions for callisto-dev group would be changed:
>
> # refs/for/refs/heads/*
>    - Abandon
>    - Create Reference
>    - Forge Author Identity (inherited from All-Projects permissions)
>    - Push 		  (inherited from All-Projects permissions)
>    - Push Merge Commit 	  (inherited from All-Projects permissions)
>    - Label Code-Review with range -2 to +2
>    - Label Verified with range -1 to +1
>    - Submit
>
> # refs/heads/*
>    - remove all permissions except:
>      - Label Code-Review with range -2 to +2
>      - Label Verified with range -1 to +1
>
> I appreciate any pointers to missing/wrong Gerrit permissions.
>
> Please vote for/against the proposal and/or give comments.
>
> Regards,
>
> Fred
>
>
>
> -------- Forwarded Message --------
> Subject: 	[cross-project-issues-dev] disable push to master for simrel
> Date: 	Mon, 25 Jun 2018 21:10:56 +0100
> From: 	Jonah Graham <jonah@xxxxxxxxxxxxxxxx>
> Reply-To: 	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
> To: 	Cross project issues <cross-project-issues-dev@xxxxxxxxxxx>
>
>
>
> Hi folks,
>
> Every release cycle there seems to be 1 or 2 (accidental) commits direct
> to master bypassing gerrit & the validation step for the simrel. AFAIK
> it is possible to disable direct push
> <https://gerrit.wikimedia.org/r/Documentation/access-control.html#category_push>
> in gerrit. Can this be done for the simrel?
>
> Jonah
>
> ~~~
> Jonah Graham
> Kichwa Coders Ltd.
> www.kichwacoders.com <http://www.kichwacoders.com>
>
>
>
>
> _______________________________________________
> eclipse.org-planning-council mailing list
> eclipse.org-planning-council@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/eclipse.org-planning-council
>
> IMPORTANT: Membership in this list is generated by processes internal to the Eclipse Foundation.  To be permanently removed from this list, you must contact emo@xxxxxxxxxxx to request removal.