On Aug 6, 2012, at 7:39 PM, Erik Moeller erik@wikimedia.org wrote:
On Mon, Aug 6, 2012 at 7:02 PM, Ori Livneh ori@wikimedia.org wrote:
(We are the only two committers to the E3Experiments repository.)
That's a good and a bad thing as it'll likely mean we're not going to get a lot of insight into the code review benefits & drawbacks unless we get a few more people excited to work on that particular extension.
A consequence of having an extension (as opposed to something standalone like the mobile app or Limn) as the test case would be that we'll have to figure out how to make it work well with the MW deployment process - not sure how hard that would be in practice, but again something you'd have to solve without leaning too much on others.
When I talked to Ori, the idea here was not to set up in E3Experiments in lieu of other setups, but in addition to them.
The reality of anything that gets deployed on cluster is that the repository would have to be managed in gerrit. This means that the targets (until a decision is made) are to use phabricator on:
1) do extension that is in deploy but then gate on merge into gerrit. 2) do experimental extensions that aren't in deploy 3) do a project that isn't in gerrit/deploy train.
Ori's falls into the first. I have a number of projects that might fit into that in Features, so I can ask around, but this is actually extra work (currently) for whoever acts as the gate. Ori seems willing to for E3Experiments :-)
As for (2), the only project that could do this would be Flow which has no code written. My guess is the decision would be made before we get to the point where we're developing Flow in earnest.
As for (3), I think mobile would be the best candidate and Brion would proceed with that.
The work Ori is doing can be used to host more than just E3Experiments. ;-)
….and we're up: http://phab.256.io/
But I'll grant you that it's the fastest thing to do. :) I'd be in favor of moving it to a Labs instance when possible.
And when they do, we could try oth