Re: [teampractices] Code review social norms

On 03/16/2016 01:33 PM, Kevin Smith wrote: I'm curious what the inherent benefit is of having multiple people collaborate on a patch, as opposed to having a series of patches by different people, each of which advances the product incrementally. At least, it sounded like you (Rob) were

Re: [teampractices] Code review social norms

On 03/16/2016 02:33 AM, Rob Lanphier wrote: On Tue, Mar 15, 2016 at 8:03 PM, Mukunda Modell > wrote: On Tue, Mar 15, 2016 at 6:48 PM, Kevin Smith > wrote: I would mention

Re: [teampractices] Code review social norms

On 03/14/2016 03:40 PM, James Forrester wrote: On 14 March 2016 at 19:15, Greg Grossmeier >wrote: (CC'ing Matt F who lead the "Make code review not suck" session at WikiDev16, not sure if his on the list or not.) Related to the other

Re: [teampractices] [FYI] connection between great teams and psychological safety

I read that article as well .. To me, this section stood out: /"What Project Aristotle has taught people within Google is that no one wants to put on a ‘‘work face’’ when they get to the office. No one wants to leave part of their personality and inner life at home. But to be fully present at

Re: [teampractices] Converting etherpad notes to wiki markup

On 02/17/2016 11:09 AM, Max Binder wrote: Anyone have a process or tool for this besides manually editing the text in an etherpad? I've encountered this hiccup with a few teams now. Most folks I've talked to about it would like an easy way to transfer text from etherpads to wikis quickly,

Re: [teampractices] Document what should be a column on Phab workboards and what better not?

I did not see this email till now. Yes, the Parsoid board is a weird mix of columns right now I was experimenting with what makes sense and I initially thought of making it process-specific, and then thought perhaps it can be a place for easy access to different categories of tasks