Greetings all,
Last month Arthur made significant strides to remove a lot of WMF
customizations inside MobileFrontend (http://bit.ly/Ht9StP). That was
a good first step at addressing the issues rasied in
http://bit.ly/HZbgVW but more needs to be done if we want to reach
Brion's vision of,
"One codebase to do everything except WAP".
In order to do this, MediaWiki at its core has to become device aware.
We have to get to a point where providing output for desktop, mobile,
tablet, etc is as simple as described in bugzilla:30405
(http://bit.ly/I70xI7)
We've drawn up a task list and documented it at http://bit.ly/Hw5TbT .
While some tasks block on the new parser most do not. Specifically
* Move mobile actions to special pages (in order to avoid caching
related issues)
* Move DOM parsing to core
* Improve DOM parser caching
* Skinning + making MW device aware
are all tasks that can be picked up now. If you've wanted to hack on
mobile then this is a great time to set the future of how editors,
developers, etc create device aware solutions.
Please throw up comments on the discussion page and join us on
#wikimedia-mobile.
— Tomasz
Hi everyone,
In order to avoid stomping on the Easter holiday in Europe, we're
postponing the first day of the deployment of MediaWiki 1.20wmf01
Tuesday, April 10, 18:00-20:00 UTC (11am-1pm PDT): MediaWiki 1.20wmf01
deployment - test2, potentially mediawiki.org
Wednesday April 11, 18:00-20:00 UTC (11am-1pm PDT): Potentially window
for MediaWiki.org 1.20wmf01 deployment if needed
Monday, April 16, 18:00-20:00 UTC (11am-1pm PDT): MediaWiki 1.20wmf01
deployment - Deploy to all non-Wikipedia sites (commons, Wiktionary,
Wikisource, Wikinews, Wikibooks, Wikiquote, Wikiversity) --
potentially split into two deployments if needed
Monday, April 23, 18:00-20:00 UTC (11am-1pm PDT): MediaWiki 1.20wmf01
deployment - Deploy to English Wikipedia
Wednesday, April 25, 18:00-20:00 UTC (11am-1pm PDT): MediaWiki
1.20wmf01 deployment - Deploy to other Wikipedias
Also, some bikeshedding on the branch name: I vote that the branch
name to be wmf/1.20wmf01 , and subsequent deployments to follow that
scheme. That way, we can still say 1.20wmf01 as shorthand, and people
can figure out that "oh, you prefix wmf/ on the front for permissions
reasons".
Other work that's underway or needs to get underway:
* Chad has started the work of converting make-wmf-branch to Git:
https://svn.wikimedia.org/viewvc/mediawiki/trunk/tools/make-wmf-branch/defa…
* Aaron is also working on the scripts for pulling our WMF-specific
hacks and reapplying them in 1.20.
* We still need to audit the scap/sync scripts to make sure that .git
folder is being excluded on scap. Roan has started looking at that
now.
During the next few weeks while both 1.19wmf1 and 1.20wmf01 are out
there, we're going to need to use both Subversion and Git for
deployment-oriented code.
Rob
Hi,
Chad recently mentioned that based on opinion of wikimedia users, most
of users prefer simple options, I guess we could create a feature,
perhaps a checkbox "Display advanced options" to user preferences,
move lot of current settings which aren't really supposed to be
changed by people who do not understand how they work and implement
various new options in that.
The advanced options could allow users to customize their recent
changes feed and many similar pages, hiding certain links, or toggling
various stuff. This would be great benefit for regular users since the
option would be more clear and contain only stuff they likely want to
change.
I think we should move following to hidden section:
Anything related to unified logins, new users do not need to use this
Image size limit etc, most of regular users do not even understand
what is this for
Advanced options (whole section)
Watchlist token, most of regular users do not even understand what is this for
Search: Disable AJAX suggestions, Enable enhanced search suggestions
(Vector skin only)
Whole misc
Instead of these options we could fill the space with description of
remaining options
When user check the "Advanced" they would of course see all options +
some extra new options
I guess this would be benefit either for advanced users as well as
newbies / computer illiterates
Hi everyone,
I'm putting together the list of existing extensions that want to
be migrated with the next batch. Everyone who has an existing
extension and wishes to be migrated in this batch, please add
your extension and maintainer(s) to the page on mw.org[0].
I believe there was some confusion and people were signing up
on the "new repositories" page. All of those entries were moved
to the new page.
The deadline to get on the list is Wednesday at 23:59 UTC.
The planned migration window is going to be on Friday.
Again, this is only for extensions that are already in SVN.
-Chad
[0] http://www.mediawiki.org/wiki/Git/Conversion/Extensions_queue
Hello all,
I'm presenting a GSOC proposal for a native desktop
application designed for mass uploading files on
upload campaigns.
This follows the call by Odder at [1] for such a tool,
and indeed the scope of the tool would be tailored to
WikiLovesMonuments.
The deliverable is such an application, which shall be:
* A tiny autocontained program (probably in C++), with
different versions for each target operating system.
* Configurable defaults for uploading to Wikimedia Commons
own images as cc-by-sa with given templates and categories.
* The user shall be able to change the license / categories
if needed.
* Request the monument id for the image.
* Validation of the monument identifier through a web
service if available and time permits.
* Basic documentation of the competition (rules and FAQ)
* Contains the WLM logo somewhere.
* Localisable through translatewiki.net for at least the
28 countries of [2]
* Save configuration of images description for later upload.
* Asynchronous upload of the images in the background.
Opinions? Improvements? Sexy names? Mentors?
All of them are welcome!
1-
http://lists.wikimedia.org/pipermail/wikilovesmonuments/2012-March/002538.h…
2-
http://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Monuments_2012/Partici…
Hey all,
If some of you used the deployment site at wmflabs.org please note
that I am renaming the central wiki this week from:
labs.wikimedia.beta.wmflabs.org to
deployment.wikimedia.beta.wmflabs.org
The previous domain should redirect, but it may result in some
outages. This rename is done as a result of discussion we had between
some other devs, there were some complains that the current name is
confusing people, since some of them thought that deployment site is
wikimedia labs, while in fact it's a project of wikimedia labs. If
there are any issues or requests regarding deployment site, please
create a ticket in bugzilla, we have a section deployment beta cluster
in Wikimedia Labs product.
Thank you
Hi,
I am participating in GSOC'12 with my proposal for Green SMW [1].
This proposal is about reducing the carbon footprint of SMW , in other
words it will enhance the performance of SMW significantly.
All the details are on [1], suggestions to improve or comments are most
welcome.
I have also been contributing to MW with my new Extension:AllTimeZones [2],
comments to that are welcomed as well.
My other contributions to MW are listed here [3].
[1]www.mediawiki.org/wiki/User:Nischayn22/Gsoc
[2]www.mediawiki.org/wiki/Extension:AllTimeZones
[3]www.mediawiki.org/wiki/User:Nischayn22
--
With Regards
Nischay Nahata
B.tech 3rd year
Department of Information Technology
NITK,Surathkal
[[User:JohnnyMrNinja]] contacted me today to ask for developer input on
his proposal to complete account unification. I copied his comments
from the discussion on meta to a bug
(https://bugzilla.wikimedia.org/35707) and said I would post the request
here.
I don't know enough about SUL to know what would be involved in carrying
out his proposal. It sounds reasonable to me and it appears to have a
lot of support on Meta, but that is the extent of my insight.
Please comment here on-list if you have any thoughts -- I'll point to
this thread in Bugzilla.
Thanks!
Mark.
Heads-up. If you need a travel subsidy, you can apply for a
participation grant: https://meta.wikimedia.org/wiki/Grants:Participation
Call for talks: http://www.mcn.edu/mcn-2012-call-proposals
-Sumana
-------- Original Message --------
Subject: A strongly encouraged RFP >MCN 2012: Call for Proposals
Date: Thu, 15 Mar 2012 12:14:17 -0400
From: Lori Phillips <lori.byrd.phillips(a)gmail.com>
Please see the Museum Computer Network's call for proposals below. There
has been a stable Wikimedia presence at MCN for the past few years, and
I hope that we'll keep it up!
This year, I was shocked to be invited to be a part of the conference
program committee, specifically for my unique insights as a Wikipedian
and emerging museum professional. If that doesn't say something about
their status as Wikipedia-supporters, I don't know what does.
As a conference for museum technologists and theorists, this is a great
opportunity to show off more specific uses of Wikimedia and mediawiki
tools in museums. They no longer need convincing of cooperating with
Wikipedia - they're looking for the next steps in how to integrate our
tools and resources into their systems, and vise versa. It's an
important year for more technically-inclined Wikipedians to step in and
help facilitate this ongoing partnership with museum technologists more
generally.
The deadline for submissions is April 27th, and I do hope you'll
consider submitting a proposal.
Let me know if you have any questions - and please disperse this
liberally! (Local lists, Tech lists, whatever lists.)
Thanks so much,
Lori
---------- Forwarded message ----------
From: *Elizabeth Neely* <eneely(a)artic.edu <mailto:eneely@artic.edu>>
Date: Thu, Mar 15, 2012 at 12:02 PM
Subject: [MCN-L] MCN 2012: Call for Proposals
To: mcn-l(a)mcn.edu <mailto:mcn-l@mcn.edu>
*The Museum Unbound:*
*Shifting Perspectives, Evolving Spaces, Disruptive Technologies
*
MCN 2012 Seattle
November 7 - 10, 2012
*Call for Proposals* <http://bit.ly/xSVMXY>
The annual Museum Computer Network (MCN) conference brings together a
diverse community of museum professionals interested in using technology to
improve their organizations and enhance the visitor experience. It is not a
conference purely for technologists – it’s for anyone who wants to explore
exciting opportunities—and tackle the unique challenges—associated with
using technology in cultural organizations.
This year’s theme, “The Museum Unbound: Shifting Perspectives, Evolving
Spaces, Disruptive Technologies”, focuses on exploring how the quickening
pace of technological innovation is expanding the very definition of what
it means to be a museum.
MCN Seattle will feature a newly expanded program with a diverse set of
offerings. The conference will kick off with ‘Ignite MCN’, a fast-paced and
provocative idea forum. Supporting the innovation theme, the program will
also feature a full set of ‘Maker’ hardware-hacking activities and a
revamped un-conference program. These new activities will work hand-in-hand
with the main program’s set of excellent workshops, sessions, and
roundtables, providing attendees with many ways of exchanging ideas,
interacting with peer professionals and learning new skills.
MCN Seattle promises to be an inspiring and energetic gathering, which will
be assured with your your participation!
*Share your ideas and know-how: submit a proposal
<http://bit.ly/xSVMXY>for a session or paper at the conference.
*
CONTACT US
Need more information? Have questions?
Koven Smith & Liz Neely, Program Co-Chairs: program(a)mcn.edu
<mailto:program@mcn.edu>
_______________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum
Computer Network (http://www.mcn.edu)
To post to this list, send messages to: mcn-l(a)mcn.edu <mailto:mcn-l@mcn.edu>
To unsubscribe or change mcn-l delivery options visit:
http://mcn.edu/mailman/listinfo/mcn-l
The MCN-L archives can be found at:
http://toronto.mediatrope.com/pipermail/mcn-l/
--
Lori Phillips
Web Content Specialist | Wikipedian in Residence
The Children's Museum of Indianapolis
US Cultural Partnerships Coordinator
Wikimedia Foundation
703.489.6036 | http://loribyrdphillips.com/
Hi,
I would am interested in doing the GSoC. My proposal is here
https://www.mediawiki.org/wiki/User:Johnnorro/GSoC_2012_application
The 'integrate upload from Flickr and Picasa' would be perfect for me
as I have already worked with the Picasa API in the past and I am aware
of its uses and capabilities, the Flickr API is very similar to it.
I know this is a bit late for amendments, but any feedback I receive
would be much appreciated.
Also does anyone know someone who could be interested in mentoring
a project such as this?
Regards,
John