![[staff profile]](https://www.dreamwidth.org/img/silk/identity/user_staff.png){kind=small}
Entry tags:
Docs work moving into Bugzilla
As you might have seen from rho's entry and my entry to ![[site community profile]](https://www.dreamwidth.org/img/comm_staff.png)
dw_docs, we're moving to using Bugzilla for major docs projects, since it's been very easy for us to lose track of what needs to be documented.
Very little will change for dev work because of this! However, if you're implementing a bug that will require FAQ changes, whether it's because you're adding a new feature that needs to be documented from scratch or making changes to an old feature that may require FAQ updates, please open a docs bug for it. We'll be doing doc work in separate bugs from the bugs for the feature itself (so it doesn't hold up resolving the bug that's assigned to you and so the FAQ team can assign the bugs to themselves and get credit for their changes), so just open a new bug and mark it as blocking the bug you're working on. There doesn't need to be a new docs bug for every development bug -- only the ones that will require major FAQ changes. (For minor changes, just leave a note in adw_docs entry, or email me or ![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
rho.)
New docs bugs should be in the Project Documentation product, and the User documentation component. Default assignee is fine, and you don't need to do anything about the priority/severity/keywords; I'll handle that the way I handle other bugs people don't prioritize/keyword.
And, of course, if any of you want to pick up some docs bugs and submit FAQ drafts or revisions of FAQs along with your changes, that would be wonderful!
dw_docs, we're moving to using Bugzilla for major docs projects, since it's been very easy for us to lose track of what needs to be documented.Very little will change for dev work because of this! However, if you're implementing a bug that will require FAQ changes, whether it's because you're adding a new feature that needs to be documented from scratch or making changes to an old feature that may require FAQ updates, please open a docs bug for it. We'll be doing doc work in separate bugs from the bugs for the feature itself (so it doesn't hold up resolving the bug that's assigned to you and so the FAQ team can assign the bugs to themselves and get credit for their changes), so just open a new bug and mark it as blocking the bug you're working on. There doesn't need to be a new docs bug for every development bug -- only the ones that will require major FAQ changes. (For minor changes, just leave a note in a
dw_docs entry, or email me or rho.)New docs bugs should be in the Project Documentation product, and the User documentation component. Default assignee is fine, and you don't need to do anything about the priority/severity/keywords; I'll handle that the way I handle other bugs people don't prioritize/keyword.
And, of course, if any of you want to pick up some docs bugs and submit FAQ drafts or revisions of FAQs along with your changes, that would be wonderful!
no subject
no subject
no subject