[00:00:41] (03CR) 10jenkins-bot: [V: 04-1] Add pre-commit hook script [extensions/Thanks] - 10https://gerrit.wikimedia.org/r/207286 (owner: 10Mooeypoo) [00:16:12] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Create a Timer based reminder for workflows - https://phabricator.wikimedia.org/T88781#1516843 (10Whatamidoing-WMF) > Is there an example of a workflow that always concludes on the same week day (e.g. Monday)? [[ http://meta.wikimedia.org/wiki/Tech/News | Tech/Ne... [00:24:46] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Flow pages scrolls to the wrong place from Echo Notifications - https://phabricator.wikimedia.org/T99996#1516851 (10Mattflaschen) 5Open>3Resolved a:3Etonkovidova [00:24:59] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Flow pages scrolls to the wrong place from Echo Notifications - https://phabricator.wikimedia.org/T99996#1303277 (10Mattflaschen) Please reopen if you reproduce again. [00:39:05] (03PS1) 10Jforrester: Migrate to extension.json and deprecate PageTriage.php [extensions/PageTriage] - 10https://gerrit.wikimedia.org/r/230016 (https://phabricator.wikimedia.org/T87954) [00:39:15] (03CR) 10jenkins-bot: [V: 04-1] Migrate to extension.json and deprecate PageTriage.php [extensions/PageTriage] - 10https://gerrit.wikimedia.org/r/230016 (https://phabricator.wikimedia.org/T87954) (owner: 10Jforrester) [00:39:25] (03CR) 10Jforrester: [C: 04-1] "Doesn't work, untested, ghastly." [extensions/PageTriage] - 10https://gerrit.wikimedia.org/r/230016 (https://phabricator.wikimedia.org/T87954) (owner: 10Jforrester) [00:41:21] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 7Design: Display categories in Flow side rail - https://phabricator.wikimedia.org/T92874#1516879 (10Mooeypoo) a:3Mooeypoo [00:41:41] (03PS1) 10Mooeypoo: [wip] Add categories to the sidebar [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230017 (https://phabricator.wikimedia.org/T92874) [00:43:03] (03CR) 10jenkins-bot: [V: 04-1] [wip] Add categories to the sidebar [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230017 (https://phabricator.wikimedia.org/T92874) (owner: 10Mooeypoo) [00:52:36] Breaking for dinner. [00:56:43] (03CR) 10Catrope: [C: 032] Fix undo pages [extensions/Flow] - 10https://gerrit.wikimedia.org/r/228138 (https://phabricator.wikimedia.org/T107232) (owner: 10Sbisson) [00:56:52] (03CR) 10Catrope: Fix undo pages (031 comment) [extensions/Flow] - 10https://gerrit.wikimedia.org/r/228138 (https://phabricator.wikimedia.org/T107232) (owner: 10Sbisson) [00:59:36] (03Merged) 10jenkins-bot: Fix undo pages [extensions/Flow] - 10https://gerrit.wikimedia.org/r/228138 (https://phabricator.wikimedia.org/T107232) (owner: 10Sbisson) [01:46:47] (03PS30) 10Catrope: [WIP] Create an OOUI editor widget [extensions/Flow] - 10https://gerrit.wikimedia.org/r/220665 (https://phabricator.wikimedia.org/T103572) (owner: 10Mooeypoo) [01:48:08] (03CR) 10jenkins-bot: [V: 04-1] [WIP] Create an OOUI editor widget [extensions/Flow] - 10https://gerrit.wikimedia.org/r/220665 (https://phabricator.wikimedia.org/T103572) (owner: 10Mooeypoo) [03:49:45] (03PS5) 10Mattflaschen: Expose post and topic history through the API [extensions/Flow] - 10https://gerrit.wikimedia.org/r/222260 (https://phabricator.wikimedia.org/T103032) (owner: 10Happy5214) [04:01:23] 10Echo, 6Collaboration-Team-Backlog: Bug in signature parsing code of notifications - https://phabricator.wikimedia.org/T108278#1517018 (10Gryllida) 3NEW [04:05:19] 10Echo, 6Collaboration-Team-Backlog: Bug in signature parsing code of notifications resulting in mention notif not being delivered on ja.wp - https://phabricator.wikimedia.org/T108278#1517026 (10Legoktm) [04:06:18] 10Flow, 6Collaboration-Team-Backlog: Board history navigation bar is gone - https://phabricator.wikimedia.org/T108279#1517029 (10Mattflaschen) 3NEW a:3Mattflaschen [04:10:09] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Board history navigation bar is gone - https://phabricator.wikimedia.org/T108279#1517038 (10Mattflaschen) [05:40:01] (03Abandoned) 10Legoktm: Add an option to disable email notification while defining an Echo $notification [extensions/Echo] - 10https://gerrit.wikimedia.org/r/227648 (https://phabricator.wikimedia.org/T97925) (owner: 1001tonythomas) [05:57:01] (03CR) 10Mattflaschen: [C: 032] "Good work, keep it up." [extensions/Flow] - 10https://gerrit.wikimedia.org/r/222260 (https://phabricator.wikimedia.org/T103032) (owner: 10Happy5214) [05:59:14] (03Merged) 10jenkins-bot: Expose post and topic history through the API [extensions/Flow] - 10https://gerrit.wikimedia.org/r/222260 (https://phabricator.wikimedia.org/T103032) (owner: 10Happy5214) [06:49:18] 10Flow, 6Collaboration-Team-Backlog: Return replies list for view-post? - https://phabricator.wikimedia.org/T108260#1517192 (10Mattflaschen) [06:49:18] 10Flow, 6Collaboration-Team-Backlog, 10Pywikibot-Flow: Add a flag to view-post to include replies - https://phabricator.wikimedia.org/T106733#1517193 (10Mattflaschen) [06:58:24] 10Flow, 6Collaboration-Team-Backlog, 10Pywikibot-Flow: Expose Flow history in API (tracking) - https://phabricator.wikimedia.org/T103030#1517217 (10happy5214) [06:58:25] 10Flow, 6Collaboration-Team-Backlog, 5Patch-For-Review, 5WMF-deploy-2015-08-11_(1.26wmf18): Expose Flow post history in API - https://phabricator.wikimedia.org/T103034#1517216 (10happy5214) 5Open>3Resolved [06:58:40] 10Flow, 6Collaboration-Team-Backlog, 10Pywikibot-Flow: Expose Flow history in API (tracking) - https://phabricator.wikimedia.org/T103030#1380711 (10happy5214) [06:58:42] 10Flow, 6Collaboration-Team-Backlog, 5Patch-For-Review: Expose Flow topic history in API - https://phabricator.wikimedia.org/T103032#1517219 (10happy5214) 5Open>3Resolved [07:01:14] 10Flow, 6Collaboration-Team-Backlog, 10Pywikibot-Flow: view-topiclist and view-topic should support wikitext - https://phabricator.wikimedia.org/T100244#1517222 (10Mattflaschen) a:3matthiasmullie Matthias fixed this in {97eea33a4b957564d0261d1dadf0e6b623256f58}. [07:01:21] 10Flow, 6Collaboration-Team-Backlog, 10Pywikibot-Flow: view-topiclist and view-topic should support wikitext - https://phabricator.wikimedia.org/T100244#1517225 (10Mattflaschen) 5Open>3Resolved [07:08:09] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Board history navigation bar is gone - https://phabricator.wikimedia.org/T108279#1517237 (10Mattflaschen) [07:17:17] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Contributions apparently could have wrong pagination - https://phabricator.wikimedia.org/T108289#1517244 (10Mattflaschen) 3NEW a:3Mattflaschen [07:17:51] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Contributions apparently could have wrong pagination - https://phabricator.wikimedia.org/T108289#1517244 (10Mattflaschen) [07:18:26] 10Flow, 6Collaboration-Team-Backlog: Contributions apparently could have wrong pagination - https://phabricator.wikimedia.org/T108289#1517244 (10Mattflaschen) [07:43:30] 10Flow, 6Collaboration-Team-Backlog: Give the user the number of history items they asked for - https://phabricator.wikimedia.org/T108291#1517279 (10Mattflaschen) 3NEW [07:43:42] 10Flow, 6Collaboration-Team-Backlog: Give the user the number of history items they asked for - https://phabricator.wikimedia.org/T108291#1517288 (10Mattflaschen) [07:43:54] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Board history navigation bar is gone - https://phabricator.wikimedia.org/T108279#1517291 (10Mattflaschen) [07:43:54] 10Flow, 6Collaboration-Team-Backlog: Give the user the number of history items they asked for - https://phabricator.wikimedia.org/T108291#1517279 (10Mattflaschen) [07:49:40] (03PS1) 10Mattflaschen: Correctly show the navigation bar again when needed [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230047 (https://phabricator.wikimedia.org/T108279) [07:50:41] 10Flow, 6Collaboration-Team-Backlog: Give the user the number of history items they asked for - https://phabricator.wikimedia.org/T108291#1517302 (10Mattflaschen) [07:51:57] (03CR) 10jenkins-bot: [V: 04-1] Correctly show the navigation bar again when needed [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230047 (https://phabricator.wikimedia.org/T108279) (owner: 10Mattflaschen) [08:16:09] 10Echo, 6Collaboration-Team-Backlog: Echo should warn users who tries to notify more than N other users that they won't be notified - https://phabricator.wikimedia.org/T108293#1517327 (10He7d3r) 3NEW [08:31:02] 10Echo, 6Collaboration-Team-Backlog: Surface new notifications in a way alerts and messages can be anticipated - https://phabricator.wikimedia.org/T108190#1517346 (10Ankit-Maity) I wouldn't mind ditching the orange bar if it's integrated into the badge. Also, how about we just have an unified badge and then t... [09:44:48] 10Echo, 6Collaboration-Team-Backlog: Bug in signature parsing code of notifications resulting in mention notif not being delivered on ja.wp - https://phabricator.wikimedia.org/T108278#1517555 (10whym) I quickly tested on my local instance of MW 1.26alpha (7b835dd), and it appears that it fails when there are a... [10:16:04] 10Echo, 6Collaboration-Team-Backlog: Surface new notifications in a way alerts and messages can be anticipated - https://phabricator.wikimedia.org/T108190#1517579 (10Pginer-WMF) > I thought that we would separate the panels, and have two dropdowns -- Alerts and Messages. I think that would help people underst... [10:59:37] 10Echo, 10Flow, 6Collaboration-Team-Backlog: "You have new messages" stuck after all messages are 'Mark as read' - https://phabricator.wikimedia.org/T106033#1517687 (10Pginer-WMF) >>! In T106033#1516782, @Quiddity wrote: > Users very much appreciate the extra-loud notice (orange bar) for new messages on thei... [11:49:20] (03CR) 10Sbisson: [C: 04-1] "Did you consider saving the siderail state preference when the user expands or collapses the single topic view?" (031 comment) [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229996 (https://phabricator.wikimedia.org/T103584) (owner: 10Mooeypoo) [11:52:43] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Measure the number of unread notifications over time - https://phabricator.wikimedia.org/T108208#1517728 (10Pginer-WMF) [11:53:05] 10Echo, 10Flow, 6Collaboration-Team-Backlog, 6Design Research Backlog: Improve organization and control for Flow notifications (tracking + ideas) - https://phabricator.wikimedia.org/T100528#1517730 (10Pginer-WMF) [11:53:07] 10Echo, 6Collaboration-Team-Backlog: Surface new notifications in a way alerts and messages can be anticipated - https://phabricator.wikimedia.org/T108190#1514617 (10Pginer-WMF) [11:57:17] (03CR) 10Sbisson: "Nevermind my previous comment. I see that you did it. I don't know why it wasn't working at first when I tested it." [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229996 (https://phabricator.wikimedia.org/T103584) (owner: 10Mooeypoo) [12:04:08] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 5Patch-For-Review: Add width-expanding toggle on Topic pages - https://phabricator.wikimedia.org/T103584#1517732 (10SBisson) @mooeypoo, @dannyh This patch adds the collapse/expand button to the single topic page, the old revision topic pag... [12:13:22] 10Echo, 6Collaboration-Team-Backlog: Surface new notifications in a way alerts and messages can be anticipated - https://phabricator.wikimedia.org/T108190#1517740 (10Pginer-WMF) [12:15:20] 10Flow, 6Collaboration-Team-Backlog: Incorrect order of flow replies - https://phabricator.wikimedia.org/T108309#1517748 (10Lejonel) 3NEW [12:16:28] 10Flow, 6Collaboration-Team-Backlog: Incorrect order of flow replies - https://phabricator.wikimedia.org/T108309#1517758 (10Lejonel) [12:16:41] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Measure the user responsiveness to notifications over time - https://phabricator.wikimedia.org/T108208#1517763 (10Pginer-WMF) [12:24:14] (03CR) 10Sbisson: "I think this patch is missing" [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229996 (https://phabricator.wikimedia.org/T103584) (owner: 10Mooeypoo) [12:24:32] 10Echo, 6Collaboration-Team-Backlog: Surface new notifications in a way alerts and messages can be anticipated - https://phabricator.wikimedia.org/T108190#1517784 (10Pginer-WMF) I added in the ticket description a proposal based on the idea of separating further the concepts of alerts and notifications: {F706... [12:43:06] 10Flow, 6Collaboration-Team-Backlog: Flow is very slow loading a page - https://phabricator.wikimedia.org/T108313#1517802 (10Paladox) 3NEW [12:44:42] 10Flow, 6Collaboration-Team-Backlog: Flow should show recently edited topics - https://phabricator.wikimedia.org/T108314#1517810 (10Paladox) 3NEW [12:46:17] 10Echo, 6Collaboration-Team-Backlog: Surface new notifications in a way alerts and messages can be anticipated - https://phabricator.wikimedia.org/T108190#1517819 (10Pginer-WMF) [12:46:24] 10Flow, 6Collaboration-Team-Backlog: Flow should take the page - https://phabricator.wikimedia.org/T108315#1517820 (10Paladox) 3NEW [13:07:48] 10Flow, 6Collaboration-Team-Backlog: Flow should show recently edited topics - https://phabricator.wikimedia.org/T108314#1517848 (10SBisson) You can sort by "Recently active topic". {F710339} [13:08:51] 10Flow, 6Collaboration-Team-Backlog: Flow should show recently edited topics - https://phabricator.wikimedia.org/T108314#1517852 (10Paladox) Can that be made the default please. [13:16:45] 10Flow, 6Collaboration-Team-Backlog, 10pywikibot-core, 7Pywikibot-tests: paraminfo for flow submodule view-topic-history fails - https://phabricator.wikimedia.org/T108317#1517867 (10jayvdb) 3NEW [13:19:59] 10Flow, 6Collaboration-Team-Backlog: Flow should show recently edited topics - https://phabricator.wikimedia.org/T108314#1517876 (10SBisson) I don't know if we want it as the default. It's more of a @dannyh question but it's a sticky preference when you are logged in. Change it to "Recently active topic" and i... [13:38:45] 10Flow, 6Collaboration-Team-Backlog, 10pywikibot-core, 7Pywikibot-tests: paraminfo for flow submodule view-topic-history fails - https://phabricator.wikimedia.org/T108317#1517923 (10XZise) If this happens often we might really need something for {T100779}. [13:47:30] (03PS1) 10Sbisson: Fix api-flow-topic-history [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230098 (https://phabricator.wikimedia.org/T108317) [13:47:54] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 10pywikibot-core, and 2 others: paraminfo for flow submodule view-topic-history fails - https://phabricator.wikimedia.org/T108317#1517967 (10SBisson) a:3SBisson [13:51:10] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 10pywikibot-core, and 2 others: paraminfo for flow submodule view-topic-history fails - https://phabricator.wikimedia.org/T108317#1517977 (10SBisson) [13:51:37] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 10pywikibot-core, and 2 others: paraminfo for flow submodule view-topic-history fails - https://phabricator.wikimedia.org/T108317#1517979 (10SBisson) [14:04:20] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 10pywikibot-core, and 2 others: paraminfo for flow submodule view-topic-history fails - https://phabricator.wikimedia.org/T108317#1518051 (10jayvdb) [14:04:38] (03CR) 10John Vandenberg: [C: 04-1] Fix api-flow-topic-history (031 comment) [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230098 (https://phabricator.wikimedia.org/T108317) (owner: 10Sbisson) [14:05:20] (03PS2) 10Sbisson: Fix api-flow-topic-history and api-flow-post-history [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230098 (https://phabricator.wikimedia.org/T108317) [14:08:42] (03CR) 10Sbisson: Fix api-flow-topic-history and api-flow-post-history (031 comment) [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230098 (https://phabricator.wikimedia.org/T108317) (owner: 10Sbisson) [14:12:08] (03CR) 10John Vandenberg: [C: 031] Fix api-flow-topic-history and api-flow-post-history [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230098 (https://phabricator.wikimedia.org/T108317) (owner: 10Sbisson) [14:21:28] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Measure the user responsiveness to notifications over time - https://phabricator.wikimedia.org/T108208#1518074 (10Huji) Defining the "norm" is going to be hard. It would be unrealistic to expect that most people (or even the "ideal" users so to speak) check all th... [14:42:39] (03PS22) 10Paladox: Add extension.json, empty PHP entry point [extensions/Echo] - 10https://gerrit.wikimedia.org/r/211298 (https://phabricator.wikimedia.org/T87910) [16:08:49] 10Flow, 6Collaboration-Team-Backlog: Flow renders interwiki links as external links - https://phabricator.wikimedia.org/T97552#1518404 (10Josve05a) This also causes [[:en:WP:Flow#Design FAQ]] -> https://en.wikipedia.org/wiki/Wikipedia:Flow#Design%20FAQ meaing that seciton links with spaces in them breaks. This... [16:08:55] 10Flow, 6Collaboration-Team-Backlog: Flow renders interwiki links as external links - https://phabricator.wikimedia.org/T97552#1518405 (10Josve05a) p:5Normal>3High [16:26:17] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Create a Timer based reminder for workflows - https://phabricator.wikimedia.org/T88781#1518477 (10He7d3r) MediaWiki deployments happen weekly (and this often require tech users to check for breaking changes which might affect their scripts/gadgets): https://wikite... [16:28:04] 10Echo, 6Collaboration-Team-Backlog: Notifications: Linking a username in an Edit-Summary should trigger a notification - https://phabricator.wikimedia.org/T51446#1518509 (10He7d3r) [16:28:05] 10Echo, 6Collaboration-Team-Backlog, 10MediaWiki-Page-editing: Notify user when username used in an edit summary - https://phabricator.wikimedia.org/T32750#1518510 (10He7d3r) [16:28:13] 10Echo, 6Collaboration-Team-Backlog: Bug in signature parsing code of notifications resulting in mention notif not being delivered on ja.wp - https://phabricator.wikimedia.org/T108278#1518514 (10He7d3r) [16:28:36] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 5Patch-For-Review: [betalabs] Board description still partially displayed when collapsed - https://phabricator.wikimedia.org/T107948#1518522 (10SBisson) a:5Mattflaschen>3SBisson [16:41:11] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 5Patch-For-Review, 5WMF-deploy-2015-08-11_(1.26wmf18): F4. Add legal text to Flow side rail - https://phabricator.wikimedia.org/T97371#1518588 (10SBisson) On a new board that never had a description {F728577} [17:09:11] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 5Patch-For-Review, 5WMF-deploy-2015-08-11_(1.26wmf18): Change "About this discussion" in side rail to "About this board" - https://phabricator.wikimedia.org/T104775#1518686 (10Etonkovidova) Checked in betalabs in FF, Chrome, Safari, and... [17:20:37] 10Flow, 6Collaboration-Team-Backlog: "Must have data to write to external storage" when using Special:EnableFlow on non-existent page with header field empty - https://phabricator.wikimedia.org/T108348#1518743 (10Mattflaschen) 3NEW [17:22:42] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: "Must have data to write to external storage" when using Special:EnableFlow on non-existent page with header field empty - https://phabricator.wikimedia.org/T108348#1518768 (10Mattflaschen) [17:34:06] legoktm, ping meeting :) [17:36:15] 10Flow, 6Collaboration-Team-Backlog: Flow-author links for IP-editors should go to Special:Contributions not userpage - https://phabricator.wikimedia.org/T108352#1518846 (10Quiddity) 3NEW [17:45:04] 10Flow, 6Collaboration-Team-Backlog: Editing topicsummary made by another user cuases bad code - https://phabricator.wikimedia.org/T108353#1518873 (10Josve05a) 3NEW [17:49:31] 10Flow, 6Collaboration-Team-Backlog: Editing topicsummary made by another user shows raw i18n code - https://phabricator.wikimedia.org/T108353#1518895 (10Mattflaschen) [17:49:39] 10Echo, 10Flow, 6Collaboration-Team-Backlog, 6Design Research Backlog: Learn about use of notifications - https://phabricator.wikimedia.org/T100650#1518897 (10Capt_Swing) Per latest conversation with @dannyh, my understanding is that this research is not a current priority for Collab. So I'm pausing it for... [17:53:01] (03CR) 10Sbisson: [C: 032] Style resolved topics differently in TOC [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229478 (owner: 10Catrope) [17:53:04] (03CR) 10jenkins-bot: [V: 04-1] Style resolved topics differently in TOC [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229478 (owner: 10Catrope) [17:53:31] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: F9. Run LQT conversion script on mediawiki.org Project:Support desk - https://phabricator.wikimedia.org/T106614#1518921 (10Mattflaschen) ``` +----------------------------------------------------------------------------------------------------... [17:53:35] 10Flow, 6Collaboration-Team-Backlog, 7I18n: Editing topicsummary made by another user shows raw i18n code - https://phabricator.wikimedia.org/T108353#1518922 (10Josve05a) [17:55:26] (03CR) 10Mattflaschen: [C: 032] "Sorry about this. I flagged it in an earlier review, but forgot to follow up." [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230098 (https://phabricator.wikimedia.org/T108317) (owner: 10Sbisson) [17:57:35] 10Flow, 6Collaboration-Team-Backlog: Flow should take the page - https://phabricator.wikimedia.org/T108315#1518945 (10Josve05a) Well, you can hide the description on the left side, which will make Flow take the page width. Not enough? [17:57:58] (03PS5) 10Sbisson: Style resolved topics differently in TOC [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229478 (owner: 10Catrope) [17:59:57] (03CR) 10Sbisson: "Rebased manually because of conflict in TocTopicListFormatter.php" [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229478 (owner: 10Catrope) [18:00:05] (03CR) 10jenkins-bot: [V: 04-1] Style resolved topics differently in TOC [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229478 (owner: 10Catrope) [18:00:26] 10Flow, 6Collaboration-Team-Backlog, 7I18n: Editing topicsummary made by another user shows raw i18n code - https://phabricator.wikimedia.org/T108353#1518962 (10Ainali) And it is not locally in his client, since I could see it too.{F736121} [18:00:55] (03PS6) 10Sbisson: Style resolved topics differently in TOC [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229478 (owner: 10Catrope) [18:01:44] (03Merged) 10jenkins-bot: Fix api-flow-topic-history and api-flow-post-history [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230098 (https://phabricator.wikimedia.org/T108317) (owner: 10Sbisson) [18:03:13] 10Flow, 6Collaboration-Team-Backlog: Flow should take the page - https://phabricator.wikimedia.org/T108315#1518970 (10Paladox) But an improvement would be to allow it to be on top similar to LiquidThread which would allow both description and the extra width. [18:03:31] (03CR) 10Sbisson: [C: 032] Style resolved topics differently in TOC [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229478 (owner: 10Catrope) [18:04:44] matt_flaschen: do you have some time to talk about LQT? [18:04:46] (03CR) 10Mattflaschen: "You forgot to add the autoload. I mentioned this in patch set 2, but I also forgot to follow up. See https://gerrit.wikimedia.org/r/#/c/2" [extensions/Flow] - 10https://gerrit.wikimedia.org/r/222260 (https://phabricator.wikimedia.org/T103032) (owner: 10Happy5214) [18:04:59] Just need a minute or two. [18:06:09] (03Merged) 10jenkins-bot: Style resolved topics differently in TOC [extensions/Flow] - 10https://gerrit.wikimedia.org/r/229478 (owner: 10Catrope) [18:09:48] 10Flow, 6Collaboration-Team-Backlog: Incorrect order of flow replies - https://phabricator.wikimedia.org/T108309#1518999 (10Mattflaschen) [18:09:48] 10Flow, 6Collaboration-Team-Backlog: Flow: It is unclear shows indentation - https://phabricator.wikimedia.org/T94924#1519000 (10Mattflaschen) [18:12:05] stephanebisson, okay, ready. [18:12:18] I don't really know all the details of LQT's write actions, but i'm glad to help. [18:12:46] matt_flaschen: I see 'reply', 'edit' and I can block those in read-only mode [18:12:57] Okay, cool. I also didn't check if it's broken for the other write actions. [18:13:28] there is 'delete' that is restricted based on the user [18:13:38] It's unfortunate we have to work on this. It's not conversion-specific. It's something LQT should have already been doing (if it's not an LQT page (anymore) it shouldn't treat it like one). [18:13:42] But, so it goes. [18:13:45] I can leave this one open so a thread can still be moderated [18:14:07] stephanebisson, the core actions (e.g. action=delete) should still work. We should only block the LQT-specific write actions. [18:14:13] Can you point me to the moderation code? [18:15:16] stephanebisson, do you prefer I make a tracking task or broaden https://phabricator.wikimedia.org/T107894 ? [18:15:43] matt_flaschen: let's wait and see what kind of scope we end up with [18:15:48] (03CR) 10Legoktm: [C: 032] Remove use of deprecated TestUser->user [extensions/Echo] - 10https://gerrit.wikimedia.org/r/230119 (owner: 10Addshore) [18:15:50] Okay [18:16:49] there's 2 delete: delete the page which seems to be standard mw, and delete a message, which seems to be LQT specific but I haven't located the code yet [18:17:36] stephanebisson, why did you special-case the prop value (getUseLiquidThreadsPropValue)? Can't we just use LqtDispatch::isLqtPage? [18:18:19] matt_flaschen: here's the thing: after you remove the magic word your page is back to wikitext and everything is fine [18:18:29] the problem is in the Thread NS [18:19:32] are you suggesting we change LqtDispatch::isLqtPage to return false when it's the thread NS but the prop is gone? [18:19:51] stephanebisson, but it knows which page it's associated with (which I hope can only be one). E.g. https://www.mediawiki.org/wiki/Thread:Project_talk:Language_policy/Migration_list/Status is associated with Project talk:Language policy/Migration list . [18:19:54] Let me take a look. [18:20:31] I thing doing so would not create a read-only mode but remove LQT completely [18:20:34] 10Flow, 6Collaboration-Team-Backlog: Add log entries to history pages - https://phabricator.wikimedia.org/T90071#1519040 (10Quiddity) [18:21:06] stephanebisson, it already returns false for NS_LQT_THREAD. It must go via a slightly different path. [18:21:27] (isLqtPage I mean) [18:22:02] (03Merged) 10jenkins-bot: Remove use of deprecated TestUser->user [extensions/Echo] - 10https://gerrit.wikimedia.org/r/230119 (owner: 10Addshore) [18:24:07] stephanebisson, so it looks like if $thread->getTitle() is not an LQT page, no write actions should be allowed. [18:24:19] $thread would be an object of class Thread. [18:24:38] For the "not an LQT page" it should be able to reuse isLqtPage. [18:24:56] ok [18:25:06] 10Flow, 6Collaboration-Team-Backlog: Make Flow pages history compatible with normal history action - https://phabricator.wikimedia.org/T101420#1519085 (10Quiddity) [18:25:11] are 'split' and 'merge' write actions? [18:25:27] 10Flow, 6Collaboration-Team-Backlog: Add Mediawiki:Histlegend to Board/Topic history pages - https://phabricator.wikimedia.org/T101420#1519092 (10Quiddity) [18:25:31] what about page-level actions (delete, move, protect)? [18:26:29] Yes, split and merge definitely seem to be. [18:27:42] I'm looking if it exposes those actions with its own interface or just listens to core's hooks. [18:28:17] did you mean $thread->article() ? because $thread->getTitle() would return 'Thread:something' [18:29:14] Thread->getTitle just returns Thread->article()->getTitle(). I got that by checking lqt_from_talk, but I'll double-check. [18:30:25] right [18:31:46] so we can easily remove those links from the view, like I've started doing, but do you know where to block those actions from being executable at all? [18:32:47] oh I see, it's all in thread.php [18:35:50] I'm trying to figure out how to load a Thread from the shell. [18:39:07] It just keeps returning arrays of null. [18:39:36] matt_flaschen: I don't want to take too much of your time with this [18:39:48] matt_flaschen: do we want to block page-level actions (delete, move, protect)? [18:39:55] 10Flow, 6Collaboration-Team-Backlog: Add "View logs for this page" link to Flow board and topic history pages - https://phabricator.wikimedia.org/T96455#1519194 (10Quiddity) [18:39:56] 10Flow, 6Collaboration-Team-Backlog: Add Mediawiki:Histlegend to Board/Topic history pages - https://phabricator.wikimedia.org/T101420#1519193 (10Quiddity) [18:39:58] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 5Patch-For-Review: Board history navigation bar is gone - https://phabricator.wikimedia.org/T108279#1519192 (10Quiddity) [18:40:00] 10Flow, 6Collaboration-Team-Backlog, 7Mobile, 3Reading-Web: action=history should not redirect to Special:History for Flow boards - https://phabricator.wikimedia.org/T93491#1519195 (10Quiddity) [18:40:02] 10Flow, 6Collaboration-Team-Backlog: Add log entries to history pages - https://phabricator.wikimedia.org/T90071#1519196 (10Quiddity) [18:40:04] 10Flow, 6Collaboration-Team-Backlog, 7Tracking: Flow history page issues (tracking) - https://phabricator.wikimedia.org/T108363#1519191 (10Quiddity) [18:41:01] stephanebisson, finishing looking at that. [18:45:55] stephanebisson, no, since I think all of them are just listening to core actions and updating accordingly, or thin wrappers around core (I think that's what ThreadProtectionFormView is doing). [18:46:52] matt_flaschen: so we restrict reply, edit, split, merge? Do you see anything else? [18:48:48] There is undelete, but in my opinion we shouldn't block for the same reason. [18:50:12] stephanebisson, all the write actions in ApiThreadAction should be blocked if it's not an LQT page. [18:50:32] I think these are: [18:51:28] Actually, I guess they're all write actions, except inlineeditform might only be setting up a form. [18:51:55] But still makes sense to block that. [18:52:31] There are some internal things like moveToParent, but if the entrypoints are blocked, probably don't need to worry about that. [18:53:46] 10Flow, 6Collaboration-Team-Backlog: Don't trim messages in RSS/Atom feeds - https://phabricator.wikimedia.org/T96439#1519243 (10Quiddity) [18:54:34] makes sense, I'll block the API actions with a blanket message ($title is not an LQT page, or something) and then remove the buttons [18:55:52] matt_flaschen: thanks [18:56:06] No problem [18:56:43] Ooh, Special:Log has autocomplete for the performer now. Fancy. [18:59:03] getTitle is correct: https://phabricator.wikimedia.org/P1855 [18:59:29] Breaking for lunch [19:09:08] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Flow: Notifications links for "created a new topic" highlight too much - https://phabricator.wikimedia.org/T75049#1519313 (10Quiddity) [19:10:54] 10Echo, 10Flow, 6Collaboration-Team-Backlog: Flow: Notifications links for "created a new topic" highlight too much - https://phabricator.wikimedia.org/T75049#1519319 (10Josve05a) If I click https://sv.wikipedia.org/w/index.php?title=Wikipediadiskussion:Flow/Sandl%C3%A5da&topiclist_sortby=newest&fromnotif=1#... [19:26:10] 10Flow, 6Collaboration-Team-Backlog, 7Regression: Clicking the reference up-arrow on a Flow board, scrolls to page top and mis-places the intended target's topic up there - https://phabricator.wikimedia.org/T108366#1519343 (10Quiddity) 3NEW [19:48:03] 10Flow, 6Collaboration-Team-Backlog: Author names for Flow topic summaries should be linked - https://phabricator.wikimedia.org/T108369#1519383 (10Quiddity) 3NEW [20:21:29] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 5Patch-For-Review: Board history pagination controls are missing - https://phabricator.wikimedia.org/T108279#1519501 (10Quiddity) [20:50:11] 10Flow, 6Collaboration-Team-Backlog: Images used in flow without the |thumb parameter don't show captions as tooltips - https://phabricator.wikimedia.org/T108380#1519578 (10Quiddity) 3NEW [20:53:27] 10Flow, 6Collaboration-Team-Backlog, 6Multimedia: Images used in flow without the |thumb parameter don't show captions as tooltips - https://phabricator.wikimedia.org/T108380#1519593 (10Josve05a) [21:16:25] 10Echo, 6Collaboration-Team-Backlog: Surface new notifications in a way alerts and messages can be anticipated - https://phabricator.wikimedia.org/T108190#1519693 (10Legoktm) YES YES YES to splitting the flyouts. This will also result in us moving the edit-user-talk notification to messages right? > Don't sh... [21:18:01] 10Echo, 6Collaboration-Team-Backlog: Notification emails should embed icons as data URIs - https://phabricator.wikimedia.org/T55479#1519697 (10Legoktm) Hardcoded HTTP was fixed as {T104835}/{b12efddf30315f1dc1f45a9fc7d1462ce74883c9}. [21:18:51] 10Echo, 6Collaboration-Team-Backlog, 7Easy: Override Echo system notification icons for all Wikimedia projects - https://phabricator.wikimedia.org/T49662#1519703 (10Legoktm) [21:25:12] (03PS2) 10Mooeypoo: [wip] Add categories to the sidebar [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230017 (https://phabricator.wikimedia.org/T92874) [21:26:59] (03CR) 10jenkins-bot: [V: 04-1] [wip] Add categories to the sidebar [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230017 (https://phabricator.wikimedia.org/T92874) (owner: 10Mooeypoo) [21:28:00] 10Echo, 6Collaboration-Team-Backlog: Echo: Granular icons in the Notifications Badge - https://phabricator.wikimedia.org/T58476#1519730 (10Legoktm) This is kind of being brainstormed in {T108190}. [21:30:55] RoanKattouw, ready? [21:31:01] One minute [21:31:07] Okay, no problem. [21:33:45] matt_flaschen: OK, let's roll [21:34:11] So, columns [21:34:22] Yeah [21:34:30] So, do you want to start with the Current board? [21:34:33] Sure [21:34:58] Now that we're not using sprints, is there any use for https://phabricator.wikimedia.org/project/sprint/burn/1384/ ? [21:35:43] I'm asking because I'm wondering if we can/should get rid of Done, but I think the Sprint extension uses that to determine what's been closed. [21:35:47] (rather than Resolved) [21:35:56] Pfft really? [21:36:05] That's kind of disappointing [21:36:47] So, the line I got from Stephane about burndown charts (which I agree with) is that they make sense when you are going through a fixed-size backlog and want to estimate when you'll be done [21:36:57] I don't think that matches our current situation that well [21:37:28] Like, it's not like "we have this clearly defined set of tasks that when they're all done, we can deploy X in on Ywiki" [21:37:37] (We did a few months ago with the Catalan thing) [21:38:16] And even if/when we do have that, I think we'd apply that to a different board/project/tag/thingy [21:38:36] Yeah, I believe so (re Done column). It definitely used to be that way (https://phabricator.wikimedia.org/T90826#1069316) and has not changed as far as I know. [21:38:45] I agree burndown is not useful with a refilling task list. [21:38:47] So basically that's my reasoning for "maybe we should stop caring about that chart" [21:38:54] Yeah, so hide Done? [21:38:54] (for the time being) [21:39:06] Yeah, maybe [21:39:07] Hmm actually [21:39:10] I have another idea [21:39:24] How about we make "Done" something like "Next train" [21:39:32] And clear it every Tuesday [21:39:49] Do you think that would be valuable? [21:41:01] 10Flow, 6Collaboration-Team-Backlog, 10VisualEditor, 10VisualEditor-ContentEditable, and 2 others: VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page - https://phabricator.wikimedia.org/T52321#1519780 (10Josve05a) [21:41:01] RoanKattouw, we could do it with a filter using the Forrest bot tags, but I don't really object to the column. We would still need to review either way, since not all Gerrit changes have a task. [21:41:10] Right, yeah [21:41:19] Yeah, maybe it doesn't have that much value [21:41:42] Is it possible to configure the board to hide resolved tasks by default? [21:42:06] (Like, in a way that affects other users' view of the board, not just your own) [21:42:15] Not that I know of, but the open task view can be bookmarked (which is more convenient now that the URLs won't change). [21:43:03] https://phabricator.wikimedia.org/project/sprint/board/1384/query/open/ [21:43:05] OK that's fine too [21:43:31] 10Flow, 6Collaboration-Team-Backlog, 10VisualEditor, 10VisualEditor-ContentEditable, and 2 others: VisualEditor: Ctrl-Click / middle-click on a link should open it in another window; on an image, should open the image's description page - https://phabricator.wikimedia.org/T52321#1519793 (10Jdforrester-WMF)... [21:44:09] RoanKattouw, are we going to do the changes now, or just decide then do it later? [21:44:28] I'm OK with making them now [21:44:34] Okay. Should I hide Done? [21:44:42] Yeah, I think that's a good idea [21:45:03] Taking a quick look at the others, it looks like they're all still relevant [21:45:11] Yep [21:45:52] Okay, backlog board is a little more complicated. [21:46:15] Yeah [21:46:34] So, I think the idea of an Untriaged column makes sense (for totally unsorted tasks) [21:46:48] So one thing we talked about before but I wasn't sure if you agreed was desirable: should we distinguish between "untriaged stuff that someone randomly added" and "stuff we've actively decided not to do in the near future" [21:46:51] ...jinx [21:47:06] Yeah, Untriaged vs Freezer is what I mean [21:47:15] Yeah, I think you convinced me we need all three: [21:47:17] Or whatever names we want to call them [21:47:46] Untriaged, Freezer (valid tasks we've looked at but aren't in the short-term backog), and Backlog (will probably go to Ready to pickup relatively soon). [21:48:04] OK [21:48:20] There's no fundamental difference between Freezer and Backlog, it's just the theory that a massive Backlog column will not be sorted meaningfully. [21:48:24] So "Backlog" is "not now" and Freezer is "not this year" (approximately)? [21:48:41] 10Flow, 6Collaboration-Team-Backlog: Realtime updates (auto-refresh) for Flow boards and topics - https://phabricator.wikimedia.org/T108391#1519805 (10Quiddity) 3NEW [21:48:43] I guess Backlog would be more like "soon" [21:48:49] Something like that, not sure how big Backlog would be. [21:49:04] Right, you just reminded me that the point was for Backlog to not be very big [21:49:44] OK, so what is currently "Backlog" we'd rename to "Untriaged" [21:49:55] Then we'd add "Freezer" and "Backlog" [21:50:04] And rename "Ready for next sprint" to "Ready for pickup" [21:50:26] Wait, you want three (not counting Untriaged)? [21:50:30] Also rename "Current sprint" to ... something [21:50:55] Yes? [21:50:56] [14:47] matt_flaschen Yeah, I think you convinced me we need all three: [21:50:59] Also, I don't like having two columns called Ready for pickup. [21:51:03] I thought that's what you meant [21:51:15] OK yes, I guess Ready is redundant with the Ready column on the current board [21:51:20] RoanKattouw, those three were: Untriaged, Freezer, Backlog (it was including Untriaged that time) [21:51:31] OK [21:51:55] Also, I wasn't sure if we should rename Backlog or add an Untriaged. I don't know if anything in there is sorted meaningfully. [21:52:11] So something that's going to be worked on very soon or is already in progress (and therefore is on the "current" board), where would that be? In a special column? Or remove it from this board entirely? [21:53:16] RoanKattouw, I was thinking it would be better to just have it be in Collaboration-Team-Backlog or Collaboration-Team-Sprint, but not both. [21:53:30] To do that, I think we need to change the Herald rule so it only adds Backlog if it's not in Sprint. [21:53:48] Right [21:53:51] Yes, makes perfect sense [21:54:26] Re meaningful sorting in the current backlog: from talking to Danny I get the impression things aren't meaningfully sorted anywhere except for the short-term columns [21:54:31] And maybe the bug queue to some extent [21:54:35] Okay, I'll file that. I don't seem to have rights for that kind of rule. [21:54:56] I think the Bug queue is like half-way, but I still wouldn't want to drop that ordering. [21:56:44] https://phabricator.wikimedia.org/T108393 [21:57:18] Thanks [21:57:25] Okay, so if that's implemented we can drop 'Current sprint', but we'll have to wait and see. [21:57:31] Yeah [21:57:39] Should I go ahead and rename Backlog to Untriaged? [21:57:43] Yeah I think so [21:57:50] And create empty Backlog and Freezer columns [21:58:37] RoanKattouw, should I rename Bug queue to Backlog, since it's roughly the same thing (except we're expanding it to cover all kinds of work)? [21:59:10] Hah! Yeah good idea [21:59:13] I hadn't considered that [21:59:17] That's a clever way to maintain order [21:59:30] Okay, I'll do that. [22:02:03] RoanKattouw, and then I think we could get rid of Ready for next sprint by moving it to the top of the Backlog (preserving order so everything in Ready for next sprint beats items already in Backlog). What do you think? [22:02:16] Yeah, makes sense [22:02:21] Is that something Phab lets you do automatically? [22:03:02] I don't think so, but I'm not sure. quiddity knows a little about the batch edit interface. quiddity, does it let you do column moves? [22:03:26] err, I've used it once, back when phabricator was new [22:03:46] (to bulk remove a few CCs from tasks) [22:03:48] I mean, if it's easy, go for it, but I'm not sure it's worth spending significant time on [22:04:05] There's only 36, it will just take me a minute or so. [22:04:41] Oh OK [22:08:53] Done. [22:09:37] I guess we can leave LQT for now, but worth thinking of a better approach for that (e.g. we can search on intersection between Collaboration-Team boards and LiquidThreads). [22:10:02] Right [22:10:07] As for the others [22:10:12] Design/Requirements we should probably keep? [22:10:18] Yeah [22:10:27] Do we want to create a Freezer column? [22:10:31] Yeah. [22:10:33] I think the order: [22:10:53] Untriaged -> Freezer -> Design/Requirements -> Story grooming/estimation -> Backlog makes sense. [22:11:00] Yes [22:11:03] We could skip some in certain cases, but I think that order is reasonable. [22:11:19] We could potentially rename "Story grooming/estimation" to just "Story grooming" [22:11:22] (or something) [22:11:40] As I envision it it's the "we should talk about this in a meeting" column [22:14:16] RoanKattouw, that might make the difference between 'Design/requirements' and 'Story grooming' a little confusing. Of course, in reality estimation meetings also usually lead to design/requirements changes. There's natural overlap. [22:14:23] Hmm yes [22:15:06] I also moved all the weird columns to the left so you can imagine the "Current" board immediately to the right of the Backlog board and stuff just keeps moving right. Don't know if that makes sense, but it's easy to rearrange columns. [22:16:33] So for subprojects, I was thinking it could be useful for things like Collaboration-Team-Curation or Flow-Workflows. We might have changed enough for today, but worth thinking about. [22:17:14] Yeah maybe [22:17:20] * RoanKattouw refreshes board [22:17:39] OK yeah this looks good [22:18:16] Cool, hopefully Danny likes it. [22:18:27] And everyone [22:18:52] Thanks for doing all the hard work matt_flaschen :) [22:19:17] RoanKattouw, don't worry, I'll rest my dragging muscles over the weekend. [22:27:27] 10Flow, 6Collaboration-Team-Backlog: New flow topics not appearing in watchlist - https://phabricator.wikimedia.org/T108396#1519949 (10Quiddity) 3NEW [22:38:45] 10Flow, 6Collaboration-Team-Backlog: Topic summary edits should not be attributed to the board history - https://phabricator.wikimedia.org/T108397#1519976 (10Josve05a) [22:44:45] 10Flow, 6Collaboration-Team-Backlog: Convert LQT topics for talk pages where {{#useliquidthreads:1}} was removed after a thread was created - https://phabricator.wikimedia.org/T107654#1520001 (10Mattflaschen) For most of them, we look for where useliquidthreads:1 is missing (this could be omitted, or explicitl... [22:47:50] 10Flow, 6Collaboration-Team-Backlog: References in isolated posts, create duplicate "[1]" (#cite_note-1) links - https://phabricator.wikimedia.org/T108398#1520004 (10Quiddity) 3NEW [22:52:32] 10Flow, 6Collaboration-Team-Backlog: References in isolated posts, create duplicate "[1]" (#cite_note-1) links - https://phabricator.wikimedia.org/T108398#1520041 (10Josve05a) Sam with if I click the first [1] in https://sv.wikipedia.org/w/index.php?title=%C3%84mne:Smjt4fgf3hp4ifr9&topic_showPostId=smjt4fio5wa... [22:53:45] 10Flow, 6Collaboration-Team-Backlog: Flow mentions (tracking) - https://phabricator.wikimedia.org/T108400#1520045 (10Quiddity) 3NEW [22:55:40] 10Flow, 6Collaboration-Team-Backlog, 7I18n: Flow-rev-message-edit-post-recentchanges-summary may need to mention the user explicitly - https://phabricator.wikimedia.org/T75477#1520056 (10Quiddity) [22:56:20] 10Flow, 6Collaboration-Team-Backlog: Flow: email notification for Flow mentions gives a link to a blank Flow page if that topic was suppressed - https://phabricator.wikimedia.org/T63714#1520058 (10Quiddity) [22:57:04] (03CR) 10Legoktm: "recheck" [extensions/Thanks] - 10https://gerrit.wikimedia.org/r/230121 (owner: 10Addshore) [23:05:36] 10Flow, 6Collaboration-Team-Backlog: Add an option to Flow's @mention for multiple users at once - https://phabricator.wikimedia.org/T108403#1520095 (10Quiddity) 3NEW [23:08:54] 10Flow, 6Collaboration-Team-Backlog: Add an option to Flow's @mention for multiple users at once - https://phabricator.wikimedia.org/T108403#1520110 (10Quiddity) [23:08:55] 10Flow, 6Collaboration-Team-Backlog: Mention inspector box is not fully displayed in text placeholder for a new topic - https://phabricator.wikimedia.org/T107345#1520111 (10Quiddity) [23:08:57] 10Flow, 6Collaboration-Team-Backlog: Copying mentions from posts into VE doesn't work in Firefox - https://phabricator.wikimedia.org/T101376#1520114 (10Quiddity) [23:08:59] 10Flow, 6Collaboration-Team-Backlog: 'Start new topic' edit area displays Link and Mention boxes as cutoff - https://phabricator.wikimedia.org/T102252#1520113 (10Quiddity) [23:09:01] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Template:FlowMention missing, new mentions of users are broken - https://phabricator.wikimedia.org/T106575#1520112 (10Quiddity) [23:09:06] :/ [23:09:10] 10Flow, 6Collaboration-Team-Backlog: Flow mentions (tracking) - https://phabricator.wikimedia.org/T108400#1520109 (10Quiddity) [23:09:21] :D [23:18:34] 10Echo, 6Collaboration-Team-Backlog: Surface new notifications in a way alerts and messages can be anticipated - https://phabricator.wikimedia.org/T108190#1520150 (10Mattflaschen) >>! In T108190#1517579, @Pginer-WMF wrote: >> I thought that we would separate the panels, and have two dropdowns -- Alerts and Mes... [23:24:16] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Opt-in for Flow on your own user talk page - https://phabricator.wikimedia.org/T98270#1520163 (10Mattflaschen) >>! In T98270#1514824, @Pginer-WMF wrote: > Even in that case, I'm not sure which could be the issue: a user that likes flow discus... [23:28:17] 10Flow, 6Collaboration-Team-Backlog, 7Tracking: Flow mentions (tracking) - https://phabricator.wikimedia.org/T108400#1520167 (10Legoktm) [23:31:58] 10Flow, 6Collaboration-Team-Backlog: Flow should either notify me or give live-updates, about new posts made in the topic I'm currently typing a reply in - https://phabricator.wikimedia.org/T94918#1520193 (10Quiddity) [23:31:59] 10Flow, 6Collaboration-Team-Backlog: Realtime updates (auto-refresh) for Flow boards and topics - https://phabricator.wikimedia.org/T108391#1520192 (10Quiddity) [23:32:38] 10Flow, 6Collaboration-Team-Backlog: Switch User_talk:Amire80 in en.wikipedia, mediawiki.org and meta.wikimedia.org to Flow - https://phabricator.wikimedia.org/T107148#1520201 (10Mattflaschen) [23:33:00] 10Flow, 6Collaboration-Team-Backlog: Switch User_talk:Amire80 in en.wikipedia, mediawiki.org and meta.wikimedia.org to Flow - https://phabricator.wikimedia.org/T107148#1487976 (10Mattflaschen) Archiving is now done automatically by Special:EnableFlow. [23:35:14] 10Flow, 6Collaboration-Team-Backlog, 7Documentation, 7Easy, 7I18n: documentation inconsistent with behavior - https://phabricator.wikimedia.org/T96511#1520213 (10Quiddity) [23:38:01] 10Flow, 6Collaboration-Team-Backlog: Compare selected revisions for Flow history - https://phabricator.wikimedia.org/T108407#1520217 (10Quiddity) 3NEW [23:42:30] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current, 7Design, 5Patch-For-Review: Display categories in Flow side rail - https://phabricator.wikimedia.org/T92874#1520240 (10Mooeypoo) This can't work with HotCat because, as far as I could see, there's no way to listen to changes made by HotCa... [23:45:41] matt_flaschen, i am running into the WEIRDEST BUG EVER[tm] in my category commit. Help will be appreciated. I am adding categories in the description. Say, Cat1, Cat2, Cat3. They all appear properly (yay). Now I go in and delete Cat2 and Cat3. So, I effectively only have Cat1. Except no I don't -- all three appear still. I refresh and I *still* have all three, despite the fact that in the BODY of the description there's only one. [23:46:09] And the three that I get from the initial refresh of the page come from View.php that gives me the categories through $categories = array_keys( $title->getParentCategories() ); [23:46:18] * matt_flaschen checks if this is a bug in production [23:46:31] matt_flaschen, so, it seems that array_keys( $title->getParentCategories() ); gives me all the added categories even if I removed them [23:46:32] whaaaaa. [23:49:22] mooeypoo, yeah, it is. :( [23:49:28] You can check with wgCategories. [23:49:28] oy [23:49:40] Am I right that categories are added instantly as expected, but never removed? [23:49:57] matt_flaschen, wait, but that's going to only work once. it doesn't get updated after I save the description [23:50:20] I'm running another API request for categories after I save the description to get the real categories again (and that's a wrong response too) [23:50:23] Old bug I forgot about: https://phabricator.wikimedia.org/T94569 [23:50:33] The actual tables are probably wrong. [23:51:00] mooeypoo, I can take that if you want; shouldn't block you but necessary to display sane results. [23:51:03] ok we should take into account that my commit *exposes* this bug pretty visibly [23:51:15] You now have a box of categories and it's really obvious that none are erased :\ [23:51:16] Right, hence why I think we should bring it in. [23:51:24] * mooeypoo nods [23:51:36] okay I wanted to make sure first that it wasn't something I was requesting wrong [23:51:40] or constructing wrong from view.php [23:51:47] Okay, I'll move it in. I have some stuff on my plate already, so I won't actually assign it to myself, but I will try to get to it if no one else does. [23:51:58] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Old categories are not removed properly when removing and re-adding a template to summary (or just adding new categories) - https://phabricator.wikimedia.org/T94569#1520274 (10Mattflaschen) [23:52:03] I'll take a look at it but might need help with database stuff [23:52:23] 10Flow, 6Collaboration-Team-Backlog, 10Collaboration-Team-Current: Old categories are not removed properly when removing and re-adding a template to summary or header (or just adding new categories) - https://phabricator.wikimedia.org/T94569#1520277 (10Mattflaschen) [23:53:41] mooeypoo, okay, feel free to ping me (and if you're taking it claim it in Phab). Places to start: ReferenceRecorder and LinksTableUpdater. [23:57:11] 10Thanks, 6Collaboration-Team-Backlog, 10MobileFrontend, 7Jenkins, 3Reading-Web: mwext-Thanks-qunit-mobile is failing on unrelated commit - https://phabricator.wikimedia.org/T108409#1520292 (10Mattflaschen) 3NEW [23:57:16] (03PS3) 10Mooeypoo: Add categories to the sidebar [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230017 (https://phabricator.wikimedia.org/T92874) [23:57:26] 10Thanks, 6Collaboration-Team-Backlog, 10MobileFrontend, 7Jenkins, 3Reading-Web: mwext-Thanks-qunit-mobile is failing on unrelated commit - https://phabricator.wikimedia.org/T108409#1520300 (10Mattflaschen) p:5Triage>3Unbreak! [23:58:30] (03CR) 10jenkins-bot: [V: 04-1] Add categories to the sidebar [extensions/Flow] - 10https://gerrit.wikimedia.org/r/230017 (https://phabricator.wikimedia.org/T92874) (owner: 10Mooeypoo) [23:58:49] matt_flaschen: hmm, I'm not sure if we still need the qunit-mobile jobs anymore...I'm asking Krinkle. [23:58:59] legoktm, okay, thanks.