![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png){kind=small}
filing bugs for needed FAQ updates
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.
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.