We've had a few MediaWiki talks at OSCON recently (this year Trevor and
Roan did a great presentation about ResourceLoader); it tends to be a good
mixer conference for the US FOSS community and has had great JavaScript and
mobile tracks the last couple years (though it does have some vendor
overload in other areas).
Just a heads-up that the call for presentations is due in January:
http://www.oscon.com/oscon2012/public/cfp/197?imm_mid=079f65&cmp=em-conf-os…
-- brion
I have a parser function that is not being rendered properly by the experimental Preview tab in WikiEditor. The function does the following:
* It add a custom property "foo" to the ParserOutput object, with value "bar"
* It hooks OutputPageBeforeHTML to render the value "bar"
When I use the "Save Page" or "Show Preview" buttons below the edit box everything works fine. With the experimental Preview tab, though, the value doesn't get rendered. (It is in the ParserOutput object though.) I'm guessing that OutputPageBeforeHTML doesn't get called by the Preview tab.
I also tried hooking EditPageGetPreviewText to render the value also, but that doesn't work either with the Preview tab.
Any advice appreciated. Should I be using a better/additional hook?
Thanks,
DanB
Do we have a reason we have php5-common pinned in puppet? (see
generic-definitions.pp::145 generic::webserver::php5 )
The reason I ask is that with this, another generic definition
(generic::webserver::php5-mysql) breaks due to the dependancy of
5.3.2-2wm1 , while the pinning causes the installation of
5.3.2-1ubuntu4.10
I would change the generic::webserver::php5 definition to remove the
pin, but I want to make sure that nothing breaks first.
Leslie
--
Leslie Carr
Wikimedia Foundation
AS 14907, 43821
Greetings,
After some discussion in the IRC, http://www.mediawiki.org/wiki/Project:Glossary has been setup to house MW related terminology.
Right now it's largely MW related terms borrowed from enWP's glossary. However, over time we should try putting terms commonly used on MW.org or in MW documentation on the Glossary.
An early example of entries is clarity on the terms "enterprise wikis" vs. "third-party wikis" vs. "corporate wikis".
Feel free to email me off-list if there are terms you'd like added but just don't feel compelled to add yourself. :)
-greg aka varnent
-------
Gregory Varnum
Founding Principal, VarnEnt
Lead Administrator, WikiQueer
Lead, Aequalitas Project
@GregVarnum
fb.com/GregVarnum
Looking over some bug entries about layout on mobile for some pages,
especially Portal pages, reminds me that formatting is not just MediaWiki's
responsibility -- it's also the wiki authors' responsibility. And of course
since it's a wiki, that includes us. ;)
Starting from <https://bugzilla.wikimedia.org/show_bug.cgi?id=32123> and
friends I looked over some of the mobile style issues on <
https://en.wikipedia.org/wiki/Portal:Literature> and its related portals.
The two main issues that stood out:
* two-column layouts being too small to fit their content on small screens
* hardcoded table layouts, usually of icons of related portals to click on
The two-column layout I found I was able to make fall back to a
single-column layout with a little tweaking: moving the hardcoded float &
width styles out to a class in MediaWiki:Common.css, and using CSS media
queries to disable the width settings and let them become full column on
smaller screens.
(The media query right now won't actually get used on mobile, since we
don't actually load the MediaWiki:Common.css -- but it has the same effect.
:)
I started a discussion on this at <
https://en.wikipedia.org/wiki/MediaWiki_talk:Common.css#Portal_column_width…>
-- if this is working well we can go ahead and fix up a bunch of portal
pages by bot.
For the hardcoded tables of icons, I started on a new template with a more
modern layout that simply fits the window, similar to how <gallery> got a
facelift a while ago.
Links to that template & demo are at the above talk thread.
Don't forget -- MediaWiki extends to and binds with its content, and making
our flagship sites look good on large and small screens alike should be all
our responsibility. Chip in and help fix any bad layouts you find!
-- brion
Just a quick note: Antoine updated the diff view styles in trunk to use the
green/blue scheme that's been in use on fr.wikipedia.org and others for
some time:
<https://www.mediawiki.org/wiki/Special:Code/MediaWiki/105280>
This should be a bit more consistent than the scheme we were using in 1.18,
and is specifically designed to be legible to people with various types of
color blindness as well as the general population.
-- brion
Just gave Jamie Thingelstad (thingles) extensions access, to work on the
Piwik integration extension. Welcome, Jamie!
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation
Just a reminder this will be happening today at 2100UTC/1pm PST!
---------- Forwarded message ----------
From: Mark A. Hershberger <mhershberger(a)wikimedia.org>
Date: Tue, Dec 6, 2011 at 3:23 PM
Subject: Fundraising -- use your technical skills to help
To: wikitech-l <wikitech-l(a)wikimedia.org>, foundation-l <
foundation-l(a)lists.wikimedia.org>
Cc: Arthur Richards <arichards(a)wikimedia.org>
What: Fundraising triage
When: Wednesday, December 7, 2100UTC
Time zone conversion: http://hexm.de/bc
Where: #wikimedia-dev on freenode
Use http://webchat.freenode.net/?channels=wikimedia-dev
if you don't have an IRC client
Etherpad: http://etherpad.wikimedia.org/BugTriage-funcom
Tomorrow, I'll be holding an IRC meeting on the open fundraising-related
issues that Arthur Richards and I identified today as things that could
benefit from community involvement.
If you are able to contribute any help on these issues -- several of
which are targeted to the CentralNotice system -- you will improve the
experience of many users of the Wikimedia projects.
* https://bugzilla.wikimedia.org/17108 Make "Hide" Cookies notice
independent
* https://bugzilla.wikimedia.org/24950 Make CentralNotice option checkboxes
sortable
* https://bugzilla.wikimedia.org/26026 Add API module for
Special:FundraiserStatistics
* https://bugzilla.wikimedia.org/26387 Add better key to Fundraiser stats
page
* https://bugzilla.wikimedia.org/30818 Special:FundraisingStatistics should
display selected yea...
* https://bugzilla.wikimedia.org/32441 Year filtering on
Special:FundraiserStatistics broken
* https://bugzilla.wikimedia.org/32536 CentralNotice API
Bring your javascript and PHP chops and I'll see you there!
Mark.
--
Arthur Richards
Software Engineer
Fundraising/Features/Offline/Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Now that $wgMessageCache is obsolete in 1.18.0, what is the approved way for an extension to add a system message dynamically at runtime?
That is, what is the new way to do $wgMessageCache->addMessage(a, b)?
http://www.mediawiki.org/wiki/Manual:$wgMessageCache does not say.
Thanks,
DanB