On 04/03/2013 02:02 AM, Chad wrote:
> On Wed, Apr 3, 2013 at 1:55 AM, Chad wrote:
>> I've now run this on mediawiki/core, and the repo went from 3.0G down to
>> ~620M on disk.
>>
>
> I copy+pasted this wrong. This is actually 323M on disk. To give you an
> idea of the kind of savings we're lookin
On Wed, Apr 3, 2013 at 2:02 AM, Chad wrote:
> This is actually 323M on disk.
Wow. Bravo. That is truly an extraordinary improvement.
*-- *
*Tyler Romeo*
Stevens Institute of Technology, Class of 2015
Major in Computer Science
www.whizkidztech.com | tylerro...@gmail.com
On Wed, Apr 3, 2013 at 1:55 AM, Chad wrote:
> I've now run this on mediawiki/core, and the repo went from 3.0G down to
> ~620M on disk.
>
I copy+pasted this wrong. This is actually 323M on disk. To give you an
idea of the kind of savings we're looking at for fetch & clone, here's my
test clone I
Hi all,
tl;dr: I've cleaned up the mediawiki/core repo, and performance for fetch/clone
operations should be noticeably faster.
So, due to some recent upgrades in Gerrit, we've now got GC support in JGit as a
result. Gerrit supports this functionality, which will greatly reduce
the size of our
re
This is awesome!!! Thanks Jon :) And no, I didn't look at the code, too
scared :)
On Wed, Apr 3, 2013 at 1:14 AM, Jon Robson wrote:
> I feel very dirty having done this but I made a chrome extension that
> autoexpands all comments and adds a comment count next to unexpanded older
> patchsets.
>
I feel very dirty having done this but I made a chrome extension that
autoexpands all comments and adds a comment count next to unexpanded older
patchsets.
The code's horrible but it works - feel free to try it out:
https://github.com/jdlrobson/gerrit-be-nice-to-me
I suspect the best long term s
Christian Aistleitner wrote:
>while I do not want to discourage discussion of those items on
>wikitech-l, I nevertheless filed them in bugzilla, so we can keep
>track of the issues / solutions.
This is wonderful. Thank you for filing these bugs, Christian. I'll take a
look at them now.
MZMcBride
On 04/02/2013 05:30 PM, Brad Jorsch wrote:
> Slightly related here, https://gerrit.wikimedia.org/r/#/c/57067/
> should be included in 1.21.
Very related. Thanks for pointing this out.
https://gerrit.wikimedia.org/r/#/c/57198/
If anyone else is aware of similar bug fixes that should go into 1.21,
Slightly related here, https://gerrit.wikimedia.org/r/#/c/57067/
should be included in 1.21.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Since I don't think anyone reads mobile-l.
-- Forwarded message --
From: Yuvi Panda
Date: Wed, Apr 3, 2013 at 12:53 AM
Subject: New Beta release of Wikimedia Commons App!
To: mobile-l
Hello! New beta release of commons app went out today!
Features of v1.0 beta 6 include:
##
On 02.04.2013, 20:16 Mark wrote:
> I've been pondering a bit about the two options for serving mobile
> ResourceLoader requests with Varnish: on the bits caches or on the
> mobile caches. I don't fully like either option to be honest. On one
> hand I'd like to keep mobile device detection off our
On 04/02/2013 12:27 PM, OQ wrote:
> Is the large read-only textbox on the final install screen normal or not?
"Normal" in that I saw it as well during my quick sanity check of the
tarball, but I think it deserves a bug. Please file one:
https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWi
On Sun, Mar 31, 2013 at 6:49 PM, Mark A. Hershberger wrote:
> I've just finished preparing the first release candidate for MediaWiki
> 1.21 and I'd like your help testing it before the final release.
>
> Please download the release candidate and test it. If you find any bugs
> please report them
Hi Max,
On Mar 29, 2013, at 10:45 AM, Max Semenik wrote:
> Hi, we at the mobile team are currently working on improving our
> current hit rate, publishing the half-implemented plan here for review:
> == Proposed strategy ==
> * We don't vary pages on X-Device anymore.
> * Because we still need
For my own changes I have a workflow that's a little clunky, but works for
me. I'll comment or mark done on every comment, so if I see the same
number of drafts as comments, I know I've addressed them all.
The workflow I have not found is a way to efficiently re-review other
people's changes that
i.org/wiki/Bug_management/Triage/20130402
For more information on Triaging in general, check out
https://www.mediawiki.org/wiki/Bug_management/Triage
Looking forward to seeing you there!
andre
[1] Timezone converter: http://www.timeanddate.com/worldclock/converter.html
[2] See http://meta.wikimedia.org/wi
On Tue, Apr 2, 2013 at 9:03 AM, MZMcBride wrote:
> Would it be possible to have Gerrit import a JavaScript page from
> MediaWiki.org (e.g., "MediaWiki:Gerrit.js")? This might allow dedicated
> users to override some of the default behavior (such as the block-level
> comment auto-collapsing) or add
Antoine Musso wrote:
>Le 02/04/13 04:39, MZMcBride a écrit :
>> I'm concerned that Gerrit actively discourages discussion currently.
>
>So do not use it? We have lists, wiki and private emails.
>
> [...]
>
>I would prefer having all the code and implementations discussion where
>the code is, aka
I have been drafting a proposal to attract new contributors, help them
settle in, and connect them to interesting tasks. It turns out that many
of these problems are not unique to new contributors. We suffer them as
well and we are just used to them.
The proposal has evolved into a deeper rest
Hi,
while I do not want to discourage discussion of those items on
wikitech-l, I nevertheless filed them in bugzilla, so we can keep
track of the issues / solutions.
On Mon, Apr 01, 2013 at 10:39:50PM -0400, MZMcBride wrote:
> * auto-collapsing all comments except the most recent;
https://bugzil
On Tue, Apr 2, 2013 at 5:46 PM, Antoine Musso wrote:
>
> Le 02/04/13 04:39, MZMcBride a écrit :
> > I'm concerned that Gerrit actively discourages discussion currently.
>
> So do not use it? We have lists, wiki and private emails.
Private email would be even worse... I'm surprised you even though
Le 02/04/13 04:39, MZMcBride a écrit :
> I'm concerned that Gerrit actively discourages discussion currently.
So do not use it? We have lists, wiki and private emails.
> I see a few issues:
>
> * auto-collapsing all comments except the most recent;
> * no reply feature or support for quoting (si
22 matches
Mail list logo
