Hmmm, I'll look into this a bit. Right now, every time you say "Bug Tracker", I think of the actual "BugTracker" software, which conjures nightmares for me based on my work experiences with it before we moved to Jira. So I think I'm having an emotional reaction to that as a work tool without having any experience using it as a community-resources tool.
My at-home experience with online communities is with Forums. Which is what my husband knows best, too. I might look to see if there is a way to incorporate an issue tracker into an online forum (that isn't too expensive.) The more locations we have to visit in order to research something, the less likely it is to get researched. That's just human nature. Similarly, if community is over here and issue reporting is over there, that set-up lowers the (already small) likelihood of people checking to see if their issue was already reported before reporting it.
Maybe over the weekend I'll look to see if there are any integrated solutions we could leverage. And I'll check to see what he actually prefers. My life revolves heavily around the Software Development Lifecycle, but his doesn't. So he might not actually be comfortable with using an issue tracker. I'll find out.
Thanks for the idea!