Hi list,
I recently helped shepherd a new skin into Mediawiki;
https://www.mediawiki.org/wiki/Skin:Erudite
I would like to think it is perfect in every way, but one area it
hasn't had any love is making sure it works well on mobile devices.
To the best of my knowledge it shouldn't do anything particularly
heinous, but I don't have any such devices to test it on. If anybody
has a few minutes and could have a play, and see if anything could
be improved, please do and let me know on list.
A live example of it is at
https://www.dur.ac.uk/nick.white/erudite-demo/mediawiki-current/
which should have full editing etc rights enabled. It's a dummy
wiki, so add whatever you like.
Thanks in advance!
Nick White
Yes, and we are updating our DB from the toolserver DB. There seem to be
several issues, and Tomasz Finc or Arthur can summarize them.
In brief, we had to do things in a temporary way in order to meet the
deadline.
And there were reasons we used our DB instead of the one on toolserver, but
once the contest is over, the traffic will be a lot less.
Phil
On Fri, Sep 28, 2012 at 8:45 AM, Lodewijk <lodewijk(a)effeietsanders.org>wrote:
> Hi Philip,
>
> Maybe I'm wrong here, but as far as I'm aware, the current monument
> database is actually being scraped each night from the wikipedia lists. So
> basically it is a mirror of the lists with a lag up to 24 hours (if
> toolserver works etc). But maybe we're talking about different databases?
> Probably it would be easiest to just use one way or another the Monument
> Database we're running, rather than reinventing the wheel.
>
> Lodewijk
>
>
> 2012/9/28 Philip Chang <pchang(a)wikimedia.org>
>
>> Back to Lodewijk's idea of articles and monuments, we unfortunately have
>> an issue with monuments, simply because the database is not maintainable.
>> However, I have wondered about accessing monuments through the Wikipedia
>> pages that list them.
>>
>
>
> _______________________________________________
> Wiki Loves Monuments mailing list
> WikiLovesMonuments(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments
> http://www.wikilovesmonuments.org
>
--
Phil Inje Chang
Product Manager, Mobile
Wikimedia Foundation
415-812-0854 m
415-882-7982 x 6810
Great input, thanks Lodewijk and Tomasz.
Your thoughts echo the thinking of the mobile team in terms of a broader
vision of mobile contributions. The difficulty is in biting off smaller
pieces that can realistically be achieved.
Making articles that are geo-tagged available is a current initiative and
requires new infrastructure. We currently use Geonames in the WIkipedia
apps, which is an external service and limited in usage volume. We want to
add the nearby function to the mobile site (which has much higher traffic
than the apps) and that is what is driving this new infrastructure
currently.
Then there is the idea of adding geo tags to articles. What a great usage
of mobile! Photos are an easy way to do this (killing two birds with one
stone), so your thinking is right in line with what we are hoping to do.
But there are some issues around submitting geo coordinates, whether
automatically or not, that have to be worked through.
Back to Lodewijk's idea of articles and monuments, we unfortunately have an
issue with monuments, simply because the database is not maintainable.
However, I have wondered about accessing monuments through the Wikipedia
pages that list them.
So yes, there are a number of next steps to be pursued. I will have to
defer to Howie and Maryana to pick this up, as today is technically my last
day. But as I said, I will be available as a volunteer.
Phil
On Fri, Sep 28, 2012 at 8:20 AM, Tomasz W. Kozłowski
<odder.wiki(a)gmail.com>wrote:
> Hi Philip,
> this wouldn't be very related to your question, but I've been recently
> pointed to the idea of user notifications; e.g. when user passes by a
> building (for instance a monument) for which we have geocoordinates
> but no picture, s/he might receive a notification from the app to take
> a photo.
>
> This was originally thought as a feature for the WLM app, but it might
> be useful for another purposes, too (for instance, for buildings which
> are not monuments, etc.).
>
> --
> Tomasz W. Kozłowski
> a.k.a. [[user:odder]]
>
> _______________________________________________
> Wiki Loves Monuments mailing list
> WikiLovesMonuments(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/wikilovesmonuments
> http://www.wikilovesmonuments.org
>
--
Phil Inje Chang
Product Manager, Mobile
Wikimedia Foundation
415-812-0854 m
415-882-7982 x 6810
Here is an idea:
Turn the WLM app into a similar app for uploading photos related to
Wikipedia articles. This was in fact the original goal of the mobile photo
upload project.
One take on this is to use the Nearby search and article search as a way to
find articles, then the upload will be given a title related to the article
and some metadata can include the article ID.
The WLM app will otherwise run the risk of not being functional past
October, due to backend issues.
Just a quick thought. Let the mobile team know if you think this is a good
idea.
Phil
--
Phil Inje Chang
Former Product Manager, Mobile
Wikimedia Foundation
Human.io is the new thing from Joshua Schachter, founder of bookmarking
site del.icio.us.
This time, however, he's not suggesting you share your travels with a few
friends — he's suggesting that you turn them into an army.
"If you want to build a flash mob, but have it actually do something
useful, this is your API," Schachter said. "It lets you invite your
audience to become part of the action."
The concept—developed by Paul Rademacher, creator of legendary
Craigslist/Google Maps mashup Housingmaps, and Nick Nguyen, formerly of
Yahoo and Mozilla — is straightforward enough: Human.io is a platform for
performing "micro-tasks".
First, you publish a simple, crowdsourceble activity, such as voting on
something, going to a particular location, or taking photos — anything that
might be accomplished with a smartphone's UI and its sensors. Then you tell
your readers, followers or friends about it. They start the app, get
cracking, and, finally, the results are sent back to you.
To illustrate how the platform works, Human.io developed an app aimed at
benefiting the Creative Commons, and Wiki Loves Monuments in particular: <
http://wikipedia.human.io/>.
The idea is to help Wikipedia's project to improve public access to
photography of the world's architectural and local heritage. If you want to
participate, install the free Human.io app (iOS, Android) and select the
"Photograph a historic place" task. It'll cough up a list of anything
nearby that's in the online encyclopedia's monument hit list. All you have
to do is head out, take a shot, and let Human.io do the rest. It'll show up
immediately at wikipedia.human.io, released under the Creative Commons
Attribution 3.0 Unported License.
It bridges the gap between a useful task — in this case, contributing to
Wikipedia's potential coverage of your neighborhood's history — and folks
who might not otherwise be in a position to help out, let alone have fun
doing so.
<http://boingboing.net/2012/09/25/humanio.html>
Inspired by the discussions of the design team meetings, I have been
playing around with a few ideas for a simple navigation model for the
mobile that can extend the feature set of tools and options available to
users. It struck me that the article lead, some images and infobox data can
give a very good idea of a topic that is alien to the reader and such a
compact view on the mobile screen has a lot of value.
It got me thinking of the possibility of decomposing any wiki page into
multiple 'views' or layers that can alter the way one views the same page
by selectively rearranging and hiding the content based on user usage
patterns. Possible page layers could be:
A) Overview: Condensed view of the article optimized for the small touch
screen. It can also contain an index of topics covered that can act as
navigation aid to jump directly to a section in the Article layer
B) Article: The whole article, just like what you see in the current mobile
site
C) Gallery: Thumbnails of pictures, videos from the article. Could also
fetch related content from other wikimedia projects
D) Category: Allows you to jump to related topics if you are interested in
the subject.
E) Discussion: The talk page to discuss
The search and other page functions including language selections go into a
menubar that floats above the article. It would work like the menubar in
Google Now which Pau Giner had showed during our meetings. When you scroll
down its hidden, as you scroll up, the menu pops up again, which means that
all the functions including search can be accessed from any part of the
page (A variation of the sticky nav). This also saves screen space when you
are reading and scrolling down, giving you a full page view of the article
with no distractions.
You can see a visual overview of this here:
http://upload.wikimedia.org/wikipedia/commons/f/fe/Wikimedia_mobile_layer_n…
Just an idea, more discussion with the design team pending.
--
Arun Ganesh
(planemad) <http://en.wikipedia.org/wiki/User:Planemad>
<http://j.mp/ArunGanesh>
FYI
---------- Forwarded message ----------
From: Philip Chang <pchang(a)wikimedia.org>
Date: Thu, Sep 20, 2012 at 8:53 PM
Subject: WLM Android app v1.2.4 Daigo-ji
To: Wiki Loves Monuments Photograph Competition <
wikilovesmonuments(a)lists.wikimedia.org>
Dear WLM Members,
The WLM Android app has been updated to v1.2.4, named Daigo-ji.
Release notes:
* Dynamically loads localization updates
* Clears large image previews before taking another photo - may help with
"out of memory" errors
* Stops "Mobile to desktop upload" category from being added to uploads
from the app - this category should be limited to desktop uploads from a
mobile upload
Please note: there are issues with the Cordova interface to the camera that
are outside of our control (Cordova is the app framework used to build our
mobile apps).
There are a significant number of users experiencing crashes and we are
limited in our ability to debug these problems, for several reasons:
* We are not able to reproduce these problems on the same devices that
seems to be experiencing the problems
* Google Play captures a part of the error which does not include the
Cordova aspects
* Google Play does not allow us to contact reviewers or people reporting
crashes
Therefore, if you hear of any users having such problems, please have them
contact us by email at: mobile-feedback-l(a)lists.wikimedia.org.
Thanks for your support.
Phil
--
Phil Inje Chang
Product Manager, Mobile
Wikimedia Foundation
415-812-0854 m
415-882-7982 x 6810
What is the meaning of the message wpmobj2me-lang-dialog-title in the
mobile Wikipedia app? "Language Set" can be translated in many
different ways.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
