Hi, This is mostly off-topic, but it needs to be set right.
On 04.03.21 16:16, Liviu Ionescu wrote: > Not directly related, but similar in results, is the absurd strictness of > GitHub access rights, even for project leads and committers. > > For example, if I want to set the Embedded CDT description in GitHub, an > operation that usually takes less than a minute, I cannot do it myself, I > have to open a Bugzilla ticket and some authorised Foundation administrator > will do it for me. This used to be the case, mainly because GitHub only had read, write, or admin permissions. Admin permissions are powerful because one can potentially blow of their foot quite easily. In the meantime, the "maintain" permissions has been added by GitHub, which is now **the default permissions for every project lead**. The maintain permissions allows a few mundane tasks (like setting repo descriptions, etc.) to be handled, but there is certainly room for improvement (we can't do much more than request features on GitHub and wait for them to be implemented). Your example is not accurate since you are a project lead with admin permissions on all repos under github.com/eclipse-embed-cdt. We don't hand out admin permissions on a silver plate, but for reasonable requests, we can grant them temporarily or even permanently. > Completely inefficient, as many other Foundation procedures. :-( There is always room for improvement, but don't hate the player, hate the (legal) game! Regards, Fred -- Frederic Gurr Release Engineer | Eclipse Foundation Europe GmbH Berliner Allee 47, D-64295 Darmstadt Handelsregister: Darmstadt HRB 92821 Managing Directors: Gaël Blondelle, Mike Milinkovich _______________________________________________ cross-project-issues-dev mailing list cross-project-issues-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
