Rights on Eclipse project organisations and repositories

Hi The Eclipse OpenSmartCLIDE project has some questions I could not answer to:

Is it planned that even the project leads have no rights to tweak settings in "our" organisation and "our" repositories?

For example:

• We cannot change the logo (probably not that important for now, but a good example)
• We cannot tweak the "Branch protection rules" settings for any of the opensmartclide repositories.
• We cannot change the visibility settings for packages that we built (see [here])(eclipsefdn/emo-team/emo#367 (comment 1027772)).
• ...probably many more...

cf. eclipsefdn/emo-team/emo#367 (comment 1027773)

Can you help us on that? Thx a lot

/cc: @sscholze366

mentioned in issue eclipsefdn/emo-team/emo#367 (closed)

The privileges available to the various roles are describe in the handbook:

https://www.eclipse.org/projects/handbook/#resources-github-access

We didn't put a pointer to the privileges table in the handbook. I'll add it.

https://docs.github.com/en/organizations/managing-access-to-your-organizations-repositories/repository-roles-for-an-organization

Ok thanks for clarification. That was not that easy to find out. Also, I was not aware that "Manage Branch Protection" requires Admin Level Access.

Anyhow, our biggest issue right now is the following:

• We cannot change the visibility settings for packages that we built (see also above).

How to handle this issue?

Hi @fgurr, Can you help us on this issue: "We cannot change the visibility settings for packages that we built (see also above)." Thx a lot

@mward, I talked today with @wbeaton. Wayne told me that our packages should not be private but public. It certainly happened during the migration from the Eclipse Research Labs to the Eclipse OpenSmarCLIDE organisation: https://github.com/orgs/eclipse-opensmartclide/packages We don't have the right to change their status. Can you fix it, please? Thx a lot

added IT-prioritylow IT-severitylow ~16280 team:releng labels

assigned to @fgurr

We cannot change the logo (probably not that important for now, but a good example)

Unfortunately we are limited by GitHub's permission model.

We cannot change the visibility settings for packages that we built (see also above).

The visibility of all existing packages have been set to public.

closed

Closed to early.

@sscholze366 If you provide a logo, I can add it to the org.

I think this issue can be closed for now, otherwise it will stay open quite long, because we have no logo yet for opensmartclide, only for our H2020 EC project SmartCLIDE.

Ok. No worries. Once you have a logo, please open a new ticket (or reopen this one).

reopened

closed

added Research label