Re: [teampractices] Who doesn't love calendars?

On Thu, Apr 7, 2016 at 11:05 AM, Quim Gil wrote: > Some of you might have realized that we have a problem of calendars in > Wikimedia. If you are interested in improving / resolving this problem at > least in the context of Wikimedia Tech, please check > https://phabricator.wikimedia.org/T1035#21

[teampractices] Apologies to Greg (Re: Code review social norms)

ions before letting them spill onto public mailing lists. Rob On Tue, Mar 15, 2016 at 6:37 PM, Rob Lanphier wrote: > On Tue, Mar 15, 2016 at 11:26 AM, Greg Grossmeier > wrote: > >> >> > On Mon, Mar 14, 2016 at 12:40 PM, James Forrester < >> jforres...@wikimedia.o

Re: [teampractices] Code review social norms

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 that in some cases, I would prefer to accept the commit >> as is, and then perform minor refactoring, such as changing a name, fixing >> a typo, or rearranging the co

Re: [teampractices] Code review social norms

On Tue, Mar 15, 2016 at 11:26 AM, Greg Grossmeier wrote: > > > On Mon, Mar 14, 2016 at 12:40 PM, James Forrester < > jforres...@wikimedia.org> > > wrote: > > > > > On 14 March 2016 at 19:15, Greg Grossmeier wrote: > > > > > >> Backgroun: > > >> * This started as this task in our Phab: > > >>

Re: [teampractices] Code review social norms

On Mon, Mar 14, 2016 at 12:40 PM, James Forrester wrote: > On 14 March 2016 at 19:15, Greg Grossmeier wrote: > >> Backgroun: >> * This started as this task in our Phab: >> https://phabricator.wikimedia.org/T121751 "Document best practices to >> amend a change written by another contributor"

[teampractices] Fortune article about "The Open Organization"

Hi folks, I thought you all might be able to glean some insights worth sharing from a book written by Jim Whitehurst. Jim Whitehurst took over at Red Hat CEO a few years ago, and wrote a book called "The Open Organization". Fortune wrote a small piece about his book: http://fortune.com/2015/06/0

Re: [teampractices] [Discussion] Term for always prepping for the next thing

On Mon, Sep 7, 2015 at 1:27 PM, Max Binder wrote: > Everything is set at an equally high priority, with each upcoming task > usurping the priority of the current task. There are no low priority moments > because stress of the upcoming tasks is the motivator to do the work. I also > do believe that

Re: [teampractices] [Discussion] Term for always prepping for the next thing

On Fri, Sep 4, 2015 at 1:27 PM, Max Binder wrote: > The future tasks matter, but so do the current tasks, and yet in order to > execute the next task, a sacrifice is made to current productivity. > I think the term you may be looking for is "analysis paralysis

Re: [teampractices] how to mark tasks as high, but not immediate, priority

On Mon, Feb 9, 2015 at 10:00 AM, S Page wrote: > Leave it Normal priority but move the task near the top of its column in the > backlog or next sprint workboard. I agree with this. For what it's worth, I think "Low" and "Needs Volunteer" priority are severely underutilized. "Normal" should mea

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

On Sat, Feb 7, 2015 at 9:50 PM, Greg Grossmeier wrote: > > > But, I am now thinking of removing some of the columns that can be > > subprojects and use the custom queries that you mention below. But, the > > custom queries would have to be bookmarks or be stored on some wiki page > .. > > so it

[teampractices] The "Epic" tag

Hi folks, Chad recently created the "Epic" Phab tag for our use in the MediaWiki Core team (for this epic , not this epic ). Basically, we want to use Phabricator to track proje

Re: [teampractices] mingle seats

On Fri, Nov 7, 2014 at 11:53 AM, Bryan Davis wrote: > The matrix view is cute, but once everything is in Phabricator it > seems like there could just be a project for each team (like > ) and a > project for SoS. Tag your issues with your

Re: [teampractices] Bugzilla migration Re: Project management tools review: Regressions/tradeoffs; migration

On Tue, Mar 25, 2014 at 4:50 PM, Quim Gil wrote: > If we end up going for Phabricator... it looks like the main bottleneck is > the migration from Bugzilla (based on casual conversations with Andre and > Chad). > > Going for Phabricator while keeping Bugzilla would be a half-backed > solution tha

Re: [teampractices] Project management tools review: Regressions/tradeoffs; migration

On Tue, Mar 25, 2014 at 9:14 AM, Andre Klapper wrote: > * How to do cross-component tagging ("keywords"): If nothing similar > exists, use dependencies? Are keywords important to us? Hi Andre, I became intensely curious about this after our conversation this morning, so I did a little searching

Re: [teampractices] Scrum-y tools based on BZ (was Re: Scrumbu.gs)

On Thu, Oct 31, 2013 at 12:47 PM, Matthew Flaschen wrote: > I don't think we should get into weird substitutions just because people > are edit warring. > > The active maintainers/team (whether they be volunteer or WMF) should have > the final say on prioritization and which bugs are open. > > Low