+googol
On Wed, Jul 1, 2015 at 9:49 AM, Dan Garry dga...@wikimedia.org wrote:
I'm creating epics to track the Discovery Department Q1 2015-16 goals
https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q1_Goals#Discovery,
and thought it might be useful to track organisation-wide
aricha...@wikimedia.org
wrote:
On Mon, Jun 8, 2015 at 9:25 AM, James Douglas jdoug...@wikimedia.org
wrote:
A team should review their open patchsets before writing new code.
+1, this is a great way to remind ourselves to focus on priorities.
While in principle I agree with this notion, I
...@wikimedia.org wrote:
On 9 June 2015 at 09:44, James Douglas jdoug...@wikimedia.org wrote:
Wouldn't that a misprioritization?
In a literal sense, yes. However, as the curators and owners of an open
source project, we have a responsibility to review code contributed by our
volunteers
Exactly. And thus a team prioritizing Bar might continue coding on Bar,
allowing the queue of pending Foo code reviews to pile up.
Bingo!
On Tue, Jun 9, 2015 at 1:55 PM, Kevin Smith ksm...@wikimedia.org wrote:
On Tue, Jun 9, 2015 at 1:10 PM, James Douglas jdoug...@wikimedia.org
wrote
A team should review their open patchsets before writing new code.
+1, this is a great way to remind ourselves to focus on priorities.
This is also basic product management; if I'm working on B while the patch
for A sits around unused, I'm implying that B is a higher priority than A.
That may
I think we can do this with Google Calendar, in the same way that other
shared calendars (e.g. WMF Engineering) work.
I haven't set one up before, but surely it can be done.
On Tue, May 26, 2015 at 2:30 PM, Kevin Smith ksm...@wikimedia.org wrote:
Hi all,
Do we have any best practices for
