Skip to content

Triager log/How to become a triager #852

Description

@ezio-melotti

Currently we have:

As far as I know, there is no equivalent to the developer log for triagers, and there is a section about becoming triagers.

I think we should:

  • Add a triager log (possibly generated by the file proposed in Machine-parsable developers list #848)
  • Add a link to the "becoming a core dev" page to the "becoming triager" section, or move both to the same page
  • Improve the documentation on how to become a triager, including steps such as
    • making an official announcement on Discourse
    • adding the new triager to the triagers team on GitHub
    • reclaiming the GitHub mannequin
    • join the Discord server
  • Add links between the developer/triager logs and the "becoming *" section and the other way around

Activity

  1. ezio-melotti commented on May 4, 2022

    @ezio-melotti
    MemberAuthor

    Another thing that should be documented (if it isn't already), is the "Python Triage Membership" requests found at https://github.com/python/core-workflow/issues/new/choose (e.g. python/core-workflow#416).

    Currently it's not obvious if these issues are requesting the addition to someone to the GitHub Triage team, or if it's a request to consider them as potential candidate. It is also not entirely clear who should act on these issues and what should be done.

    As far as I understand:

    • the user has already been accepted as a triager by the team
    • the user must be invited to the python org (if he isn't already part of it)
    • the user must be invited to the python-triage team (this might automatically send an invite to join the org)
    • the mannequins for the user should be reclaimed after they join the org

    I suggest to:

    • document in the devguide that a request should be submitted to the core-workflow repo
    • add a link to this new devguide in the issue template
    • automatically ping people that can invite users/add them to teams/reclaim mannequins
      • by adding a specific label that people can subscribe to
      • by mentioning a team that can do this in the template
      • by automatically assigning the issue to someone (like me)
  2. ezio-melotti commented on May 5, 2022

    @ezio-melotti
    MemberAuthor

    I just found out that there is a docs-triagers team too. Maybe they should also be included.

    More info at https://discuss.python.org/t/documentation-triagers/13850

  3. added
    type-featureAdditions; New content or section needed
    and removed
    type-featureAdditions; New content or section needed
    on Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions