@lafayette maybe i’m mistaken i figured u needed to create GitHub account in order to use the bug report forms

I'm not sure if it's been stated, we want to be able to tell from the title alone of a forum post whether it's "fixed" or not. Opening each forum post to then look for a 'github issue' card is a lot of overhead (in which case things become unworkable). If we can label the 'closed' or 'fixed' forum threads, that would be helpful.

A de-facto way that "forums" works in general, anything that is 'old' tends to be considered closed. Kinda a nature of this format. If we only ever look at posts that have been updated in the previous month, then there is extra importance in creating the formal bug ticket (in GH issues).

Bottom line: I believe there is consensus here. Specifically to "drive" players to the forums for issues/help/bugs. We'll reserve creating actual bug reports to those who are in the know. If anyone wants to fix up the forum descriptions/texts/layout (who has forum admin/moderator), please feel free to do so.

@ubernaut said in Unarchiving Bug Reports in TripleA Forums?:

people that don’t do git hub will just ignore that but folks that understand it may prefer interfacing that way.

I don't think it should be a matter of preference. The framing IMO is wrong (I kinda reject the framing, those that think 'github' is just for developers are ignorant. Specifically when we are just talking about using "github.com" for its web UI and its web forms. I digress though.)

I read somewhere that one project allows public access to github (GH) discussions, and only those from a select group access to issues. The idea was the general public discusses items, the team creates the bugs. (Side note, GH discussions is incredibly under-used by us. We should use that for feature request tracking, but I digress again!)

I think similar idea potentially here. Try to focus on 'issues' as being bona fide bug reports. A formal bug report is a real thing, and for good reason.. you want people to spend time diagnosing a bug, not spending their time first trying to understand what the bug report is even saying.

Thanks for the response @beelee

w.r.t:
@beelee said in Unarchiving Bug Reports in TripleA Forums?:

Slightly off topic but I've thought for a while that a "Common Bugs" or some such thread could be helpful. I don't really understand the errors that well to be confident in doing it though.

Hopefully "common bugs" would be resolved rather than left as a "known issue". The bug queue itself is ideally searchable enough.. I don't think that works very well (at all) in practice for an average user, but who is to say a list of common bugs would not have all the same problems and just be as difficult to find information from?