Contributing tools 2.1.0

[alexis-]

• [ ] Issues to test

  • [ ] Overlay ? https://attractiveapproach.blogspot.com/2013/05/how-can-i-make-transparent-window-in-wpf.html https://github.com/sourcechord/FluentWPF/blob/master/FluentWPF/AcrylicWindow.cs

  • [ ] Dialog

  • [ ] Opt-in

  • [ ] Filters

  • [ ] Project repo (SMA, PDF, LaTeX, ...)

  • [ ] Bugs, Enhancement

  • [ ] Show only issues with certain labels (e.g. needs-testing)

  • [ ] Bounty value

  • [ ] Testing process

  • [ ] If there is an issue to report, then it the process is clear: the user will write about the issue, ideally guided by an Issue template from GitHub

  • [ ] If there is no apparent bug, then what ? Should he post a message "OK for me ?". Keeping in mind that absence of evidence is not evidence of absence

• [ ] Read/Send GitHub issues from SMA
  • [ ] Screenshot upload
  • [ ] Record videos
  • [ ] Use GH templates
  • [ ] Defaults resources (e.g. icons ?)
  • [ ] Search by keyboard hotkey

SuperMemo.wiki - sma-dev [673076667358511124].zip

[alexis-]

@bjsi @nikedinikedi @dumbyme Additional thoughts ? Especially for the "Testing process" bullet point

[nikedinikedi]

If there is no apparent bug, then what ? Should he post a message "OK for me ?". Keeping in mind that absence of evidence is not evidence of absence.

This gives me some vague thought about some kind of "vote" system. Where people could give reports about functionality simply by one click. It gives an idea how "widespread" the bug is (i.e. is it simply about one persons settings or more general bug)

This could be implemented in the "issue filter" or "robot clipper" or "helping center" function (whatever you want to call it) as shown in the image