Hi,
perhaps I am too naive that it could be implemented with a git-based repo,
but is there a kind of download, "clone", or access statistics available
for core and extensions ?
Hello,
The Wikimedia Language Engineering team [1] invites everyone to join
the team’s monthly office hour on May 8, 2013 (Wednesday) at 1700
UTC/1000 PDT on #wikimedia-office. During this session we would be
talking about some our recent activities and updates from the ongoing
projects. Event details and the general agenda is mentioned below.
See you all at the IRC office hour!
Thanks
Runa
Event Details:
===========
# Date: May 8, 2013
# Time: 1700-1800 UTC, 1000-1100 PDT
#IRC channel: #wikimedia-office on irc.freenode.net
Agenda:
------------
# Introductions
# Universal Language Selector - Development updates, Deployment schedule
# MediaWiki Language Extension Bundle (MLEB) Release
# Maven program - upcoming events
# GSoC update - we are participating in GSoC
# Q/A - We shall be taking questions during the session. Questions can
also be sent to runa at wikimedia dot org before the event and can be
addressed during the office-hour.
[1] http://wikimediafoundation.org/wiki/Language_Engineering_team
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hi,
A discussion has started on-wiki about a global watchlist, and other
related improvements to the watchlist feature.
A few people have started to organize the various bug reports about
watchlists, but there is still much to do before we have a clear &
prioritized vision of what the watchlist feature should become.
Improving a feature as used and central as the watchlist has the
potential of drastically improving the users' experience, but is also
likely to cause an outcry if proper research isn't done in advance,
given that everyone has their own workflow.
One comment that came up during the discussion was that people didn't
want to spend time working on research, specifications &
prioritization of features unless they had some sort of guarantee that
their work wouldn't just be ignored and rot in a corner because
nobody's interested in actually implementing the changes. I think this
is a fair and understandable request: nobody wants their hard work to
go to waste.
Therefore, if a few developers could declare their interest in
tackling the watchlist issue in the foreseeable future, it would help
arouse interest and enthusiasm from users, and motivate them to
organize user research in order to design a better watchlist feature.
I don't think we need a formal pledge or commitment; a simple
declaration of interest would imho be enough to get started. The
specifics can be ironed out later.
So, I have two questions:
* Does this make sense?
* Are you interested in improving the watchlist feature within, say,
the next 6 months?
More information:
Discussion: https://www.mediawiki.org/wiki/Talk:Watchlist_wishlist
Draft product page: https://www.mediawiki.org/wiki/Watchlist_wishlist
--
Guillaume Paumier
tl;dr
New OpenID extension version 3.30 20130505
https://www.mediawiki.org/wiki/Extension:OpenID
A new version "3.30 20130505" has been published today.
It's a security fix and fixes some CSRF and XSS vulnerabilities.
The new version is strongly recommended.
Has been tested and works with latest MediaWiki including 1.22alpha
and also PHP versions including the 5.5.0beta versions.
If you find bugs, please file them directly in our bug tracker
https://bugzilla.wikimedia.org/enter_bug.cgi?product=MediaWiki%20extensions…
Thomas
Hello,
I'm new to this ml, and would like to have some relevant links so I can
gather information to have a global overview of how you organize and how
to make useful contributions.
Kind regards,
mathieu
FYI
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Mon, May 6, 2013 at 9:44 AM
Subject: Jared Zimmerman joins Wikimedia Foundation as Director of UX
To: wikimediaannounce-l(a)lists.wikimedia.org
Hi folks,
It’s my great pleasure to announce that today, Jared Zimmerman will
start as Wikimedia Foundation’s Director of User Experience. As UX
Director, Jared will lead the design team and have a hands-on role on
the team, contributing his own design work. It’s still a small team
(Brandon, Vibha, May, and Pau), but we expect to hire an additional
3-4 designers in the coming 12-18 months.
Prior to Wikimedia, Jared was Principal Interaction Designer at
Autodesk, where he worked with engineers, visual artists, and user
experience researchers to create new software solutions for
architecture and design professionals with an emphasis on AutoCAD for
Mac and soon to be released online design collaboration tools. Jared
has led cross-disciplinary design teams in his roles at Autodesk,
Ammunition Group, and iconmobile, including creative direction.
At Autodesk, he was part of the transition to agile development and
helped his design teams apply those principles to their work. During
his time there he worked with design management to establish designers
as product owners in the scrum process, to further integrate them into
the development process from start to finish, as well as teaching his
team best practices for use of agile design tools.
Jared has degrees in Graphic Design (BGD) and Fine Art Photography
(BFA) from the Rhode Island School of Design. His photography has been
in featured in publications such as Travel + Leisure Magazine,
ZonaRetiro, and Huffington Post.
In addition to starting in his new job, Jared is also planning his
wedding in July to his fiancée Shannon. [1] In his spare time Jared is
wrapping up a remodel to their home, working on his first iPhone app,
experimental cooking, photographing the bay area & abroad [2], and
answering questions on Quora. [3]
I look forward to Jared’s leadership in helping elevate a delightful,
consistent and efficient User Experience to becoming a key measure of
success for our work.
Please join me in welcoming Jared! :-)
Erik
[1] http://shannonbadiee.com/
[2] http://www.flickr.com/photos/spoinknet/
[3] https://www.quora.com/Jared-Zimmerman/answers
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Hi,
It seems to me that there are 15-20 distinct GSoC projects with interested
mentors, depending on how you count it. Here's the list I compiled:
Core MediaWiki:
- Automatic category redirects
- MediaWiki API 2.0
General extensions:
- Book structures
- Inline commenting
- MediaWiki-Moodle Extension
- Pronunciation Recording Extension
- Refactoring of Proofread Page extension
- UploadWizard improvements
Technical, but not MediaWiki (I think):
- Incremental data dumps
- Language Coverage Matrix Dashboard
Semantic MediaWiki:
- Improvement of Lingo and Semantic Glossary
- Section handling for Semantic Forms
Translation:
- Android app for translation
- jQuery.IME
VisualEditor:
- VisualEditor i18n support
- VisualEditor Math Equation Plugin
- VisualEditor source code plugin
Wikidata:
- Entity suggester for Wikidata
- Mobilize Wikidata
- Wikidata language fallback and conversion
That's 20, but some of the projects have overlapping mentors - the
translation, VisualEditor and Wikidata projects all seem to have basically
the same set of mentors across their proposals; which, if true, and
assuming that can't be worked out somehow, could bring down the number of
doable projects to 15.
That's just my analysis, and it could be incorrect in places.
-Yaron
--
WikiWorks · MediaWiki Consulting · http://wikiworks.com
Heya folks :)
We've created https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
to keep all the development discussions around Wikidata in one public
place. Feel free to subscribe if you are interested.
Cheers
Lydia
--
Lydia Pintscher - http://about.me/lydia.pintscher
Community Communications for Technical Projects
Wikimedia Deutschland e.V.
Obentrautstr. 72
10963 Berlin
www.wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg
unter der Nummer 23855 Nz. Als gemeinnützig anerkannt durch das
Finanzamt für Körperschaften I Berlin, Steuernummer 27/681/51985.
Gerrit used to send out an email message when someone has "uploaded a
new patch set" on an existing change that I was involved in (I believe
listed as a reviewer).
The last one I seem to have received was on April 23. Since then, I
have only received comments *about* new patch sets (including the
automatic Jenkins votes).
I still get "reexamine a rebased change"
Did the configuration for this change? I don't see anything relevant at
https://gerrit.wikimedia.org/r/#/settings/ .
Thanks,
Matt Flaschen