On 02/26/2013 02:29 AM, Luca de Alfaro wrote:
- We need a way to poll the database for things like what are all
revision_ids of a given page. We could use the API instead, but it's less
efficient.
Yes, as others have said LAbs should allow that either now or shortly.
You should sign
On 02/26/2013 02:14 PM, Luke Welling WMF wrote:
Specifically, do we use MySQL specific syntax that is more efficient (but
breaks elsewhere) or do we attempt to write lowest common denominator SQL
that will run more places, but not run as efficiently on our primary target?
There's a DB layer
On 02/19/2013 02:36 AM, MZMcBride wrote:
Hi.
I wrote https://www.mediawiki.org/wiki/Gerrit/Reports over the weekend.
Cool! And a creative bot name, as always.
Matt Flaschen
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
On 02/26/2013 11:35 PM, Jeremy Baron wrote:
On Feb 26, 2013 11:25 PM, Matthew Bowker matthewrbowker.w...@me.com
wrote:
I hate to be that guy, but is it supposed to be password protected? Is
there somewhere non-ops people can look for server status, or is
http://status.wikimedia.org it?
try
On 02/26/2013 11:55 PM, Leslie Carr wrote:
Thanks - I'll try to get status.wikimedia updated in the morning.
Can you try with https now ? I had forgotten to reload apache when
pushing out a change to the https config (to allow https without
login). You can also use http.
HTTPS works.
On 02/23/2013 02:46 PM, Casey Brown wrote:
Would the fact that Bugzilla uses your e-mail address publicly for
everything (rather than a separate account name) cause any problems
when switching to OpenID?
It should be careful not to publicize people's wiki email (sometimes
private and used only
On 02/25/2013 12:53 PM, Sumana Harihareswara wrote:
The question: what do we need to test more often to keep RDBMSes happy?
https://www.mediawiki.org/wiki/Database_testing
https://www.mediawiki.org/wiki/New_installer/Test_plan Permissions,
searching, schema setup, schema changes, quoting
On 02/25/2013 09:21 PM, Luca de Alfaro wrote:
I am writing this message as we hope this might be of interest, and as we
would be quite happy to find people willing to collaborate. Is anybody
interested in developing a GUI for it and talk to us about what API we
should have for retrieving this
On 02/22/2013 09:38 PM, Chad wrote:
So, I've seen this site tossed around quite a bit recently, and I'm curious:
is there any plan to start integrating this jenkins and our other jenkins?
More importantly: is there any chance to get the results of these sorts of
tests in Gerrit? I think it's
On 02/22/2013 03:43 PM, Marc A. Pelletier wrote:
On 02/22/2013 03:17 PM, maiki wrote:
Is this up for discussion, or are we at the point of planning
deployment?
The latter. I can elucidate a number of scenarios where that is
beneficial, but the primary one from my perspective is that of
On 02/22/2013 06:33 PM, Brian Wolff wrote:
Which coincides to several bots/tools and would generally be quite useful.
Quite honestly having bots make edits directly on someones behalf using
their account sounds scary.
For autonomous bots, yes (they should keep using their own accounts).
But
On 02/22/2013 11:32 PM, Brian Wolff wrote:
What ive always wondered is what happens if your oid provider goes
under/otherwise dissapears. I imagine that means you lose your user account
all across the internet, which is a scary thought
Some sites, like Stack Overflow, allow you to add
On 02/16/2013 01:50 PM, Basil George wrote:
*We have tried to address the privacy issues in obtaining IPs
herehttp://meta.wikimedia.org/wiki/Grants_talk:IEG/Mapping_History:_Revision_History_Visualizer_and_Improvement_Suggester_using_Geo-Spatial_Technologies#Addressing_privacy_concerns.
As we
On 02/16/2013 12:30 PM, Basil George wrote:
Please go through the proposal
herehttp://meta.wikimedia.org/wiki/Grants:IEG/Mapping_History:_Revision_History_Visualizer_and_Improvement_Tracker_using_Geo-Spatial_Technologies
and
do endorse it if you find it interesting.
I also think you should
On 02/15/2013 06:03 PM, Sîrbu Nicolae-Cezar wrote:
Hello,
What is Lua?
Thanks,
Sirbu Nicolae-Cezar
It is a programming language used for embedded scripting. Scribunto is
a MediaWiki extension that allows you to write templates in Lua (other
languages possibly coming later). Done right,
On 02/15/2013 03:33 PM, Rob Lanphier wrote:
Hi everyone,
We're planning to deploy Lua to a long list of wikis on Monday,
February 18, 23:00-01:00 UTC (stretching into Tuesday UTC), including
English Wikipedia.
Details here:
http://meta.wikimedia.org/wiki/Lua
This is A Big Deal.
On 02/14/2013 07:29 PM, Krinkle wrote:
Due to the way Git and Gerrit interact, a revert (unlike a merge) is
a two-step process. It considers it to be a separate commit (which it
is, of course). So clicking Revert only drafts a commit, it still
needs to be merged. This is generally done
On 02/13/2013 07:57 PM, Chad wrote:
On Wed, Feb 13, 2013 at 4:35 PM, Sumana Harihareswara
suma...@wikimedia.org wrote:
Maybe our rule should be: if an extension is not
deployed on Wikimedia sites, then we should basically allow anyone to
merge new code in (disallowing self-merges), unless the
On 02/13/2013 09:20 PM, Brian Wolff wrote:
And more importantly
https://www.mediawiki.org/wiki/Extension:MWSearchalong
There was a typo. The URL is
https://www.mediawiki.org/wiki/Extension:MWSearch
Matt Flaschen
___
Wikitech-l mailing list
On 02/14/2013 12:04 AM, Dmitriy Sintsov wrote:
That is a really great idea. If there were
mediawiki/extensions/(wmf|non-wmf-unimportant|non-wmf-important)/*
subdirectories introduced, such classification should encourage
extension developers to improve their extensions so they can move up
On 02/14/2013 12:25 AM, Brian Wolff wrote:
I would consider git pull to mysteriously stop working because somebody
moved the git repo to be a pretty big disadvantage.
Similar to what I said earlier, I don't think anyone needs to request
review/merge rights for all non-WMF less important
On 02/11/2013 09:50 AM, Brian Wolff wrote:
Maria: see http://www.mediawiki.org/wiki/API:Calling_internally for info
on calling the api internally.
I think you're misunderstanding what she's saying. She's talk about
ordinary PHP classes, methods and hooks, basically the way an extension
On 02/11/2013 09:33 PM, Chad wrote:
There might be a few problems left over with the IRC notifications,
I'll tackle those tomorrow (making sure replication is working properly
now). If you spot any other problems, please let me know.
I'm getting Internal Server Error intermittently in the add
On 02/11/2013 10:27 AM, Sumana Harihareswara wrote:
On 02/08/2013 02:31 PM, Matthew Flaschen wrote:
I've started an RFC about making password requirements stronger, in a
workable way that is configurable by group.
See
https://www.mediawiki.org/wiki/Requests_for_comment/Password_requirements
On 02/08/2013 12:55 PM, Aaron Schulz wrote:
Yes a654a6e79adc8f4730bb69f79e0b6a960d7d3cbe should be fixed. It should add
the nullLockManager back.
Done, please review.
https://gerrit.wikimedia.org/r/#/c/48144/
Thanks,
Matt Flaschen
___
Wikitech-l
On 02/08/2013 08:35 PM, Paul Selitskas wrote:
According to the manual, as there were no pros heard from Design-l, now
the extension must undergo a technical design review, before it is decided
whether the extension is able to fly on production sites - deployment
review.
Out of curiosity,
On 02/07/2013 03:14 AM, MZMcBride wrote:
Sure, I picked Gists. It didn't seem like a very difficult choice. All
cleaned up (redirected) now.
I don't think that makes sense. If someone has a link to
http://www.mediawiki.org/wiki/Extension:Gist from a README or something,
they're now going to a
On 02/06/2013 08:09 PM, Aaron Schulz wrote:
nullLockManager is defined in Setup.php.The code:
LockManagerGroup::singleton()-get( 'nullLockManager' );
... works fine in eval.php and is used in production.
However, $wgLockManagers is redefined in parserTest.inc .
It looks like it's basically
On 02/05/2013 04:45 AM, MZMcBride wrote:
you have a link to a demo?
https://en.wikipedia.org/wiki/Main_Page?tour=test
And gettingstarted. E.g.
https://en.wikipedia.org/wiki/Wikipedia?tour=gettingstarted .
Matt Flaschen
___
Wikitech-l mailing list
On 02/05/2013 10:31 PM, Tim Starling wrote:
On 06/02/13 00:12, Matma Rex wrote:
Vector is a weird mess of extensions to the skin, extensions to
general functionality, and unused broken scripts. Merging it
properly would require some work and some deleting.
That sounds like a good reason to
On my local Vagrant MediaWiki install
(https://github.com/wikimedia/wmf-vagrant), I'm getting:
Running test BUG 1887, part 2: A math with a thumbnail- math
enabled... No lock manager defined with the name `nullLockManager`.
when running the parser tests:
php tests/parserTests.php
On 02/07/2013 01:02 AM, Sumana Harihareswara wrote:
Who's we? WMF isn't using any for obvious reasons (arbitrary code
injection).
We is the Wikimedia technical community, I'd wager. :-)
My point was three different people made those extensions, and while we
can encourage them to work
On 02/07/2013 01:17 AM, Tyler Romeo wrote:
Yes, but we don't have to keep all three extension pages. As the MediaWiki
community, don't we want to make things simpler for sysadmins? We can't
force them to work together, but I don't see how keeping all three
extensions on MW.org is useful.
I
On 02/04/2013 03:58 PM, Steven Walling wrote:
Sorry for cross-posting, but for MediaWiki developers, this is a good
opportunity to ask any questions you might have about the newly-released
Extension:GuidedTour, and how to leverage it to build any tours yourself.
Specifically, any extension
On 01/30/2013 11:36 AM, Daniel Renfro wrote:
We're finding that when using jQuery's .ready() (or similar)
function, the callbacks seem to execute in different (unexepected,
browser-dependent) order. This causes errors.
jQuery will execute ready events in the order bound. See e.g.
On 01/31/2013 03:08 AM, Robert Vogel wrote:
Hi Daniel,
I'm not very experienced with ResourceLoader, but maybe
'mw.loader.using()' [1] suits your needs. You can specify a module
dependency and a callback function on the client side.
using is the right solution for server scripts, or
On 01/28/2013 04:55 PM, Krinkle wrote:
Requiring that the wiki install it seems like a trivial thing. That can't
be the real reason.
I presume that when you say it is unknown whether the wiki has it
installed, the real issue is that it is unknown whether the wiki has it
enabled at this
On 01/28/2013 04:10 PM, Alolita Sharma wrote:
Runa believes newer platforms and devices used for content delivery and
adoption through local languages make it an exciting time for growth of
open source language tools.
Welcome! Indeed, it's an exciting time.
Matt Flaschen
On 01/27/2013 07:58 PM, S Page wrote:
How can an extension have a soft requirement on a module, so that it
only adds that module to its ResourceLoader dependencies if the
extension providing that module is loaded?
For example, there's no sense in depending on ext.eventLog if the wiki
On 01/25/2013 08:01 AM, Daniel Kinzler wrote:
* When using system messages to translate the error codes from the API, these
messages will often contain wikitext. How can we best avoid this? Wikitext is
likely to be quite useless to the client - it would be better to return HTML;
or
pass all
On 01/24/2013 04:28 AM, Georgiy Tugai wrote:
Also, a lightbox feature may help - expand the image to the full size
(as sent by the server) on click, then link to the file page upon a
second click (hide the lightbox upon a click outside of the image
borders).
I am unsure how difficult this
On 01/23/2013 10:07 PM, Georgiy Tugai wrote:
As the linked thread mentioned, MediaWiki is used on many deployments
outside of Wikimedia.
For example, I'm running three instances on a server with 10 GB of disk
space.
Therefore, this should be an option in LocalSettings.php rather than a
On 01/22/2013 05:24 PM, Paul Selitskas wrote:
It will just strip the whole attribute if there is a quote in. That is why
we have {{urlencode:{{{1}}}|WIKI}} (or any other mode).
URL-encoding is not the same as HTML-encoding for an attribute. I'm not
sure if we have a parser function for the
On 01/22/2013 07:52 PM, Paul Selitskas wrote:
Filed a bug report: https://bugzilla.wikimedia.org/show_bug.cgi?id=44262.
On Wed, Jan 23, 2013 at 1:34 AM, Matthew Flaschen
mflasc...@wikimedia.orgwrote:
On 01/22/2013 05:24 PM, Paul Selitskas wrote:
It will just strip the whole attribute
On 01/21/2013 03:00 AM, David Gerard wrote:
On 21 January 2013 07:56, Andre Klapper aklap...@wikimedia.org wrote:
at all implies that some spambots are blocked at least?
Yes, but to count as successful it would have to block approximately
all, I'd think.
That's dubious. Blocking all
On 01/15/2013 03:18 AM, Robert Vogel wrote:
Hi everybody!
I'm writing an extension that needs to replace/disable the build-in
suggestion feature of the search box. In earlier versions this could be
archived by setting $wgEnableMWSuggest
On 01/15/2013 03:08 PM, Rob Lanphier wrote:
Hi everyone,
I’m delighted to introduce Munagala Ramanath (a.k.a. “Ram”), who
started yesterday as a Senior Software Engineer in our Platform
Engineering group (MediaWiki Core, specifically).
Welcome, Ram! I look forward to working with you.
On 01/15/2013 06:58 AM, Nikola Smolenski wrote:
In my opinion, if the typo is trivial (f.e. someone typed fo instead
of of), there is no need to -1 the commit, however if the typo
pertains to a crucial element of the commit (f.e. someone typed fixed
wkidata bug) perhaps it should, since
On 01/14/2013 11:01 PM, Harsh Kothari wrote:
Hi Shailja
Thanks for your interest.
You can go through it
http://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker
Here is all the details you want. Need any help just ping . Hope you will
get your information.
I'd also be glad to
On 01/12/2013 09:15 AM, Mark A. Hershberger wrote:
The more I look at ContentHandler, the more it seems like a major new
feature for MW.
Are there any examples of this in use on Labs?
Is there more information on how to use and extend it for things like
WorkingWiki?
There is some talk
On 01/12/2013 10:02 AM, Mark A. Hershberger wrote:
On 01/12/2013 09:32 AM, Matthew Flaschen wrote:
Last I heard, significant progress was made on 2.0, but the project is
currently on hold. Thus, there's not a need to notify people right
away. When the time comes, I don't think initial
On 01/12/2013 09:59 AM, Mark A. Hershberger wrote:
On 01/12/2013 09:32 AM, Matthew Flaschen wrote:
On 01/12/2013 09:15 AM, Mark A. Hershberger wrote:
Are there any examples of this in use on Labs?
Is there more information on how to use and extend it for things like
WorkingWiki?
Matt
On 01/12/2013 06:40 PM, Mark A. Hershberger wrote:
On 01/12/2013 04:33 PM, Matthew Flaschen wrote:
That will cause problems throughout wikidom.
Yes, if the issue was ignored. However, I believe a bot could do the
one-time conversion.
This solution is just as good as ignoring the problem
On 01/09/2013 02:03 PM, Mark A. Hershberger wrote:
We're still a few months from a release of 1.21, but I'd like to start
thinking about what we can tell the users of MediaWiki about it.
In that vein, what changes or features have you been working on? I'll
spend some time looking over the
On 01/09/2013 08:56 PM, Jay Ashworth wrote:
It's the new year, and in light of the recent poll about which devs are
working on what, let me make another, albeit vaguely macabre, suggestion:
If you're a developer, or other staffer, can the people around you pick
up the pieces if you get hit
On 01/09/2013 08:44 PM, Mark A. Hershberger wrote:
Do you have a couple of sentences that would help me and other
developers understand this better? Or, if your job was to advertise
this, how would you promote it?
Tired of all your MediaWiki i18n messages showing on the JavaScript side
as
On 01/04/2013 08:21 AM, Matma Rex wrote:
You are both assuming that there are no other wikis except for the
English Wikipedia.
I'm not assuming that. I explicitly said Every wiki has a different
approach to bots.. I meant it, and I welcome people providing
information about other wikis.
For
On 01/04/2013 08:00 AM, Krinkle wrote:
Doxygen is indeed not meant for JavaScript. With some hacks it can be tricked
into reading comment blocks from javascript files, but that won't scale for
our code base, nor will it be enough to make a useful structure given the
dynamic way JavaScript
On 01/02/2013 03:03 AM, Bináris wrote:
Before generalizing it will be very useful to overview various
wikis. According to the interwikis, very few wikis have an explicit
bot policy like enwiki and even less have BAG. Definition of a bot
may vary, too: in the bot policy of enwiki only
On 01/02/2013 08:25 AM, Lars Aronsson wrote:
On 01/02/2013 03:29 AM, Matthew Flaschen wrote:
He may have misspoke on the we part. However, for wikis with bot
approval processes (e.g.
https://en.wikipedia.org/wiki/Wikipedia:Bot_Approvals_Group ), there is
tracking on what bots work on (due
On 01/02/2013 01:24 PM, Federico Leva (Nemo) wrote:
Matt, let's be clearer then: what you describe is ok ONLY for en.wiki.
ALL the other wikis have a different system.
I was replying to Lars, who made the across-the-board statement once
the status is granted, that idea can change without having
On 12/28/2012 07:08 PM, Merlijn van Deen wrote:
(responding to Siebrand, although others have made the same p
I hope that you're excluding adding people as reviewer to all patch sets by
user L10n-bot, by the way...
Initially not, but I just added an exception for L10n-bot - all it's
changes
On 01/02/2013 05:38 PM, Merlijn van Deen wrote:
On 2 January 2013 21:34, Matthew Flaschen mflasc...@wikimedia.org wrote:
Thank you Could you please also exclude the owner? In other words,
don't add the owner as a reviewer to their own change.
Great, thank you.
Matt Flaschen
On 01/01/2013 01:29 PM, Alex Brollo wrote:
As I told, I don't know if HTML5 is in use or not; but try to save a span
id=container data-test=This a test data/span into the raw code of
any page, then save it, and then use js console of Chrome from the resultin
page in view mode with this:
On 01/01/2013 08:38 PM, Lars Aronsson wrote:
On 12/27/2012 11:13 AM, Petr Bena wrote:
Someone once suggested we create a control panel for bots. I think the
first step would be to create a page where we could see overview of all
bots we are running on projects.
This assumes that we are
On 12/31/2012 09:19 AM, Strainu wrote:
Hi Pine,
It might be because of the alcohol I've ingested these last days, but
- what are you proposing exactly?
I think Pine is just proposing people read the text and/or links, and
consider what Big Data means for Wikimedia.
Matt Flaschen
On 12/31/2012 12:11 PM, Quim Gil wrote:
On 12/30/2012 09:08 PM, gnosygnu wrote:
Hi everyone. I wrote an open-source, offline wiki application and
wanted to announce it here. My apologies if this email is off-topic
for this mailing list, but I am hoping XOWA will interest some of you.
Thank
On 12/28/2012 12:57 PM, Juliusz Gonera wrote:
On 12/27/2012 10:31 AM, Matthew Flaschen wrote:
* What is the difference between +1 and +2, especially in Verified?
I think just how certain you are.
I still don't get it. I either think the code is good and should be
merged or it's not good
On 12/28/2012 09:12 AM, Merlijn van Deen wrote:
Hello all,
To add to the great work by Ori and Jon, I have my own recent pet
project to announce: Reviewer-bot, which adds reviewers to any new
changes uploaded to Gerrit.
The basic idea is as follows:
1) reviewer-bot listens to Gerrit's
On 12/28/2012 02:09 PM, Brad Jorsch wrote:
IMO leave it to Jenkins, if Jenkins is set up for the project. But if
you want to use it to indicate that you ran the unit tests yourself
and/or extensively tested it manually, feel free I guess as long as it
doesn't confuse Jenkins.
My understanding
On 12/29/2012 01:06 AM, Arthur Richards wrote:
Thanks everyone for helping to clarify. The fact that there is still
confusion, uncertainty, and 'from my understating's though is
disconcerting. Can someone in the know document the actual
implications/guidelines/automated behavior/etc for this?
On 12/27/2012 01:18 PM, Juliusz Gonera wrote:
* What is the difference between Verified and Code Review? When would I
put +1 in one of them but -1 in the other?
I'm relatively new, but this is my understanding. Verified means you
actually tested it. Code Review means it looks good
* What is
On 12/27/2012 05:04 PM, Sébastien Santoro wrote:
So we're speaking about potential need to incorporation and potential
trademark agreements.
But this isn't a bureaucratic road. Okay...
It specifically says may be incorporated not must be incorporated.
MediaWiki groups may allow that kind of
We have all these JavaScript documentation comments, but we're not
actually generating docs. This has been talked about before, e.g.
http://www.gossamer-threads.com/lists/wiki/wikitech/208357?do=post_view_threaded,
https://bugzilla.wikimedia.org/show_bug.cgi?id=40143,
On 12/21/2012 02:43 PM, Chris Steipp wrote:
Sorry for the delay, this link should work!
https://plus.google.com/hangouts/_/8e5a52bc254a36c4c78b2a999110fb10a2a3f32c
I started an Etherpad for notes.
http://etherpad.wmflabs.org/pad/p/secure_documentation
Matt Flaschen
On 12/21/2012 01:30 PM, Chad wrote:
You should also consider making http://app.net/mediawiki . app.net is
an ad-free subscription social network, and it's currently very popular
with us techies (but broadening its base).
Fwiw, I've never even heard of this until now.
Yeah, it's still
On 12/21/2012 01:24 PM, Quim Gil wrote:
Thank you for the suggestion. Do you (or someone you know) want to
maintain that? We can talk.
Yes, I'm willing to step up to do that.
We would have to decide how to do it. They allow up to 256 characters,
along with optional embedded media
On 12/19/2012 10:11 PM, Chris Steipp wrote:
I'll have both a google hangout for video, and an audio line for
anyone who prefers to avoid closed technology. If you want to dial in,
please let me know so I can get you a phone number in advance.
I'd like to join this.
Thanks,
Matt Flaschen
On 12/20/2012 04:15 PM, Chris McMahon wrote:
Considering that testwiki has a nice documentation page [0] and
test2wiki doesn't [1], I think we should probably clear that up before
announcing any policy.
[0] http://wikitech.wikimedia.org/view/Test.wikipedia.org
[1]
On 12/19/2012 05:57 AM, vita...@yourcmc.ru wrote:
Hello!
28 SEPTEMBER I've pushed minor changes to the gerrit, to the Drafts
extensions.
Since then I've corrected two of them (uploaded patch set 2), but
after that, nobody did the review. As I understand, Gerrit will abandon
changes after a
On 12/20/2012 07:50 PM, bawolff wrote:
Seems kind of odd to only run unit tests for code from experienced
people. While everyone benefits from the unit tests, I imagine
inexperienced new developers would benefit the most (One assumes
people with @wikimedia.org emails ought to be experienced ;)
On 12/19/2012 06:43 PM, Quim Gil wrote:
It's not completely sorted out but there has been a big progress in just
a couple of days:
https://www.mediawiki.org/wiki/Social_media
Summary: follow like MediaWiki in your social networks to read
promote MediaWiki Wikimedia tech news.
*
On 12/19/2012 02:41 PM, Tyler Romeo wrote:
I've had patchsets that I submitted in August and they still haven't been
merged. For example, the account creation API, which has actually been
approved, but never merged.
Which one are you referring to, https://gerrit.wikimedia.org/r/#/c/18127/ ?
On 12/19/2012 05:06 PM, Tyler Romeo wrote:
Yep, that patch. If you notice, patches 8, 16, 18, 20, and 21 have all been
approved, i.e., +2 on CR. But it's yet to have been merged. At the very
least, its dependency has been merged. I'm not in a humongous rush or
anything, I'm just pointing out
On 12/19/2012 04:58 PM, Matma Rex wrote:
On Wed, 19 Dec 2012 22:55:24 +0100, Matthew Flaschen
mflasc...@wikimedia.org wrote:
On a simpler note, why does it have your name as Parent5446?
https://gerrit.wikimedia.org/r/#/dashboard/278
Can someone fix this?
There's a bug for that:
https
On 12/18/2012 06:50 PM, bawolff wrote:
On Tue, Dec 18, 2012 at 5:41 PM, Kevin Israel pleasest...@live.com wrote:
Even if you do not check Remember my login on this browser, the
username is saved for 180 days (which, by the way, is four times the
duration set out in the WMF privacy policy).
On 12/19/2012 12:47 AM, Tyler Romeo wrote:
Maybe I'm missing something, but where is the 180 days number coming from.
When User::setCookies() sets the cookies, it gives it no expiry, so in
reality the cookie persists until the browser removes it.
Here
On 12/11/2012 07:30 PM, James Forrester wrote:
TL;DR: Today we are launching an alpha, opt-in version of the
VisualEditor[0] to the English Wikipedia. This will let editors create
and modify real articles visually, using a new system where the
articles they edit will look the same as when you
On 12/12/2012 11:08 AM, Roan Kattouw wrote:
On Tue, Dec 11, 2012 at 10:55 PM, Lee Worden worden@gmail.com wrote:
Very exciting - congratulations!
I know these are early days for the VisualEditor, but is there a plan for
extension developers to be able to hook in to provide editing for the
On 12/12/2012 12:44 PM, Jon Robson wrote:
I would love this status.
I'd suggest calling it PENDING
I could imagine states:
PENDING
I'd prefer something more specific. I actually think PATCH_IN_GERRIT
(the keyword) would work well as a status.
Matt Flaschen
On 12/11/2012 03:02 PM, Brion Vibber wrote:
However, every other mobile browser I've tested doesn't support Ogg Theora
or WebM formats. Mobile Safari, Chrome, the old stock Android browser,
Opera Mobile, and the IE 10 engine in our Windows 8 tablet app will show
the thumbnail, but won't play
On 12/12/2012 03:26 PM, Thomas Gries wrote:
I started this thread.
I filed this bug https://bugzilla.wikimedia.org/show_bug.cgi?id=42989
Gerrit: show link for raw file content in gerrit diff views (a
solution is proposed inside)
It has been closed as RESOLVED INVALID instead of deploying a
On 12/12/2012 04:15 PM, Sébastien Santoro wrote:
Currently there is a patch-in-gerrit keyword in Bugzilla. When a bug
report ends up as RESOLVED FIXED there usually had been a codefix in
Gerrit that got merged. Hence patch in gerrit could be considered
another state on the journey of a bug
On 12/12/2012 05:09 PM, Krinkle wrote:
I agree with Sébastien. ASSIGNED is enough.
I don't see the significance of whether there is a Gerrit change yet?
If there is no Gerrit change, it doesn't mean nobody is working on it.
And if there is a change, it may not be a good one and/or one
On 12/07/2012 04:19 PM, Antoine Musso wrote:
Le 07/12/12 04:56, Sébastien Santoro wrote
snip
This is very disturbing when browsing Gerrit for revisions still to
review and doesn't really give any useful information (as the
important information here would be the verified -1).
Lets open the
On 12/07/2012 05:02 PM, James Forrester wrote:
On 7 December 2012 13:06, Terry Chay tc...@wikimedia.org wrote:
Please join me in a belated welcome of Matthew Flaschen to the Wikimedia
Foundation. :-)
Welcome aboard, Matt! Excited to be working alongside you.
Thanks! I look forward
On 12/07/2012 05:19 PM, Maryana Pinchuk wrote:
I was really excited when I heard we were interviewing the ProveIt guy,
and Matt certainly didn't disappoint :)
Thanks! I should also give credit to everyone that's worked on ProveIt,
though. Besides me:
* Kurt Luther
* Terris Jordan
* Prof. Amy
On 12/06/2012 05:22 AM, Daniel Kinzler wrote:
On 05.12.2012 22:06, Matthew Flaschen wrote:
More specifically, what if Wikidata exposed a JSON object representing
an external version of each change (essentially a data API).
This already exists, that's more or less how changes get pushed
On 12/05/2012 06:34 AM, Daniel Kinzler wrote:
I think that makes sense. The spam filters will work best if they are
aware of how wikidata works, and have access to the full JSON
information of the change.
You really want the spam filter extensions to have internal knowledge of
Wikibase?
On 12/05/2012 12:28 PM, Chris Steipp wrote:
On Wed, Dec 5, 2012 at 3:34 AM, Daniel Kinzler dan...@brightbyte.de wrote:
You really want the spam filter extensions to have internal knowledge of
Wikibase? That seems like a nasty cross-dependency, and goes directly against
the idea of
401 - 500 of 507 matches
Mail list logo
