Hello,
I would like to announce the release of MediaWiki Language Extension
Bundle 2013.10. This bundle is compatible with MediaWiki 1.20.7 and
MediaWiki 1.21.2.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.10.tar…
* sha256sum: 04b1a1db293439553c225765a41add5f0bcd3ad4dce7f89e1f098276470e96c4
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.
-- Kartik Mistry
== Babel and CleanChanges ==
* Only localization updates.
== CLDR ==
* Use native digits on 'onGetHumanTimestamp'.
* Localisation updates.
== Translate ==
=== Noteworthy changes ===
* Introducing of the TranslationStash feature. It's the place where
sandboxed users can store their translations before they are given
full translator rights.
** Added special page for TranslationStash.
** Show the translations of the user for review in Special:TranslateSandbox.
* The Autonym font is now used in the language list and the tagcloud
in Special:SupportedLanguages.
* Bug 55607: Use group source language instead of hardcoded 'en'
language. For most cases (e.g., at translatewiki.net) the source
language of translations is English, this is not always the case.
Source language is set to group's source language now.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Bug 54594: Keep correct lang attribute when the display settings are closed.
* Bug 53734: Fix the monospace font usage for input fields for Latin scripts.
* Bug 55492: Use of jquery.ime with the VisualEditor has been disabled
in the Universal Language Selector until Input Method support is
improved.
* Reset the language and the font while live preview of content font
from Display Settings. If not reset, the font-family will persist for
languages without font preferences.
* Use the Autonym font for language autonyms in the Language Search
box and Interlanguage links.
=== Fonts ===
* Use AbyssinicaSIL font for Ge'ez and Tigre languages.
* Update Meera font from upstream.
=== Input methods ===
* Improvement in the Hindi Phonetic keyboard.
* Added support for shift key mappings.
* Added Shift+Space = ZWNJ support for Persian Keyboard.
== Known bugs ==
* Bug 56160: Input Method labels are displayed with inconsistent text
in the Language Settings panel when layouts are changed usin keyboard
menus on input boxes.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
PLEASE FORWARD TO WHOEVER MIGHT BE INTERESTED
Wikimedia will participate in the FOSS Outreach Program for Women -
Round 7. Interns of this program work full time in an open source
project during 4 months.
https://www.mediawiki.org/wiki/FOSS_Outreach_Program_for_Women
Candidates interested are encouraged to add themselves to the table at
https://www.mediawiki.org/wiki/Outreach_Program_for_Women/Round_7#Candidates
- even if you are still preparing your proposal.
We are actually running late (my fault). The application process is open
until November 11. The internship period goes from December 10 to March
10, 2014.
The Wikimedia Foundation is planning to fund up to 8 interns. This is a
great opportunity for Wikimedia / MediaWiki related projects. Our
process is quite simple: define a project, find the mentors and go for it!
https://www.mediawiki.org/wiki/Mentorship_programs/Possible_projectshttps://www.mediawiki.org/wiki/Mentorship_programs/Possible_mentors
The previous featured projects and confirmed mentors have been moved
respectively to the Raw and Bench sections. If you want to participate
in this OPW round move the entries back to the featured sections.
New projects and mentors are welcome too, of course!
If you have any questions please ask.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
The HTTP Archive (<http://httparchive.org/>) audits the setup and
performance of popular websites, reporting things like load times,
download sizes, performance scores, waterfall charts, and cache
headers. They provide per-site reports as well as aggregate data about
trends in web technology.
They added several Wikimedia wikis to their index last month and the
first two reports (dated Oct 1 and Oct 15) are available. The reports
for the desktop site of the English Wikipedia are available here:
<http://httparchive.org/viewsite.php?pageid=11675485>.
(I do not expect to see much variation across Wikimedia wikis, since
they are co-hosted on the same infrastructure.)
There's a wealth of data available. It should help us assess how we're
doing relative to other sites and where we need to improve. I plan on
studying this data on an ongoing basis and I invite / encourage you to
do the same. Be sure to share your discoveries with this list.
---
Ori Livneh
ori(a)wikimedia.org
On 10/25/2013 02:51 AM, Jared Zimmerman wrote:
> Matt, we're not planning on getting rid of blue buttons but the colors
> will now have meaning, and since this is a one step action (send a
> password reset email) it gets a green button here.
I see, my mistake. I unintentionally exaggerated the semantic changes
you're making.
The colors do have meaning already, though the well-known blue button
has somewhat orthogonal semantics. mw-ui-primary is currently the key
(primary) button of a form, e.g. Log in. That translates to blue in
Vector, and is the one currently used on Login and Signup.
mw-ui-constructive is green, and mw-ui-destrructive is read (roughly the
same as the proposed standard, though the appearance is different).
> Blue = Progressive (more steps in the process)
> Green = Constructive/Completion (only/final step in a process)
> Red = Destructive
Still, that is a change in usage. It means both the login and signup
will be green, for starters.
Matt Flaschen
Running mw.loader.inspect('css') in a JavaScript console will now
report CSS stats for each active ResourceLoader style module,
including the total count of selectors and the percentage of those
that match some node in the current DOM.
---
Ori Livneh
ori(a)wikimedia.org
Liangent and Micru have proposed to use Code-in to get a bunch of
wikitext templates rewritten in Lua. Let's do it! I also believe that
this is a very good type of task for Google Code-in.
https://www.mediawiki.org/wiki/Google_Code-In#Lua_templates
Please list there wikitext templates that you want to seee rewritten in
Lua.
It is important to have a couple of meta-mentors for this Lua templates
category of tasks. Ideally we should get also involved the maintainer(s)
or original author(s) of the templates, so they can help checking that
the end result fulfulls the requirements of the original template.
There is no need to file bug reports about each template at this point.
Linking to the templates is enough for now.
PS: those of you involved in the subcommunity of templates writers,
please help spreading this call. We need help mentoring, and in exchange
we can get a lot of fresh help getting tasks done.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi,
I am Nasir, an active contributor of Bengali WIkipedia. I use the email
notifications for the change on my watch list pages. The email is not
formatted as it should. I faced the following issues for the Bengali emails
and i think these should be fixed soon.
* Sometimes a new line appeases between the words of a page name, and
sometimes new line appears after 4/5 words in a sentence. I think we are
using a fixed DIV width for these texts. If it will be removed then it may
be fixed.
* Unicode URLs are not readable at all. For the Bengali wiki urls we can
make some changes to make the url more readable. like url format could be
like this <a href="PAGE_LINK">http://bn.wikipedia.org/wiki/PAGE_NAME</a>
*--
*regards
*Nasir Khan Saikat* <http://profiles.google.com/nasir8891>
www.nasirkhn.com
Hi all,
OrenBachman has asked several questions about how to evaluate the impact of
Hackathon events on the Evaluation Portal*[1]* and I'm hoping some folks
from this list can share their advice and perspectives.
Please read and respond there if you have input. Several outstanding
questions are:
1. do you know of any available publicly stats on how many first time
MediaWiki hackers make use of git/gerrit?
2. can you share any good strategies for getting as many attendees as
possible to set up git/gerrit userids prior to the event?
3. can you provide any examples of reports from previous Hackathons that do
a good job of describing various impact/participation metrics?
4. Safe space policy - How have breaches to the safe space policy been
handled in recent events? How have they been reported?
I'm going to follow up elsewhere about the legal issues OrenBachman raises,
but feel free to share your experiences with those as well.
Thanks for your assistance,
Jonathan
*[1]*
https://meta.wikimedia.org/wiki/Programs:Evaluation_portal/Parlor/Questions…
--
Jonathan T. Morgan
Learning Strategist
Wikimedia Foundation