Skip to content
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

Close issues #774

Closed
Nebucatnetzer opened this issue Jun 9, 2019 · 8 comments
Closed

Close issues #774

Nebucatnetzer opened this issue Jun 9, 2019 · 8 comments

Comments

@Nebucatnetzer
Copy link

There are a lot of open issues which should get closed IMO.
Keeping them open gives the impression that the repo isn't properly maintained.
If it helps I can compile a list of all rhe issues that should get closed im my opinion.

@wiswedel
Copy link

If it helps I can compile a list of all rhe issues that should get closed im my opinion.

👍

@Nebucatnetzer
Copy link
Author

Okay I'll have a go. Might take a few days.

@J0WI
Copy link
Contributor

J0WI commented Nov 3, 2019

@Nebucatnetzer what is the current status of this?

@Nebucatnetzer
Copy link
Author

Nebucatnetzer commented Nov 4, 2019

#236 is over two years old and the author hasn't answered since over a year.
#200 as well very old.
#182 last comment over a year ago.
#178 last comment over a year ago.
#157 last comment over a year ago.
#130 last comment over two years ago.
#102 last comment over two years ago.

As a note to the issues listed here. I personally would close old stuff from time to time to keep things in order.
For certain issues it might be better to comment with something like "We'll put it on our feature list, no ETA however." and then close it.
Same goes for the stuff with the "Help wanted" label. Does it make sense to keep an issue around for two years?
IMO that just clogs things up.
Btw I'm not using the # in ordner not to necro post all the old issues.

@J0WI
Copy link
Contributor

J0WI commented Nov 4, 2019

Thanks for the list!

@paulfantom
Copy link

You can implement something like probot/stale to do this automatically and also remind that you have stale issues :)

@Nebucatnetzer
Copy link
Author

Nebucatnetzer commented Nov 7, 2019

Aye that would work as well but it is up to the devs to decide if they want to automate this.

@joshtrichards
Copy link
Member

Closing this. 😉 All the mentioned issues have been dealt with long ago. Any further needed "meta" discussions about repo management can go into new issue(s) or other channels.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants