I really don't like the idea to have the information spread on different mediums, that usually end up with discrepancies and an overhead of work. I like the flexibility of the public spreadsheet, but:R-Tape wrote: ↑Fri May 24, 2019 8:57 amAs the main person currently doing corrections at the moment, what do you prefer @druellan ? Would it be useful to have a volunteer (perhaps @StooB ?) to keep on top of a finalised corrections spreadsheet, that is basically a list of ZXDB ID and a concise explanation of the correction needed? (Or would you rather be left alone to get on with it?!)
A spreadsheet is really not a good bug reporting platform at all, it makes the information difficult to post, edit and read. Not everyone has a Google account, that means to leave everything open and editable, and that's kind of concerning, not because someone is going to sabotage or post nonsense (can happen), but it is easy delete or alter the information by mistake if you are just looking.
The sheet works best as an index for all the bugs reported and solved (or not) on the forum. I'm already doing that myself, just to keep track on everything I'm looking at, perhaps is not a big deal to open a public spreadsheet and add everything there.
Could be nice to use such a sheet as a triage process for the reports, but makes no sense of doing that if I'm the only one focusing on this area.
Besides that, I think we still need to inform something to the person that posted the report, without the hassle of looking on a spreadsheet, this also helps me to quickly catch posts I missed, something that can happen when a discussion fires up. If we can't find a plugin or a hack to "mark" a post, the best way to do it is just edit the post and add some kind of tag, like [IN PROGRESS] or [DONE]. Those tags can also be color PNGs and added to the forum as Smilies.
But for my own requirements, the "like" approach works, so we can start with a public sheet of reports solved or in progress if you like, and go on from there.