In Wikidata there is an open bug to implement badges (see email below by
Lydia), with the open question if this should be handled by the Mediawiki
software itself or in some other way. "Template: Link FA" and
"Template:Link GA" is the system currently used in all Wikipedias [1]
In addition to this, during the Wikimania Open Access project panel [2][3]
there were some suggestions about how to engage the scientific community to
contribute more content to Wikipedia. Apparently one major blocker is the
lack of credit attribution in collaborative environments. By being able to
attribute credit to major contributors of featured/good articles,
scientists could (voluntarily) link their Wikipedia profile to an external
authoring organization who would aggregate these contributions to their
standard journal-based ones.
According to Denny, once SUL is in place, it should be possible to link
Wikidata items representing authors both to their wikimedia profile and to
any external authoring organization representing their identity. However,
the information that this would provide would be of little use unless the
api could provide a list of "featured contributions".
Any thoughts or ideas about these issues?
Cheers,
Micru
[1] https://www.wikidata.org/wiki/Q16467https://www.wikidata.org/wiki/Q5462767
[2]
https://wikimania2013.wikimedia.org/wiki/Submissions/Open_Access_%26_Wikipe…
[3] http://en.wikipedia.org/wiki/Wikipedia:WikiProject_Open_Access
---------- Forwarded message ----------
From: Lydia Pintscher <lydia.pintscher(a)wikimedia.de>
Date: Fri, Aug 16, 2013 at 8:58 AM
Subject: [Wikidata-tech] badges support - decision needed?
To: Wikidata technical discussion <wikidata-tech(a)lists.wikimedia.org>
Hey :)
It seems that badges support is stalled on a decision about how
exactly to define the set of available badges if I read
https://bugzilla.wikimedia.org/show_bug.cgi?id=40810 correctly. Can we
make a decision and move forward? It's the most voted on bug we have.
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.
_______________________________________________
Wikidata-tech mailing list
Wikidata-tech(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata-tech
--
Etiamsi omnes, ego non
Hello all,
As we outlined in our blog post on the future of HTTPS at the Wikimedia
Foundation[0], the plan is to enable HTTPS by default for logged in
users on August 21st, this Wednesday.
We are still on target for that rollout date.
As this can have severe consequences for users where HTTPS is blocked by
governments/network operators *in addition to* users who connect to
Wikimedia sites via high latency connections, we've set up a page on
MetaWiki[1] describing what is going on and what it means for users and
what they can do to report problems.
Please help watch out for any unintended consequences on August 21st and
report any negative issues to us as soon as you can. Bugzilla[2], IRC
(#wikimedia-operations), or the (forthcoming) OTRS email are all fine.
Also, feel free to email myself or ping me directly on IRC.
Best,
Greg
[0] https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/
[1] https://meta.wikimedia.org/wiki/HTTPS
[2] https://bugzilla.wikimedia.org
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
Hi,
<tl;dr>
I do not really enjoy the way the mandatory-for-editors HTTPS was
introduced, mainly for time frame and communications (still) reasons,
although I’m globally really enthousiastic about a better security and
particularly the activation of HTTPS. Generally speaking I do _hope_ in
the future WMF will give more time and more discussion space to handle
major changes.
<end tl;dr>
History: (I concede I may lack some readings, but I think I have the big
picture)
After the PRISM scandal in June (2.5 months ago) everybody condemned that
program and the Internet security became a major concern for Internet
users. HTTPS is in important means to improve the security (although
concerns about the protocol and the way it is implemented appear) and
since it was a matter of time before it could be globally activated the
blog post published on August 1st announced HTTPS will be activated for
logged-in users 20 days after, with solutions about the blocked China
HTTPS to be found [1], after a discussion on wikitech-l [2].
Some Chinese editors made petitions [3] (starting on 08/08) and Iranian
users raised a similar problem [4] (on 14/08). In parallel these last two
weeks there were discussions on wikitech-l about some way to opt-out by
user and/or geographically. And in parallel the last two weeks there were
discussions on wikitech-l whether some opt-out mechanism should be
implemented with two opposed points of view:
1/ this security about the protection of the password must be for everyone
else it is unuseful (which is true in a perfect world), no matter if China
and other HTTPS-unlucky people cannot login (and hence must edit under IP
or not edit);
2/ although security is very important, not to allow HTTP logins in China
(and other HTTPS-unlucky people) will destroy etablished parts of the
community and should be avoided, so implementation of work-arounds is
needed.
And this last discussion had not to be on wikitech-l because it is
political, and was only a few raised elsewhere (where HTTPS is technical
and should be discussed on wikitech-l.)
Finally some work-arounds were implemented; first it was a list of wikis
where HTTP login will be allowed (this decision became public on Monday
[5]) and yesterday (sic) it was announced a geolocalised solution [6].
Secondly there will be a preference for the users, although until
yesterday it was not clear for everybody how exactly it was implemented.
In parallel the central notice was set up two days ago with an
English-only page, pywikipediabot was announced to be ready some hours
ago. And in some hours there should be the deployment target.
[1] http://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/
[2] http://lists.wikimedia.org/pipermail/wikitech-l/2013-July/070981.html
[3]
http://meta.wikimedia.org/wiki/Requests_for_comment/Petition_of_HTTPS_defau…
[4] https://bugzilla.wikimedia.org/show_bug.cgi?id=52846
[5] https://meta.wikimedia.org/wiki/HTTPS?diff=5731209&oldid=5728786
[6] http://lists.wikimedia.org/pipermail/wikitech-l/2013-August/071348.html
Conclusion:
I know the fact we now know we are spied is disturbing, but…
Why the hell HTTPS is so truly *urgent* we cannot spent more than three
weeks (at all) to think about the problem, investigate related problems
(including political and communitical here), think about solutions and
user interfaces/interactions, implement solutions, widely avertize the
problem and solutions, and peacefully deploy the patches?
I would have loved some RFC and some discussion elsewhere than on
wikitech-l with structured problems and solutions, and more time allowed
for discussing all that with the community -- because I guess it was
widely discussed internally in technical and operations teams, but the
community discovered these plans and had to report potential problems in a
time frame of 3 weeks.
More generally speaking, I would love the WMF share more their internal
plans long before rollout -- even if I concede writing and discussion is
more time-consuming than oral speak and introduce latencies -- and
probably in some digest and expanded forms (I know there are already both,
it’s probably to be improved and perhaps more targeted to avoid everyone’s
burnout). And perhaps slow the rhythm of the technical changes to have a
more stable environment (I understand this is personal and there are other
PoV).
Thanks,
~ Seb35
Le Wed, 21 Aug 2013 11:37:35 +0200, Pierre-Selim <pierre-selim(a)huard.info>
a écrit:
> First of all, I'm sorry If my tone was not appropriate (keep in mind I'm
> not a native speaker).
>
> 2013/8/21 Terry Chay <tchay(a)wikimedia.org>
>
>> On Aug 21, 2013, at 1:39 AM, Pierre-Selim <pierre-selim(a)huard.info>
>> wrote:
>>
>> > Just a question: Why imposing HTTPS ? Really, it will be damaging
>>
>> The reason why is outlined in Ryan's blog post as well as his previous
>> post and the Wikipedia entry on https linked from that post.
>>
>> The short answer is the current state is known to present a number of
>> privacy and security vulnerabilities further emphasized by the now-known
>> existence of software designed to deliberaty target these
>> vulnerabilities
>> in Wikipedia specifically.
>>
>> https://blog.wikimedia.org/2013/08/01/future-https-wikimedia-projects/
>
>
> I just think the user should be informed of this and should have the
> choice
> (so the user can make an enlightened choice). And that is mostly my
> point.
> All the explanation you have given are good, and the work of the WMF is
> good IMO..
>
>
>> > Thank you for all the time you spent on this feature, however I'm not
>> > convinced at all.
>>
>> Luckily, the standard for the Movement is consensus, not catering to
>> every
>> extremist view with 100% buy-in. The latter standard is impossible as
>> people would be affected either way. The technical component is
>> informing
>> the decision and helps to hash out some of the details, but this is a
>> case
>> where parts of the Vision are being compromised today, and a different
>> (hopefully better) compromise is being reached through this rollout.
>>
>
> Off course, I was just giving my opinion, I'm one user and do not
> represent
> more than that. We will see how it works out, and I would be happy to owe
> you a drink if everything goes smooth.
>
>
>> Take care,
>>
>> terry
>
>
> Thank you for your answer and have a nice roll out.
>
>
>
>> >
>> >
>> > 2013/8/21 Ryan Lane <rlane(a)wikimedia.org>
>> >
>> >> On Wed, Aug 21, 2013 at 4:38 AM, Brion Vibber <bvibber(a)wikimedia.org>
>> >> wrote:
>> >>
>> >>> On Tue, Aug 20, 2013 at 1:33 PM, Nathan <nawrich(a)gmail.com> wrote:
>> >>>
>> >>>> Hi, context please?
>> >>>
>> >>>
>> >>> Continuation of this thread from wikitech-l:
>> >>
>> http://lists.wikimedia.org/pipermail/wikitech-l/2013-August/thread.html#712…
>> >>>
>> >>>
>> >>> tl;dr summary:
>> >>> * ops plans to switch logins to HTTPS
>> >>> * switching all logins to HTTPS is known to break access for
>> logged-in
>> >>> users in countries where Wikimedia's HTTPS servers are blocked by
>> >>> government censorship
>> >>> * there are some plans to mitigate this by excluding some languages
>> from
>> >>> the requirement
>> >>> * this is controversial for several reasons, one of which is that it
>> will
>> >>> break access for users in those countries on language projects that
>> are
>> >> not
>> >>> excepted (eg English Wikipedia in mainland China)
>> >> The last point isn't accurate. The original plan was to exempt
>> certain
>> >> languages from the login redirection, and those projects would be
>> "home"
>> >> wikis. When someone logged-in there, they'd also be logged-in
>> everywhere
>> >> else via central auth. The current plan is to disable the HTTPS
>> redirect
>> >> using geolocation for countries that have a > 5% error rate for HTTPS
>> >> requests.
>> >>
>> >> This discussion is technical, so I'm going to move back to
>> wikitech-l,
>> now.
>> >>
>> >> - Ryan
>> >> _______________________________________________
>> >> Wikimedia-l mailing list
>> >> Wikimedia-l(a)lists.wikimedia.org
>> >> Unsubscribe:
>> https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>> >> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>> >
>> >
>> >
>> > --
>> > Pierre-Selim
>> > _______________________________________________
>> > Wikimedia-l mailing list
>> > Wikimedia-l(a)lists.wikimedia.org
>> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>> _______________________________________________
>> Wikimedia-l mailing list
>> Wikimedia-l(a)lists.wikimedia.org
>> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
>> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
Hi all,
we really would like to deploy the URL datatype to Wikidata with the next
deployment, i.e. next week. But it would make a lot of sense to have the
SpamBlackList extension be aware of ContentHandler for that.
There's already a +1 on the changeset, we would really appreciate someone
reviewing and merging it:
<https://gerrit.wikimedia.org/r/#/c/75867/>
Your help would be very much appreciated.
Cheers,
Denny
--
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.
Hey all,
Chris Steipp found a bug in CentralNotice yesterday and I've applied a
modified version of his patch. He has asked me not to commit it to gerrit
until Friday's security release.
I've applied that patch to wmf12 and wmf13.
Please do not git submodule update the CentralNotice extension!
In the event that the patch is causing issues; the patch file is:
tin:/home/mwalker/CentralNotice-bug53032.patch
~Matt Walker
Wikimedia Foundation
Fundraising Technology Team
Usually central notice banners link to an announcement that can be
viewed in many languages.
The HTTPS banner that is being displayed at the moment links to a
rough page[0] that has only English version. Could anyone craft an
announcement suitable for translation?
----
[0] https://meta.wikimedia.org/wiki/HTTPS
--
З павагай,
Павел Селіцкас/Pavel Selitskas
Wizardist @ Wikimedia projects
Here is your weekly dose of deployment highlights!
Full schedule always available at:
https://wikitech.wikimedia.org/wiki/Deployments
Next week's:
https://wikitech.wikimedia.org/wiki/Deployments#Week_of_August_19th
Highlights below...
== Monday ==
* We'll be enabling Ceph on production. Ceph is used for storage of
media files (eg: images, videos, etc). More (very detailed)
information about this can be found at:
https://wikitech.wikimedia.org/wiki/Ceph
* We'll be deploying OAuth to the set of test wikis (test.wikipedia,
test2.wikipedia, mediawiki.org, and test.wikidata.org). More
information about the OAuth work can be found at:
https://www.mediawiki.org/wiki/Oauth
* MediaWiki 1.22wmf13 will be deployed to the second group of wikis,
ie: all non-Wikipedia project sites.
For the list of important changes, see:
https://www.mediawiki.org/wiki/MediaWiki_1.22/wmf13#Important_Changes
== Tuesday ==
* Notifications (Echo) will be deployed to the first set of non-english
pilot sites, specifically French and Polish.
See the Notifications release plan at:
https://www.mediawiki.org/wiki/Echo/Release_Plan_2013
== Wednesday ==
* We will enable secure login (via HTTPS) by default. This means that
all logged in users will read and edit the site via a secure
connection over HTTPS. Given some restrictions/internet blocks in some
jurisdictions, we will disable this feature on specific language
wikis.
There is a page on MetaWiki explaining this, with a link to the
Wikimedia blog post that originally announced the plan here:
https://meta.wikimedia.org/wiki/HTTPS
This is a first step along a route to improved security while also
taking into account internet censorship in certain jurisdictions.
There will be more communication about this rollout on Monday the
19th.
== Thursday ==
* MediaWiki 1.22wmf13 will be deployed to the last group of wikis, ie:
all Wikipedia project sites.
For the list of important changes, see:
https://www.mediawiki.org/wiki/MediaWiki_1.22/wmf13#Important_Changes
If you have any questions, please let me know.
Greg
--
| Greg Grossmeier GPG: B2FA 27B1 F7EB D327 6B8E |
| identi.ca: @greg A18D 1138 8E47 FAC8 1C7D |
FOSDEM will take place on 1 and 2 February 2014 in Brussels. Now it's
the time to apply for DevRooms and main track sessions.
https://fosdem.org/2014/news/2013-08-06-call-for-participation/
Key dates:
15 September
* deadline for developer room proposals
1 October
* deadline for main track proposals
* accepted developer rooms announced
I think Wikimedia needs FOSDEM and FOSDEM needs Wikimedia. We could
mobilize European developers and tech-friendly chapters to work on a
combined outreach action.
First things first: proposing a Wiki DevRoom. What do you think? Note
that it's "Wiki", not just Wikimedia or MediaWiki.
We should also brainstorm what are the best main track session candidates.
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
At Wikimania I found out that Marius Hoch ("hoo man") is contracting
with Wikimedia Germany till September 30th and is specifically doing
accessibility bugfixes. He says: "I'm always open for suggestions and
reviewers/ testers for my changes."
So if you have a particular a11y pet peeve, or want to get his opinion
on a change to
https://www.mediawiki.org/wiki/Accessibility_guide_for_developers ,
now's a good time!
--
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation