I recently tried to create a small javascript to parse user signature times
on talk pages [1]. With it the readers would have been able to see the
signature's timestamp in their preferred timezone (and as a side effect it
would be consistent with the revision history) without breaking caching.
The main problem I had was that MediaWiki didn't provide a class attribute
wrapping the date nor the whole signature. There is a bug report on that
topic: https://bugzilla.wikimedia.org/show_bug.cgi?id=25141
After some time spent looking for a system message it seems the only
solution is to edit includes/parser/Parser.php. I added a span with a class
at this line:
https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/core.git;a=blob;f=include…
It works fine (at least in my own - limited - case).
Some questions related to what I've done:
- Would it be possible to wrap dates, or at least signatures in a class, as
suggested in bug #25141? it may be useful for others too
-- or perhaps to have a system message for dates (I'm not sure it's a good
idea)
- Is Parser.php the good place for that?
- Would a similar solution see its way into MediaWiki some day? or are
there problems I'm not seeing? (I'm not suggesting my script would be it,
it's a quick and dirty hack created with very limited knowledge.)
[1] using Moment.js <http://momentjs.com/>
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.
Since I don't think anyone reads mobile-l.
---------- Forwarded message ----------
From: Yuvi Panda <yuvipanda(a)gmail.com>
Date: Wed, Apr 3, 2013 at 12:53 AM
Subject: New Beta release of Wikimedia Commons App!
To: mobile-l <mobile-l(a)lists.wikimedia.org>
Hello! New beta release of commons app went out today!
Features of v1.0 beta 6 include:
## v1.0 beta 6
- Add categorization
- Add a 'Modifications Sync' framework for doing eventual-consistent page edits
- More consistent designb between single and multiple upload
- i18n updates
You can now add categories to your uploads, both single and multiple
uploads! They will be 'eventually consistent' - the categories aren't
saved immediately as you hit the 'save' button but will be saved on
next sync, whenever Android decides that is.
We're getting closer to a full v1.0 release - user account creation
and a bit more polish ought to do it.
Bug reports welcome at
https://bugzilla.wikimedia.org/enter_bug.cgi?product=Commons%20App
(pick the Android component).
Pull requests welcome at https://github.com/wikimedia/android-commons
Thank you!
--
Yuvi Panda T
http://yuvi.in/blog
--
Yuvi Panda T
http://yuvi.in/blog
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
Thanks everyone! Very excited to be working with you!
-Monte
On Mon, Apr 1, 2013 at 10:35 AM, Leslie Harms <lharms(a)wikimedia.org> wrote:
> Welcome Monte!!
>
>
> On Mon, Apr 1, 2013 at 10:25 AM, Kul Wadhwa <kwadhwa(a)wikimedia.org> wrote:
>
>> Monte - we're glad you left the ice fishing behind to join us. Welcome
>> aboard!
>>
>> --Kul
>>
>> On Mon, Apr 1, 2013 at 9:55 AM, Rachel Farrand <rfarrand(a)wikimedia.org>wrote:
>>
>>> Message from Tomasz!:
>>>
>>> ------
>>> Greetings all!
>>>
>>> I'm pleased to welcome Monte Hurd to the Wikimedia Foundation. He
>>> starts on April Fools Day!
>>>
>>> Arriving (most recently and quite gladly) from snowy Minnesota to join
>>> WMF as a software engineer, he's been enthusiastically focused on
>>> native mobile app development for the last few years since getting off
>>> the startup roller coaster.
>>>
>>> His native app projects have included image processing, drawing,
>>> physics asset pipelines, video creation, background server sync and
>>> experimental user interfaces.
>>>
>>> He joins the community and mobile team efforts to develop native, user
>>> friendly media management apps which co-evolve with the exploding
>>> capabilities of modern mobile hardware, with the goal of expanding the
>>> contribution possibilities of both users on-the-go and users whose
>>> only computing device may be a mobile device. Monte joining will
>>> complete the app team of Brion and Yuvi and will allow for them to
>>> knowledge share effectively across both iOS and Android. His initial
>>> task will be to support the store launch of the iOS Commons App to get
>>> us closer to our monthly 1,000 unique uploaders goal annual goal.
>>>
>>> Monte lives for solving programming and climbing challenges and spent
>>> a good portion of last year near Yosemite to be close to some of the
>>> best climbing on the planet. He's glad to be back in sunny CA!
>>>
>>> --
>>>
>>>
>>> --tomasz
>>>
>>>
>>> _______________________________________________
>>> Wmfall mailing list
>>> Wmfall(a)lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>>
>>>
>>
>>
>> --
>> Kul Wadhwa
>> Head of Mobile
>> Wikimedia Foundation
>>
>> _______________________________________________
>> Wmfall mailing list
>> Wmfall(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>
>>
>
>
> --
> Leslie Harms
> Office Assistant
> Wikimedia Foundation
> 415.839.6885 ext 6743
> https://donate.wikimedia.org/
>
>
>
>
> _______________________________________________
> Wmfall mailing list
> Wmfall(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
>
Welcome Monte! Welcome to the awesome mobile team.
-Alolita
On Mon, Apr 1, 2013 at 10:25 AM, Kul Wadhwa <kwadhwa(a)wikimedia.org> wrote:
> Monte - we're glad you left the ice fishing behind to join us. Welcome
> aboard!
>
> --Kul
>
> On Mon, Apr 1, 2013 at 9:55 AM, Rachel Farrand <rfarrand(a)wikimedia.org>
> wrote:
>>
>> Message from Tomasz!:
>>
>> ------
>> Greetings all!
>>
>> I'm pleased to welcome Monte Hurd to the Wikimedia Foundation. He
>> starts on April Fools Day!
>>
>> Arriving (most recently and quite gladly) from snowy Minnesota to join
>> WMF as a software engineer, he's been enthusiastically focused on
>> native mobile app development for the last few years since getting off
>> the startup roller coaster.
>>
>> His native app projects have included image processing, drawing,
>> physics asset pipelines, video creation, background server sync and
>> experimental user interfaces.
>>
>> He joins the community and mobile team efforts to develop native, user
>> friendly media management apps which co-evolve with the exploding
>> capabilities of modern mobile hardware, with the goal of expanding the
>> contribution possibilities of both users on-the-go and users whose
>> only computing device may be a mobile device. Monte joining will
>> complete the app team of Brion and Yuvi and will allow for them to
>> knowledge share effectively across both iOS and Android. His initial
>> task will be to support the store launch of the iOS Commons App to get
>> us closer to our monthly 1,000 unique uploaders goal annual goal.
>>
>> Monte lives for solving programming and climbing challenges and spent
>> a good portion of last year near Yosemite to be close to some of the
>> best climbing on the planet. He's glad to be back in sunny CA!
>>
>> --
>>
>>
>> --tomasz
>>
>>
>> _______________________________________________
>> Wmfall mailing list
>> Wmfall(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/wmfall
>>
>
>
>
> --
> Kul Wadhwa
> Head of Mobile
> Wikimedia Foundation
>
> _______________________________________________
> Wmfall mailing list
> Wmfall(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wmfall
>
--
Alolita Sharma
Director of Engineering
Language Engineering
Wikimedia Foundation
On 03/31/2013 10:58 PM, Dmitrii Kouznetsov wrote:
> Should I install git ?
No, this is a complete, downloadable version.
> Should I install PHP ?
Yes, MediaWiki requires at least version 5.3.2 of PHP.
> Should I install MathJax ?
> Should I install C++?
> Suould I install Latex?
None of these is needed.
> What versions of the software above are required for and compatible with
> your version of wiki?
Note that this is a release candidate for MediaWiki 1.21.0 -- it is not
"my" version of the software as I've done nothing special with this. I
am the release manager for MediaWiki and this is a release candidate for
a normal release.
This may not be absolutely clear since I used my own server for the
release instead of download.wikimedia.org. I had the release ready and
didn't want to wait for someone to upload it to download.wm.o, so I put
it on my own server. The next release candidate will be on download.wm.o.
> Does your version of wiki support pictures in PDF and/or EPS format?
MediaWiki supports uploading PDF and EPS files with the right
configuration. I haven't tried uploading EPS files, but providing
thumbnails of these and the PDFs should work.
--
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