Skip to content

Suggestion: Community contributor, SIG info, reviewers split #159

Description

@sptramer

During review of #158, it became clear that information about community, SIGs, and available reviewer/maintainer roles is duplicated or split in a hard-to-discover way across multiple files. This issue is for awareness of the problem to produce a full RFC if needed, or at least discussion within the project.

As a starting point, I would suggest the following be how the information is maintained and organized:

  • README.md - Should not just be an index of the SIGs/repos - should be a short summary of the project, who we are, etc.
  • CONTRIBUTING.md - The current community-membership.md page should be merged into CONTRIBUTING.md, excepting the role descriptions.
  • ROLES.md - An expanded description of community roles (currently maintained in the docs affected by Contrib update #158) including chairperson, TSC/TAC roles and how they are staffed, as well as links to any SIG-specific roles (such as sig-docs-community requiring a "Website reviewer" role)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions