At webpack-contribs inception there was a significant backlog of stale issues & pull requests.
Individually checking each issue for viability and waiting for response isn't an efficient solution to the problem.
Any issue / PR older than X number of days (60 / 90) gets a standard message ( open a new issue / pr if still valid in current version ) and then close & lock conversation. This is to be executed across the entire organization by the admin team in one shot without exception.
Create a keep me label for libs with designated maintainers to keep active older issues.
Any remaining issues will be triaged & properly labeled with severity / priority. This will be a tracked project for all repos in the org.
Any new issue will be handled as above.
Dependent on github label set
Dependent on webpack-contrib label util ( wip )
The only way to get ahead of the tech debt is the clean slate approach. Anything else is a time sink and given the state of things, has already been proven to not be viable
Being a member of JSF comes with a support obligation, as an organization we need to improve here. The options are spending time grinding through old issues that are probably not valid or putting that effort into current issues, seems to be a clean choice.
The current clutter is of no value to anyone. Both maintainers & users alike have to sift through it to find information and then figure out if it's even valid. The issue clutter is is equally detrimental to the admin teams ability to identify maintenance issues at an organization level.
The impact to the users in minimal(ish), create new issue & copy paste info or link to old issue to preserve valuable conversation around the issue.
Existing pull request already have to be closed & opened to trigger the CLA workflow, little to no impact here.
At
webpack-contribsinception there was a significant backlog of stale issues & pull requests. Individually checking each issue for viability and waiting for response isn't an efficient solution to the problem.current version) and then close &lock conversation. This is to be executed across the entire organization by the admin team in one shot without exception.keep melabel for libs with designated maintainers tokeepactive older issues.webpack-contriblabel util ( wip )The only way to get ahead of the tech debt is the clean slate approach. Anything else is a time sink and given the state of things, has already been proven to not be viable
Being a member of
JSFcomes with a support obligation, as an organization we need to improve here. The options are spending time grinding through old issues that are probably not valid or putting that effort into current issues, seems to be a clean choice.The current
clutteris of no value to anyone. Both maintainers & users alike have to sift through it to find information and then figure out if it's even valid. The issue clutter is is equally detrimental to the admin teams ability to identify maintenance issues at an organization level.The impact to the users in minimal(ish), create new issue & copy paste info or link to old issue to preserve valuable conversation around the issue.
Existing pull request already have to be closed & opened to trigger the CLA workflow, little to no impact here.