On 09/19/2013 04:53 PM, Ori Livneh wrote:
I can commit to documenting this on mw.org if / when the proposal is
accepted and the patch is merged.
This is a good example. I recommend adding it to
https://www.mediawiki.org/wiki/Requests_for_comments/LESS/Conventions.
Matt Flaschen
On 09/17/2013 05:59 AM, Daniel Friesen wrote:
Side topic https://en.wiktionary.org/w/r/t is messed up: To check for
r/t on Wikipedia, see: //en.wikipedia.org/wiki/r/t
https://en.wikipedia.org/wiki/r/t
Good catch, filed: https://bugzilla.wikimedia.org/show_bug.cgi?id=54357
Matt Flaschen
On 09/26/2013 02:46 PM, Juliusz Gonera wrote:
I think the best way to proceed right now is to use the `code` key to
determine what to do and we should figure out how to make it better in
future. Is there any way I can get notified when your patch gets merged?
Not sure if there is such an option
On 09/27/2013 06:03 AM, Gryllida wrote:
I would be concerned about proper work of this feature in wikilinks. [[Main
Page?action=history|Foo]] makes a red broken link.
So does:
[[/w/index.php?title=Main Page|Foo]]
Neither would be expected to work. Anything to the left of the pipe in
your
On 10/03/2013 06:25 PM, Mark A. Hershberger wrote:
On 10/03/2013 04:41 PM, Aaron Schulz wrote:
In any case, I would not want to see file cache removed until CDN support
was evaluated, documented, and cleaned up, so people have an easy
alternative in it's place.
If file cache is a stand-in for
On 10/01/2013 04:43 PM, Ryan Lane wrote:
I'm not saying we should make the software unusable for shared hosts, but
we also shouldn't worry about supporting them for new features or
maintaining often broken features (like file cache) just because they are
useful on shared hosting. It makes the
On 10/07/2013 04:52 PM, Bryan Davis wrote:
I have just posted a new draft RFC on changing the thumbnail storage
and caching pipeline for Wikimedia projects [0].
I added a link from the earlier RFC about thumbnail sizes
On 10/07/2013 12:01 PM, Brion Vibber wrote:
Is anyone interested in helping out or picking up the project to move it
towards proper playback? If not, it'll be one of my weekend fun projects
I occasionally tinker with off the clock. :)
I don't have cycles to help at the moment, but that's
On 10/07/2013 11:40 PM, Erik Bernhardson wrote:
Status class:
A review of the code within this class tells me that its primary use
case(its single responsibility if you will) is to assist the caller in
generating user facing error messages about an operation that can fail. If
null/false is an
On 10/08/2013 02:59 PM, Rob Lanphier wrote:
Hi everyone,
I'm excited to announce that Ori Livneh will be moving into Platform
Engineering as Senior Performance Engineer. This work is riffing off
of the work that he's done with the Growth (nee E3) team, where a big
part of his job was
On 10/16/2013 03:40 AM, Ken Snider wrote:
Hello!
I'm extremely pleased to announce that we've had two promotions
within the Technical Operations team!
Congratulations to both of you!
Matt Flaschen
___
Wikitech-l mailing list
On 10/15/2013 11:15 PM, MZMcBride wrote:
I looked at your original e-mail and gerrit-patch-uploader itself and
couldn't find a link to the source code. Could one be added to the user
interface? I think it would help sustain the project.
I agree a link in the UI would be good. For now, it's
On 10/22/2013 06:49 PM, Ori Livneh wrote:
The HTTP Archive (http://httparchive.org/) audits the setup and
performance of popular websites, reporting things like load times,
download sizes, performance scores, waterfall charts, and cache
headers. They provide per-site reports as well as aggregate
On 10/24/2013 10:04 AM, Dan Andreescu wrote:
That's really cool Ori. Have people looked into why jQuery UI gets loaded
by default? It seems to not be used in any obvious way.
Yes. See https://bugzilla.wikimedia.org/show_bug.cgi?id=0 . I have
two patches that together I think should
On 10/24/2013 05:43 PM, Jon Robson wrote:
I think we are all in agreement that the CSS in MediaWiki is a mess
but it's not clear how to solve the mess.
I think I've created a useful bit of JS to visualise this mess and
make a path to solving it clearer.
If you visit:
On 10/24/2013 08:27 PM, Steven Walling wrote:
Thanks for doing this Jon.
When I used the Vector version, at first I got an all black screen, which
made me think it was broken. I guess that was just a CSS rule to click and
delete? :)
Yes.
Yeah, if we don't have a bug about settling on one
On 10/24/2013 08:04 PM, Steven Walling wrote:
On Thu, Oct 24, 2013 at 7:04 AM, Dan Andreescu dandree...@wikimedia.orgwrote:
That's really cool Ori. Have people looked into why jQuery UI gets loaded
by default? It seems to not be used in any obvious way.
One reason I've heard for doing
On 10/25/2013 02:51 AM, Jared Zimmerman wrote:
Matt, we're not planning on getting rid of blue buttons but the colors
will now have meaning, and since this is a one step action (send a
password reset email) it gets a green button here.
I see, my mistake. I unintentionally exaggerated the
On 10/27/2013 03:37 PM, Steven Walling wrote:
Many FOSS communities have dealt with the trade off between great-looking
fonts and freedom by commissioning foundries to get their own free fonts.
See also: Ubuntu, Android, and more. I've talked to the design team about
this idea, including perhaps
On 10/28/2013 07:43 AM, Liangent wrote:
btw. Be aware of internationalization issues: not to say that fonts are
usually tied to a (group of) alphabets. Even digits can be affected by the
language info of the context they live.
See [1]: this is the standard English Wikipedia signup screen, and
On 10/29/2013 06:30 PM, S Page wrote:
This seems right. I repeat, there is no benefit to putting the free
names first, unless designers think they look better.
One important benefit is that we encourage use of free fonts, even when
both free and proprietary fonts are installed. This fits
On 10/29/2013 06:04 PM, Rob Lanphier wrote:
Hi everyone,
I'd like to introduce Rummana Yasmeen, a new Software Test Engineer in
our QA team through April in our San Francisco office. Rummana is
going to be working with our Visual Editor team primarily on manual
testing, finding bugs so you
On 10/29/2013 07:14 PM, Daniel Friesen wrote:
The extremely few users who manually customize their font-matching can
still override e.g. what Nimbus Sans L points to on their machine.
You're basically suggesting that users who have customized their
browsers/OS to handle the patterns used on the
We have merged a couple changes so that jQuery UI is not loaded by code
that doesn't need it. See
https://bugzilla.wikimedia.org/show_bug.cgi?id=0 for details.
That means gadgets and user scripts that use jQuery UI should explicitly
load the appropriate module.
On 10/31/2013 10:57 AM, Greg Grossmeier wrote:
Also good reading on the topic, from one of the main authors of Opus
(the best audio codec available, and it happens to be big F Free) and
long time Wikipedian Greg Maxwell:
http://lwn.net/SubscriberLink/571978/3226db9ce394bf07/
Thanks, that was
On 10/31/2013 08:02 AM, Lukas Benedix wrote:
Maybe you want to read this article:
http://xiphmont.livejournal.com/61927.html
lbenedix
Thanks for the pointer. I somewhat understand where he is coming from.
However, it is still disappointing. Open source projects get licensed
(if partial
On 10/31/2013 05:26 AM, Brion Vibber wrote:
We're churning through some internal discussion with legal on if and how
how this affects our potential options...
Note that the specific thing announced there doesn't include a licensed AAC
*audio* codec which would be required to generate audio and
On 11/01/2013 12:06 PM, Quim Gil wrote:
WE NEED PEOPLE PROPOSING TASKS
Even if you can't mentor a specific task we still want to know about it.
All we need is a bug report with
gci2013 https://www.mediawiki.org/wiki/Google_Code-In#Candidate_tasks
This is great. I will not be mentoring this
On 11/08/2013 11:09 PM, Steven Walling wrote:
I would be okay just turning off assignment.
I don't support turning off assignment. A large number of MediaWiki
projects use only Bugzilla (which is also the only open source tracker
the WMF uses). Even for stuff WMF engineers work on, there
On 11/06/2013 04:54 PM, Chad wrote:
How about we make editbugs self-granting? That is, if you've got editbugs
you can give it to others (like we did with Coder a few years ago). It works
pretty well, scales infinitely, and tends to protect itself against abuse.
I agree with the others that the
On 11/06/2013 05:50 AM, Ori Livneh wrote:
What you are proposing is that we determine who is infallible and
benevolent, so we can style them dictators for life. This kind of
wide-eyed earnestness about the term architecture is very dangerous.
It misses the essential irony, and in so doing it
On 11/06/2013 06:35 AM, Antoine Musso wrote:
I would have a look at the way IETF is handling its RFC process. I wrote
about it back in July in the thread proposed RFC process:
http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070241.html
The IETF does have a long, successful track
On 11/08/2013 12:00 PM, Bryan Davis wrote:
I think the second is more consistent with the tenor of the discussion
here so far, because in the first case, the coupling between job
titles and responsibilities in our community might be too tight to
maintain flexibility and openness. It would also
On 10/29/2013 11:48 AM, Zack Weinberg wrote:
Theoretically speaking, the right way to do this would be to identify
the (small, one hopes) number of *sources* of sensitive data and
change them to return objects of a special class, which would then
automatically print out as [REDACTED] (if so
On 11/13/2013 01:22 PM, Quim Gil wrote:
Wikimedia's Engineering Community team is responsible for developing
clear documentation for MediaWiki. All of our documentation is written
collaboratively in wiki pages, involving all kinds of profiles, from WMF
professional developers to anonymous users.
On 10/31/2013 01:14 AM, Matthew Flaschen wrote:
// Load jquery.ui.button so button styles work in wikitext
mw.loader.using( 'jquery.ui.button' );
Commons is now doing this conditionally, only if the CSS class is
present on the page (or specifically the HTML from wikipage.content).
See https
On 11/14/2013 12:57 PM, Mark Holmquist wrote:
On Wed, Nov 13, 2013 at 07:21:01PM -0500, Tyler Romeo wrote:
MediaWiki participates in a number of student competitions and programs as
an open source mentor (such as GSoC, Code-In, etc.). Today I ran into
another one: Facebook's Open Academy
On 11/18/2013 06:38 PM, Rob Lanphier wrote:
I'm thrilled to announce that Aaron Arcos has agreed to volunteer for
the Wikimedia Foundation as a developer with our Multimedia team
through May.
Welcome. I look forward to working with you.
Matt Flaschen
On 11/26/2013 05:28 PM, Antoine Musso wrote:
Git submodules are a mess, needs to download code from github/whatever.
And I tend to dislike submodules.
If we went with this option, we could just have straight Gerrit mirrors
of any git repos we wanted to bundle. When we updated the
On 12/06/2013 01:37 PM, Jon Robson wrote:
Currently we have an issue live on all wikipedias which makes a
language button show up on all pages - even those without articles.
x
https://en.m.wikipedia.org/w/index.php?title=Diggers_%26_Dealerstitle=Diggers_%26_Dealers
When the language button at
On 12/09/2013 09:29 PM, MZMcBride wrote:
* You can specify debug=true.
** Specifying the URL parameter can damage reproducibility.
** URL parameter is non-obvious to just about everyone.
I can't think of a more straight-forward name. It's also clearly
documented.
* Minification is a form
On 12/09/2013 11:30 PM, MZMcBride wrote:
Matthew Flaschen wrote:
On 12/09/2013 09:29 PM, MZMcBride wrote:
* You can specify debug=true.
** Specifying the URL parameter can damage reproducibility.
** URL parameter is non-obvious to just about everyone.
I can't think of a more straight-forward
On 12/10/2013 01:05 PM, Isarra Yos wrote:
What about using the thank feature for good edits?
Thanking is for when someone does something special. Not barnstar
worthy (that's even more special), but more than just a trivial fix.
There are a lot of good edits that probably aren't
On 12/10/2013 01:04 PM, Amir E. Aharoni wrote:
In the Hebrew Wikipedia it's pretty straightforward: A proposal is made at
the Village Pump-like page, people bring up arguments for and against, and
if there are no strong arguments against, an administrator makes the gadget
default after a few
On 12/06/2013 08:51 PM, Daniel Friesen wrote:
And the MediaWiki development community is separate from Wikimedia and
consists of more than just people developing features intended for the
Wiki[pm]edia community.
I do not believe it should be the responsibility of volunteer MediaWiki
community
On 12/12/2013 08:08 PM, Terry Chay wrote:
Hello everyone,
It’s with great pleasure that I’m announcing that Kunal Mehta[1] has
joined the Wikimedia Foundation as contractor in Features Engineering.
Welcome aboard! :) It's been great working with already, and I look
forward to continuing to
On 12/27/2013 08:48 PM, Matthew Walker wrote:
I believe Twig does this better than Mustache. Twig does allow for complex
for loops and if statements, but it's all about manipulating the rendered
output. Try to think how you would implement a pager in Twig vs Mustache.
In twig you can pass in a
On 01/02/2014 11:19 PM, Matthew Flaschen wrote:
This doesn't seem like a great use case. Almost any realistic pager is
going to have too much data to send it all to the client. This even
includes a pager of all the revisions of a single article (a lot of
pagers in MW have far more pages than
On 01/03/2014 10:48 PM, Sumana Harihareswara wrote:
Hi! As of yesterday, I'm back after my three-month sabbatical at Hacker
School.
Welcome back! I'm glad to hear you had a great experience and improved
your skills.
Matt Flaschen
___
Wikitech-l
On 01/06/2014 07:02 PM, Rob Lanphier wrote:
Hi everyone,
I'm pleased to introduce Gilles Dubuc, who is a newly-arrived Senior
Software Engineer and serving as Tech Lead for the Multimedia team
here at WMF. We searched far and wide to find him, and we're thrilled
to finally have him to filling
On 01/13/2014 04:47 AM, James Salsman wrote:
Can someone more familiar with the Foundation's server infrastructure
needs than I please create a page somewhere with a checklist of
packages, modules, tools, etc., which need to be on arm but aren't
yet? Jasper mentioned that we need virtualization
On 01/14/2014 04:21 PM, Gryllida wrote:
On Wed, 15 Jan 2014, at 4:52, Sumana Harihareswara wrote:
On the RFC Process talk page, I'm presenting some questions about our RFC
process and suggesting *my* answers:
Where can I find previous RFCs?
They are listed at
On 01/13/2014 01:59 PM, Nathan Larson wrote:
I can't exactly post a bug to MediaZilla saying Create Inclupedia and
then have a bunch of different bugs it depends on, because non-WMF projects
are beyond the scope of MediaZilla.
That's not the case. There are components for software the WMF
On 01/21/2014 01:50 PM, Terry Chay wrote:
Hello everyone,
It’s with great pleasure that I’m announcing that Sam Smith[1] has
joined the WIkimedia Foundation as a Software Engineer in Features
Engineering. He'll be working with the Growth team.[2]
Welcome, Sam. :) It's been great working with
On 01/21/2014 09:47 PM, Amir Ladsgroup wrote:
One of the things I can't understand is why we are extracting summary of
pages for Yahoo? Is it our job to do it? the dumps are really huge
e.g. forwikidata:http://dumps.wikimedia.org/wikidatawiki/20140106/
On 01/21/2014 11:10 PM, Amir Ladsgroup wrote:
why? can we make it compressed? It's really annoying to see that huge file
there for (even almost) no reason.
It's probably because it's relatively small on major wikis (e.g. English
Wikipedia has it 3.8 GB). However, I see no reason not to
where:
1. Get the ID and timestamp of the last revision.
2. Get the text of that revision.
3. Do long-running computation based on that text.
4. POST an edit (resulting from that computation) with basetimestamp set
to the timestamp obtained in #1.
will cause a race condition.
Matthew Flaschen
Original Message
Subject:[teampractices] Front End Ops Conference, San Francisco in April
Date: Wed, 29 Jan 2014 11:00:51 -0700
From: Chris McMahon cmcma...@wikimedia.org
Reply-To: A mailing list to discuss team practices in Wikimedia
organizations
On 02/04/2014 07:05 PM, Andre Klapper wrote:
Today I removed the This page is currently a draft banner on
https://www.mediawiki.org/wiki/Bug_management/Bugzilla_etiquette
as the comment rate on its Discussion page has been very low recently,
hence I assume consensus has been found.
The
On 02/14/2014 06:40 PM, Lars Aronsson wrote:
On 02/14/2014 10:39 PM, Gabriel Wicke wrote:
VisualEditor is an HTML editor and doesn't know about wikitext.
That single sentence explains so much.
I think Gabriel is simplifying a little. VisualEditor is an editor that
understands, edits, and
On 02/19/2014 05:49 AM, Antoine Musso wrote:
A requirement Wikimedia has nowadays is that the code MUST be supported
with HipHop Virtual Machine. As an example, I do not think it
implements the SPL classes. So that needs to be carefully checked.
A good number of them are available now
).
Yes, that's the advantage. I wouldn't be so contrary as to make
MyExtension\User, though. But I do have a PageFilter class safely
namespaced like this, which could easily end up used as a name by core
(but currently isn't) or an extension.
Matthew Flaschen
I'm adding the design list. I talked about this recently with a couple
of the designers.
Matt Flaschen
On 02/28/2014 12:07 PM, Mansi Gokhale wrote:
hello,
These are some approaches i can think of instead of a text based captcha.
The image idea where users are asked to spot the odd one out
On 03/06/2014 10:44 PM, Tyler Romeo wrote:
On Thu, Mar 6, 2014 at 10:13 PM, George Herbert george.herb...@gmail.comwrote:
Based on the timing description here, it seems more like Either rush 1 or
rush 2.
This is also not true. Something does not have to be reverted in Gerrit in
order for it
On 03/06/2014 08:29 PM, Jon Robson wrote:
For the record this the test that alerted us to this issue was the following:
On 03/06/2014 09:58 PM, Tyler Romeo wrote:
I don't think you see the problem here. Consider this case as an example (I
agree that this is case-by-case, so let's limit the scope to this one).
You're forgetting that the original patch fixes a bug. In fact, it fixes a
pretty serious UX bug in my
On 03/06/2014 05:07 PM, Chris McMahon wrote:
Beyond that, there are serious concerns with any feature that a) requires
javascript support in the client in order to create an account on the wiki
and b) does not honor the characters that the user types in the username
and password fields.
I
On 03/11/2014 05:21 PM, Jon Robson wrote:
If people forget they exist I would say that equates to no one cares
about them and no one maintains them.
Isarra was referring to skins outside of core.
There's a difference between core developers forgetting non-core skins
exist, and the developers
On 03/08/2014 05:10 PM, Ryan Lane wrote:
You don't work for WMF, so you personally have no responsibility for the
stability of the site. It's the WMF developers who have a responsibility to
ensure code they're pushing out won't break the site. As an aside, root
isn't necessary to maintain
On 03/10/2014 02:38 PM, Chris McMahon wrote:
On Mon, Mar 10, 2014 at 10:59 AM, Tyler Romeo tylerro...@gmail.com wrote:
It's been repeated multiple times, but I'll say it again: it is disputed as
to whether account creation was broken.
It is not disputed.
When you get to the end of the
I could use a review on Gerrit 113525
(https://gerrit.wikimedia.org/r/#/c/113525/), Store page_id in logging
table for deletions and make queryable. If you can look at it, I'd
appreciate it.
Basically, it logs the page_id for deleted pages.
Before, it generally did not return a page_id for
On 04/06/2014 04:05 PM, Antoine Musso wrote:
Le 06/04/2014 21:11, David Gerard a écrit :
I originally went what on earth too, then I went to the bug and
looked at the samples. Here's how the previous font stack rendered in
Chrome on Windows without Cleartype on:
http://i.imgur.com/9QD1ujH.png
On 05/05/2014 01:21 PM, Quim Gil wrote:
I created
https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/versus_Bugzillato
consolidate the relevant information for bug reporters.
https://www.mediawiki.org/wiki/Requests_for_comment/Phabricator/versus_Bugzilla
Phabricator still does
On 05/02/2014 03:56 PM, C. Scott Ananian wrote:
[greg-g] cscott: James_F crazy idea here: can some teams use it for
real (I think growth is, kinda?) and export/import to a future real
instance?
frontend...
No, we're not using it for real currently. We (Growth) have talked
about potentially
On 05/08/2014 01:28 PM, James Forrester wrote:
Rob,
It's been a pleasure working with you. Thank you for everything;
using VisualEditor is so much better because of your work. Best
wishes with Growth – they're lucky to get you. :-)
Yep. Rob, it's great to have you on board.
Matt Flaschen
On 05/04/2014 05:08 AM, Max Semenik wrote:
This proposal makes no sense: all these namespaces _are_ dependent on wiki
language, so even if you force Project down the throats of non-English
users, project talk would still be e.g. Project_ахцәажәара for Abkhazian
wikis and so on.
I think you may
On 05/13/2014 11:37 AM, Daniel Kinzler wrote:
Hi all!
During the hackathon, I worked on a patch that would make it possible for
non-textual content to be included on wikitext pages using the template syntax.
The idea is that if we have a content handler that e.g. generates awesome
diagrams from
On 05/13/2014 06:13 PM, Sumana Harihareswara wrote:
I am trying to figure out how thumbnail retrieval caching works right
now - with Swift, and the frontline secondary (frontend and
backend) Varnishes. (I am working on the caching-related bit of the
performance guidelines, and want to
On 11/20/2013 08:55 AM, Petr Bena wrote:
aha I see now, I should have branch before patch1. I didn't. What am I
supposed to do now?
I think:
git checkout production
git checkout -b patch1
(that was just to back up patch1, in case you didn't have it anywhere
else)
git checkout production
On 05/14/2014 12:43 PM, Dan Andreescu wrote:
* File namespace serving raw data from Commons (where people are familiar
with take down notices and have the infrastructure to deal with that)
We shouldn't let copyright considerations dictate which WMF project
hosts the data.
On 05/21/2014 02:22 PM, C. Scott Ananian wrote:
I gave SplEnum a quick read as well. It seems they are solving a
different use case. SplEnum appears to be optimized for the case
where you have some inherently-integer constants floating around your
code (due to legacy or interoperation with C
On 05/21/2014 12:55 PM, Bryan Davis wrote:
The CentralAuth role and the associated puppet config that allows
creation of multiple wikis as Apache virtual hosts on a single
MediaWiki-Vagrant virtual machine have been merged! Go forth and
debug/extend CentralAuth. :)
This is really great.
On 05/27/2014 02:29 PM, Rob Lanphier wrote:
Hi everyone,
I'd like to welcome Dan Duvall to Wikimedia Foundation in his role as
Automation Engineer in our Release and QA group. Dan comes to us most
recently from Giant Rabbit, where he worked for a few months doing web
development consulting, and
On 05/27/2014 03:08 PM, Marc A. Pelletier wrote:
The problem with either is that, short of installing a very
complicated and brittle full URL parser in the SVG validation code,
you open the door to a number of very nearly insurmountable (and
highly catastrophic) security issues, the most
On 05/27/2014 09:11 PM, John wrote:
How would this work for non-wmf wikis?
It could be configurable, and default to only allowing content under the
image upload path on the local wiki (if it's enabled at all).
what about executing JavaScript that is posted to a approved wiki? This would
On 05/27/2014 09:09 PM, Marc A. Pelletier wrote:
On 05/27/2014 09:05 PM, C. Scott Ananian wrote:
I agree that a simple whitelist might be workable, but it does depend
on a bit of code auditing of librsvg to ensure that it can be done
robustly.
That works to protect the image scalers, if
On 05/27/2014 10:52 PM, Brian Wolff wrote:
I specifically said bits.wikimedia.org and upload.wikimedia.org (and not
commons.wikimedia.org), neither of which host user JavaScript.
Matt Flaschen
Gadgets are on bits and they are user controlled. Ditto for
mediawiki:common.js et al. (Unless
On 05/27/2014 11:57 AM, Bryan Davis wrote:
I think we should create a new repository in gerrit
(mediawiki/core/contrib? Bikeshed as needed) where composer is used
to manage importing specific versions of external libraries that are
needed for the wiki[mp]edia cluster deployments.
Is the idea
On 05/28/2014 07:11 AM, Christopher Johnson wrote:
Hi,
Wikidata needs to monitor dispatch statistics per Bug 65291 (
https://bugzilla.wikimedia.org/show_bug.cgi?id=65291).
We would like to use ICINGA to send an IRC alert if the dispatch lag
exceeds a critical threshold. A nagios plugin for
On 06/02/2014 08:16 PM, Steven Walling wrote:
GuidedTour's backend has also undergone a major refactor, which is close
to being merged. This is described in full at the commit, which is just
waiting on us to update logging: https://gerrit.wikimedia.org/r/#/c/116228/
As Steven noted, you should
On 05/14/2014 01:07 PM, Siebrand Mazeland wrote:
Op 14 mei 2014 om 14:58 heeft Krinkle krinklem...@gmail.com het volgende
geschreven:
I don't think it is possible or worth the effort to scan for these in an
automated fashion within Jenkins.
Static analysis is virtually impossible due to
On 05/22/2014 09:25 PM, James Forrester wrote:
Possibly, though I would suggest that it is not loaded by default. Frankly
if an extension's authors have abandoned their extension to the extent that
after several years' clear warning and a six month-long notice period they
still didn't do a
On 06/03/2014 09:04 PM, James Forrester wrote:
There have been a number of high-profile semi-announcements as well as
comments and code reviews relating to this, most obviously this one:
http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064280.html
True, that's only one piece
On 06/05/2014 05:23 PM, Nuria Ruiz wrote:
I can see those images in the CSS file that results after this call as
background images on the default skin of es.wikipedia. They look correct in
the CSS:
On 05/31/2014 08:52 AM, Bartosz Dziewoński wrote:
I don't like this idea, for the same reasons that other have already
given. Grafting histories with git-replace might be viable, but it'd
still be clunky and non-intuitive.
Why don't we just suggest that people use shallow clones? Git supports
On 06/03/2014 03:29 PM, Matthew Flaschen wrote:
We are polishing the API and finishing final testing. The documentation
for the upcoming API is available at
http://growthdoc.wmflabs.org/NonLinearGuidedTourPreview/ (this URL is
temporary), so if you think something could be clarified or tweaked
On 06/17/2014 08:57 PM, Ryan Kaldari wrote:
The specific need is that I want to set the 'Mobile-frontend-terms-url'
message to '//m.wikimediafoundation.org/wiki/Special:MyLanguage/Terms_of_Use'
via the WikimediaMessages extension, so that people clicking the 'Terms of
Use' link at the bottom of
On 06/19/2014 11:09 PM, Daniel Friesen wrote:
B) If we even have anything similar to Content-MD5 (I don't remember
seeing anything) it's optional and the clients most likely to have a
buffer bugs like that are going to be the ones that don't use it.
There is an optional md5 parameter in the
On 06/29/2014 03:08 PM, Antoine Musso wrote:
Le 29/06/2014 20:15, Thomas Mulhall a écrit :
Well jquery iu says that less then 1% of those are using those
browser so I think we should discontinue support for these browser
windows xp can still get internet explorer 8 which supports more
things
On 06/29/2014 01:33 PM, Brian Wolff wrote:
I would expect basic site functionality to work in IE 6. You should be
able to edit a page, you should be able to read your talk page, etc. I
wouldn't expect fancy new features to work unless they are critical to
site function.
Agreed, and that can be
1 - 100 of 507 matches
Mail list logo
