Package-maintenance: Document the current 'top 10' express' issues

[Eomm]

@Eomm, ideally we should document the current 'top 10' in an issue (either here or in the express repo) and have at least a pointer from this repo so that we can actively track what we should encouraging people to help out with.

_Originally posted by @mhdawson in https://github.com/nodejs/package-maintenance/pull/230#issuecomment-512923710_

Reference https://github.com/nodejs/package-maintenance/pull/230

[mhdawson]

@wesleytodd FYI, once you have the list can you post a link here for the team as an FYI

[dougwilson]

Can a top ten item from Express be to help triage new incoming issues? Or can it only be existing, open issues? What about help monitoring our chat rooms and helping answer questions or other similar things?

[mhdawson]

@dougwilson when I talked with @wesleytodd we had talked about how to identify issues that the team wanted help to triage/answer questions. The key thing we talked about was how to make people comfortable in doing that even if they don't have the level of expertise that the existing Express team has. The hesitation being that they might get it wrong. Some kind of signal from the Express team that for these issues "trying" to help is appreciated even if you might not be an expert would probably help.

After the discussion my understanding of what the ask from the Express team was that it would most likely be along the lines of:

1) Help to triage/answering questions
2) top ten list as identified
3) help in moving forward key objectives.

Having "help with triage" in the top 10 list as well might be good to reinforce that aspect but would be good to have some other concrete issues people could work on.

In terms of getting some additional help on the triage side next step might be to figure out how to make people comfortable with jumping in even if they don't feel they have as high a level of expertise as they'd like.

[wesleytodd]

I have some specific ideas for how this can work which I can go over in our TC meeting. Mainly I think we can use the existing issue tags and a small bit of automation to look at all the repos and assemble a list.

1. Help to triage/answering questions
2. top ten list as identified
3. help in moving forward key objectives.

For initial triage, I thought we could have a list of most recent issues opened across all the repos, and then also use the discuss and question tags to direct people to where they can help with low knowledge/effort.

For the "top 10 issues", that is really what this issue is about identifying. The top ~10 things express needs today. Might be tests or documentation or even just a always number 1 "help with triage". These are the second tier of participation. It might take some context to help, but hopefully not much. This list could be automated a bit, and I have an initial one I will post before the TC meeting.

The last category of contribution would be major contributions, maybe best for people on track to join the TC or champion major parts of the Express ecosystem.

[wesleytodd]

I started getting the tagging going: https://github.com/expressjs/express/pulls?q=is%3Apr+is%3Aopen+label%3A%22Top+Priority%22

More to come soon!

[wesleytodd]

So this is still a WIP, but I just pushed some changes which make this mostly usable.

https://expressjs.github.io/statusboard

The issues lists are made from actual tagged issues. I am having trouble with what I think is GitHub Actions timing out the index job, but most of the work on this is functional. Once I get the build issues worked out I will merge and it will attempt to re-index every 2 hours.

My hope for this project is that it helps communities similar to Express to manage work being done across many repos. I have talked a little with Jory from the OpenJS Foundation as a place to centralize the meeting tagged events, but I think it might also be a good use for this group. If we wanted to create a page for the projects we are working with, and get them to use consistent tagging, we can send volunteers to it as a starting place.

Obviously this needs a lot more work, so any contributions or input is welcome!