search

alexames / DeltaBot

GNU General Public License v3.0
65 stars 18 forks source link

Cleaning up and Closing Issues #58

Closed projectdelphai closed 10 years ago

projectdelphai commented 10 years ago

So I'm /u/wmcscrooge from reddit making this issue because of the post by /u/Snorrlax about the amount of issues on this project. I've spent yesterday and today looking through all the issues and noticed that there are a lot of times where the issues are stale and don't need to be open anymore. The following is a list of all the issues and what I think should be done with them.

1 - Issue #1 should probably be closed. Not because it is done or necessarily because it is useless, but it is so far down the list that I doubt very few people are actually working on it. Regardless of whether you choose to keep it or not, the information should definitely be placed on the README at least so that people know about it coming in. 3 - Issue #3 as far as I can tell was referenced incorrectly slightly giving the impression that it was fixed which was wrong. It should stay open. 4 - This is a big issue that seems to have no work done on it. It should stay open and should be added to the README. 6 - All the work for this issue seems to have been fixed with Issue #50 which was not pulled and was supposed to be added in manually. It should work fine as long as someone updates the code to work with the current version. 18 - This issue can be closed, since it was fixed by Issue #56. 22 - This issue can be closed. I went through all the formatting problems and they have been fixed. 32 - This issue seems to have been eventually scrapped because of hardness to implement because of the way reddit is designed. In addition, a probably fix has already been submitted so this issue can be closed. 35 - This issue is really just asking about whether anyone is working on the issues. It isn't actually an issue as far as I can tell and should be closed. 38 - This issue can be closed because a pull request was submitted by chilee which solves this problem. 42 - This issue is more about actually developing and formatting and should be moved to the documentation so new developers can read it. It should be closed. 47 - This issue looks like it should stay open, even though it doesn't have any recent activity. Can someone say whether this is still an issue? 48 - This issue can be closed since Travis Cl has already been implemented. 50 - This issue should be closed since it needs to be manually implemented or at least updated. Someone should start anew using this and #6 as a base.

The above list basically says that the following issues should be closed:

  1. 1

  2. 6

  3. 18

  4. 22

  5. 32

  6. 35

  7. 38

  8. 42

  9. 48

  10. 50

After this, only 3 issues will be open. I know that this will seem rather radical, but I would strongly recommend that you just go through and close all the above-listed issues unless you know for a fact that it is still a problem. Pretty much all of the 10 issues have not seen any activity in the last couple weeks. If people complain or show that it is still a problem, then you can reopen them, but I think that right now, it is just cluttering up the issues page.

I'll probably come up with a pull request soon that updates the README so that it includes all the major issues for new developers and has the information recorded in the closed issues.

Hope it helps!

PixelOrange commented 10 years ago

All issues have either been closed or commented on. Issue #3 was closed and then re-opened under a fresh issue to avoid further confusion.

projectdelphai commented 10 years ago

Awesome! I'll close this issue so that it's one less issue to deal with.