Michael MacTaggert is a software developer looking for work, host of a law review podcast called Amicus Lectio, and a moderator of Programming Discussions (invite.progdisc.club). Follow me on Twitter!
Seems unnecessary and potentially harmful in the context of keeping a record of the project. Sometimes it's better when people don't get everything they think they want out of a tool.
Abusive issues where the discussion goes into personal attack territory
Regarding security issues, I do not think this feature will be effective. There are bots which make use of Github API to look for credentials of AWS/Azure/Google Cloud, etc. People will simply create bots for scraping issues and saving them to archive.is or similar sites. Since the issue deletion involves manual intervention, the delete action will merely remove it from the project page and not necessarily from public record.
Spam and duplicate issues can already be closed. I am not sure if deleting them solves any problems.
It can be useful for the last category of issues but there is already an option for locking issues and moderating abusive comments.
And like any tool, there is always potential for misuse e.g delete genuine bugs without justification.
We will have to wait and watch how the community uses this feature.
Been using UNIX since the late 80s; Linux since the mid-90s; virtualization since the early 2000s and spent the past few years working in the cloud space.
Location
Alexandria, VA, USA
Education
B.S. Psychology from Pennsylvania State University
Bad because there are important issues that will be deleted for pure use of power by the maintainer(s)
That kind of abuse tends to be a self-limiting problem. Projects that are abusive tend to lose users and contributors β either by complete abandonment or forking.
Ok spam is annoying, but what difference do you see between a closed and a deleted issue ?
As the default filter is on open issues, I don't see both anyway.
Top comments (11)
Seems unnecessary and potentially harmful in the context of keeping a record of the project. Sometimes it's better when people don't get everything they think they want out of a tool.
What this feature aims to solve:
Regarding security issues, I do not think this feature will be effective. There are bots which make use of Github API to look for credentials of AWS/Azure/Google Cloud, etc. People will simply create bots for scraping issues and saving them to archive.is or similar sites. Since the issue deletion involves manual intervention, the delete action will merely remove it from the project page and not necessarily from public record.
Spam and duplicate issues can already be closed. I am not sure if deleting them solves any problems.
It can be useful for the last category of issues but there is already an option for locking issues and moderating abusive comments.
And like any tool, there is always potential for misuse e.g delete genuine bugs without justification.
We will have to wait and watch how the community uses this feature.
Bad because there are important issues that will be deleted for pure use of power by the maintainer(s)
Good cuz it will avoid a lot of spam
That kind of abuse tends to be a self-limiting problem. Projects that are abusive tend to lose users and contributors β either by complete abandonment or forking.
That's awesome! There is was really dumb issues.
Could you show an example of what you would call a "dumb issue" ?
Spam? Maybe.
So that's what you have been doing with my issues :p
Ok spam is annoying, but what difference do you see between a closed and a deleted issue ?
As the default filter is on open issues, I don't see both anyway.