Skip to content

Duplicate paragraph #906

@gstjepan2

Description

@gstjepan2

https://github.com/rust-lang/rust-forge/blob/master/src/compiler/membership.md?plain=1#L103

## Not just code
It is worth emphasizing that becoming a member of the compiler team does not necessarily imply
writing PRs. There are a wide variety of tasks that need to be done to support the compiler and
which should make one eligible for membership. Such tasks would include organizing meetings,
participating in meetings, bisecting and triaging issues, writing documentation, and working on the 
rustc-dev-guide.

It is worth emphasizing that becoming a member of the compiler team does not necessarily imply
writing PRs. There are a wide variety of tasks that need to be done to support the compiler and
which should make one eligible for membership. Such tasks would include organizing meetings,
participating in meetings, bisecting and triaging issues, writing documentation, working on the
rustc-dev-guide. The most important criterion for elevation to compiler team member, in particular,
is **regular and consistent** participation. The most important criterion for elevation to
maintainer is **actively shaping the direction of the team or compiler**.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions