Hi,
I need changes of the former projects in Wikimedia Venezuela.
Wikimedia-Small-Projects-User-Group-TechCom > Re-activate
#acl_wikimedia-venezuela-internal_policy_admins > Change name to 'wikisp' instead of 'wikimedia venezuela'. Remove all members except me and change the edit policy, instead the actual to me.
I talked to the chapter and they agree on it. Will be used for WikiSP, although it is not yet recognized, is in process.
Regards.
Hi, I've updated Wikimedia-Small-Projects-User-Group-TechCom; could you please update its project description at https://phabricator.wikimedia.org/project/manage/2865/ ?
Will Wikimedia-Small-Projects-User-Group-TechCom have any work to plan for which the planning must not be public?
Done.
Will Wikimedia-Small-Projects-User-Group-TechCom have any work to plan for which the planning must not be public?
Some tech tasks will be blocked from the public view for legal or security reasons. If T273346 is solved, the space will be used for non-tech tasks too.
Wikimedia-Small-Projects-User-Group-TechCom is used as pseudo-acl for rWSP and the edit/join policy must not be changed.
Where does rWSP come from? How and why was this created in Diffusion, by who? What would be hosted in that repository?
Asking as this is the first time a repository was mentioned, and I'm not a big fan of using pseudo-ACLs...
T159660 -> Requested the git repo (formely known as rWMVE). Intended to host the mw configs of wmve
T159660#3114071 -> You converted Wikimedia-Venezuela to pseudo-ACL for that repo and later changed to wmve-tech (now Wikimedia-Small-Projects-User-Group-TechCom).
I intended to host the wmve server files, but upon resigning it was abandoned until I took it back to the aforementioned group. I takeover the Wikimedia-Small-Projects-User-Group-TechCom along with the repo and the code will be hosted now: 72a19cf188dd
T159660 requested rWMVE; this is now about rWSP; it's been confusing without previous context that things get renamed to unrelated other things instead of letting WMVE be WMVE.
I'm not sure if Wikimedia still offers hosting in Phabricator Diffusion as a canonical location (except for Tools due to Striker integration), and I'm not sure if https://www.mediawiki.org/wiki/Phabricator/Diffusion#Creating_and_managing_repositories is up-to-date. Adding Diffusion-Repository-Administrators.
Ah, thanks. All the unrelated renaming makes things harder to understand; and I am not sure that Wikimedia still support setups that were okay four years ago. :-/
I requested to the chapter the "takeover" and renaming of tech stuffs and acl. That seemed better to me than asking for new things. After all, I was still managing the repository and by default the associated project. The rest of Wikimedia-Venezuela stuffs are still intact.
I'm not sure if Wikimedia still offers hosting in Phabricator Diffusion as a canonical location (except for Tools due to Striker integration), and I'm not sure if https://www.mediawiki.org/wiki/Phabricator/Diffusion#Creating_and_managing_repositories is up-to-date. Adding Diffusion-Repository-Administrators.
Since I asked something for a wikimedia quasi-affiliate, I thought it was the right thing to do.
Ah, thanks. All the unrelated renaming makes things harder to understand; and I am not sure that Wikimedia still support setups that were okay four years ago. :-/
Actually the only missing thing was to activate the project and rename the other. Respect to the pseudo-acl, isn't to hide, just manage easily the repo as I stated. Is better if one group maintain the repo and not two individuals, add new members to the repo, for example.
@Aklapper any update about this? I'm not worried about request new space, project or acl if that speeds up this request.
About the policy change I take the guideline of https://m.mediawiki.org/wiki/Phabricator/Creating_and_renaming_projects#Project_policies > Restricting edit and join policy allows my succesors to take care of repo and/or project. If you don't like the pseudo-acl, I can change the edit and push policy of repo to me.
I'd prefer to have input if Wikimedia still supports creation of manual Diffusion repositories and then use a project as ACL though its name doesn't start with acl*, basically:
Ping - could Release-Engineering-Team please provide input whether we are fine with more repositories hosting code canonically in Phabricator Diffusion (as adding Diffusion-Repository-Administrators did not seem to trigger answers)?
Well, that delay is for the pseudo-acl in repo (my fault in let you know about the repo just delaying and nothing productive) right? What about the renaming and takeover of #acl_wikimedia-venezuela-internal_policy_admins ?
Ideally we would no longer host code canonically in Diffusion if it's possible to avoid.
FWIW the acl* naming convention is not necessary going forward. We can use the lock icon to indicate ACL projects. The acl prefix on the name is not particularly helpful.
@Aklapper what about this bug? We need #acl_wikimedia-venezuela-internal_policy_admins changed
I've