Aklapper added a comment.

Description says "//technical// documentation". Would e.g. Task 64446 still be 
"technical documentation" or already user docs (if something like that exists)? 
Is a license file still documentation (Task 67270, I think not)? What is 
non-technical documentation? (Developer vs end user docs? API docs vs some 
on-wiki docs? Phun phun phun! Probably we do not want to discuss this here; 
it's bikesheddy.)

- Create a #documentation tag: Sounds good to me if commonly considered an 
umbrella tag.
- Then kill https://phabricator.wikimedia.org/T2001 by adding that new tag to 
all tickets: Yes! Also see https://phabricator.wikimedia.org/T75703.
- I propose creating a Herald rule to automatically add the #documentation tag 
to tasks that have the projects 
https://phabricator.wikimedia.org/tag/mediawiki-documentation/ and 
https://phabricator.wikimedia.org/tag/pywikibot-documentation/ set (like for 
VE, see https://phabricator.wikimedia.org/T76954).
- Manually add the new tag to open tickets under these previously existing 
projects. More complete search results for the win.
- Keep https://phabricator.wikimedia.org/tag/mediawiki-documentation/ as is for 
the time being. Long version: It has 25 open tasks 
<https://phabricator.wikimedia.org/maniphest/query/lWQYGbOJ6C0m/#R>. Initially 
I thought I'd like to kill that component but some stuff really is in MW Core's 
specific /doc area which I consider a "partial codebase that can be defined" 
(my very personal definition of a project). Might kill and move to generic 
project once the slighly derailed discussion in 
https://phabricator.wikimedia.org/T76942 has ended in $something-actionable.
- Unrelated: Want to kill https://phabricator.wikimedia.org/T66840 too in favor 
of https://phabricator.wikimedia.org/tag/pywikibot-documentation/. I've 
commented there. (Another messy fragmentation example thanks to Bugzilla's 
tracking bugs, keywords, components. There are many such examples.)


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



_______________________________________________
Pywikipedia-bugs mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/pywikipedia-bugs

Reply via email to