Hello,
we plan to change the availability to hide a user account in CentralAuth
from the 'centralauth-lock' to the 'centralauth-oversight' right. This
is done as a side effect of logging the hiding of global accounts in the
suppression log from now on to protect it from public access.
For Wikimedia stewards this wont change anything. The only visible
change on Wikimedia wikis this will result in is then the change of the
logging behavior (which is bug 18060).
https://bugzilla.wikimedia.org/18060https://gerrit.wikimedia.org/r/26902
Cheers,
Marius Hoch (hoo)
Forwarding from the mediawiki-api list.
This seems like a pretty minor change, but I think it won't hurt to get a notificatin about it here as well.
------- Forwarded message -------
From: "Brad Jorsch" <bjorsch(a)wikimedia.org>
To: "MediaWiki API announcements & discussion" <mediawiki-api(a)lists.wikimedia.org>, mediawiki-api-announce(a)lists.wikimedia.org
Cc:
Subject: [Mediawiki-api] BREAKING CHANGE: Format of action=query&list=logevents&leprop=details changing
Date: Wed, 02 Jan 2013 19:28:43 +0100
Due to bug 43221 and Gerrit change I1a3c7ac6, the format of the
"details" for some log events will be changing. In particular, any
event with details that were returned with a key resembling "4::foo"
will now be returned under a key of simply "foo".
This change will be deployed with 1.21wmf7, which is scheduled for
today on mediawiki.org, test.wikipedia.org, and wikidata; 7 January
for non-Wikipedia sites; 9 January for enwiki; and 14 January for the
other Wikipedias.
--
Matma Rex
Thanks for being on this list and helping communicate about technology
on Wikimedia sites.
What kinds of discussions or notifications would you like to have on
this list? Or in general, if you don't think they quite belong here?
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf5
This week and next week we're deploying a new version of MediaWiki to
your wiki, as usual. This upgrade includes one-click (AJAX) patrolling,
for both new page and diff patrol (see bug 7851). Also, I thought you'd
want to know about these changes:
Internationalisation/localization:
* Now formatted numbers in Spanish use space as separator
for thousands, as mandated by the Real Academia Española.
* Kurdish formatted numbers now use period and comma
as separators for thousands and decimals respectively.
* Narayam: removed MyBest keyboard because of failing tests and no
documented reference
Template, user script, & skin hackers:
* The <data>, <time>, <meta>, and <link> elements are allowed within
wikitext for use with Microdata.
* The HTML5 <mark> tag has been whitelisted.
* jQuery upgraded from 1.8.2 to 1.8.3.
* In your wiki's MediaWiki:<skin>.css, h4, h5, or h6 headings in the
sidebar have to be changed to h3 to work (more details at
https://gerrit.wikimedia.org/r/#/c/30361/ and bug 457)
Wikisourcers:
* ProofreadPage gets an OAI-PMH API:
https://www.mediawiki.org/wiki/Extension:Proofread_Page#OAI-PMH
As always, more at https://www.mediawiki.org/wiki/MediaWiki_1.21/wmf5
and deployment dates at
https://www.mediawiki.org/wiki/MediaWiki_1.21/Roadmap . Please let us
know of any bugs! Thank you for your feedback!
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
Hi,
I am launching a wiki that is aimed at an older target market in Ireland. I am wondering if there are any good tutorials in existence for users, so I can point to them.
Any help would really be appreciated.
Regards,
Seamus
fyi
-------- Original Message --------
Subject: Follow / like MediaWiki @ social media
Date: Wed, 19 Dec 2012 15:43:41 -0800
From: Quim Gil <qgil(a)wikimedia.org>
Organization: Wikimedia Foundation
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
It's not completely sorted out but there has been a big progress in just
a couple of days:
https://www.mediawiki.org/wiki/Social_media
Summary: follow & like MediaWiki in your social networks to read &
promote MediaWiki & Wikimedia tech news.
* http://identi.ca/mediawiki
* https://twitter.com/MediaWiki
* https://www.facebook.com/MediaWikiProject
These channels pay a lot of attention to critical mass. The more
followers and shares/likes the more promoted you get (more or less).
Your support is welcome.
See also how we can redistribute your relevant updates:
https://www.mediawiki.org/wiki/Social_media#Sharing_your_updates
There are still some details to polish e.g. how to automate the process
including Facebook (& Google+) or how to clear the FB mess. If you enjoy
social media your ideas are welcome:
https://www.mediawiki.org/wiki/Talk:Social_media
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hello all,
I have put the question in the general talk page at nl-wiki:
https://nl.wikipedia.org/wiki/Wikipedia:De_kroeg#Feedback_van_lokale_gemeen…
Several reactions came on that:
* users experience Bugzilla as unfriendly, and rather use w wiki page for bugs.
* other users do not know where to put their questions and problems.
* users want technicians be more visible and better reachable.
* one user had been searching for a technician to help for a year long and couldn't find one.
I try to fullfill my role as ambassador between tech and local users of Dutch projects. I do have a bit more feeling with Bugzilla, and what I try is to translate bugs to Bugzilla. On the Dutch Wikipedia we have a technical discussion room ( https://nl.wikipedia.org/wiki/Wikipedia:SHEIC ), we will transform that page to one where people can add their bugs and problems. In this way we hope to help users better to solve problems/bugs directly (often personal preferences, already known bugs, error in template or just the outlook of a page messed up by inserted code, etc).
I think a lot of the communication can and should be picked up by local users with enough technical knowledge and experience to help in that local language.
Greetings - Romaine
> Date: Fri, 7 Dec 2012 17:03:52 +0100
> From: Guillaume Paumier <gpaumier(a)wikimedia.org>
> To: "Coordination of technology deployments across
> languages/projects"
> <wikitech-ambassadors(a)lists.wikimedia.org>
> Subject: [Wikitech-ambassadors] Local discussions about how
> to improve
> communication between users and
> developers
> Message-ID:
> <CAHLKNV2TjuwnryCqODj2oYRE6nX2H+4R+=1su2dxMxzYdHDh6Q(a)mail.gmail.com>
> Content-Type: text/plain; charset=UTF-8
>
> Greetings,
>
> Summary: I'm trying to get comments and ideas on how to
> improve
> communication between developers and Wikimedia editors, and
> I'd like
> to ask the help of people on this list to ask your local
> communities
> what they think, and post the results of those discussions
> here.
>
> Longer version:
>
> Communication between Wikimedia contributors and "tech
> people"
> (primarily MediaWiki developers, but also designers and
> other
> engineers) hasn't always been ideal. In recent years,
> Wikimedia
> employees have made efforts to become more transparent, but
> what I'd
> like to discuss today is how we can better engage in true
> collaboration and 2-way discussion, not just reports and
> announcements. It's easy to post a link to a new feature
> that's
> already been implemented, and tell users "Please provide
> feedback!".
> It's much more difficult to truly collaborate every step of
> the way,
> from the early planning to deployment.
>
> Some "big" tech projects sponsored by the Wikimedia
> Foundation are
> lucky enough to have a Community Liaison who can spend a lot
> of time
> discussing with editors, basically incarnating this 2-way
> communication channel between users and engineering staff.
> But one
> person can only do so much: they have to focus on a handful
> of
> features, and primarily discusses with the English
> Wikipedia
> community. We want to be able to do this for dozens of
> engineering
> projects with hundreds of wikis, in many languages, and
> truly
> collaborate to build new features together. Hiring hundreds
> of
> Community Liaisons isn't really a viable option.
>
> There are probably things in the way we do tech stuff (e.g.
> new
> software features and deployments) that drive editors
> insane. You
> probably have lots of ideas about what the ideal situation
> should be,
> and how to get there: What can the developer community
> (staff and
> volunteers) do to get there? (in the short term, medium
> term, long
> term?) What can users do to get there?
>
> Instead of just postulating that "The problem is X" and "The
> solution
> is obviously Y", I've started an extensive consultation
> process to
> learn from users, to hear you, to listen to your complaints
> and your
> ideas on how to fix the issues. I'm hoping that this open
> and
> collaborative thinking process will yield better results
> than a
> one-sided analysis.
>
> An preliminary consultation took place last month with
> projects in
> English and French. I've summarized the initial findings
> and
> proposals:
> https://www.mediawiki.org/wiki/Technical_communications/Fall_2012_consultat…
>
> I'm hoping that we can now expand this consultation to more
> projects
> and more languages, with your help. It isn't feasible for me
> to launch
> a discussion on each wiki in each language, but I'm hoping
> that you
> can help me spread this message and start those discussions
> with your
> local communities.
>
> I realize this will take some of your time, but I think it's
> worth
> spending a little time to discuss this now in order to make
> big
> improvements later on how we communicate with each other.
>
> I'm available to answer comments, concerns and questions.
>
> Many thanks for your help!
>
> --
> Guillaume Paumier
> Technical Communications Manager ? Wikimedia Foundation
> https://donate.wikimedia.org
fyi
-------- Original Message --------
Subject: Proposal: MediaWiki Group Marketing
Date: Thu, 13 Dec 2012 10:43:27 -0800
From: Quim Gil <qgil(a)wikimedia.org>
Organization: Wikimedia Foundation
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Hi, following the process for requesting the creation of a MediaWiki
group, here is a proposal for
MediaWiki Group Marketing
http://www.mediawiki.org/wiki/Groups/Proposals/Marketing
Your endorsements, improvements and feedback are welcome at the wiki
page. Thank you!
PS: see also http://www.mediawiki.org/wiki/Groups/Proposals
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
FYI
---------- Forwarded message ----------
From: Erik Moeller <erik(a)wikimedia.org>
Date: Tue, Dec 11, 2012 at 1:10 AM
Subject: [Site issue] s3 wikis read-only until replication catches up
To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>
Wikimedia wikis hosted on the "s3" cluster (pretty much all but the
very large wikis, click on the "s3" box in
https://noc.wikimedia.org/dbtree/ to get a full list) are currently in
read-only mode due to severe replication lag. This problem was
apparently caused by a logic issue in the job queue, which should now
be fixed, but it will still take at least 2-3 hours for replication to
catch up. We apologize for the inconvenience, and are continuing to
monitor the situation.
Erik
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
--
Erik Möller
VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
An analysis of what happened was circulated a few days ago and now
published:
<https://wikitech.wikimedia.org/view/TranslationNotifications_issues_2012-12>
It's fairly technical but it's supposed to help improve for the future,
although so far it wasn't acted upon: «TL;DR: Changes in MW core exposed
a bug in TranslationNotifications. The same bug is also present in other
extensions. Many people participated in preventing further damage and
fixing the issue. More work remains to be done.»
We still don't know if the translation notifications should now work or
what's going to happen to the job queue, nor how/if todays' jobqueue
disaster
(http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65703
) may impact it.
Nemo