Without deliberately making it an even longer term plan, as I think it is a
great idea, another long goal solution to the same problem would be (as
Flow gets Wikipedians into the idea of tagging) that categories get largely
replaced by tags. That way they lose much of their absoluteness and
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
You probably want to run those jobs via maintenance/runJobs.php that way
you can have more control over when and where they get run.
You can control the type of jobs that get run, so you can effectively
create priority specific behavior or at least move expensive jobs onto
machines that won't
Ori's advice rings true with me. It's something I need to get better at.
On the email titiel sidetrack, it should not create a 4th way. Without
verifying them those all look like valid representations of the same data.
MIME encoded word syntax only has two possible encodings, quoted printable
On Thu, Mar 21, 2013 at 12:04 PM, Mark A. Hershberger m...@everybody.orgwrote:
On 03/21/2013 11:45 AM, Luke Welling WMF wrote:
On the email title sidetrack, it should not create a 4th way.
The pedant in me says there are at least two more ways -- different
capitalization for UTF-8. But your
If you want to play cat and mouse, a good reference for things that work is
http://samy.pl/evercookie/
It's mostly targeted at a single domain stopping users from deleting
cookies, but some of the same things should break cross domain security
too.
I'm not sure that end of web ethics is where we
It would be a good application for mobile too.
In browser would be reasonably easy with Flash, and can be done with
JavaScript in modern browsers but not yet in a consistent way. There is a
W3 spec but using a library like
https://github.com/jussi-kalliokoski/sink.js/ would be easier than
The advice on
https://wikitech.wikimedia.org/wiki/Query_profiling_for_features_developers
sounds
good.
Is there more detail somewhere on how to do this part Test your query
against production slaves prior to full deployment?
Luke
On Wed, Mar 6, 2013 at 8:14 PM, Matthew Flaschen
I don't see the purpose of adding a licence string back on to JavaScript
post-minification. Any recipient wanting to create a derivative work or
redistribute those files is going to go back to the much more readable
source files.
It would be good form to add licence information to all the JS
Yes. There seems little value in unqualified people debating if it is
legally required.
The mainstream FOSS licences all predate minification and seem to have been
written with compiled languages in mind, not interpreted languages. Most
have language that requires the licence in the source
We should discuss them separately, but this core mediawiki JS is GPL2
https://github.com/wikimedia/mediawiki-core/tree/master/resources
This JS which was mentioned in the forwarded email that started this
discussion is available via a wiki page so is probably under a CC-BY-SA-3.0
as it is
Do we have an official position on cross database compatibility?
Some of the MediaWiki SQL is in separate files and can be easily directed
at a specific database engine. A lot of it though is scattered as
fragments though other code and is going to be run on any engine we connect
to.
I am strongly of the opinion that within broad ranges deployment frequency
does not matter. It really does not matter if you deploy twice an hour or
every second day.
But, having the machinery to make it so that you could deploy twice an hour
if you wanted to is all kinds of valuable.
Putting
Do you want help?
I don't know much about the API at the moment, but it is my Level-Up
assignment this quarter. Documenting things is a good way to learn them.
I have written a lot of courseware in the past.
Luke Welling
On Thu, Feb 7, 2013 at 6:20 PM, Yuri Astrakhan
I don't know if we are talking at cross purposes, or if I missed it, but
this paper:
http://elie.im/publication/text-based-captcha-strengths-and-weaknesses
does not try to answer my question.
What I want to know is *How many humans get turned away from editing
Wikipedia by a difficult captcha?*
Even ignoring openness and privacy, exactly the same problems are present
with reCAPTCHA as with Fancy Captcha. It's often very hard or impossible
for humans to read, and is a big enough target to have been broken by
various people.
I don't know if it's constructive to brainstorm solutions to a
That was not the end of the problem I was referring to. We know our
specific captcha is broken at turning away machines. As far as I am aware
we do not know how many humans are being turned away by the difficulty of
it. It's a safe bet that it is non-zero given the manual account requests
we get,
I don't mind getting dinged for typos. If I'm being sloppy it's fair to
point it out.
However, I think the social contract should be that after I fix the typos
you requested then you owe me a real code review where you look at the
merits of the code. Code review is an awesomely useful but time
Is this bug the same issue? It looks like somebody put up a partial fix
https://bugzilla.wikimedia.org/show_bug.cgi?id=38432
- Luke Welling
On Mon, Jan 7, 2013 at 6:30 PM, Aran Dunkley a...@organicdesign.co.nzwrote:
The file was a .doc, but I've tried changing it to docx and get the same
It should be an ignorable warning.
There are occasionally situations where trailing white space is necessary.
MySQL for instance can be funny about combining multi line strings into one
query, although I don't think it presents when called via PHP.
Luke
On Fri, Dec 21, 2012 at 9:59 AM, Chad
\+\%#\@!$/
autocmd InsertLeave * match ExtraWhitespace /\s\+$/
autocmd BufWInLeave * call clearmatches()
On Fri, Dec 21, 2012 at 10:20 AM, Luke Welling WMF
lwell...@wikimedia.orgwrote:
It should be an ignorable warning.
There are occasionally situations where trailing white space is
necessary
I've spoken at it the last 13 years, but I was thinking of skipping it this
time.
I've also been on the committee the last few years. I don't yet know if I
will be this year, but if you want my perspective on what gets accepted
I'd be happy to share it. In general state of TechnologyX is tough
22 matches
Mail list logo
