Clean up inactive issues

[leonorader]

There are a lot of open issues in this repo, but lots of there are just simply abandoned, not bugs or something. I suggest closing issues which have been inactive for a long time. These are easily found through sorting by least recently updated. I suggest closing issues which come up there which are older than ~2 months. Of course, also read through them a bit and use common sense.

This piece of text could be added as a comment:

I’m closing this issue because it has been inactive for a few months. This probably means that it is not reproducible, it has been fixed in a newer version, or the issuer did not reply.
Please reopen if you still encounter this issue with the latest stable version.
Thank you!

[danfickle]

Hi @leonorader,

I think that we could use that approach for some issues, but unfortunately, most of them are still valid issues.

Could you list some issues here that you propose closing? Then, if all interested parties agree, we can go ahead and close them.

Thanks again for your help.

[leonorader]

@danfickle , I checked open issues up to 200 and these are th ones I think could be closed (up to my understanding):

#28 + move to wiki
#46
#75
#71
#54
#76
#256
#50
#61
#73
#99
#100 - there a few issues asking for documentation - merge into one with subtasks?
#105
#110
#111
#112
#113
#117
#119
#122
#129
#130
#134
#147
#160
#166
#169
#173
#174
#178
#179 + documentation
#182
#183
#186

I also recommend to use some labels (as categories of issues):

• language, locale
• css
• documentation
• environment
• etc
• hacktoberfest?