Just FYI, the new version of MediaWiki has been finally deployed to the
Wikipedias along with the new OO.ui.LookupElement class, after a
two-week delay due to WMF All Hands and MediaWiki Dev Summit
(announcement
I think you mean https://phabricator.wikimedia.org/T89385, don't you?
Il 12/02/2015 20:50, Thomas Mulhall ha scritto:
Hi does vendor have an api like the extension api which tells you name of the
extension and version. Because I have ask for WikiApriary to support vendor in
there tracking
What would be the letter for it then? s? t? a?
On Thu, Feb 12, 2015 at 8:31 PM, Pine W wiki.p...@gmail.com wrote:
I think bot edits are most closely aligned with fully automated editing.
Perhaps semi-automated edit would work.
Pine
On Feb 12, 2015 10:34 AM, Marc A. Pelletier m...@uberbox.org
[X-posted announcement]
Hello,
The next monthly IRC office hour of the WMF Language Engineering team will
be on February 18, 2015 (Wednesday) at 1300 UTC on #wikimedia-office.
Please note that for this instance the session has been set to a much
earlier hour.
We will be taking questions and
I'd suggest, James, that relying on suggestions from a
six-year-old strategy document when we're about to start a new strategic
session, isn't the best course of action.
I'd also query what exactly is the plan for doing something with this
information. Collecting lists of things that might no
Hi
Some of you who use JS and Python were probably excited about
deployment of new RCStream (1) and some of you who use .Net were
probably disapointed how complex it is to get it, JSON and
websockets.IO running on .Net in order to get it working.
Here I made a super simple C# library that
Risker wrote:
... relying on suggestions from a six-year-old strategy document
when we're about to start a new strategic session, isn't the best
course of action.
A strategy proposal which never garnered criticism after so many
opportunities would seem to qualify as at least an emergent
I like that volunteer flag, please keep it.
On Fri, Feb 13, 2015 at 6:42 PM, Andre Klapper aklap...@wikimedia.org wrote:
Apparently the idea to rename the Priority field value from Lowest in
Bugzilla to Needs Volunteer in Phabricator created more confusion than
expected. I am sorry for that -
On Fri, 2015-02-13 at 18:48 +0100, Petr Bena wrote:
I like that volunteer flag, please keep it.
Let me repeat what I wrote below:
If you feel like helping make a decision by adding some *additional*
arguments based on your experience, please raise your voice in T78617
after reading the existing
I would go with S or T depending on what you choose to call these edits. I
lean towards S.
This can be changed later of there is an upswell of bikeshedding, but I
hope that people will be grateful either way. (:
Pine
On Feb 13, 2015 3:22 AM, Petr Bena benap...@gmail.com wrote:
What would be
Apparently the idea to rename the Priority field value from Lowest in
Bugzilla to Needs Volunteer in Phabricator created more confusion than
expected. I am sorry for that - wasn't intended.
To fix that, there are two questions that welcome input in
https://phabricator.wikimedia.org/T78617 :
1)
On Fri Feb 13 2015 at 9:43:00 AM Andre Klapper aklap...@wikimedia.org
wrote:
Apparently the idea to rename the Priority field value from Lowest in
Bugzilla to Needs Volunteer in Phabricator created more confusion than
expected. I am sorry for that - wasn't intended.
To fix that, there are
James, it received a single support vote. It was not included in any
final strategy documents. I think it could more accurately be described as
something not worthy of the attention of the Wikimedia community.
While I have no doubt that the WMF and the Wikimedia community care about
the
I say working in node is sure better than not working at all. :D
Keep it up!
-- brion
On Thu, Feb 12, 2015 at 3:45 PM, Daniel Friesen dan...@nadir-seen-fire.com
wrote:
((Jump to the -- TL;DR -- if you just want to answer my question))
Hey guys, right now managing extensions is a complete
Hi,
On Thu, Feb 12, 2015 at 7:24 AM, C. Scott Ananian
canan...@wikimedia.org wrote:
In addition to (even better than?) a breaking-changes list would be for
every piece of software we distribute to have a very prominent ChangeLog
(or RELEASE-NOTES) file, which is kept up to date. When you git
On 02/13/2015 02:14 PM, Max Semenik wrote:
Sorry for all the trolling, but why instead of discussing how we need a
responsive skin for MediaWiki and waiting for Winter to come don't we just
do it:
* Move Minerva out of MobileFrontend
https://phabricator.wikimedia.org/T71366
-- Legoktm
On 13 February 2015 at 17:25, Max Semenik maxsem.w...@gmail.com wrote:
On Fri, Feb 13, 2015 at 2:23 PM, Risker risker...@gmail.com wrote:
Help me out here. Why does anyone care that the article was last edited
13
days ago by Omeganian? And even if they do, why is that the very first
On 2015-02-13 2:19 PM, Chad wrote:
On Fri Feb 13 2015 at 2:15:29 PM Max Semenik maxsem.w...@gmail.com wrote:
Sorry for all the trolling, but why instead of discussing how we need a
responsive skin for MediaWiki and waiting for Winter to come don't we just
do it:
* Move Minerva out of
On Fri, Feb 13, 2015 at 2:23 PM, Legoktm legoktm.wikipe...@gmail.com
wrote:
https://phabricator.wikimedia.org/T71366
Note that my proposal is explicitly different from Jon's plans about that
bug: he wants to continue overriding special pages, etc. while I want to
leave everything like this
On Fri, Feb 13, 2015 at 12:59 AM, Ricordisamoa ricordisa...@openmailbox.org
wrote:
the overflow of the lookup menu is now clipped by the dialog :-/
Could you please add a bug to phabricator with reproduction steps?
Thanks,
Trevor
___
Wikitech-l
Risker wrote:
... it received a single support vote
There are two supporters including myself who indicated they are
willing to work on it, and it also recieved support at
https://strategy.wikimedia.org/wiki/Favorites/Lodewijk
Many of the implemented proposals received less formal process
On 13 February 2015 at 17:19, Chad innocentkil...@gmail.com wrote:
On Fri Feb 13 2015 at 2:15:29 PM Max Semenik maxsem.w...@gmail.com
wrote:
Sorry for all the trolling, but why instead of discussing how we need a
responsive skin for MediaWiki and waiting for Winter to come don't we
just
On Fri, Feb 13, 2015 at 2:23 PM, Risker risker...@gmail.com wrote:
Help me out here. Why does anyone care that the article was last edited 13
days ago by Omeganian? And even if they do, why is that the very first
thing that someone sees?
See the part about improvements.
--
Best regards,
We really need to just evolve Vector. It's not a sacred cow, and it's sort
of sad how little it's been changed since I made in back in 2009. How it
looks, how it works and how it responds to different devices can all be
changed incrementally, and we can do this without continued or additional
Sorry for all the trolling, but why instead of discussing how we need a
responsive skin for MediaWiki and waiting for Winter to come don't we just
do it:
* Move Minerva out of MobileFrontend
* Leave all mobile-specific improvements, improvements and hacks in MF
* Polish Minerva to do everythig a
On Fri Feb 13 2015 at 2:15:29 PM Max Semenik maxsem.w...@gmail.com wrote:
Sorry for all the trolling, but why instead of discussing how we need a
responsive skin for MediaWiki and waiting for Winter to come don't we just
do it:
* Move Minerva out of MobileFrontend
* Leave all mobile-specific
https://phabricator.wikimedia.org/T89494
Il 13/02/2015 20:05, Trevor Parscal ha scritto:
On Fri, Feb 13, 2015 at 12:59 AM, Ricordisamoa ricordisa...@openmailbox.org
wrote:
the overflow of the lookup menu is now clipped by the dialog :-/
Could you please add a bug to phabricator with
Hello,
The timeline and flame graph features of Chrome's DevTools have been very
useful for us as we work to understand and improve the performance of
VisualEditor. Someone asked me today about how we use these tools, so I
recorded a short (3-minute) screencast. It unfortunately cut off near the
PS: added these links to our growing collection of JS optimization tips at
https://www.mediawiki.org/wiki/Learning_JavaScript#Profiling.
On Fri, Feb 13, 2015 at 5:15 PM, Gabriel Wicke gwi...@wikimedia.org wrote:
Thanks, Ori!
Another great tool that we have been using heavily for JS profiling
Furthermore, the initial limited subtask would be much more difficult
to evaluate as a strategy without a working prototype, including by
the Bot Approvals Group which demands working code before making a
final decision on implementation. Trying to second guess the BAG is
presumptuous.
es
On Feb 13, 2015 6:15 PM, Max Semenik maxsem.w...@gmail.com wrote:
Sorry for all the trolling, but why instead of discussing how we need a
responsive skin for MediaWiki and waiting for Winter to come don't we just
do it:
* Move Minerva out of MobileFrontend
* Leave all mobile-specific
On Fri, Feb 13, 2015 at 2:23 PM, Risker risker...@gmail.com wrote:
Help me out here. Why does anyone care that the article was last edited 13
days ago by Omeganian? And even if they do, why is that the very first
thing that someone sees?
This is rather off-topic, but to answer the question
Thanks, Ori!
Another great tool that we have been using heavily for JS profiling is
https://github.com/jlfwong/chrome2calltree. It allows you to use the
excellent KCachegrind profile viewer, which has call graphs, relative call
frequency, grouping by file other useful features. It works with
On Sat, Feb 14, 2015 at 2:42 PM, Ricordisamoa
ricordisa...@openmailbox.org wrote:
Can I just say that I hate it?
It does not even give access to the talk page!
Looks like here is the best place to discuss design decisions:
https://www.mediawiki.org/wiki/Talk:Beta_Features/Minerva
--
John
Google is showing their This site may be hacked. note when showing
the enwp article about Anonymous, with a link to
https://support.google.com/websearch?p=ws_hacked
https://www.google.com/search?q=Anonymous+group
Found via
http://thestack.com/anonymous-this-site-may-be-hacked-wikipedia-120215
Trevor Parscal wrote:
We really need to just evolve Vector. It's not a sacred cow, and it's sort
of sad how little it's been changed since I made in back in 2009. How it
looks, how it works and how it responds to different devices can all be
changed incrementally, and we can do this without
Pine W wrote:
There is the
https://lists.wikimedia.org/mailman/listinfo/wikitech-announce
email list which perhaps could be used for emailing the weekly tech
newsletters and major changes.
There's also the mediawiki-announce list. While new mailing lists are
cheap enough to create, I don't think
When I logged into the webmaster tools and followed their instructions to
resolve the issue it said that en.wikipedia.org had no security issues.
I guess whatever happened has been fixed and we just need to wait for it to
resolve.
Dan
On 13 February 2015 at 20:57, John Mark Vandenberg
On Sat, Feb 14, 2015 at 4:41 PM, Dan Garry dga...@wikimedia.org wrote:
When I logged into the webmaster tools and followed their instructions to
resolve the issue it said that en.wikipedia.org had no security issues.
I guess whatever happened has been fixed and we just need to wait for it to
We've had this happen at least one other time (for a different article) and
both then and now I've never found any cause. I think it' s likely on
Google's side. For both occasions I've done deep dives on the page to see
if anything out of the ordinary existed that could cause it as well as
through
Thanks James. Do you recall what the previous articles were?
--
John Vandenberg
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
As promised in the meeting, here is are the minutes for the VisualEditor
weekly triage meeting on 2015-02-11.
*Item 1 – Release criteria*
The release criteria at
https://phabricator.wikimedia.org/tag/%C2%A7_visualeditor_q3_blockers/ were
considered. After a brief discussion, no changes were
Can I just say that I hate it?
It does not even give access to the talk page!
Il 13/02/2015 23:14, Max Semenik ha scritto:
Sorry for all the trolling, but why instead of discussing how we need a
responsive skin for MediaWiki and waiting for Winter to come don't we just
do it:
* Move Minerva out
See https://phabricator.wikimedia.org/T75305 for a previous instance. The VPT
thread linked there (now archived at [1]) has some other relevant discussions,
including an IRC log.
TTO
--
[1]
44 matches
Mail list logo