Re: [Wikitech-l] OPW final report and thanks to you all

[Dan Duvall]

Thanks so much for all your hard work, Frances!

I had a great time pairing with you on the Ruby-related stuff, and I'm
incredibly appreciative of the "gold standard" that you've developed. We've
already made some improvements to our internally used Ruby client that were
guided in large part by your recommendations [1]—the client library didn't
quite make the cut at the time due to its limitations and the fact that it
was essentially serving as a minimal dependency of mediawiki-selenium. As
soon as fab.wmflabs.org is back in action I'll be adding the tasks
necessary to bring the library fully up to snuff.

PS: Good luck with the Growstuff API! I've just signed up, so keep me in
the loop about any cool applications you develop. :)

Dan

On Tue, Sep 9, 2014 at 4:26 PM, Frances Hocutt 
wrote:

> My (belated) final report for my OPW project is up on my progress
> reports page:
> https://www.mediawiki.org/wiki/Evaluating_and_Improving_MediaWiki_web_API_client_libraries/Progress_Reports#Final_report
> . Thank you to everyone who has helped me learn as much and contribute
> as much as I have this summer, and special thanks to my mentors and
> technical advisers. This has been a great experience, and I'm happy to
> be leaving API:Client code in better shape than I found it!
>
> I hope to stick around the MediaWiki development community as I move
> on in my career as a software developer. I've applied for the January
> batch of Hacker School. Until that starts, I'll be working on API
> applications for Growstuff (http://growstuff.org): a gardening site
> that collects crowdsourced data from local gardeners around the world
> and freely licenses the resulting data. Wherever I end up after this,
> I'm glad to have gotten my start on MediaWiki.
>
> -Frances
>
> ___
> Wikitech-l mailing list
> Wikitech-l@lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikitech-l




-- 
Dan Duvall
Automation Engineer
Wikimedia Foundation 
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Disabling JS support in additional browsers

[Erik Moeller]

On Sat, Aug 23, 2014 at 11:22 AM, Erik Moeller  wrote:
> The IE6 disable patch is in prod now. I've tested on a few wikis and
> have not noticed any issues - if anything, IE6 actually feels usable
> now when before it kept throwing errors or was just slowing to a
> crawl. If there are no objections, I'll do the same with IE7 after
> wmf19 lands on mw.org (to give us a little bit more time for any
> issues to be reported).

This is ready to be merged unless folks have final concerns:
https://gerrit.wikimedia.org/r/#/c/157774/

IE7 is pretty badly broken in prod (and has been for a long time), so
AFAICT this will be a clear net improvement.

Erik
-- 
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation

___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] RfC Discussions Today/Next week

[Andrew Green]

Hi all,

The RfC on using Composer-manager libraries [1] is definitely a 
potential game-changer here. BTW, the data mapper and dependency 
injection RfCs and the implementations were created before that was 
accepted. I still hope that they can be spaces for talking about 
possible change in these areas, and that the implementations at least 
serve to scope out possible directions. Cheers,

Andrew

[1] 
https://www.mediawiki.org/wiki/Requests_for_comment/Composer_managed_libraries_for_use_on_WMF_cluster


On 03/09/14 18:39, Tyler Romeo wrote:

Well unfortunately I will not be able to attend either of these meetings 
(mainly since one of them was today). If somebody could make sure to mention 
third-party libraries on my behalf at the September 10th meeting, I would 
greatly appreciate it. (It would really be a facepalm if MediaWiki implemented 
its own ORM….again.)
--
Tyler Romeo
0x405D34A7C86B42DF

From: Rachel Farrand 
Reply: Wikimedia developers >
Date: September 3, 2014 at 14:08:22
To: Wikimedia developers >, Development and Operations 
engineers (WMF only) >
Subject:  [Wikitech-l] RfC Discussions Today/Next week

Hello,
If you are interested in joining today's RfC discussion,
the Architecture Committee will be discussing the following RfCs:

* SOA Authentication (Chris Steipp)
https://www.mediawiki.org/wiki/Requests_for_comment/SOA_Authentication
* Server-side Javascript error logging (Gergő Tisza)
https://www.mediawiki.org/wiki/Requests_for_comment/Server-side_Javascript_error_logging

Wednesday, 03 September 2014, in #wikimedia-office on Freenode IRC,
21:00-22:00 UTC
*http://www.timeanddate.com/worldclock/fixedtime.html?msg=RFC+Meeting&iso=20140903T14&p1=224&ah=1
*


*Proposed agenda for Sep 10: *
* Data Mapper (Andrew Green)
https://www.mediawiki.org/wiki/Requests_for_comment/Data_mapper
* Dependency injection (Andrew Green)
https://www.mediawiki.org/wiki/Requests_for_comment/Dependency_injection

Wednesday, 10 September 2014, in #wikimedia-office on Freenode IRC,
21:00-22:00 UTC
*http://www.timeanddate.com/worldclock/fixedtime.html?msg=RFC+Meeting+Sep+10&iso=20140910T21&p1=1440&ah=1
*

Thanks!
Rachel
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Disabling JS support in additional browsers

[James Forrester]

On 10 September 2014 13:45, Erik Moeller  wrote:

> On Sat, Aug 23, 2014 at 11:22 AM, Erik Moeller  wrote:
> > The IE6 disable patch is in prod now. I've tested on a few wikis and
> > have not noticed any issues - if anything, IE6 actually feels usable
> > now when before it kept throwing errors or was just slowing to a
> > crawl. If there are no objections, I'll do the same with IE7 after
> > wmf19 lands on mw.org (to give us a little bit more time for any
> > issues to be reported).
>
> This is ready to be merged unless folks have final concerns:
> https://gerrit.wikimedia.org/r/#/c/157774/
>
> IE7 is pretty badly broken in prod (and has been for a long time), so
> AFAICT this will be a clear net improvement.
>

​This is now done.

J.
-- 
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.

jforres...@wikimedia.org | @jdforrester
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Closure creation benchmark

[Daniel Kinzler]

Hi all.

During the RFC doscussion today, the question popped up how the performance of
creating closures compares to creating objects. This is particularly relevant
for closures/objects created by bootstrap code which is always executed, e.g.
when registering with a CI framework.

Attached is a benchmark I quickly hacked up. It indicates that creating objects
is about 40% slower on my setup (PHP 5.4.9). I'd be curious to know how it
compares on HHVM.

In absolute numbers though, creating an object seems to take about one
*micro*second. That seems fast enough that we don't really have to care, I 
think.

Anyone want to try?

Cheers,
daniel
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Closure creation benchmark

[Daniel Kinzler]

Apperently the attached file got stripped when posting to the list.
Here's a link:

http://brightbyte.de/repos/codebin/ClosureBenchmark.php?view=1

Here is the code inlined:

x = $x;
}

public function foo( $y ) {
return $this->x * $y;
}
}

function timeObjects( $n ) {
$start = microtime( true );

for ( $i = 0; $i < $n; $i++ ) {
$obj = new ClosureBenchmarkTestClass( $i );
}

$sec = microtime( true ) - $start;
print "  It took $sec seconds to create $n objects.\n";

return $sec;
}

$m = 10;
$n = 100;

for ( $i = 0; $i < $m; $i++ ) {
$ctime = timeClosures( $n );
$otime = timeObjects( $n );

$dtime = $ctime - $otime;
$rtime = ( $ctime / $otime );
$fasterOrSlower = $dtime > 0 ? 'faster' : 'slower';
print sprintf( "Creating %d objects was %f seconds %s (%d%%).\n", $n, 
abs(
$dtime ), $fasterOrSlower, abs( $rtime ) * 100 );
}





___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

[Wikitech-l] Determine if a extension's commit is live

[Tim Landscheidt]

Hi,

I want to check if https://gerrit.wikimedia.org/r/157836/ is
live on dewp.

So I would get MediaWiki core's SHA1 from
http://de.wikipedia.org/w/api.php?action=query&meta=siteinfo,
extract the extension name from the Gerrit page, look at
core's extensions/$EXTENSION SHA1 for the $VERSION_SHA1 and
see if in the extension's repository $CHANGE_SHA1 is a par-
ent of $EXTENSION_SHA1.

That sounds simple, but like work.  Has someone done that
already?  (Web tools are welcome as well.)

Tim


___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Determine if a extension's commit is live

[James Forrester]

On 10 September 2014 16:28, Tim Landscheidt  wrote:

> Hi,
>
> I want to check if https://gerrit.wikimedia.org/r/157836/ is
> live on dewp.
>
> So I would get MediaWiki core's SHA1 from
> http://de.wikipedia.org/w/api.php?action=query&meta=siteinfo,
> extract the extension name from the Gerrit page, look at
> core's extensions/$EXTENSION SHA1 for the $VERSION_SHA1 and
> see if in the extension's repository $CHANGE_SHA1 is a par-
> ent of $EXTENSION_SHA1.
>
> That sounds simple, but like work.  Has someone done that
> already?  (Web tools are welcome as well.)
>

​What I do is​ click on "Included in".

This will list a number of branches; in this case, just master and
wmf/1.24wmf20.

Go to the wiki you care about's Version page – in this case,
https://de.wikipedia.org/wiki/Spezial:Version

See that the wiki is currently running 1.24wmf19.

=> Not deployed on that wiki yet.


(There's an edge case where a commit has been merged into 1.24wmfN as
fix-up, but hasn't yet been deployed; in that case, the link in the Version
page to the current git hash which you can compare to be sure.)

J.
-- 
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.

jforres...@wikimedia.org | @jdforrester
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Determine if a extension's commit is live

[Chad]

On Wed, Sep 10, 2014 at 4:46 PM, James Forrester 
wrote:

> On 10 September 2014 16:28, Tim Landscheidt 
> wrote:
>
> > Hi,
> >
> > I want to check if https://gerrit.wikimedia.org/r/157836/ is
> > live on dewp.
> >
> > So I would get MediaWiki core's SHA1 from
> > http://de.wikipedia.org/w/api.php?action=query&meta=siteinfo,
> > extract the extension name from the Gerrit page, look at
> > core's extensions/$EXTENSION SHA1 for the $VERSION_SHA1 and
> > see if in the extension's repository $CHANGE_SHA1 is a par-
> > ent of $EXTENSION_SHA1.
> >
> > That sounds simple, but like work.  Has someone done that
> > already?  (Web tools are welcome as well.)
> >
>
> ​What I do is​ click on "Included in".
>
> This will list a number of branches; in this case, just master and
> wmf/1.24wmf20.
>
> Go to the wiki you care about's Version page – in this case,
> https://de.wikipedia.org/wiki/Spezial:Version
>
> See that the wiki is currently running 1.24wmf19.
>
> => Not deployed on that wiki yet.
>
>
> (There's an edge case where a commit has been merged into 1.24wmfN as
> fix-up, but hasn't yet been deployed; in that case, the link in the Version
> page to the current git hash which you can compare to be sure.)
>
>
git branch --contains 

That's basically what that feature does and the same thing
you can do locally.

-Chad
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Re: [Wikitech-l] Closure creation benchmark

[Gergo Tisza]

On Thu, Sep 11, 2014 at 1:02 AM, Daniel Kinzler 
wrote:

> Hi all.
>
> During the RFC doscussion today, the question popped up how the
> performance of
> creating closures compares to creating objects. This is particularly
> relevant
> for closures/objects created by bootstrap code which is always executed,
> e.g.
> when registering with a CI framework.
>
> Attached is a benchmark I quickly hacked up. It indicates that creating
> objects
> is about 40% slower on my setup (PHP 5.4.9). I'd be curious to know how it
> compares on HHVM.
>
> In absolute numbers though, creating an object seems to take about one
> *micro*second. That seems fast enough that we don't really have to care, I
> think.
>
> Anyone want to try?
>

3v4l can do HHVM as well: http://3v4l.org/barGj
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l