Change Details

**Type of activity:** //Pre-scheduled session// (or //Unconference session// if not accepted) **Main topic:** How to grow our technical community / How to manage our technical debt **Etherpad:** https://etherpad.wikimedia.org/p/devsummit17-CodeReview == The problem == Whether and when code review will happen is not predictable which can be demotivating to someone who contributed a code change proposal. Our backlog of unreviewed/unmerged patches grows. Concentrating on those performing reviews, potential problems might be: * Lack of time (or CR not being prioritized by managers) * Lack of maintainership / 'responsibility feeling' * Lack of skill or confidence to perform {effective / good} CR * Lack of interest in doing CR == Expected outcome == Discuss some of these items with an organizational and social focus (and mostly ignore technical aspects of CR tools) and how to improve the situation. Exchange and document best practices, and discuss how to foster them in other development teams. == Current status of the discussion == tbd == Links == * (More specific) sequel to last time's {T114419} * [[ https://www.mediawiki.org/wiki/Topic:Tdd8msmgw8864ig2 | Previous discussion about this very proposal ]] * Previous ideas and activities: https://lists.wikimedia.org/pipermail/wikitech-l/2016-March/085042.html

**Type of activity:** //Pre-scheduled session// (or //Unconference session// if not accepted) **Main topic:** How to grow our technical community / How to manage our technical debt **Etherpad:** https://etherpad.wikimedia.org/p/devsummit17-code-review-processes == The problem == Whether and when code review will happen is not predictable which can be demotivating to someone who contributed a code change proposal. Our backlog of unreviewed/unmerged patches grows. Concentrating on those performing reviews, potential problems might be: * Lack of time (or CR not being prioritized by managers) * Lack of maintainership / 'responsibility feeling' * Lack of skill or confidence to perform {effective / good} CR * Lack of interest in doing CR == Expected outcome == Discuss some of these items with an organizational and social focus (and mostly ignore technical aspects of CR tools) and how to improve the situation. Exchange and document best practices, and discuss how to foster them in other development teams. == Current status of the discussion == tbd == Links == * (More specific) sequel to last time's {T114419} * [[ https://www.mediawiki.org/wiki/Topic:Tdd8msmgw8864ig2 | Previous discussion about this very proposal ]] * Previous ideas and activities: https://lists.wikimedia.org/pipermail/wikitech-l/2016-March/085042.html

**Type of activity:** //Pre-scheduled session// (or //Unconference session// if not accepted) **Main topic:** How to grow our technical community / How to manage our technical debt **Etherpad:** https://etherpad.wikimedia.org/p/devsummit17-CodeRcode-review-processes == The problem == Whether and when code review will happen is not predictable which can be demotivating to someone who contributed a code change proposal. Our backlog of unreviewed/unmerged patches grows. Concentrating on those performing reviews, potential problems might be: * Lack of time (or CR not being prioritized by managers) * Lack of maintainership / 'responsibility feeling' * Lack of skill or confidence to perform {effective / good} CR * Lack of interest in doing CR == Expected outcome == Discuss some of these items with an organizational and social focus (and mostly ignore technical aspects of CR tools) and how to improve the situation. Exchange and document best practices, and discuss how to foster them in other development teams. == Current status of the discussion == tbd == Links == * (More specific) sequel to last time's {T114419} * [[ https://www.mediawiki.org/wiki/Topic:Tdd8msmgw8864ig2 | Previous discussion about this very proposal ]] * Previous ideas and activities: https://lists.wikimedia.org/pipermail/wikitech-l/2016-March/085042.html