Dear Wikitech (cc'd Wikisource)
A recent discussion in English Wikisource's Scriptorium was querying
why commercial book companies, etc. were getting higher search hits,
especially where they may just have summary information, rather than
full text. In that discussion someone pointed to some of the webmaster
information at Google, eg. [1], which (ultimately) talks about their
microformat (preferred) or JSON-LD as a means to put in more
particular metadata as explained at schema.org (for creative works
[2])
I went to play, and ultimately failed, and was pointed to the
inability to <script> for security reasons, and the inability to add
micodata (<cite user="bawolff">microdata attributes are implemented in
MediaWiki, but currently disabled via
$wgAllowMicrodataAttributes</cite> thx).
So my naive questions to those that know these things are
1) How do we look to improve external search engine hits for the
sister sites where they are particularly pertinent to a search
[wikipedia already gets Google special treatment]
2) if the schema.org metadata is a preferred means to progress, what
is the recommended means to progress such an issue
3) presumably some of this fits into the discussion about Structured
Data discussion, and what means is there to include this into that
discussion?
Thanks for the guidance.
Regards, Billinghurst
[1] https://support.google.com/webmasters/answer/3227642?hl=en&ref_topic=3222270
[2] http://www.schema.org/CreativeWork
Hi all,
So I figure we all need to band together and crowd fund a calendar for
whoever is responsible for this little gem - https://i.imgur.com/UaLgRXX.png
On a more serious note - is the downtime on Wednesday the 10th, or Friday
the 12th?
-- Lewis
Hello and welcome to the latest edition of the WMF Engineering Roadmap
and Deployment update.
The full log of planned deployments next week can be found at:
<https://wikitech.wikimedia.org/wiki/Deployments#Week_of_December_8th>
A quick list of notable items...
== All Week ==
* Fundraising on-going through the rest of the year
* HHVM: reimaging servers to HHVM, should be completed by end of year
== Tuesday ==
* MediaWiki deploy
** group1 to 1.25wmf11: All non-Wikipedia sites (Wiktionary, Wikisource,
Wikinews, Wikibooks, Wikiquote, Wikiversity, and a few other sites)
** <https://www.mediawiki.org/wiki/MediaWiki_1.25/wmf11>
== Wednesday ==
* Phabricator:
** Enabling the "Sprint" extension:
** <https://phabricator.wikimedia.org/T1322>
* MediaWiki deploy
** group2 to 1.25wmf11 (all Wikipedias)
** group0 to 1.25wmf12 (test/test2/testwikidata/mediawiki)
Thanks and as always, questions and comments welcome,
Greg
--
Greg Grossmeier
Release Team Manager
Hi,
I uploaded the following file to Commons:
https://commons.wikimedia.org/wiki/File:VisualEditor_MediaWiki_theme_clear_…
The file is taken form the VisualEditor repo:
extensions/VisualEditor/lib/ve/lib/oojs-ui/themes/apex/images/icons/clear.svg
If it's viewed on the above file description page, the appearance is
broken: I see a partial circle and a rectangle.
If I view it directly in my browser then it appears correctly as a circle
with a diagonal line:
https://upload.wikimedia.org/wikipedia/commons/7/7a/VisualEditor_MediaWiki_…
I guess that either something is broken in the SVG file or in MediaWiki's
server-side SVG to PNG rendering.
Any ideas?
Thanks.
--
Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
http://aharoni.wordpress.com
“We're living in pieces,
I want to live in peace.” – T. Moore
Hello!
I am an OPW Intern for round#09 and will be working on a spelling
dictionary project, the proposal of which is available here
<https://www.mediawiki.org/wiki/User:Ankitashukla/Proposal>.
Also, we'd be using this
<https://github.com/ankitashukla/spelling-dictionary-opw> github repo for
version controlling.
Before we start off with the coding part, my mentors Kartik and Amir, and I
thought it would be a great idea to have suggestions from everyone that
might turnout to be very useful for us during the development of the
project.
We welcome all ideas of what your expectations are from the project, any
specific design advice, any particular implementation or any advice, big or
small, that might be useful to us.
Thanks and regards,
Ankita Shukla
[x-posted announcement]
Hello,
Please save the date for the monthly IRC office hour of the Wikimedia
Language Engineering team on Wednesday, December 10, 2014 at 1700 UTC
on #wikimedia-office. Project updates will include information about
the new version of Content Translation[1] and plans for the next
release.
Please see below for event details and local time.
Thanks
Runa
[1] https://www.mediawiki.org/wiki/Content_translation/Announcement-November2014
Monthly IRC Office Hour:
=======================
# Date: December 10, 2014 (Wednesday)
# Time: 1700 UTC (Check local time:
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20141210T1700)
# IRC channel: #wikimedia-office
# Agenda:
1. Updates from the Content Translation project
2. Q & A/Discussions
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Thanks for all your outstanding work, Ori! This one was so fantastic I had
to forward a bit... at least you can admit you have a problem :p
-Adam
---------- Forwarded message ----------
From: Ori.livneh (Code Review) <gerrit(a)wikimedia.org>
Date: Thu, Dec 4, 2014 at 4:55 AM
Subject: [Ops] [Gerrit] Emit alert when Ori commits on a weekend - change
(operations/puppet)
To:
Ori.livneh has uploaded a new change for review.
https://gerrit.wikimedia.org/r/177521
Change subject: Emit alert when Ori commits on a weekend
......................................................................
Emit alert when Ori commits on a weekend
Provisions an Icinga check on palladium that issues an alert if the time is
between Friday 21:00 and Monday 01:00 and there exists a commit from me in
the
last hour in operations/puppet.
Change-Id: I2c4fd0d6ef907e4afe91f0248e7039f31d70696c
---
A files/icinga/check-ori-commits
M manifests/misc/monitoring.pp
M manifests/site.pp
3 files changed, 37 insertions(+), 0 deletions(-)
git pull ssh://gerrit.wikimedia.org:29418/operations/puppet
refs/changes/21/177521/1
diff --git a/files/icinga/check-ori-commits b/files/icinga/check-ori-commits
new file mode 100755
index 0000000..d2d9552
--- /dev/null
+++ b/files/icinga/check-ori-commits
@@ -0,0 +1,20 @@
+#!/bin/bash
+# Icinga alert script for Ori weekend commits
+#
+# Alerts if the time is between 21:00 on Friday and 01:00 on Monday
+# (my time zone) and there exists a commit from me in the last hour.
+
+TZ="America/Los_Angeles"
+ /usr/bin/git \
+ --git-dir=/var/lib/git/operations/puppet/.git log \
+ --author=ori(a)wikimedia.org \
+ --since=1hour \
+ --format=%cd | /bin/grep -Pq '(Fri .* 2.:|Sat|Sun)'
+
+if [ $? -eq 0 ]; then
+ echo "CRITICAL: Ori committed a change on a weekend"
+ exit 2
+else
+ echo "OK: Ori is behaving himself"
+ exit 0
+fi
diff --git a/manifests/misc/monitoring.pp b/manifests/misc/monitoring.pp
index b333799..baf49ad 100644
--- a/manifests/misc/monitoring.pp
+++ b/manifests/misc/monitoring.pp
@@ -613,3 +613,19 @@
],
}
}
+
+
+class misc::monitoring::ori_weekend_commits {
+ file { '/usr/local/lib/nagios/plugins/check-ori-weekend-commits':
+ source => 'puppet:///files/icinga/check-ori-weekend-commits',
+ owner => 'root',
+ group => 'root',
+ mode => '0555',
+ }
+
+ nrpe::monitor_service { 'ori_weekend_commits':
+ description => 'Ori committing changes on the weekend',
+ nrpe_command =>
'/usr/local/lib/nagios/plugins/check-ori-weekend-commits',
+ require =>
File['/usr/local/lib/nagios/plugins/check-ori-weekend-commits'],
+ }
+}
diff --git a/manifests/site.pp b/manifests/site.pp
index 688fa18..f3bf770 100644
--- a/manifests/site.pp
+++ b/manifests/site.pp
@@ -2162,6 +2162,7 @@
include role::access_new_install
include role::puppetmaster::frontend
include role::pybal_config
+ include misc::monitoring::ori_weekend_commits
$domain_search = [
'wikimedia.org',
--
To view, visit https://gerrit.wikimedia.org/r/177521
To unsubscribe, visit https://gerrit.wikimedia.org/r/settings
Gerrit-MessageType: newchange
Gerrit-Change-Id: I2c4fd0d6ef907e4afe91f0248e7039f31d70696c
Gerrit-PatchSet: 1
Gerrit-Project: operations/puppet
Gerrit-Branch: production
Gerrit-Owner: Ori.livneh <ori(a)wikimedia.org>
_______________________________________________
Ops mailing list
Ops(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ops
Hi everyone!
I'm trying to write my notification for Echo and I'm a bit stuck coding the
formatter. The standard way to write a formatter seems to override the
processParam function (like in Thanks extension). There is a lot of magic
in the code below, I can't figure out how the processParam function must be
handled. My questions are in the comments and if someone can explain a
little bit of what's possible to do inside processParam, I'd be very
grateful.
class EchoThanksFormatter extends EchoBasicFormatter {
protected function processParam( $event, $param, $message, $user ) {
if ( $param === 'difflink' ) {
$eventData = $event->getExtra();
if ( !isset( $eventData['revid'] ) ) {
$message->params( '' );
return;
}
$this->setTitleLink(
$event,
$message,
array(
'class' => 'mw-echo-diff',
'linkText' => wfMessage(
'notification-thanks-diff-link' )->text(),
'param' => array( // what is the possible structure of
this param array?
'oldid' => $eventData['revid'],
'diff' => 'prev', //what is that? Are diff and prev
some kind of reserved words? Where can I find the whole list of these
words?
)
)
);
} else {
parent::processParam( $event, $param, $message, $user );
}
}
}
Cheers,
-----
Yury Katkov
fyi, a feedback from duala, cameroon, concerning uploading fotos to commons.
---------- Forwarded message ----------
From: Kasper Souren <kasper.souren(a)gmail.com>
Date: Wed, Dec 3, 2014 at 12:01 AM
Subject: Re: [African Wikimedians] Afripédia Douala
To: Mailing list for African Wikimedians
<african-wikimedians(a)lists.wikimedia.org>
On Tuesday, December 2, 2014, Florence Devouard <anthere(a)anthere.org> wrote:
>
> I wanted to outline that both Kumusha Takes Wiki and Wiki Loves Africa are being conducted in English and French
>
Great!
>
> https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Africa
I see the contest is over now, will there be another one coming up?
>
>
> I was quite disappointed by the limited participation of Cameroom to the photo contest. Given the effort already been done in that country to train editors and to promote the project, I expected more input.
>
While trying to upload some pictures to
https://commons.wikimedia.org/wiki/Category:Afripedia_Douala I'm
starting to understand at least one part of the issue. Internet
connections are really bad. Very high ping times, both at the French
institute as well as in the hotel I'm staying in now, which I can't
easily consider cheap (at least in terms of pricing).
Is there a robust way to upload pictures to Commons over bad internet
connections?
Facebook and G+ Android apps have done a fairly good job at uploading
pictures automatically, but now I still need to first download them to
my laptop and then upload them through the Upload Wizard, which is
failing me. Using the Commons Android app is not a good alternative
from the hotel connection because it wants me to enter a user/pass
combination too often on my phone.
Cheers,
Kasper
_______________________________________________
African-Wikimedians mailing list
African-Wikimedians(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/african-wikimedians
Hello all,
*TL;DR*: Reminder to please bike-shed at
[[mw:Phabricator/Diffusion/Callsign_naming_conventions]]
<https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conven…>
before
December.
Just when you thought it was safe, there's the next stage in our migration
of developer tools over to Phabricator: moving all our code into the
Diffusion module <https://www.mediawiki.org/wiki/Phabricator/Diffusion>.
This is *not* about doing code review in Phabricator; that task will be
left for another time. However, it does establish some immutable URLs and
so there's a lot of scope for discussion and verification about how exactly
we want to do things.
We currently use gitblit to provide our service at git.wikimedia.org ; it's
a down-stream, read-only, HTTPS service for browsing all our git repos.
We'd like to replace this service with the single platform of Phabricator
because (a) we need to make these decisions anyway for the code review
workstream, (b) fewer tools makes for a simpler learning environment for
newbies, and (c) more integrated tools makes for fewer hacky bots and "work
arounds" for everyone.
To explore what Diffusion looks like, compare:
- GitBlit:
http://git.wikimedia.org/summary/VisualEditor%2FVisualEditor.git
- GitHub: https://github.com/wikimedia/visualeditor
- Diffusion: https://phabricator.wikimedia.org/diffusion/VE/
We need to agree how we are going to name our repos, and much more
importantly because it can't change, what their "callsign" is. These will
be at the heart of e-mails, IRC notifications and git logs for a long time,
so it's important to get this right rather than regret it after the fact.
A handful of repos are so important and high-profile that we can use an
acronym without too much worry, like "MW" for MediaWiki or "VE" for
VisualEditor. For the rest, we need to make sure we've got a good enough
name that won't cause inconveniences or confusion, and doesn't repeat the
mistakes we've identified over time. We've learnt since the SVN to git
migration a few years ago that calling your repository "/core" is a bad
plan, for instance.
*Action request*
The proposed naming conventions
<https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conven…>
and
in particular the plan for what we'll call the existing repos
<https://www.mediawiki.org/wiki/Phabricator/Diffusion/Callsign_naming_conven…>
when we duplicate them would benefit from more people looking at them, if
only to say that you don't care. :-) We've had these under discussion since
October so you may well have seen these before.
We plan to declare the current list as "agreed" in a week's time (that is,
by the end of 1 December) unless there's significant on-going discussion.
Yours,
--
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester
