Integrate Stale GitHub Plugin for openshot-qt repo #3770
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I give full credit to the GitLab-CE project for some of this wording. It was so artfully said, I adapted a version for OpenShot. Not sure how to give proper credit, so hopefully this works.
We have been using the stale plugin for a while on our libopenshot, and libopenshot-audio repos. This PR adds the same functionality to the openshot-qt repo. Essentially, I understand the arguments for and against the use of this GitHub plugin, but I feel that if an issues goes unnoticed, uncommented, and unassigned for 180 days, it is marked with the 'Stale' label, and 10 days later it is auto-closed. I think if an issue has gone unnoticed for that long, it should be closed (and either improved, reworded, verified, etc... before reopening). This also gives 10 days for someone to respond and keep the issue open.
OpenShot is only a few volunteers, but we have millions of users. In other words, we are understaffed and we tend to get a lot of unhelpful issues reported (bad tickets, unclear, no logs, no steps, etc...). We don't have the resources to go close each and every bad ticket. So, I hope this will really help the good quality tickets stand out more (and the bad tickets to disappear).