filing bugs for needed FAQ updates

[denise]

The perpetual bane of any product is making sure the documentation is up to date. We've been falling down on documentation for a while, and there are lots of reasons for that but I'd once again like to start trying to change it. Now that it's a new year, it's time to once again start in on a concerted effort to figure out what's missing from the FAQs (and then, of course, work to fix that, but the first step is identifying the scope of the problem!)

I have a few people working off the code tours to identify what we've added that needs to be documented, but consider this an open invitation to join them. If there's something you identify as missing from the FAQ, please open a bug for it (or if you don't want to navigate Bugzilla, you can just leave a comment here and someone will move it into Bugzilla for you).

See Bugzilla: How to enter, find and work on docs bugs for reference, and the list of open docs bugs to see what's already been reported.

Comments

Notifications

[insignia]

The FAQ says that "All notifications will automatically be sent to your inbox." However, some notifications are only sent to your e-mail address. Perhaps changing "all" to "most" would be a good idea, to avoid confusion.

[rike_tikki_tavi]

So I'd like to try and help. Found an easy bug to work on (actually the one reported above) and I have one question. Lots of the FAQs include links. Should we just ignore those when writing a new/revised FAQ text or what should we do?

[adannu]

Ooh. I've been thinking about volunteering for this and was wondering how/where to get started so yay. :D