On Mon, Aug 6, 2012 at 7:02 PM, Ori Livneh <[email protected]> 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. > I'd like to set this up on a third-party host so we don't add to the list of > machines ops has to worry about, and so we aren't affected by labs upgrades. > The monetary cost would be trivial and I don't mind shouldering it myself. I'm not terribly fond of that idea as it sounds like a truly dead-ended approach; it'd be nice to have something that can potentially grow in number of users / maintainers, and can be more straightforwardly prepared for deployment on production servers. Labs upgrades will happen, yes, but we have to grow discipline in minimizing downtime by eating our own dogfood. > ….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. -- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate _______________________________________________ Wikitech-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikitech-l
