[00:00:58] 6Phabricator, 10Gerrit-Migration: Plan for small "todo" author owned tasks - https://phabricator.wikimedia.org/T95987#1240481 (10Negative24) https://secure.phabricator.com/T6474 (and that then goes to https://secure.phabricator.com/T3820) would be needed if we implement a support model similar to T555 (what I'... [07:29:02] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1240995 (10NiharikaKohli) [10:39:40] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 10Possible-Tech-Projects, 10Wikimedia-Hackathon-2015, and 2 others: Possible Project for a Newsletter MediaWiki extension - https://phabricator.wikimedia.org/T76199#1241220 (10Qgil) Congratulations @Tinaj1234 and welcome to #Google-Summer-of-Code-2... [12:05:38] 6Project-Creators, 6CA-team: New Project: Privacy - https://phabricator.wikimedia.org/T92889#1241357 (10PerfektesChaos) 5Resolved>3stalled [12:07:08] 6Project-Creators, 6CA-team: New Project: Privacy - https://phabricator.wikimedia.org/T92889#1122781 (10PerfektesChaos) The new baby will need a workboard, but I don't know whether to create an empty one or copy an existing, and which parent? [12:32:14] 6Project-Creators, 6CA-team: New Project: Privacy - https://phabricator.wikimedia.org/T92889#1241411 (10Aklapper) 5stalled>3Resolved See above: [[ https://www.mediawiki.org/wiki/Phabricator/Project_management | Recommended practices for project and workboard management in Phabricator ]] are available (sect... [13:12:41] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1241466 (10NiharikaKohli) @Qgil, I'm a bit unclear on how the bonding period report differs from the bonding period e... [13:13:18] 6Project-Creators, 6Labs, 10Labs-Vagrant, 10Labs-project-extdist, and 10 others: Labs' Phabricator tags overhaul - https://phabricator.wikimedia.org/T89270#1241473 (10valhallasw) > Question: I'm also wondering if renaming Tool-Labs to #Tool-Labs-Infrastructure might make people realize it's not about proje... [13:29:45] 6Project-Creators: replace schema change tracking T51188 - https://phabricator.wikimedia.org/T97412#1241505 (10Springle) 3NEW [13:36:20] 6Engineering-Community, 3ECT-April-2015, 3Outreachy-Round-10: Community bonding evaluation for Newsletter Extension - https://phabricator.wikimedia.org/T97413#1241519 (10Tinaj1234) 3NEW a:301tonythomas [13:38:33] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 10Possible-Tech-Projects, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: GSoC'15 Proposal for Newsletter Extension Project - https://phabricator.wikimedia.org/T93583#1241531 (10Tinaj1234) [13:38:34] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 10Possible-Tech-Projects, 10Wikimedia-Hackathon-2015, and 2 others: Possible Project for a Newsletter MediaWiki extension - https://phabricator.wikimedia.org/T76199#1241532 (10Tinaj1234) [13:38:37] 6Engineering-Community, 3ECT-April-2015, 3Outreachy-Round-10: Community bonding evaluation for Newsletter Extension - https://phabricator.wikimedia.org/T97413#1241530 (10Tinaj1234) [13:39:05] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Community bonding evaluation for Newsletter Extension - https://phabricator.wikimedia.org/T97413#1241519 (10Tinaj1234) [13:44:14] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 10Possible-Tech-Projects, 10Wikimedia-Hackathon-2015, and 2 others: Possible Project for a Newsletter MediaWiki extension - https://phabricator.wikimedia.org/T76199#1241538 (1001tonythomas) >>! In T76199#1241220, @Qgil wrote: > Alright, let's start... [14:02:43] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1241587 (10Qgil) The bonding period evaluation task will be closed by the end of the bonding period, and therefore it... [14:04:02] 6Engineering-Community, 10MediaWiki-extensions-Newsletter, 10Possible-Tech-Projects, 10Wikimedia-Hackathon-2015, and 2 others: Possible Project for a Newsletter MediaWiki extension - https://phabricator.wikimedia.org/T76199#1241591 (10Tinaj1234) @01tonythomas, @Qgil - Thanks a lot for the opportunity. Crea... [14:07:36] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1241600 (10NiharikaKohli) Then how about keeping the detailed plan in the student proposals itself? They are already... [14:21:24] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1241619 (10Qgil) Keeping the plan in the student's proposal makes sense, since it's already there, yes. The communit... [14:43:38] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1241687 (10NiharikaKohli) [14:47:33] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1241689 (10NiharikaKohli) I updated the task accordingly. [14:51:26] 6Engineering-Community, 3ECT-April-2015, 3Google-Summer-of-Code-2015, 3Outreachy-Round-10: Goal: Successful start of all GSoC / Outreachy projects - https://phabricator.wikimedia.org/T94166#1241693 (10NiharikaKohli) @sitic, @sumit, @happy5214, @ferdbold, @Sarvesh.onlyme, @ankita-ks, @polybuildr, @vcamx, @p... [16:15:23] 6Phabricator, 10Wikimedia-Bugzilla, 6operations, 7Tracking: Tracking: Remove Bugzilla from production - https://phabricator.wikimedia.org/T95184#1241948 (10JohnLewis) [16:15:25] 6Phabricator, 10Wikimedia-Bugzilla: Complete migration of all Bugzilla users and their data - https://phabricator.wikimedia.org/T95266#1241946 (10JohnLewis) 5Open>3declined Right, I'm closing this (yet again) for the same reason listed multiple times. Please do **not** reopen this issue (as this is extrem... [16:16:20] andre__: ^ is starting to annoy me now. See my close (again) and feel to add anything if you ultimately need to but I asked questions to be answered that prove the issue is needed otherwise it's just disruptive/edit warring [16:36:27] 6Phabricator, 6operations: have any task put into ops-access-requests automatically generate an ops-access-review task - https://phabricator.wikimedia.org/T87467#1242033 (10mmodell) Doesn't phabricator always assume the author has access? maybe I can work around that. [16:36:42] JohnFLewis: It annoys me too. [16:44:42] andre__: I feel people are just finding un necessary reasons to keep deprecated services online because they want despite the technical implications (security) and maintenance. [16:45:21] likely. [16:57:04] 6Engineering-Community, 3ECT-April-2015, 3ECT-May-2015: Engineering Community quarterly goals for April-June 2015 - https://phabricator.wikimedia.org/T93770#1242082 (10Qgil) [17:01:34] 6Phabricator, 6operations: have any task put into ops-access-requests automatically generate an ops-access-review task - https://phabricator.wikimedia.org/T87467#1242086 (10chasemp) >>! In T87467#1242033, @mmodell wrote: > Doesn't phabricator always assume the author has access? maybe I can work around that.... [17:11:25] 6Phabricator, 10Wikimedia-Bugzilla, 6operations, 7Tracking: Tracking: Remove Bugzilla from production - https://phabricator.wikimedia.org/T95184#1242133 (10Nemo_bis) [17:11:27] 6Phabricator, 10Wikimedia-Bugzilla: Complete migration of all Bugzilla users and their data - https://phabricator.wikimedia.org/T95266#1242132 (10Nemo_bis) 5declined>3Open [17:14:39] andre__: and he's reopended it again with no comment. /me sighs [17:16:30] * andre__ could set the Edit policy [17:17:11] what issue is this? [17:18:14] <^d> "I think we discussed somewhere already that complete migration of Bugzilla users was not a goal." -> for the initial migration. [17:18:28] <^d> A discussion of whether that's eventually worthwhile now that dust has settled isn't a bad one to have. [17:19:08] it's basically impossible to say all [17:19:22] so many are noise / ephemeral / forgotten secondaries [17:19:34] <^d> All, sure. [17:19:50] <^d> Absolutes are bad, mmky :) [17:19:53] <^d> mmkay [17:20:01] it's just not possible nor feasible. [17:20:05] well complete migration rings of an 'all' [17:20:09] at least without someone saying it's not all [17:20:11] i guess [17:20:15] and I've asked Nemo in #wikimedia-tech if he can please stop reopening. [17:20:36] <^d> I don't think it hurts to have the task open while it's being discussed. [17:20:50] <^d> Edit warring over exact statuses is counterproductive compared to the actual question at hand [17:21:04] ^d: Well, if you have good counter-arguments, add them to the task. I don't see any good reasons. [17:21:22] People didn't use their accounts in BZ before either. It just wasn't that visible. Now it is in Phab. [17:21:35] ^d I think the fatigue comes into play here as well, andre__ and I have been battling some unrealistic expectations on this front [17:21:41] for a long time now, and one of those is the 'all' [17:21:56] or complete migration of every user before old bz changes state in any way [17:22:05] I'm not even really sure there has been a defined middle ground [17:22:12] <^d> Gotta be [17:22:13] <^d> :) [17:22:19] other than, where we are now [17:22:40] middle ground exists but not equally for all people :) [17:23:38] I personally don't care anymore [17:23:49] but the idea is useless unless someone figures out what they want [17:23:56] that isn't what we have now and intends to acheive it [17:23:57] "Make everybody use their accounts again" is just unrealistic. But that's what it boils down to, IMHO. [17:27:14] <^d> Middle ground: identify further dupe/alternate accounts and try to merge [17:27:18] <^d> ? [17:27:22] <^d> Might help some :) [17:27:25] are you willing to do it? [17:27:30] or do you know someone who is? [17:27:54] afaik it's all rhetoric from teh "it's not good enough yet" side of the conversation [17:28:19] <^d> Not right now, but I don't think it hurts to have a task open to be hopeful for a time when someone has found those extra hours in the day we're missing :) [17:28:47] that issue isn't really set for what you are proposing here [17:28:53] could coopt it and realign [17:28:59] <^d> Fair enough :) [17:29:02] but your argument would be objected to as well [17:29:34] thus, it's a never ending sea of pointlessness with no real value added [17:29:39] <^d> It's ok, I'm stubborn and can take it :p [17:29:45] and no one wants ot actually //do// anything [17:29:49] good enough for me [17:30:01] <^d> Oh, I've got about a bajillion things I want to do [17:30:05] <^d> This would be on the list. [17:30:09] <^d> It comes down to hours/day :) [17:30:24] if you don't see yourself doing it in teh next 5 years then I think the issue should be closed [17:30:25] honestly [17:30:28] and I doubt it happens [17:30:33] not because I think you couldn't but [17:30:40] because it's basically a useless exercise [17:30:46] <^d> We've had bugs open forever. No harm in wishlists imho [17:31:02] there is if it prevents bugzilla from dying [17:31:07] ^d: To me it boils down to: How to make people reclaim their email accounts (once used in BZ) in Phab if they might not have access to these accounts anymore (to confirm)? [17:31:07] <^d> (I for one don't find open bugs harmful. I suppose it hurts the pretty graphs that managers like :p) [17:31:08] and costs hours to maintain and keep up forever [17:31:12] I don't consider it solvable, simply. [17:31:30] ^d: yeah idk if the issue remains the sticking point is [17:31:55] is this issue worth the cost of putting effort into bz [17:32:00] <^d> Oh I don't think it's a blocker at all, long as we still have the BZ data in a dump [17:32:10] ^d: we will [17:32:17] <^d> Fuck, we could shut BZ off tomorrow for all I care :p [17:32:21] then you definitely need your own ticket :) [17:32:26] <^d> Long as the DB dump is about, we're good [17:32:48] sure no one cares about someone inteh future improving things afaik [17:32:53] ^d: the plan is getting rid of it about 2 weeks after legal give an okay to make the dump public [17:33:00] people only care about having to keep bz around for no reason [17:33:03] <^d> andre__: For "all" users, no. But I think identifying possible dupes with /existing/ users is an interesting possible middle ground (and worth its own task :)) [17:33:18] ^d, ah. there are some, I'm totally sure. [17:33:27] but that might be a different task. :P [17:33:31] <^d> Indeed [17:33:59] lots of fun things to do but it's basically orthogonal to this issue :) [17:34:10] of whether all users must claim their bz before bz can ever die [17:42:09] andre__: in all seriousness [17:42:10] "Otherwise we have no way to know and contact previous subscribers and they have no way to recover lost subscriptions when they register in Phabricator." [17:42:13] being teh argument [17:42:15] 6Phabricator, 10Gerrit-Migration, 6Labs: Stabilize vcs-user owned files and directories in Phab-02 - https://phabricator.wikimedia.org/T95982#1242353 (10coren) Given that only one instance uses this for the moment, this does not block turning off idmap. [17:42:38] teh second argument is invalid if it means account claiming in phab is somehow tied to bz [17:42:41] because it is not [17:43:17] Account claiming in Phab is not related to BZ being available if the DB (which is independent from BZ being online or not) is available, yeah. [17:43:26] (if my tech understanding is not entirely wrong suddenly) [17:43:45] maybe I should paste this very sentence in the task, for clearless. [17:43:47] bz isn't hit from phab at all during the process [17:43:55] and the other point is solved by the dumps [17:44:04] afaik [17:44:07] 6Project-Creators: Create Search-Team-Backlog project - https://phabricator.wikimedia.org/T97441#1242368 (10Deskana) 3NEW [17:44:30] it's beyond that even tho [17:44:36] account claiming in phab is not related to bz. [17:44:41] the db for bz has no relation [17:44:47] we have our own copy of the data [17:45:04] it was always intended not to rely on the legacy system [17:46:00] 6Project-Creators: Create Search-Team-Backlog project - https://phabricator.wikimedia.org/T97441#1242388 (10Krenair) Isn't this just the Backlog column on the #Search-Team workboard? [17:46:02] Yeah, maybe that is one point of misunderstanding because I didn't clearly express. In any case, I'll add a comment to the task. [17:46:22] 6Phabricator, 10Gerrit-Migration, 6Labs: Stabilize vcs-user owned files and directories in Phab-02 - https://phabricator.wikimedia.org/T95982#1242390 (10coren) [17:48:28] 6Project-Creators, 6Team-Practices: Create Search-Team-Backlog project - https://phabricator.wikimedia.org/T97441#1242397 (10Aklapper) Naively seconding Krenair here (if you don't plan to use your project as a "constant sprint"); also see https://www.mediawiki.org/wiki/Phabricator/Project_management#Workboard.... [17:49:33] 6Project-Creators, 6Team-Practices: Create Search-Team-Backlog project - https://phabricator.wikimedia.org/T97441#1242414 (10Deskana) @krenair Far from it. A backlog should have much more structure than a single ordered list. [17:51:47] 6Project-Creators, 6Team-Practices: Create Search-Team-Backlog project - https://phabricator.wikimedia.org/T97441#1242446 (10Deskana) We're planning to transition to a sprint-based structure at some point, but we want to ease in to that. Having a mega-board makes it pretty hard to get a picture of what's going... [17:52:08] 6Phabricator, 10Wikimedia-Bugzilla: Complete migration of all Bugzilla users and their data - https://phabricator.wikimedia.org/T95266#1242451 (10Aklapper) Kind of wondering if there are also some misconceptions involved: Claiming accounts in Phab (and previous activity imported from BZ) is not related to BZ... [17:57:17] 6Engineering-Community, 6ArchCom, 10Architecture, 3ECT-April-2015: Fix the Architecture Committee and the RfC process - https://phabricator.wikimedia.org/T87470#1242475 (10Spage) Post-reorg there's a dedicated Architecture team in the Technology group, its manager will take this on. [18:00:56] 6Project-Creators, 6Team-Practices: Create Search-Team-Freezer project - https://phabricator.wikimedia.org/T97441#1242504 (10Jdforrester-WMF) [18:02:50] 6Project-Creators, 10Search-Department-Freezer, 6Team-Practices: Create Search-Department-Freezer project - https://phabricator.wikimedia.org/T97441#1242368 (10Jdforrester-WMF) 5Open>3Resolved a:3Jdforrester-WMF [18:02:59] 6Project-Creators, 10Search-Department-Freezer, 6Team-Practices: Create Search-Department-Freezer project - https://phabricator.wikimedia.org/T97441#1242525 (10Jdforrester-WMF) Adjusted and executed per request. [18:07:50] 6Project-Creators, 10Search-Department-Freezer, 6Team-Practices: Create Search-Department-Freezer project - https://phabricator.wikimedia.org/T97441#1242541 (10Deskana) Thank you. [18:12:19] <^d> chasemp: is fab2 or fab3 in the 'gerrit' project still used anymore? [18:12:36] I think nope, should be all fair game? [18:13:07] <^d> I didn't think so, phab-\d\d are all in phabricator project now [18:13:28] I didn't actually spin any of them up but I believe so [18:15:08] <^d> fab2 was definitely me, ages ago [18:15:12] <^d> fab3 might have been me too [18:15:41] 6Project-Creators, 10Search-Department-Freezer, 6Team-Practices: Create Search-Department-Freezer project - https://phabricator.wikimedia.org/T97441#1242577 (10Aklapper) I expected the long-term backlog for the Search and Discovery Team to be tasks with lower priority values in the several existing search pr...