An Administrator can edit the Diffusion application:
https://we.phorge.it/applications/view/PhabricatorDiffusionApplication/
And change "Can Create Repositories" from Administrators to Diffusion Repository Creators
This is basically a way to allow me to help in repository requests without being able to do much more (→ without the need for myself to be a Phorge Administrators).
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T15030 Support a Phorge Extensions ecosystem | ||
| Resolved | avivey | T15220 Community Project - arc-vscode | ||
| Wontfix | valerio.bozzolan | T15219 Diffusion Application: Allow creations from Diffusion Repository Creators |
Hi Administrators! Hoping to be useful I proposed this small change in the Diffusion app. So that the privileges now are not related to Admins, but to Diffusion Repository Creators (so, Admins, plus some people if you want)
I think we already have too many groups, and not enough demand for new repositories.
I fact, I don't remember any community-project request except for mine...
I see your point. Having said that reading L1 Phorge Vision Statement I see that we are trying to decrease the privileges of the Administrators so that they are not really Super Administrators. I like that. For that reason, and just because in Phorge it's easy to decentralize permissions (while in any other platform this is a pain), and also because the proposed group Diffusion Repository Creators is editable by both the members and by Administrators themselves and so there is no risk of creating a sub-group of gatekeepers, I think creating this group can be another step in the direction of decentralizing a bit the privileges.
Also, for me, I think it could be the only possible way to be trusted to do such specific action in the future, since I don't think that you will accept me as Administrator without knowing me better.
The point in L1 about "decrease the privileges of the Administrators" was about the product, not about this install. It means allowing more things to be diverted from "admin only" to customizable permissions.
I just don't see a need for this right now, and the cost of managing yet another permission group outweighs the cost of maybe needing to find an admin to create a repo.