Hi!
Please, change the rWMVE repository policies:
- Can push: #wikimedia-ve-tech
- Can edit: #wikimedia-ve-tech
But, we need this project before changing repository policies.
Many thanks in advance.
Hi!
Please, change the rWMVE repository policies:
But, we need this project before changing repository policies.
Many thanks in advance.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | Galahad | T166986 Migración de herramientas usadas por Wikimedia Venezuela | |||
| Resolved | Oscar | T167583 Migración de Trello | |||
| Resolved | Aklapper | T167584 Create several (sub)projects for Wikimedia Venezuela | |||
| Resolved | Luke081515 | T167585 Modify rWMVE |
@White-Master So you need a project called #Wikimedia-VE-tech and their members allowed to manage that project, right?
Also rWMVE is empy. Do you plan to mirror it from somewhere else or host it here?
Regards.
That's right.
And yes, actually rWMVE is empty. My plan is host our configurations soon.
Adding Phabricator because I can't create ACL projects. @Aklapper could you please assist here? Thanks.
Workflow:
acl*wikimedia-venezuela-internal_policy_admins exists - is the membership different than for S12?
Btw, it would make sense to change "can edit" to Custom Policy, allowing #wikimedia-ve-tech and repo-admins.
I can change it, but we would need a project first.
@Luke081515 But #Wikimedia-VE-tech requires an admin as it is requested to be a policy project, and project-creators such as me don't have permission to alter project policies. I could create it if I were sure that it could be changed later.
In order not to break naming scheme, Wikimedia-Venezuela-tech would be the proper name IMHO.
We requested "Wikimedia-VE" in first instance but was changed to Wikimedia-Venezuela (avoid confusion with VisualEditor).
So, it's okay #Wikimedia-Venezuela-Tech
I changed it: https://phabricator.wikimedia.org/source/wikimedia-ve-mw-config/manage/history/#6150
I did not removed repo admins and acl operations. I did not removed #acl*operations-team because @demon added it, so I was unsure if it is stil needed. I did not removed Diffusion-Repository-Administrators since this allows to do needed maintenance in case that it is needed. Both project groups are only accessible by trusted members, so I'd not say that there is an disadvantage in keeping these projects there.
In case that there are any issues, feel free to reopen.