Hi,
is there already a schedule to update jQuery and jQuery UI to 1.9 or are
there problems at moment? I want to use the new tooltip widget of jQuery UI
1.9 [1].
Best regards,
Jan
[1] http://jqueryui.com/tooltip/
We have a first write up of how we plan to support queries in Wikidata.
Comments on our errors and requests for clarifications are more than
welcome.
<https://meta.wikimedia.org/wiki/Wikidata/Development/Queries>
Cheers,
Denny
P.S.: unfortunately, no easter eggs inside.
--
Project director Wikidata
Wikimedia Deutschland e.V. | Obentrautstr. 72 | 10963 Berlin
Tel. +49-30-219 158 26-0 | http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
Hi, we at the mobile team are currently working on improving our
current hit rate, publishing the half-implemented plan here for review:
== Current status ==
* X-Device header is generated by frontend Varnish from user-agent.
* There are currently 21 possible X-Device values, which we decreased to 20
this week.
* X-Device is used for HTML variance (roughly, Vary: X-Device).
* Depending on X-Device, we alter skin HTML, serve it full or limited
resources.
* Because some phones need CSS tweaks and don't support media queries, we
have to serve them device-specific CSS.
* Device-specific CSS is served via separate ResourceLoader modules e.g.
mobile.device.android.
== What's bad about it? ==
Cache fragmentation is very high, resulting in ~55% hit rate.
== Proposed strategy ==
* We don't vary pages on X-Device anymore.
* Because we still need to give really ancient WAP phones WML output, we
create a new header, X-WAP, with just two values, yes or not[1]
* And we vary our output on X-WAP instead of X-Device[2]
* Because we still need to serve device-specific CSS but can't use device
name in page HTML, we create a single ResourceLoader module,
mobile.device.detect, which outputs styles depending on X-Device.[2] This
does not affect bits cache fragmentation because it simply changes the way
the same data is varied, but not adds the new fragmentation factors. Bits
hit rate currently is very high, by the way.
* And because we need X-Device, we will need to direct mobile load.php
requests to the mobile site itself instead of bits. Not a problem because
mobile domains are served by Varnish just like bits.
* Since now we will be serving ResourceLoader to all devices, we will
blacklist all the incompatible devices in the startup module to prevent
them from choking on the loads of JS they can't handle (and even if they
degrade gracefully, still no need to force them to download tens of
kilobytes needlessly)[3]
== Commits ==
[1] https://gerrit.wikimedia.org/r/#/c/32866/ - adds X-WAP to Varnish
[2] https://gerrit.wikimedia.org/r/55226 - main MobileFrontend change
[3] https://gerrit.wikimedia.org/r/#/c/55446/ - ResourceLoader change, just
a sketch of a real solution as of the moment I'm writing this
Your comments are highly appreciated! :)
--
Best regards,
Max Semenik ([[User:MaxSem]])
I put together the 1.21.0rc1 this afternoon. I'll announce it shortly,
but, first, some observations.
* When you add or remove a configuration variable, it should have
release notes. When you update the release notes, please make sure that
you also update MW.o. A number of variables are mentioned in the
release notes that don't have a corresponding page on MW.o. The
following configuration variables are the currently redlinked on
<https://www.mediawiki.org/wiki/Release_notes/1.21>. If you can update
their on-wiki documentation, I (and I'm sure others) would appreciate it.
** $wgBug34832TransitionalRollback
** $wgEnableCanonicalServerLink
** $wgPageInfoTransclusionLimit
** $wgMaxShellWallClockTime
** $wgShellCgroup
** $wgSquidPurgeUseHostHeader
** $wgDebugAPI
** $wgAPIGeneratorModules
* Should the breaking changes be consolidated to a single section of the
release notes? Right now, they are in three different sections. I
think they should be moved to the top of their section at the very least
(I did this on-wiki).
* There remains one pending change that is not in the 1.21 release
candidate -- "Password Recovery system uses Tokens" -- because it hasn't
been merged into core yet. This change will probably have to wait until
1.22, but I'll leave it on https://www.mediawiki.org/wiki/MediaWiki_1.21
for now.
--
http://hexmode.com/
[We are] immortal ... because [we have] a soul, a spirit capable of
compassion and sacrifice and endurance.
-- William Faulker, Nobel Prize acceptance speech
I would like to announce the release of MediaWiki language extension
bundle 2013.03
This release is compatible with MediaWiki 1.20.3.
* https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.03.tar…
* sha256sum: be4c6b5f80e27396555dc09cef0cec92c78cca9eeef796a230da281734738810
Quick links:
* Installation instructions are at https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to https://bugzilla.wikimedia.org
* Talk with us at #mediawiki-i18n @ freenode
Release notes for each extension are below.
Amir E. Aharoni
== Babel ==
Only localization updates.
== cldr ==
=== Highlights ===
* Adding support for time units
=== Noteworthy changes ===
* (bug 38209) Remove duplicate array keys
== CleanChanges ==
Only localization updates.
== LocalisationUpdate ==
Internal code cleanup and optimization, making updates faster.
== Translate ==
=== Highlights ===
==== Translation UX ====
The new Translation UX is getting out of the beta status and becoming
release-ready.
The variable $wgTranslateUseTux can be used to control which interface
will the users see by default. The default value is true. Set it to false
to make the old green-style translations editor show by default. The user
can choose the editor version by adding tux=0 or tux=1 to the URL.
The plan is to remove the old editor in the future.
==== Other notes ====
Several internal fixes were made in File Format Support (FFS) and in core
Translate features, but no new features were introduced. See below for details.
=== Noteworthy changes ===
==== Translate UX ====
* Proofreading view added to Translate UX.
* Page view added to Translate UX. It is similar to the default "List" view,
but it gives every message more space and partially parses the messages rather
than show them as plain text.
* Added a "Discard changes" button.
* Various visual design adjustments.
* (bug 45493) Do not consider empty string to mark a translation as "unsaved"
* (bug 45481) Move focus to search for the project selector
* (bug 45488) Remove delay in enablement of "save translation" button
* Allow inserting a translation from the helper language with a click
* Workflow state selector is now only shown for groups with states
and the correct state is shown
==== File Format Support ====
* (bug 45354) XML for Android export should have escaped ' and "
* (bug 42635) Some GettextFFS messages were not unfuzzied on import:
Handling of external changes only affecting the fuzzy flag are now
handled properly on import
* Add fuzzy support to AndroidXmlFFS
* Don't create empty files in AndroidXmlFFS
* Empty msgctxt is now exported correctly in GettextFFS
* (bug 42612) Have PythonSingleFFS observe the supplied mapping
of internal language codes to product language codes
==== Other ====
* The "Recent Additions" filter displays only relevant messages -
without optional,
ignored and discouraged.
* Converted the logging code to the new LogFormatter
* (bug 44328) Do not display fuzzy translations on translation pages
* Fix and speed up translatable pages moving
* (bug 45345) Run mapped code through wfBCP47()
== UniversalLanguageSelector ==
=== Highlights ===
UniversalLanguageSelector is updated to the latest version. The latest
release of MediaWiki 1.20 supports the recent updates for the preferences
handling, and this allows users properly save their ULS preferences.
=== Noteworthy changes ===
==== Display and design ====
* (bug 42384) Don't show the tooltip if the ULS panel is on
(preventing the overlap)
* (bug 42440) Fix button state when canceling
* Styling of settings to fit the bottom of the ULS
* (bug 43568) Languages are shown multiple times
* (Bug 42439) Incorrect vertical alignment for Telugu web font
==== Webfonts ====
* Support for the Amiri webfont in the standard Arabic language (ar).
* Added the Alef font for Hebrew.
* Add Tuladha Jejeg font for Javanese
==== Other ====
* (Bug 42378) Make "disable IME tools" effects immediate as a preview
* Update jquery.uls and make it more modular
* Provide a base ULS RL module and separate UI language selection
* The non-standard language code als now redirects to the standard code gsw.
--
Amir Elisha Aharoni ። אָמִיר אֱלִישָׁע אַהֲרוֹנִי
Localization developer ። מְפַתֵּחַ תְּמִיכָה רַב־לְשׁוֹנִית
Wikimedia Foundation ። קֶרֶן וִיקִימֶדְיָה
Vagrant is a command-line tool for automatically provisioning virtual machines according to scripted specifications. The mediawiki-vagrant project bundles together specifications for quickly and easily provisioning a virtual machine running MediaWiki, suitable for development work.
I announced it a few months ago, when I had something nominally useful to share. Some people found it useful, but it was something I had cobbled together in a hacky way as I was learning Vagrant, and I wasn't very happy with the end result. In the intervening months, I got a lot of useful suggestions, and became more proficient in writing Vagrant and Puppet configurations, so I decided to do things over.
There's a lot more work to do (better profiling tools!), but I think it works quite well now, so I would appreciate some testing and feedback from others.
Installation instructions are available here: http://www.mediawiki.org/wiki/Vagrant
I hope you check it out, and that you find it useful. Feedback would be much appreciated.
I'd also like to publicly thank Yurik for testing this extensively on Windows and providing detailed logs when things broke. Thanks, Yurik!
--
Ori Livneh
All,
We are excited to announce that Brandon Black will join us this Monday
(2013-04-01) as a full-time member of the Operations Engineering team.
Brandon comes with deep and wide technical experience. Previously, he held
senior systems engineering positions in companies like SqueezeNetwork.com,
Veritas DGC, MCI WorldCom and Networks Online.
He is an active proponent and contributor of open-source software, and has
contributed a new GPL-licensed DNS software
(gdnsd<https://github.com/blblack/gdnsd>)
to accomplish global-level geographic balancing and automatic failover
without paying for expensive commercial solutions.
Brandon resides in Magnolia, TX, but has roamed the planet all his life
(like spending his High School years in Singapore). He is excited to join
the Wikimedia Ops team and hopes to learn many new things from the
experience. His interests include auto racing, being a professional
amateur, and learning new skills by starting projects which he has no idea
how to finish.
Brandon will be in San Francisco office this coming Monday and please drop
by to welcome him!
Thanks,
CT Woo
fyi, there is a nice % of grants for technical projects approved.
You can find the list at
https://meta.wikimedia.org/wiki/Grants:IEG#ieg-engaging or keep reading.
-------- Original Message --------
Subject: [Wikimedia-l] Announcing Round 1 Individual Engagement Grantees
Date: Fri, 29 Mar 2013 14:24:02 -0700
From: Siko Bouterse <sbouterse(a)wikimedia.org>
Reply-To: Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org>
To: wikimedia-l(a)lists.wikimedia.org
Hi all,
I’m happy to announce the first round of Individual Engagement
Grantees today! The Wikimedia Foundation makes a variety of types of
grants, many of which focus on groups and organizations. Individual
Engagement Grants exemplify our commitment to increase support to
individual contributors to Wikimedia projects, with a particular focus
on making online improvements. These grants will support 8 Wikimedians
working individually and in small teams for 6 months to complete
projects that benefit the Wikimedia movement, serve our mission, and
strengthen our communities.[1]
For this pilot round, which began in February 2013, Wikimedians
submitted over 50 ideas and drafts from around the world. WMF
grantmaking staff narrowed these down to 22 complete proposals meeting
the eligibility criteria for review.[2][3]
18 Wikimedians formed a volunteer committee, with participants from 12
countries and from Wikimedia projects in 14 languages. .[4] Committee
members reviewed each proposal carefully, scoring them against a
rubric of pre-defined selection criteria and making recommendations
based on available funding for this round.[5] WMF grantmaking staff
shared aggregated scores and comments back with the community, while
the committee continued its deliberations to finalize a recommendation
to WMF to fund 8 projects in total.
All eight projects have been approved for funding by the WMF. In
examining the recommendations, we were struck by how varied these
projects are in terms of grant size, project methodology and
engagement targets. A central aim of Individual Engagement Grants is
to foster innovation, with a particular focus on online impact. We
think that innovative ideas and the skills that various contributors
bring to Wikimedia projects can lead to better online environments for
everyone, and we hope to learn a lot from these grantees about how we
can support more of this across the movement.
The round 1 selected projects are:
“Build an effective method of publicity in PRChina,” led by Chinese
Wikipedian User:AddisWang, funded at $350.[6] Addis and a small team
of volunteers based in mainland China will be experimenting with
social media campaigns to grow awareness of Wikipedia in China.
“Reply Edits,” led by User:Jeph paul, funded at $500.[7] Jeph is
building a MediaWiki gadget that creates a visual playback of the edit
history of a Wikipedia article, allowing users to see an article’s
change over time.
“The Wikipedia Library,” funded at $7500 and “The Wikipedia
Adventure,” funded at $10,000, will both be led by User:Ocaasi.[8][9]
It is worth noting that we hadn’t anticipated a dual project situation
and don’t expect it to be a usual circumstance. We’ve decided to fund
both ideas in this round, though, because IEGrants focus on funding
promising, feasible projects with good community support wherever we
find them. For the Wikipedia Library, Ocaasi will be building and
consolidating partnerships with reference providers donating access to
reliable sources for Wikipedia editors, and improving the systems for
managing these programs. The Wikipedia Adventure is an on-wiki game
that will be piloted on English Wikipedia using the Guided Tours
extension to determine whether this type of interactive learning is an
effective engagement strategy for new editors.
“Consolidate wikiArS to involve art schools,” led by Catalan
Wikimedian User:Dvdgmz, funded at 7810 Euros.[10] The WikiArS outreach
program builds partnerships with art and design schools to teach
students to create images for donation to Wikimedia Commons and use in
Wikipedia articles. This grant will support focused experimentation in
the existing Catalan program’s models that can allow the initiative to
scale and to be sustained as an international program.
“Elaborate Wikisource strategic vision,” led by Catalan Wikisource
User:Micru and Italian Wikisource User:Aubrey, funded at 10,000
Euros.[11] This project brings together the global Wikisource
community and other stakeholders to define a vision for the project’s
future. They’ll begin work on near-term goals that can be accomplished
by volunteers on-wiki, and investigate paths forward for longer term
improvements to Wikisource.
“MediaWiki data browser,” led by User:Yaron K, partially funded at
$15,000 in order to pilot the initial concept.[12] Yaron’s project
will create a framework to allow any user to easily generate apps or
websites to browse sets of structured data that exist on Wikipedia and
other projects running on MediaWiki.
Finally, we’ve provisionally approved an 8th project for funding --
“MediaWiki and Javanese script,” led by User:Bennylin, funded at $3000
-- provided that a couple of dependencies can be satisfied.[13] This
project will provide technical support using a “train-the-trainers”
model that teaches volunteers how to use Javanese script online,
facilitating the transcription of Javanese texts to projects like
Javanese Wikisource. The newly developed Universal Language Selector
extension for MediaWiki makes the use of this script online
increasingly possible. Because Benny’s project will rely on the
availability of this extension on all Javanese Wikimedia projects, the
start of this grant depends on the WMF Internationalization team’s
completing its scheduled deployment in coming months. We would also
like to see more discussion and input from other members of the
Javanese community demonstrating the potential of this project, and
will be working with Benny to figure out how to support those
conversations while we await the deploy.
The new grantees will begin work on their projects in the coming weeks
and they’ll be sharing progress and learnings with us all along the
way. Please visit their pages on Meta-Wiki for complete project
information and updates.[1]
Thanks to everyone who participated in this round! We look forward to
seeing even more of your ideas and input in preparation for round 2,
which begins on August 1st.[14]
Warm regards,
Siko Bouterse, on behalf of the Wikimedia Foundation and the IEG committee
[1] https://meta.wikimedia.org/wiki/Grants:IEG#ieg-engaging
[2] https://meta.wikimedia.org/wiki/Grants:IEG#ieg-learn
[3] https://meta.wikimedia.org/wiki/Grants:IEG/Committee/Workroom/Review/All
[4] https://meta.wikimedia.org/wiki/Grants:IEG/Committee#ieg-members
[5]
https://meta.wikimedia.org/wiki/Grants:IEG/Committee/Workroom/Review#review…
[6]
https://meta.wikimedia.org/wiki/Grants:IEG/Build_an_effective_method_of_pub…
[7] https://meta.wikimedia.org/wiki/Grants:IEG/Replay_Edits
[8] https://meta.wikimedia.org/wiki/Grants:IEG/The_Wikipedia_Library
[9] https://meta.wikimedia.org/wiki/Grants:IEG/The_Wikipedia_Adventure
[10]
https://meta.wikimedia.org/wiki/Grants:IEG/Consolidate_wikiArS_to_involve_a…
[11]
https://meta.wikimedia.org/wiki/Grants:IEG/Elaborate_Wikisource_strategic_v…
[12] https://meta.wikimedia.org/wiki/Grants:IEG/MediaWiki_data_browser
[13]
https://meta.wikimedia.org/wiki/Grants:IEG/MediaWiki_and_Javanese_script
[14] https://meta.wikimedia.org/wiki/Grants:IdeaLab
--
Siko Bouterse
Head of Individual Engagement Grants
Wikimedia Foundation, Inc.
sbouterse(a)wikimedia.org
Imagine a world in which every single human being can freely share in
the sum of all knowledge.
Donate or click the "edit" button today, and help us make it a reality!
_______________________________________________
Wikimedia-l mailing list
Wikimedia-l(a)lists.wikimedia.org
Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l
Hello all,
Next week we'll be seeing the usual round of deployments, with these
highlights:
* For those that care about version numbers, we'll be starting 1.22wmf1
on Monday. :)
* On Wednesday we'll be deploying Phase II of WikiData to English
Wikipedia; expect big and good things!
For all of the gory details, see:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_April_1st
Thanks,
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |