[12:47:10] 6Team-Practices, 6Release-Engineering, 5Testing Initiative 2015: Follow up workshop & brown bag ideas from Testing: Where does it hurt? - https://phabricator.wikimedia.org/T108122#1567114 (10hashar) [12:48:45] 6Team-Practices, 6Release-Engineering: Organize "testing: where does it hurt?" workshop for the end of July - https://phabricator.wikimedia.org/T102713#1567122 (10hashar) Seems the meeting followup is tracked by {T108122} [12:49:09] 6Team-Practices, 6Release-Engineering, 5Testing Initiative 2015: Follow up workshop & brown bag ideas from Testing: Where does it hurt? - https://phabricator.wikimedia.org/T108122#1567124 (10hashar) [12:49:52] 6Team-Practices, 6Release-Engineering, 5Testing Initiative 2015: Follow up workshop & brown bag ideas from Testing: Where does it hurt? - https://phabricator.wikimedia.org/T108122#1512611 (10hashar) [12:52:35] 6Team-Practices, 6Release-Engineering, 5Testing Initiative 2015: Follow up workshop & brown bag ideas from Testing: Where does it hurt? - https://phabricator.wikimedia.org/T108122#1567136 (10hashar) [12:53:21] 6Team-Practices, 6Release-Engineering, 5Testing Initiative 2015, 7Tracking: Follow up workshop & brown bag ideas from Testing: Where does it hurt? - https://phabricator.wikimedia.org/T108122#1512611 (10hashar) [12:53:34] 6Team-Practices, 6Release-Engineering, 5Testing Initiative 2015, 7Tracking: Follow up workshop & brown bag ideas from Testing: Where does it hurt? - https://phabricator.wikimedia.org/T108122#1512611 (10hashar) [13:02:24] 6Team-Practices, 6Release-Engineering, 5Testing Initiative 2015: Talk to Greg and Arthur about Onboarding's role in establishing good testing practices/habits - https://phabricator.wikimedia.org/T108121#1567165 (10hashar) #releng does provide the infrastructure to automatically run tests on patch proposal an... [16:31:49] mbinder: would you be free for a THC editing chat? [16:32:41] Sorry dstrine meeple27 I can't join this morning [16:32:54] ok yeah it was last minute [16:32:59] yup, and optional. no worries [17:54:32] ggellerman___: the video chats have identical names, so gcal hangouts gets confused [17:56:31] mbinder: poor gcal [17:57:17] ggellerman___: we can fix that, if you want, by changing the name of one of the meetings. I would do it after that meeting, though, because if someone joins before you change the name, they'll end up in hangout purgatory [18:08:00] ggellerman___: jaufrecht dstrine mbinder meeple27 just sent an email re lunch [18:08:26] got it [18:08:31] safe travels [18:09:50] awjr: Way to respond to change! ;) [18:10:22] awjr: ggellerman___: jaufrecht dstrine mbinder meeple27: I'll be late, too, but will find you in YB [18:14:14] anyone want to coordinate lunch-gathering? I'm thinking the Westlake food court. [18:21:14] I have a meeting running right up to noon so I will have to meet people at yerba buena [18:32:54] jaufrecht: I'm game for some pair-lunch-getting [19:13:43] I'm at the park in front of the fountain on the lower level, come find me [20:36:04] https://docs.google.com/a/wikimedia.org/presentation/d/1-vKluCuHa3LbD7g_UzBP6pY02IX1yaJzRI1-5NjqMxQ/edit?usp=sharing [21:28:55] awjr: So does your proposed product process require creating a product to manage all the bookkeeping as iteration 0? [21:29:30] Or do we actually have some tool that can do all of this high>low level zooming and process tracking?