-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better management of issues #6979
Comments
Absolutely. I think we are long overdue for this. I've struggled with what might be the right length of time to do this. My general mindset is that 90 days is enough, as in my work experience it seems like things that don't get done within a quarter tend not to get done at all, so I'll throw that out as a starting point for this discussion.
In the past, we've labeled these as "help wanted." Unfortunately, we haven't seem much movement on those tasks. I think they fall into the same category of issues that have been open for too long. Maybe we should have a timeout set on those issues as well? Or is there another way you're thinking of designating these issues?
Me too! The trouble we've had in the past with "beginner" issues is that team members have quickly addressed them (I think people just breeze through the issues list and think "oh, this is easy, I'll just do it right now."). I fully support having beginner issues and if we want to start doing that again, I think we also need a rule to say that team members may not address a beginner issue unless it has been open for longer than X amount of days (maybe 30?) to make sure they stay open long enough for people to find them. |
I think the I love having
This would be great! If we as a team are aware that this is a list we'd like to maintain I think we'll be able to find a number of issues we can make for newcomers to the project. |
I think the key thing for "help wanted" is to decide on a timeout period after which we just close them. If we can decide on that, then we can go back and close a lot of the old ones we have. |
Okay, here's what I'll propose to get the ball rolling:
@eslint/eslint-team thoughts? |
Marking as accepted because we have a number of thumbs on @nzakas's proposed details. I'm happy to make a PR to add this to our docs! |
@kaicataldo go for it |
I've been going through a lot of our inactive unaccepted issues and closing them/checking in. While doing so, I had some ideas that I wanted to discuss and see what others thought.
Things we're doing well
First off, I want to say that I actually think we do quite a good job of managing issues relative to the number that come in and the bandwidth we have as a team. Many other popular projects have many more open issues than we do.
As far as getting better at managing new issues, I think we've been moving in the right direction with some of our recent policy changes, including:
I think these policies will alleviate some of the challenges we've faced previously, as all new issues will have someone who is taking on the responsibility of implementation (whether it's a team member or a community member).
Challenges
The new policies for accepting issues don't really allow us to create issues for nice-to-haves unless someone is willing to take it on immediately. This, combined with the fact that we don't close old accepted issues means that a lot of
help wanted
issues are older ones that may or may not still be relevant.Possible Solutions
help wanted
andbeginner
labels, and I wonder if we could codify our usage of those labels to help the community contribute. For example, if we encounter an issue that we have decided (through consensus) is a nice-to-have that we support but is not crucial to the roadmap and is not championed by one of us, we can label the issue withhelp wanted
and encourage the community to check these issues out (on our site, social media, etc.). And again, they should probably be culled if they've been on the shelf for too long with no activity.beginner
issues with the beginner label - i.e. simple docs changes where it's very clear what needs to be done or an enhancement that adds an option to an existing rule. I know I've talked to a number of people who were interested in contributing but didn't quite know where to start, and I think these kinds of issues could be the final nudge that gets some of our community members to contribute.It seems to me like closing older accepted issues with no activity (say, after 6 months) and creating a list of
help wanted
issues - that we have discussed and reach consensus on but do not currently have a champion for and are intended at the time of acceptance to be open for the community to help contribute to - would allow us to ensure that all issues are relevant, manageable, and make it even easier for community members to contribute.Summary
To summarize, since I know this turned into a wall of text (apologies!):
The text was updated successfully, but these errors were encountered: