Skip to content

Revise community role descriptions to make them applicable across all Gardener subprojects #1049

Description

@BoHristova

What would you like to be added?

The Community Roles document needs to be revised so that the described roles are applicable across all Gardener subprojects, similarly to how the Kubernetes Community membership document is written.

Why is this needed?

At the moment, the Gardener public website includes two separate roles documents: Community Roles and Documentation Roles.

The Community Roles document focuses on code contributors, making it difficult for some sub-projects to use the roles as a basis. This is why the Documentation Roles document was created. More generic role descriptions would allow different subcommunities to adopt the same roles framework.

Metadata

Metadata

Assignees

Labels

area/ipceiIPCEI (Important Project of Common European Interest)kind/enhancementEnhancement, improvement, extension

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions