I been thinking more about this. I have also been looking at what PMario has been doing flagging things for possible "closure". *Good work, but how does it get actioned?*
I'm guessing there are reasons that GitHub issues opened in 2013 are still open--i.e. they have some potential. Maybe part of the barrier to closure is that its either "closed" OR "open" ? *There is no in-built in-between state.* How would it look with a third state? Like: "still interesting, but way old" ... So it would be "closed" but be flagged "potential", or something like that. I think bimlas' main idea that having several hundred old issues IS off putting to potential new developers is very true. And that reducing the "live" issue numbers is a good idea--plus some procedure to keep flagged closed issues of some possible potential. Hope this is clear! Best wishes Josiah -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/a59bd8a6-2eb4-4194-9248-bae503d8f13c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
