[00:37:03] wrapping up for the day here. Please grab me before I head out if you need anything :) [01:58:07] jaufrecht: I'm close to being convinced that a column at the right edge of our product backlog board ("team-practices"). I would say to create a phab ticket for that, and maybe bring it up at the retro. I would love to do some board and column renaming at the same time, or at least consider doing so. [15:48:35] HR recommended that Max and I add the WMF staff calendar. there is a re-org feedback meeting at 9am. is this something we should attend? Does anyone else watch the staff calendar? [15:52:45] dstrine: I wouldn't particularly recommend atending the 9am, although you could take your laptop up and observe while getting work done [15:53:35] it is a follow-up to solicit additional feedback about the re-org. But it is purely collecting information. It is not intended to provide answers. (That comes later in the process) [15:53:46] I am heading up there myself, but will be working through it [15:54:19] ok thanks I just followed a few people up to the 5th floor [16:01:39] mbinder: https://office.wikimedia.org/wiki/Systems_guide_for_new_hires [16:02:35] TPG! [16:02:43] 4 eva [16:03:51] we used skype at my last org, which was awful in many ways, but I miss the emoji of the little man bowing in respect... [16:14:22] 🐙 [16:14:30] not quite the same i guess [16:26:41] excellent mustache alternative tho [16:27:35] lol i thought it was a squid? [16:28:17] 🙇 [16:28:42] that's really hard to see but it's a little man bowing! [16:28:54] and c'mon, that's totally an octopus [16:29:17] though I will compromise at cuttlefish [16:30:14] * andre__ double-checks this channel is not #wikimedia-kawaii [16:30:49] tehe [16:31:11] andre__: btw thanks for the reminder email - i'm going to followup with you later this afternoon [16:32:08] Sorry but my afternoon is already over. ;)) [16:32:10] more seriously: thanks and no worries. :) [16:32:28] :D [16:37:06] * meeple27 uses his camera time to subtly advance the idea of "Tropical Attire Fridays" [16:39:29] first-hand experience: he is, indeed, wearing a very colorful and tropics-themed shirt 👍 [16:40:55] 🐠🌴🍹 [16:41:24] this emoji thing is gonna kill my productivity [16:41:25] awjr: as with your squid? above, all I got there was some unrenderable unicode codes [16:42:02] meeple27: :( [16:43:03] https://blog.irccloud.com/emoji/ [17:32:39] http://hat.jit.su/91808 [18:25:23] meeple27: are you planning to come to the health check thing with the engineering managers? [18:25:37] awjr: I'm already in the room and hangout [18:25:41] awesome! [18:25:47] would you mind taking notes during the discussion portion? [18:25:51] meeple27: ^ [18:25:53] sure [18:25:55] ithanks :D [18:26:13] i expect it'll be about the last half [21:23:53] jaufrecht is gone. He never leaves. irccloud fail? [21:36:49] 6Team-Practices: Document WMF's unmet requirements for Phabricator - https://phabricator.wikimedia.org/T101562#1342461 (10JAufrecht) 3NEW [22:05:32] meeple27: yeah there was an outtage with IRCCloud [22:05:59] saga documented here: https://twitter.com/IRCCloud [22:14:35] meeple27, where is your wiki document that is a report on the basic processes of your team? [22:15:44] meeple27: early you mentioned you were trying to advance the idea of "tropical attire fridays" - should we start by making a team norm? [22:17:24] I'mma need to do some shoppin' [22:17:31] could someone clarify the difference between this page (https://office.wikimedia.org/wiki/User:MBinder_%28WMF%29) and this page (https://wikimediafoundation.org/wiki/User:MBinder_%28WMF%29)? I know we should make one and point the others to that one, but I'm unclear which one is the one. :) [22:17:40] office is private [22:17:49] I made wikimediafoundation my one true page [22:17:57] and put pointers on the others [22:19:11] gotcha, so if I want to keep them both, the "point-to-one" best practice, beyond the fact that there are actually 2 pages, should be the public facing page? [22:19:54] yes [22:19:58] thx [22:21:29] I made my pointers actual redirects, but noticed some TPG folks used links, instead. Is that a better practice, or just a personal preference? [22:22:06] the official advice (somewhere) was to have the foundation wiki be your primary user page, and everything else should point there [22:22:56] also meta.wikimedia.org since that (via SUL) takes care of all the wikipedias etc. [22:23:13] mbinder: I think I saw some official-looking advice to do it as a link, but I assume a redirect is perfectly acceptable [22:23:31] awjr: Tropical Fridays as a norm! \o/ [22:23:39] +1 [22:23:51] and, of course, Wednesdays we wear pink [22:24:00] +1 [22:24:10] jaufrecht: I was going to remind you about those 2 issues at the bottom of the retro that you wanted to follow up on, regarding comparing notes about email filtering and something else [22:24:23] mbinder: Hm. I'll have to do shoppin' for that one [22:24:48] awjr: should someone create a phab task to sanitize the retro notes for public posting? [22:26:18] meeple27: i am in the middle of drafting that email :) [22:26:30] :D [22:27:37] dstrine: In your google drive "shared with me", you should have access to the Q3 health check summary [22:28:47] awjr: We should also post today's deck on the TPG page, yes? [22:28:56] deck = emgt presentation [22:29:50] meeple27: i don't think so since the audience was specifically emgt [22:30:04] oh. I thought q2 was already there [22:30:10] but i was planning on sharing the deck with everyone in emgt so folks who missed the talk today could review it [22:30:19] ah that's probably our quarterly review [22:30:37] meeple27: are you looking at what's under 'how we have done' on the team page? [22:30:48] right [22:30:55] sounded similar [22:32:08] perhaps you could give that link a title so it's clear what kind of Q2 activity it was [22:32:09] Kevin, here's a skeleton of a Foundation Team process survey: https://www.mediawiki.org/wiki/WMF_Processes_Survey [22:32:22] you could add your team's process and link to your report [22:34:02] jaufrecht: Sure. but can I rename "Release Cycle" to "Cadence"? [22:34:08] sure [22:34:17] although we probably need yet another term [22:34:29] cadence, to me, is a general rhythm, but a rhythm for what? [22:34:52] if a team has a two-week sprint period and releases every four weeks, what's its "Cadence"? [22:37:18] "Iteration Length" [22:37:31] you can't release more frequently than that (except in emergencies) [22:37:52] you might release each iteration, or monthly, or quarterly, or annually, or however often you feel like (on an iteration bound) [22:37:54] VE has a quarterly iteration and a weekly release [22:38:14] so I think maybe we need descriptive, not normative, terms for these columns [22:38:16] I would be fine with Iteration Length and Release Frequency columns [22:38:39] the underlying principles being, how often does the team release code to an external audience, which is fairly objective, [22:38:48] Technically with Kanban we don't have iterations, but in reality we have weekly meetings [22:38:49] and how often does the team do some kind of planning? [22:39:06] how often *does* the team release, or *could* the team release? [22:39:18] Those two activities, Release and Planning, are fairly universal, but what terms are neutral with respect to Scrum, etc? [22:39:25] VE does release every week [22:39:55] Discovery releases stuff sometimes [22:40:02] This is a high-level survey, so does vs could already sounds too specific [22:40:20] I think few teams DO release on a tight schedule, but I could be wrong [22:40:23] can we handwave that distinction away for this survey without being misleading? [22:40:26] tight = regular [22:40:58] I think most teams have an opportunity to release weekly, on the train [22:41:01] "Planning Frequency" and "Release Frequency", and then you could put "weekly" or "weekly if necessary" or "weekly in theory, but has actually only released twice in the last six years" or whatever [22:41:21] whatever seemed helpful to someone skimming a list of 10+ teams [22:41:26] but 2/3 of Discovery isn't on the train, and I think FR tech is (mostly?) not on the train, and mobile apps is not on the train [22:41:41] I can live with that [22:42:05] so with True Scrum it would be something like 2 weeks, 2 weeks [22:42:44] and with true Kanban it would be daily, any time, as needed [22:42:55] daily, any time (as needed) [22:43:02] sounds fine [22:43:43] so for Discovery it would be weekly, as needed [22:50:05] 6Team-Practices: Write up experiences from the Scrum Gathering in Phoenix to share with team - https://phabricator.wikimedia.org/T101568#1342643 (10Awjrichards) 3NEW [22:50:24] 6Team-Practices: Write up experiences from the visit to Spotify in Stockholm to share with team - https://phabricator.wikimedia.org/T101569#1342651 (10Awjrichards) 3NEW [22:50:36] 6Team-Practices: Write up experiences from the RelEng workshop to share with team - https://phabricator.wikimedia.org/T101570#1342659 (10Awjrichards) 3NEW [23:56:06] is it weekend yet 0________________o [23:56:28] kristenlans: YES go home! [23:56:44] ah, awjr, I'm already there! [23:57:09] "if you worked here, you'd be home by now" [23:57:14] lolol [23:58:12] But seriously everyone should stop working and celebrate Friday now [23:59:44] weeeee