Revive the Triage Team

topic from agenda overflow from meeting today. to someone with the requisite permissions: please add the priority label so the bot picks it up for the next meeting

This is something I want to talk about for sure.

I am marginally involved in managing Triagers, I have stopped adding people bc I just don't feel I/we are equipped to give them a good experience rn.

But we should def get to that place ASAP

@wesleytodd

@wesleytodd I think it needs the top priority label for the bot (?)

@ctcpip

Thanks for picking it up, @ctcpip! I was just about to create an issue.

Okay, here are my two cents on the topic:

The current definition of the role is somewhat defined (see) and the steps to become a triage member here.

From what I see, this is a great role to get involved in the project, and I love this idea. However, currently, the situation is not very good in terms of triage membership experience. Also, in many cases, the implication is very low, and the retention is also low. In my opinion, this is because the support and role definition are not yet there.

I think that triage members can easily become collaborators and make meaningful contributions (I started as triage myself in this project), but we need to provide good mentorship.

Here are some ideas to change the dynamics:

Define a Captain to become the mentor of the group (I volunteer myself if needed) so that person can delegate tasks and spot easy contributions in the project to the team members so they can learn and add value from a safe environment.
Change the nomination process by getting nominated for the role rather than self-nomination. Anyone in the org can nominate new triage team members. The idea is that people who start helping with moderation and replying to issues or commenting/reviewing PRs can get nominated.
Approve and onboard the cases that have positive feedback from org members like this and this.
Close all pending self-nominations and respond to the issues with the new process in place here.
Purge the team members that are not active; currently, there are 37 members (see), most of them inactive for a long time.
Improve the definitions of what is inactive and how to review it programmatically, so we can auto-purge.

Overall, let's empower this team to help us manage the huge amount of issues and PRs across the long list of repositories that we have and to build the next generation of collaborators 🥳

I swapped to two labels for the bot. The Working session uses top priority and the TC meeting uses tc agenda. Not sure if folks like that, but feels alright to me.

Define a Captain to become the mentor of the group (I volunteer myself if needed)

Love this!!

Change the nomination process by getting nominated for the role rather than self-nomination.

So the recommended process would be to help out in issues first then be nominated? And so we need docs telling people to just start helping? I like it, but just making sure I am clear.

And yeah I am all in support of the rest of your suggestions I think! This is great, really glad to see this happening!

So the recommended process would be to help out in issues first then be nominated? And so we need docs telling people to just start helping? I like it, but just making sure I am clear.

Yes!

And yeah I am all in support of the rest of your suggestions I think! This is great, really glad to see this happening!

Cool! Let's close the details on Monday as we have the TC meeting :)

This was discussed on the last TC meeting, and the plan is approved. recording (relevant from 11:30) 🥳

Next steps:

Resolve: Nominate CBID2 to the Triage Team express#5463
Resolve: add mertcanaltin as a triager express#5487
Change the nomination process by getting nominated for the role rather than self-nomination: docs: update triage nomination policy express#5600
Update captain initiatives: docs: add UlisesGascon as triage initiative captain express#5605
Close all pending self-nominations and respond to the issues with the new process in place here.
Purge the team members that are not active (1w confirmation). See, next update on April 22nd
Improve the definitions of what is inactive and how to review it programmatically, so we can auto-purge.
Update repositories to grant access to the triage team

@0ss

Hi friend! You are reading this message because you are currently a triage team member for our organizations (expressjs, pillarjs, and jshttp). Currently, we are reorganizing the team, and we want to confirm if you are interested in participating in this new phase (details).

If you want to remain active in this role and participate in the new initiative, please reply to this thread in GitHub, so we can keep your access and send you the additional information 👍

Current team members that require confirmation (marked means confirmed) before Monday 22nd:

Note: this list does not include new additions (from today), Captains or TC members.

docs: update triage nomination policy

@UlisesGascon

Hello @UlisesGascon,
I confirm, and if possible could you please add me to the other teams too, I can participate by code contribution/maintenance too.

@UlisesGascon

@UlisesGascon Yes, I've been active and will be continuing.

@UlisesGascon

@UlisesGascon Yes, I am eager to remain active in this role and participate in the new initiative. Thanks!

@dougwilson

Hi friend! You are reading this message because you are currently a triage team member for our ...

TLDR; I have changed roles and this project is not in my priority list anymore, so pls remove my name.

I had conflicts with @dougwilson (for example #100 (comment)) in the past which neither of us took steps to resolve, and I stopped being active.

great to see the project reviving again with lot of new faces and new initiatives; one of my dream is to see express 5 released and used.

@UlisesGascon

@UlisesGascon I would like to participate in this new phase.

@UlisesGascon

@UlisesGascon This is exciting. I learnt a lot in my first stint and found the community very supportive and kind. I would like to be included and become active again.

@UlisesGascon

@UlisesGascon i know i have been inactive for a while, but i love to be included and become active with contributions again

Hi, I can't invest time at this stage, thank you all 🤝

Hi friend! You are reading this message because you are currently a triage team member for our organizations (expressjs, pillarjs, and jshttp). Currently, we are reorganizing the team, and we want to confirm if you are interested in participating in this new phase (details).

If you want to remain active in this role and participate in the new initiative, please reply to this thread in GitHub, so we can keep your access and send you the additional information 👍

Current team members that require confirmation (marked means confirmed) before Monday 22nd:

[..redacted...]

Note: this list does not include new additions (from today), Captains or TC members.

Hi, I would love to participate in this new initiative!

While I'd love to be involved, sadly I've not got the bandwidth - I assume the offer will remain though for future so will let folks know if I get the bandwidth in future :)

@UlisesGascon

@UlisesGascon I realize I've been away for some time, but I'd love to get involved and start contributing again.

Thanks for all the responses! ❤️

I just updated the team to reflect the correct members based on the responses, please direct ping me in case of any issue.

I made all the changes needed in the repos, documentation, etc.. so I close this issue.

Next steps for the @expressjs/triagers

Follow up with our calendar events and join our Slack. details
Please join the channels #express and #express-triage-team

Navigation Menu

Repository navigation

Revive the Triage Team #227

Next steps:

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Revive the Triage Team #227

Description

Activity

jonchurch commented on Apr 10, 2024

ctcpip commented on Apr 10, 2024

UlisesGascon commented on Apr 10, 2024

wesleytodd commented on Apr 11, 2024

UlisesGascon commented on Apr 11, 2024

UlisesGascon commented on Apr 15, 2024

UlisesGascon commented on Apr 15, 2024

Next steps:

UlisesGascon commented on Apr 15, 2024

3imed-jaberi commented on Apr 15, 2024

aravindvnair99 commented on Apr 15, 2024

dakshkhetan commented on Apr 15, 2024

gireeshpunathil commented on Apr 16, 2024

lucasraziel commented on Apr 16, 2024

Sushmeet commented on Apr 16, 2024

enyoghasim commented on Apr 16, 2024

rodion-arr commented on Apr 16, 2024

ejcheng commented on Apr 16, 2024

G-Rath commented on Apr 16, 2024

0ss commented on Apr 19, 2024

UlisesGascon commented on Apr 22, 2024

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions