Hi,
Is it possible to use template from english wikipedia on a different
wiki (meta in this case)? Something like {{w:Template}}.
I couldn't find this anywhere. I don't want to export it, I want to be
able to change it on 1 wiki so that change gets everywhere else as
well.
*OOjs UI 0.7.0* has been released today. It will be in MW from 1.25wmf18+.
We've tried hard to avoid breaking changes when possible, but occasionally
they will happen. The last time there were breaking changes in a release
was 2014-12-16 (wmf13), 137 OOjs UI commits ago.
*Breaking changes since last release:*
- [BREAKING CHANGE] Remove window isolation (Trevor Parscal)
Window isolation is a feature we introduced to solve certain problems in
VisualEditor a while back. It essentially places the content of a window
inside an iframe. We've since made improvements to VisualEditor to no
longer need this, and are happy to finally be able to remove this rather
problematic part of OOjs UI. We are not aware of anyone using this feature,
so it should have no effect on code in production.
We are also trying to make it easier on users of the library to stay up to
date more proactively by publicizing deprecations for at least one release
cycle before a related breaking change occurs.
*Deprecated changes since last major release:*
- DEPRECATION: GridLayout should no longer be used, instead use
MenuLayout (Bartosz Dziewoński)
GridLayout is a 2D proportional grid container that turned out to be
difficult to have features we didn't need and lacked many we did need. The
only uses of GridLayout have been removed, and we are planning to remove it
in an upcoming release. The shiny new MenuLayout is a much simpler
solution, providing a 2-pane split layout that is better suited to the
needs we actually have.
- DEPRECATION: LookupInputWidget should no longer be used, instead use
LookupElement (Bartosz Dziewoński)
In response to some feedback about using LookupInputWidget being complex
and inflexible, we've changed strategies and are now providing lookup
behavior through a mixin called LookupElement.
Also, I'd especially like to thank the volunteers and early-adopters who
contributed to this release.
- C. Scott Ananian
- Derk-Jan Hartman
- Ricordisamoa
- eranroz
If you have any further questions or need help dealing with deprecations,
please let me know. General library documentation is available at
mediawiki.org <https://www.mediawiki.org/wiki/OOjs_UI> and generated
code-level documentation at doc.mediawiki.org
<https://doc.wikimedia.org/oojs-ui/master/#!/api>.
- Trevor
Hi,
We have OAuth for browser based programs. But nothing for desktop
applications that are being used by users. (Like AWB etc).
These applications now have to ask for password, which is kind of safe
given that they are open source and running on computer of the user,
so at some point giving them password is as much insecure as giving it
to your we browser, but still, I believe that there could be slightly
better security model in use, that would make it safe to provide
password to a program that was compiled by anyone and that can be
potentially unsafe.
Let's take this sample model similar to OAuth:
* User would have extra panel in preferences, where they could
generate access tokens.
* For each token user could specify what application would have access to.
Generated tokens would be given to application instead of login and
password and the application could use them to login into mediawiki.
Users could revoke the tokens in anytime effectively invalidating any
tokens that potential hacker could steal using that 3rd application.
It sounds pretty simple to me, so why we don't have anything like that?
[Apologies for cross-post]
As a reminder, on Wednesday, 11 February 2015 at 12:00 (noon) PST (20:00
UTC)[0] there will be the first of a weekly series of open triage meetings
about VisualEditor.
We will discuss the release criteria for VisualEditor, and jointly
prioritise the work of the team, talking about the bugs and features which
are most important to you. We particularly welcome the presence of
volunteers who enjoy contributing MediaWiki code.
The joining instructions are available on MediaWiki.org[1]. Hope to see
many of you there.
[0] -
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150211T12&p1=224…
[1] - https://www.mediawiki.org/wiki/Talk:VisualEditor/Portal
Yours,
--
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
---------- Forwarded message ----------
From: Ellie Young <eyoung(a)wikimedia.org>
Date: Mon, Feb 9, 2015 at 8:55 PM
Subject: [Wmfall] Wikimania Scholarship Application Deadline is Approaching!
To: wikimedia-l(a)lists.wikimedia.org, Wikimania general list <
wikimania-l(a)lists.wikimedia.org>, Staff All <wmfall(a)lists.wikimedia.org>
The deadline for applying for a Scholarship to attend Wikimania 2015 in
Mexico City on July 15-19 is a week away!
** Monday 16 February 2015 23:59 UTC **
Please spread the word to anyone you know who might qualify.
A scholarship will cover the cost of an individual's round-trip travel,
shared accommodation,
and conference registration as arranged by the Wikimedia Foundation.
Applicants will be rated using a pre-determined selection process and
selection criteria by the Scholarship Committee, who will determine
which are successful. To learn more about Wikimania 2015 scholarships,
please visit:
https://wikimania2015.wikimedia.org/wiki/Scholarships
To apply for a scholarship, fill out the application form on:
https://scholarships.wikimedia.org/apply
It is highly recommended that applicants review all the material on the
Scholarships page
and the associated FAQ before submitting an application.
If you have any questions, please contact:
wikimania-scholarships at wikimedia.org
or leave a message at:
https://wikimania2015.wikimedia.org/wiki/Talk:Scholarships
Thank you,
Ellie Young
WMF Conference Coordinator on behalf of the Scholarship Committee
_______________________________________________
Wmfall mailing list
Wmfall(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wmfall
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
The MediaWiki Developer Summit had three main themes that helped
structuring the schedule. These themes were useful, and they can be more
useful for the hackathons in Lyon and Mexico City this year, since defining
them indvance will help everybody organizing their travel.
Anybody can propose a main theme at https://phabricator.wikimedia.org/T89084
Good candidates include Wikimedia software priorities, project meetings,
collaboration with external projects, topics of local relevance... Do not
hesitate posting proposals even if they are just an initial idea right now.
We want to agree on the main themes by the end of next week in order to
help people organizing their travel plans.
--
Quim Gil
Engineering Community Manager @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
There were several short wikitech outages last week caused by heavy
machine load on the server that (among other things) hosts the site. In
an attempt to distribute load a bit more reasonably I'm migrating that
web host to new hardware.
The transition should be fairly graceful as the new host is already up
and running. There will be a few interruptions in service, though:
- During the move the new wiki will be read-only. This should only last
about 10 minutes or so during the DNS switch-over.
- After the move there will almost certainly be a series of mishaps
involving the labs-controlling aspects of wikitech. I'll be scrambling
to fix them and don't expect to spend more than hour or so; I'll follow
up with another email if the interruption is an longer than that.
- As usual, login sessions will probably be broken necessitating a fresh
login to wikitech.
This is scheduled for Midnight GMT Tuesday, February 10th. That's 4PM
PST on Monday.
Currently, while {{urlencod}}ing, content in strip markers is skipped.
I believe this violates the expectation that the entire output
will be properly escaped to be placed in a sensitive context.
An example is in the infobox book caption on,
https://en.wikipedia.org/wiki/%22F%22_Is_for_Fugitive
There’s a brief discussions of the security implications of
some proposed solutions in the review of,
https://gerrit.wikimedia.org/r/#/c/181519/
It seems best (I guess) to just drop the content (`killMarkers()`).
Any opinions or better ideas?
Thanks,
Arlo