[08:32:11] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2194310 (10Qgil) Is "draft" and "[WIP]" the same concept? [08:34:45] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2194311 (10Nemo_bis) >>! In T113706#2194310, @Qgil wrote: > Is "draft" and "[WIP]" the same concept? No. https://gerrit-review.googlesource.com/Documenta... [13:26:58] 6Team-Practices, 6Developer-Relations: Define Cut-off date for abandoning old changesets in our code review tool - https://phabricator.wikimedia.org/T113706#2194763 (10Tgr) >>! In T113706#2189829, @jayvdb wrote: > I would be very happy for stale/incomplete patches to being a draft rather than forcibly abandoni... [16:57:34] 6Team-Practices, 7Epic: [EPIC] TPG In Real Life meetings (April 6, 7, 8 2016) - https://phabricator.wikimedia.org/T131397#2195618 (10Awjrichards) 5Open>3Resolved [17:00:56] 6Team-Practices: Research possible next steps and possible customers for Phlogiston - https://phabricator.wikimedia.org/T132360#2195641 (10Awjrichards) [17:06:47] awjr jaufrecht: Should we have an epic for all the phate of phlogiston followups? [17:07:08] parent of T132360 and of a task I should probably create to write the possible outcomes [17:07:09] T132360: Research possible next steps and possible customers for Phlogiston - https://phabricator.wikimedia.org/T132360 [17:10:39] meeple27: makes sense to me [17:12:32] awjr: I can do that unless you already plan to [17:12:46] meeple27: go for it, i'm in the middle of some other stuff right now [17:12:50] thanks :) [17:14:04] 6Team-Practices: EPIC: Follow up from phate of phlogiston meeting - https://phabricator.wikimedia.org/T132365#2195745 (10ksmith) [17:14:12] 6Team-Practices: Research possible next steps and possible customers for Phlogiston - https://phabricator.wikimedia.org/T132360#2195758 (10ksmith) [17:14:39] 6Team-Practices, 10TPG-Essential-Functions, 7Epic: EPIC: Follow up from phate of phlogiston meeting - https://phabricator.wikimedia.org/T132365#2195745 (10ksmith) [17:16:22] 6Team-Practices, 10TPG-Essential-Functions: List possible outcomes of phate of phlogiston - https://phabricator.wikimedia.org/T132366#2195774 (10ksmith) [17:16:33] done [17:47:17] erm...and by "done" I meant that I hooked up the existing task and created my own task...now I'll see if there are others to hook up, or if I should create more subtasks [17:49:18] jaufrecht: I assume you don't need a phab task to schedule the next phate meeting? [17:51:21] right [17:51:34] I feel uncomfortable that we might be dropping some of the many followups from last week's meetings [17:52:33] I guess they are all in the etherpad? Can we move the etherpad to the wiki? Are we creating phab tasks for everything? If so, could we put the phab tasks into the etherpad (and then the wiki)? [18:03:20] jaufrecht: I used Kristen's meeting notes as if they were authoritative [18:03:42] if there were action items in the etherpad that didn't make it into the email, they need to be captured somehow/somewhere [18:06:46] maxbinder: can you easily point me to a phab task or 2 that i can review to prep for our mtg? [18:28:44] meeple27: sorry, was tied up with Web team [18:28:51] meeple27: there is not a phab task I think [18:29:00] ok that's fine [18:30:26] maxbinder: having bluetooth issues..will be on as soon as i can [18:31:12] meeple27: we're ready when you are [19:46:42] derp. has anyone encountered this error logging in to wikis: "Central user log in [19:46:42] No active login attempt is in progress for your session." [19:53:43] it seems like something I saw once [19:54:19] My advice: "try again"...."restart your browser"..."reboot your computer"....you know, tech support 101 [19:56:49] 06Team-Practices, 10TPG-Essential-Functions: List possible outcomes of phate of phlogiston - https://phabricator.wikimedia.org/T132366#2196563 (10ksmith) Draft WIP workspace: https://etherpad.wikimedia.org/p/Phlogiston_possible_outcomes [20:04:02] https://etherpad.wikimedia.org/p/q32016-TPG-review [20:35:49] 06Team-Practices, 10TPG-Essential-Functions: Identify ways to make "Status Quo" strategic possibility better - https://phabricator.wikimedia.org/T131101#2196714 (10ggellerman) [21:17:12] jaufrecht: here's the notetaking thing I just wrote about: https://www.mediawiki.org/wiki/User:RobLa-WMF#Loafers [21:17:29] it has the link to the paper I was referring to [21:17:40] 06Team-Practices, 06Release-Engineering-Team, 10Developer-Relations (Jul-Sep-2016): Developer Summit 2017: Work with TPG and RelEng on solution to event documenting - https://phabricator.wikimedia.org/T132400#2196957 (10Rfarrand) [21:36:24] cool. It's clearly a best practice to start every meeting with "who's taking notes?" and a few other housekeeping and structural things, and yet it's very hard to do so consistently [21:52:04] 06Team-Practices: [EPIC] TPG decides its work tracking plan for FY2016Q4 - https://phabricator.wikimedia.org/T132402#2197046 (10JAufrecht) [21:55:12] 06Team-Practices, 15User-JAufrecht: Write up TPG work tracking options - https://phabricator.wikimedia.org/T132403#2197058 (10JAufrecht) [22:00:02] 06Team-Practices: [EPIC] TPG decides its work tracking plan for FY2016Q4 - https://phabricator.wikimedia.org/T132402#2197082 (10JAufrecht) [22:19:30] 06Team-Practices: Improve or create WMF best practices for publishing meeting notes - https://phabricator.wikimedia.org/T132406#2197231 (10JAufrecht) [22:21:07] 06Team-Practices, 10Phlogiston↝General-Backlog, 10TPG-Essential-Functions, 07Epic, 15User-JAufrecht: [EPIC] Document usage of Phlogiston - https://phabricator.wikimedia.org/T119098#2197261 (10JAufrecht) [22:24:48] 06Team-Practices, 10Phlogiston↝General-Backlog, 10TPG-Essential-Functions, 07Epic, 15User-JAufrecht: [EPIC] Document usage of Phlogiston - https://phabricator.wikimedia.org/T119098#2197321 (10JAufrecht) [22:33:56] robla: jaufrecht: One wrinkle is that I am often fine being the scribe for one portion of a meeting, but not the whole thing. Either I want to fully participate in parts, or I am distracted and need to tune out. [22:34:31] TPG does a pretty good job of ad-hoc filling in the scribe role dynamically as needed throughout our meetings, but [22:34:49] 1) that's the kind of people we are, and 2) even we aren't always successful at it [22:35:01] so although I like that we do it, I can't recommend it as a practice [22:36:11] meeple27: we should figure out a non-disruptive best practice for handing off the baton. I could have used it this morning [22:38:08] perhaps a "scribe for this slide/section" field in the header [22:38:39] robla: yeah, we haven't gone for anything explicit...it's more that someone just becomes more active and others back off...or someone notices that notes are falling behind, and steps up [22:39:47] the "stepping up" thing happens on a team like TPG probably far more frequently than other teams, I think [22:42:45] definitely