Hi!
I have the following setup: I develop on my local machine (PHPstorm) and I
save the files in one of the Vagrant shared folders. I load my js files
like that:
public static function onBeforePageDisplay( OutputPage $out, Skin
$skin ) {
$out-addModules(ext.Pydio);
}
The thing is
@John: Extensions are git repositories. Moving it to an extension involves
moving them in their own repo, like any other extension. I guess you're mostly
concerned about it being repositories not under mediawiki/extensions, because
it'll be a repository either way.
@Bartosz:
I'm inclined to
Hello Wikimanaias,
This is Osama Khalid, from the Arabic Wikipedia and Wikimedia Commons.
I was wondering whether anyone here has a good number of the raw
pagecounts downloaded so I can copy them to a hard disk during
Wikimania 2014. They have been very helpful for me in trying to
determine
Hi again!
That's the nastiest bug I've seen in a long-long time, thanks Alexey for
finding the answer. It's a Virtualbox/Vagrant bug. The solution is to turn
off the sendfile system call in httpd.conf in your apache or nginx[1]:
EnableSendfile off
I hope this will be useful for the developers
On 7/22/14, 3:09 PM, Mark A. Hershberger wrote:
Max Semenik maxsem.w...@gmail.com writes:
However all packages I know of (Debian flavors and not) split MW
directory and put its parts into different places, trying to follow
the Filesystem Hierarchy Standard. The result is [...] outright
At previous job, I've installed and maintained a wiki farm with multiple
sites, interwiki setup and caching while another emploee installed
MediaWiki from repository via single command and told to former boss that
my work is very simple. I hate anything web-related in packages because of
that.
Hi all,
I have developed the Mathoid deployment puppet script with great
support of Mwalker and Bryan Davis as far as I could get.
https://gerrit.wikimedia.org/r/#/c/148836/ aims to deploy mathoid on
beta in a first step.
Is there anything I can do to speed up the process beside waiting for
code
Hi everyone,
I’d like to announce an organizational change at Wikimedia Foundation
in the Platform Engineering group. For those that aren't terribly
interested in how WMF's org chart looks, you can skip the rest of this
email. :-)
Yesterday, we formalized “Release Engineering” as a team, and
quote name=Rob Lanphier date=2014-07-29 time=09:52:47 -0700
They are broadly responsible for the lifecycle of code from the point
that a developer is ready to check it in through its deployment on our
site, maintaining the processes and tools that reduce negative user
impact of site software
To clarify, is the QA team now under Release Engineering as Chris' comment
seems to imply, and how does this org change effect security engineering?
Thanks,
Pine
On Jul 29, 2014 10:53 AM, Greg Grossmeier g...@wikimedia.org wrote:
quote name=Rob Lanphier date=2014-07-29 time=09:52:47 -0700
To my understanding this is simply a formalisation of a change that, in
almost every regard, already happened months ago.
Dan
On 29 July 2014 11:58, Pine W wiki.p...@gmail.com wrote:
To clarify, is the QA team now under Release Engineering as Chris' comment
seems to imply, and how does this
On Tue, Jul 29, 2014 at 11:58 AM, Pine W wiki.p...@gmail.com wrote:
To clarify, is the QA team now under Release Engineering as Chris' comment
seems to imply, and how does this org change effect security engineering?
For now, I (the only security engineer) am staying in core, although
much of
Basically:
[[mw:Wikimedia Release and QA Team]] - [[mw:Wikimedia Release
Engineering Team]]
From the org perspective, now all of the team members report to me
instead of Rob. That's basically the substance of the change. QA and
Release Engineering were already the same team (effectively) since
On Tue, Jul 29, 2014 at 12:25 PM, Chris Steipp cste...@wikimedia.org
wrote:
On Tue, Jul 29, 2014 at 11:58 AM, Pine W wiki.p...@gmail.com wrote:
To clarify, is the QA team now under Release Engineering as Chris'
comment
seems to imply, and how does this org change effect security
Hi Chris M.,
I understand the difference between functional and reporting relationships.
As I understand it, QA is under RelEng in terms of reporting but
functionally works in a matrix envrionment. That seems consistent with the
OP and the WMF Wiki's pseudo-org chart. Is this your understanding
I'm trying to render an image which uses characters from all of the
languages supported by WP. Is there a single font deployed on production
servers that include all scripts? Any simple font would do, preferably TTF
arial-style.
Thanks!
___
Wikitech-l
On Tue, Jul 29, 2014 at 2:06 PM, Pine W wiki.p...@gmail.com wrote:
Hi Chris M.,
By the way, Wikimedians are a vocal group when there are problems, and I
take the general quiet of Wikimedia content editors about security and core
stability to mean that security and core QA are in good
No such font exists. You can try DejaVu Sans or FreeSerif for best coverage.
Nemo
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Thanks Federico, I used /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf
but didn't see FreeSerif. DejaVuSans doesn't seem to render Hindi. Is there
a font for that?
On Wed, Jul 30, 2014 at 2:12 AM, Federico Leva (Nemo) nemow...@gmail.com
wrote:
No such font exists. You can try DejaVu Sans
On Tue, Jul 29, 2014 at 2:06 PM, Pine W wiki.p...@gmail.com wrote:
The everyday difference that this change makes may be trivial, but it makes
sense to me to think of QA (and Security Engineering) as being part of
RelEng.
I doubt we disagree too much, but I'll put on my security evangelist
hat
++the EFF for more ideas, they are actively doing great work on so-called
perfect forward secrecy.
There are simple things we could do to achieve a better balance between
privacy and sockpantsing, such as cryptolog [1], in which IP addresses are
hashed using a salt that changes every day. In
Ambassadors (and developers),
I am tremendously happy to announce that the new PDF rendering service is
live for testing on the cluster. At this time, while we shake out
production bugs, it is only available via Special:Book using the 'e-book
(PDF, ocg latex renderer)'. You can also render a
As an addendum; when reporting bugs; we will need one of the following two
things to debug:
1) The title of page (or collection being rendered)
2) The collection_id parameter from the URL on the status page
~Matt Walker
Wikimedia Foundation
On Tue, Jul 29, 2014 at 6:17 PM, Matthew Walker
On Tue, Jul 29, 2014 at 3:46 PM, Yuri Astrakhan yastrak...@wikimedia.org
wrote:
Thanks Federico, I used /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf
but didn't see FreeSerif. DejaVuSans doesn't seem to render Hindi. Is there
a font for that?
On Wed, Jul 30, 2014 at 2:12 AM, Federico
but maybe browser and preferences
fingerprinting would be more effective anyway, since: tor.
Probably not as effective as straight up blocking tor as we do now? :P
(Although seriously - I would love if we didn't block tor like we do
now. However you can't abuse the site with tor when you can't
Chris S.,
I agree that in many cases an ounce of prevention is worth a pound of cure.
I will also say that I feel that you're a self-motivated, capable person
and you'd do good work anywhere in the org chart.
In my experince generally, Wikimedia is a more security-conscious and
privacy-conscious
26 matches
Mail list logo
