Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement developer roles on GitHub #67

Open
jh-RLI opened this issue Jul 6, 2023 · 2 comments
Open

Implement developer roles on GitHub #67

jh-RLI opened this issue Jul 6, 2023 · 2 comments
Assignees

Comments

@jh-RLI
Copy link
Contributor

jh-RLI commented Jul 6, 2023

Currently, we utilize the team @OpenEnergyPlatform/oep-developer to grant access permissions for software development. To enable more granular permission control, I propose restructuring the software development-related teams.

I recommend creating a parent team that serves as a grouping entity for all available software development teams. This parent team would not have any permissions assigned directly to it but would provide a consolidated view of all software development teams.

The teams should then be added to each repository and be granted the recommended permission.

See list of all teams and recomended permission.

The new parent team and child teams
https://github.com/orgs/OpenEnergyPlatform/teams/oef-software-developer/teams

@jh-RLI
Copy link
Contributor Author

jh-RLI commented Jul 6, 2023

Added all teams but oep-community-manager and oep-tester as they already exists and should be carefully migrated. They could also stay as they are.

jh-RLI added a commit that referenced this issue Jul 6, 2023
@Ludee
Copy link
Member

Ludee commented Jul 11, 2023

The existing teams should be integrated and harmonised with the new set.
How to deal with the OEO roles?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants