Aklapper added a comment.
@Spage: Let me try to understand your workflow needs by asking ignorant questions and
adding high-level rants.
<tl;dr>: I'm not convinced how Mozilla handles it in BZ is good. I cannot offer
a great idea either though.
In
https://phabricator.wikimedia.org/T85485#948235, @Spage wrote:
A lightweight `doc-needed` tag is the BZ approach.
@Aklapper do you think this is redundant when we have the `MediaWiki-Documentation`
project?
I wonder what is the differentiation... An open Phabricator task that has a documentation
project/tag is where some doc update or doc creation is needed. If creation of dedicated
doc tasks for "we still needs docs for the code we fixed in task xyz" has ever
happened in the past, then only sporadically.
Mozilla
<https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Getting_documentation_updated>
replaces their BZ tag with a `doc-completed` tag so lagging documentation doesn't stop
a task from being resolved
Having some BZ keyword is probably still better than a TODO comment in the code or nothing
at all //if you don't want to create a separate task about the documentation part// of
a code change.
Advantage: Separate tasks have their own status that can be open or resolved.
Disadvantage: Takes way longer to create that separate task about the docs than just
adding a tag/keyword or a dedicated field (like RedHat Bugzilla does to integrate their
"devs work on task, then docs and qa work on followup stuff for that task").
Most important: People are lazy.
I don't get the "remove doc-needed and add doc-completed" part though. I
consider any Bugzilla keywords ⩯ Phabricator projects/tags which have some semantic
relation between each other (tag Y should be set after tag X) and try to reflect some
parallel status system fundamentally busted and error-prone as those semantics cannot be
technically expressed. That would have been a usecase for a flag dropdown in BZ which we
don't have that in Phab.
In more actionable words: Why is the "doc-completed" part needed? Does someone
really want to query which docs have been fixed //specifically// for code changes of
developers who did not update/provide the docs themselves? Is such differentiation really
wanted, or could you also just remove the "doc-needed" keyword, once docs have
been fixed?
TASK DETAIL
https://phabricator.wikimedia.org/T85485
REPLY HANDLER ACTIONS
Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign
<username>.
EMAIL PREFERENCES
https://phabricator.wikimedia.org/settings/panel/emailpreferences/
To: Aklapper
Cc: Aklapper, Qgil, Spage, Gryllida, Jdforrester-WMF, Rfarrand, pywikipedia-bugs