[00:08:11] 6Engineering-Community, 10Wikimedia-Hackathon-2015, 3ECT-May-2015: Engage with established technical communities at the Wikimedia Hackathon 2015 - https://phabricator.wikimedia.org/T76325#1267595 (10Rfarrand) Two people from NASA will be coming. 20 - 25 students from Epitech will be coming and camping on the... [00:12:28] 6Engineering-Community, 6Team-Practices: Tech Talk: June 2015: Kanban - https://phabricator.wikimedia.org/T95202#1267600 (10Rfarrand) any thoughts @ksmith ? :) [00:22:06] i see a ticket that is "blocked by" another one, yet it was closed/resolved before the blocker was resolved [00:22:09] bug? [00:38:31] 6Engineering-Community, 6Phabricator, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10, and 3 others: Enable Conpherence for all Wikimedia Phabricator users - https://phabricator.wikimedia.org/T91392#1267640 (10Bawolff) >"How about we have less private conversations" Actually that part of my comment might... [00:42:17] mutante, it's possible to do that in phabricator [00:42:25] it was possible in bugzilla [00:42:47] ok? but that's the point of blocking [00:43:40] then it's more like "refers to" [00:43:56] which i miss sometimes [00:44:43] hmm.. merge doesnt merge and block doesnt block [00:46:01] mutante, it's for displaying to the user [00:46:11] it's not supposed to restrict users from doing things [00:47:01] the result is we have tasks closed and what is supposed to block them is still open [00:47:27] the user wouldn't be restricted because he can remove the block [00:47:28] oh well [00:47:34] not necessarily [00:47:44] remember phabricator allows you to do silly things with edit policies [00:48:28] i dont [00:48:32] well yea [00:48:36] maybe [00:57:32] 6Engineering-Community, 6Phabricator, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10, and 3 others: Enable Conpherence for all Wikimedia Phabricator users - https://phabricator.wikimedia.org/T91392#1267671 (10Qgil) >>! In T91392#1265570, @scfc wrote: > When mail for #Tool-Labs users was introduced, IIRC... [03:14:01] 6Phabricator, 6WMF-Legal, 5Patch-For-Review: In the footer, make "Creative Commons Attribution-ShareAlike 3.0 License" and "GNU General Public License" links - https://phabricator.wikimedia.org/T94946#1267836 (10Josve05a) [06:28:33] 6Phabricator: Hide PhabricatorManiphestApplication link icon - https://phabricator.wikimedia.org/T98328#1267972 (10Nemo_bis) Yes, I noticed. [06:39:09] 6Engineering-Community, 3ECT-May-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Community bonding evaluation for "Implement Flow support in Pywikibot" - https://phabricator.wikimedia.org/T98443#1267980 (10happy5214) 3NEW a:3jayvdb [06:44:49] 6Engineering-Community, 3ECT-May-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Community bonding evaluation for "Implement Flow support in Pywikibot" - https://phabricator.wikimedia.org/T98443#1267989 (10happy5214) [07:31:42] 6Project-Creators: Implement Flow support in Pywikibot - https://phabricator.wikimedia.org/T98444#1268010 (10happy5214) 3NEW [09:02:47] 6Engineering-Community, 3ECT-May-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1268168 (10NiharikaKohli) [09:16:41] 6Phabricator, 6Release-Engineering: Next Phabricator upgrade on 2015-05-20 (tentative) - https://phabricator.wikimedia.org/T98451#1268189 (10mmodell) 3NEW a:3mmodell [11:51:43] 6Project-Creators: Create Pywikibot-Flow project - https://phabricator.wikimedia.org/T98444#1268363 (10Qgil) [11:52:06] 6Project-Creators: Create Pywikibot-Flow project - https://phabricator.wikimedia.org/T98444#1268010 (10Qgil) [12:05:28] 6Project-Creators: Requesting a new project for GSoC 2015 - https://phabricator.wikimedia.org/T98291#1268403 (10Qgil) [12:07:46] 6Project-Creators: Create Pywikibot-OAuth project - https://phabricator.wikimedia.org/T98291#1268425 (10Qgil) 5Open>3Resolved p:5Triage>3Normal [12:08:09] 6Project-Creators, 10Pywikibot-OAuth: Create Pywikibot-OAuth project - https://phabricator.wikimedia.org/T98291#1263962 (10Qgil) Done: #Pywikibot-OAuth [12:12:55] 6Project-Creators: Create Pywikibot-Flow project - https://phabricator.wikimedia.org/T98444#1268459 (10Qgil) 5Open>3Resolved p:5Triage>3Normal [12:13:18] 6Project-Creators, 10Pywikibot-Flow: Create Pywikibot-Flow project - https://phabricator.wikimedia.org/T98444#1268010 (10Qgil) Done: #pywikibot-flow [12:15:59] 6Engineering-Community, 6Community-Liaison, 7Documentation: Improve glossaries to better help Wikimedia editors understand technical terms - https://phabricator.wikimedia.org/T90263#1268476 (10Qgil) Adding some projects just to give parents to this orphan. [12:17:12] 6Engineering-Community, 6Community-Liaison, 7Documentation: Set up a platform to create, edit and query meta wiki taxonomies - https://phabricator.wikimedia.org/T90030#1268479 (10Qgil) Just bringing some parents to this orphan task. [12:34:16] 6Phabricator, 10Phabricator-Sprint-Extension: Have Story Points field on the "Create New Task" modal - https://phabricator.wikimedia.org/T96953#1268536 (10Christopher) p:5Triage>3Normal [12:40:14] 6Phabricator, 10Phabricator-Sprint-Extension: Maniphest Task Query from Sprint Board is showing Tasks from all Projects - https://phabricator.wikimedia.org/T98464#1268565 (10Christopher) 3NEW a:3Christopher [12:40:58] 6Phabricator, 10Phabricator-Sprint-Extension: Maniphest Task Query from Sprint Board is showing Tasks from all Projects - https://phabricator.wikimedia.org/T98464#1268573 (10Christopher) [12:42:19] 6Phabricator, 6Team-Practices: Migration of Analytics Research & Data to Phabricator - https://phabricator.wikimedia.org/T826#1268576 (10Qgil) I just learned about #Search-and-Discovery-Research-and-Data-Sprint Progress! [12:46:17] 6Phabricator, 6Team-Practices, 6WMF-Design, 6WMF-Design-Research: Migration of the Design team to Phabricator - https://phabricator.wikimedia.org/T832#1268581 (10Qgil) a:5Jaredzimmerman-WMF>3None [12:49:17] 6Phabricator, 6Team-Practices, 6WMF-Design, 6WMF-Design-Research: Migration of the Design team to Phabricator - https://phabricator.wikimedia.org/T832#1268583 (10Qgil) Now there is no single Design team, but different teams embedded in different verticals. How is this impacting the use of the existing Trel... [12:50:40] 6Phabricator, 6Mobile-Apps: Migration of Mobile Apps team to Phabricator - https://phabricator.wikimedia.org/T851#1268587 (10Qgil) Any news on this front? I just want to know when can we consider this transition completed and this task Resolved. [12:52:49] 6Phabricator, 10Phabricator-Sprint-Extension: Maniphest Task Query from Sprint Board is showing Tasks from all Projects - https://phabricator.wikimedia.org/T98464#1268592 (10Christopher) p:5Triage>3Normal a:5Christopher>3None [12:52:52] 6Phabricator: Migration of Mobile Web team to Phabricator - https://phabricator.wikimedia.org/T830#1268593 (10Qgil) Now there is no single Mobile Web team, but Desktop & Mobile Web under Reading. How is this impacting the use of Trello / Phabricator, and what needs to happen to consider this task Resolved? [12:53:51] 6Phabricator, 10Phabricator-Sprint-Extension: Maniphest Task Query from Sprint Board is showing Tasks from all Projects - https://phabricator.wikimedia.org/T98464#1268565 (10Christopher) [12:54:21] 6Phabricator, 6Zero: Migration of the Zero team to Phabricator - https://phabricator.wikimedia.org/T88978#1268596 (10Qgil) I wonder what is the status of this task after the Engineering reorganization. As far as I can see in the org chart, there are no engineers assigned solely to a Zero team. [13:13:36] 6Phabricator, 7Mobile: Uploading on mobile - https://phabricator.wikimedia.org/T89580#1268636 (10Nnemo) [13:42:13] 6Phabricator, 10Phabricator-Upstream: Phabricator should only notify changes to the "Security" field if it is indeed changed - https://phabricator.wikimedia.org/T87135#1268752 (10Qgil) Is it just me and my subjective (lack of) memory, or we haven't seen this message for a while now? [13:46:45] 6Phabricator, 10Phabricator-Upstream: Phabricator should only notify changes to the "Security" field if it is indeed changed - https://phabricator.wikimedia.org/T87135#1268769 (10matmarex) Yesterday: T98425 It happens the first time a task is edited after its creation (using the full form, not the comment for... [14:01:04] 6Engineering-Community, 6Community-Liaison, 10Wikimedia-General-or-Unknown: Wikimedia wikis need better issue reporting system - https://phabricator.wikimedia.org/T29852#1268813 (10Nemo_bis) [14:01:36] 6Engineering-Community, 6Community-Liaison, 10Wikimedia-General-or-Unknown: Wikimedia wikis need better issue reporting system - https://phabricator.wikimedia.org/T29852#332110 (10Nemo_bis) > some of the statements of the task description are not valid anymore. Fixed. [14:03:19] 6Engineering-Community, 6Community-Liaison, 10MediaWiki-General-or-Unknown, 10Possible-Tech-Projects: Overall Feedback Button - https://phabricator.wikimedia.org/T97019#1268815 (10Nemo_bis) [14:03:21] 6Engineering-Community, 6Community-Liaison, 10Wikimedia-General-or-Unknown: Wikimedia wikis need better issue reporting system - https://phabricator.wikimedia.org/T29852#1268816 (10Nemo_bis) [14:13:20] 6Engineering-Community, 6Release-Engineering, 6Team-Practices: RelEng team offsite - May 2015 - Pre Wikimedia Hackathon - https://phabricator.wikimedia.org/T89036#1268878 (10Qgil) [14:54:11] 6Phabricator, 10Phabricator-Sprint-Extension: Maniphest Task Query from Sprint Board is showing Tasks from all Projects - https://phabricator.wikimedia.org/T98464#1269054 (10Christopher) This is the result of 04-26-2015 upstream change https://secure.phabricator.com/rPbe14f752749bfabc51d9ae530376ebbba1a83b5b F... [14:57:51] 6Engineering-Community, 6Team-Practices: Tech Talk: June 2015: Kanban - https://phabricator.wikimedia.org/T95202#1269067 (10ksmith) @Rfarrand Ok, I can do June 1. It puts some pressure on, but that's OK. I'll try to come up with a summary this week, but no promises. [16:03:24] 6Project-Creators: Create "German-community-wishlist" project - https://phabricator.wikimedia.org/T96366#1269316 (10Tobi_WMDE_SW) 5Open>3Resolved a:3Tobi_WMDE_SW Done: https://phabricator.wikimedia.org/project/profile/1248/ [16:23:53] 6Phabricator, 6Mobile-Apps: Migration of Mobile Apps team to Phabricator - https://phabricator.wikimedia.org/T851#1269399 (10KLans_WMF) The final step is to run the Trello import script. We've been holding off on this while we get used to Phabricator and figure out ideal workflows. We're probably getting to a... [16:26:59] 6Phabricator: Migration of Mobile Web team to Phabricator - https://phabricator.wikimedia.org/T830#1269411 (10KLans_WMF) The final step is to run the Trello import script. We've been holding off on this while we get used to Phabricator and figure out ideal workflows. We're probably getting to a place where we ca... [19:10:11] 6Phabricator, 10Phabricator-Upstream: Phabricator should only notify changes to the "Security" field if it is indeed changed - https://phabricator.wikimedia.org/T87135#1269833 (10mmodell) I've tried everything I can think of to fix this, I really don't know of any solution. [21:02:21] 6Engineering-Community, 6Team-Practices: Tech Talk: June 2015: Kanban - https://phabricator.wikimedia.org/T95202#1270506 (10Rfarrand) @ksmith Sounds good! I have reserved the largest conference room for us. Do you prefer 10am - 11am, or 11am - 12am? No major rush on the summary, just the sooner I get it th... [21:17:08] 6Engineering-Community, 6Team-Practices: Tech Talk: June 2015: Kanban - https://phabricator.wikimedia.org/T95202#1270531 (10ksmith) @Rfarrand Probably 11-12 is better. It gives those night-owl engineers a bit more time to wake up. :) [21:18:21] 6Engineering-Community, 6Team-Practices: Tech Talk: June 2015: Kanban - https://phabricator.wikimedia.org/T95202#1270537 (10ksmith) @Rfarrand Oh, or maybe 10-11 is better in case eurofolk want to participate. I guess I'll favor 10-11 but am open to whichever you think would be better. [23:24:21] 6Engineering-Community, 6Team-Practices: Tech Talk: June 2015: Kanban - https://phabricator.wikimedia.org/T95202#1270963 (10ksmith) Title: Kanban: An alternative to Scrum? Summary: Kanban is becoming a popular buzzword in software development. Some teams are looking at starting with a Kanban process as a st...