[TW5] Request for help cleaning up TiddlyWiki5 GitHub issues

[Jeremy Ruston]

As we’ve discussed on some recent hangouts, there’s a substantial problem with the large number of open GitHub issues in the TiddlyWiki5 repository - there are currently 535 open tickets. It’s a problem because there’s too many to really use them effectively. The shift of policy that we’ve discussed is to revert to using the GitHub issues list more strictly as the “todo” list for the core developers. (Other discussions should be on our mailing lists — until we’ve got federation working sufficiently).

As part of that shift we need to start to close down issues that aren’t actionable. (Closing these issues doesn’t need to close down the discussion; the comment features like notifications work just as well for closed issues).

In the past, we’ve reviewed the issues in a hangout. Now there’s a lot more of them, just reviewing each is an incredibly sizeable task: looking at each one for 1 minute seconds will take nearly 9 hours.

So, in a spirit of spreading the workload a little, I’d be very grateful if anyone who has created issues in the past to just check that all their currently open issues are still relevant and meet the standards to be retained as a useful, actionable issue ticket:

* descriptions of bugs/crashes
* concrete proposals for enhancements

To find the open issues you have created, visit https://github.com/Jermolene/TiddlyWiki5/issues and find the box labelled “Filter”. Enter the string "is:open author:twMat” (substituting your GitHub handle for Mat’s). You should see a list of open issues created by you. For example:

https://github.com/Jermolene/TiddlyWiki5/issues?utf8=%E2%9C%93&q=is%3Aopen+author%3AtwMat

Even if we can just close the outdated issues I think we could clear the total considerably.

Let me know if you have any questions or comments.

Many thanks,

Jeremy.

[Mat]

...author:twMat

Hehe - I had to chuckle from the justified-but-less-than-subtle hint there ;-)

A question: How are ongoing discussions to be discerned from the 700+ really closed-as-in-finished issues? Most open issues - while not immediately actionable - are definitely not in the same status that the closed ones are. Maybe the (really) closed discussions can be transferred to somewhere else?

Thanks

<:-)

[Jed Carty]

Looking at my open issues they seem more like a wishlist than immediately actionable things. I have a possibly workable idea of how to use twederation to help move that sort of discussion off of github and into a pure tiddlywiki solution. I will try to put together something later but I have to run for now.

[Jeremy Ruston]

Hi Mat

A question: How are ongoing discussions to be discerned from the 700+ really closed-as-in-finished issues? Most open issues - while not immediately actionable - are definitely not in the same status that the closed ones are. Maybe the (really) closed discussions can be transferred to somewhere else?

It’s useful to keep the closed issues there because they show up in searches. In fact, users are encouraged to search closed issues to see if the issue they are raising has been raised before.

We could tag unactionable “wishlist” items before they are closed.

Best wishes

Jeremy.

[Mat]

We could tag unactionable “wishlist” items before they are closed.

Yes. Maybe it would be even easier to tag the really finished ones, as a final "stamp of finished" so to say?

BTW, I hope to get started with my own threads later in this coming week.

<:-)

[Mat]

On Saturday, February 6, 2016 at 11:58:55 AM UTC+1, Jed Carty wrote:

Looking at my open issues they seem more like a wishlist than immediately actionable things. I have a possibly workable idea of how to use twederation to help move that sort of discussion off of github and into a pure tiddlywiki solution. I will try to put together something later but I have to run for now.

That would IMO be the ideal solution. Have ideas "bake" in the form of an ongoing discussion that eventually crystallizes into something ready for an actionable Issue. It would also be perfect because discussion in TWederation can(?) let you include actual code. At least actual documentation, that can be collaboratively refined.

<:-)

[Jeremy Ruston]

Thanks to everyone who has helped, now we’re down to 519 tickets (one of which is new in any case). Please don’t stop, though! It would be great to get down below 500…

Best wishes

Jeremy

--
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+...@googlegroups.com.
To post to this group, send email to tiddl...@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/5f896c3f-5832-42ee-aee9-c72b630fb5db%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tobias Beer]

Hi Jeremy,

Haven't found the time to review

that possibly lengthy chunk

of my contributions to the backlog.

Hope to do that shortly.

Best wishes,

Tobias.