new GitHub teams request for operational team #341

Topic

We in the operational team would like to have two teams, so we can use GitHub more efficiently.

Why Teach Lead Backlog?

Some alignment between teams is probably warranted.

prefix

"operational" is also quite confusing. To have transparent issue assignments and consistency to other OSS projects, we would rather prefix our teams with "infrastructure-". We already use an "infrastructure" label and not an "operational" label.

infrastructure-maintainer

We need an official "committer" team as the eclipse foundation calls it.
However "committer" is rather unknown in the OSS world. Such a group is typically called "maintainer".

So we would like to have a group "infrastructure-maintainer".
We'll use that group especially for official stuff like approving pull requests.

Permissions and Responsibilities

• As defined in https://www.eclipse.org/projects/handbook/#roles-cm and https://www.eclipse.org/projects/handbook/#contributing-committers
• With the scope of infrastructure and tooling, which will be defined via CODEOWNERS
• No changes beyond what we have today for committers. It's only about being able to address the infrastructure scope explicitly.

infrastructure-team

In addition we need a GitHub team which represents our entire team.
Since not all topics are addressed only at the maintainers.

Permissions and Responsibilities

• As defined in https://www.eclipse.org/projects/handbook/#contributing-contributors
• With the scope of infrastructure and tooling
• No changes beyond what we have today for contributors. It's only about being able to address the infrastructure scope explicitly.

Members

We would really love to maintain the members ourselves. So these groups can really serve as a living lookup of who is active in what role. Not an assigned role, but who is really living it.