Thanks Joseph! Just a followup reminder that submissions are due TOMORROW.
If you have submitted a proposal already but it's marked as a "draft",
please finalize it and mark it as "completed" by tomorrow as well. (If you
are a submitter you may already have email from me about this).
thanks everyone! We are going to have a great program this year!
Phoebe
(for the program committee)
On Sat, Apr 8, 2017 at 10:38 AM, Joseph Seddon <jseddon(a)wikimedia.org>
wrote:
> REMINDER: Deadline for submitting presentations, panels,
> roundtables and workshops to Wikimania is *April 10*.
>
> You have TWO days remaining.
>
> The deadline for posters and birds-of-a-feather sessions remains *May 15*.
>
> Please see below for the call for submissions for Wikimania, and submit
> your ideas! Please also note, for those who have already submitted, there
> is now a field in the registration form for "completed" or "in-progress"
> submission. When you are ready to have your submission reviewed, please
> note that it is "completed". Thank you!
>
> Please contact us with any questions: wikimania-program(a)wikimedia.org
>
> Seddon
>
> Phoebe
> >
> > On Tue, Feb 14, 2017 at 10:10 AM, phoebe ayers <phoebe.wiki(a)gmail.com>
> > wrote:
> >
> > > All,
> > > I'm very pleased to send out the Wikimania Montréal Call for
> Submissions,
> > > which can be found in French here:
> > > https://wikimania2017.wikimedia.org/wiki/Submissions/fr
> > > and in English here:
> > > https://wikimania2017.wikimedia.org/wiki/Submissions/en
> > >
> > > On behalf of the Wikimania programme committee,
> > > Phoebe Ayers
> > > -----
> > >
> > > Que vous soyez un membre de la communauté de l’un des projets Wikimédia
> > > (tels que Wikipédia, Wikibooks, Wikidata, Wikisource, Wikinews,
> Wikimedia
> > > Commons, Wiktionnaire, MediaWiki ou autres), un créateur de contenu
> libre
> > > ou un consommateur, nous recevrons avec plaisir votre proposition pour
> > une
> > > session lors de Wikimania 2017.
> > >
> > > *dates importantes*
> > >
> > > Appel aux propositions ouvert : 2 février 2017
> > > Date limite de soumission des présentations (conférence, panneau, table
> > > ronde et atelier) : *15 avril 2017*
> > > Date limite de soumission des brefs exposés, affiches et réunions
> > > d’oiseaux de la même plume : 15 mai 2017.
> > > Notification d’acceptation des présentations : 20 avril 2017
> > > Notification d’acceptation des brefs exposés, affiches et réunions
> > > d’oiseaux de la même plume : 10 juin 2017
> > >
> > > *Types de soumissions & Comment soumettre: *https://wikimania2017.
> > > wikimedia.org/wiki/Submissions/fr
> > >
> > > *Des questions ?* Merci de contacter le Comité du programme par
> > > wikimania-program(à)wikimedia.org.
> > >
> > > ----
> > >
> > > Whether you are a community member of one of the Wikimedia projects
> (such
> > > as Wikipedia, Wikibooks, Wikidata, Wikisource, Wikinews, Wikimedia
> > Commons,
> > > Wiktionary, MediaWiki or others), or a fellow open content creator or
> > > consumer, we welcome your proposal for a session at Wikimania 2017.
> > >
> > > *Important dates*
> > >
> > > Call for proposals opens: February 2, 2017
> > > Deadline for submitting presentation (lecture, panel, roundtable and
> > > workshop) submissions: *April 10, 2017*
> > > Deadline for submitting lightning talks, poster, and birds of a feather
> > > submissions: May 15, 2017
> > > Notification of acceptance for presentations: April 20, 2017
> > > Notification of acceptance for lightning talks, poster and birds of a
> > > feather submissions: June 10, 2017
> > >
> > > *Submission types & how to submit:* https://wikimania2017.
> > > wikimedia.org/wiki/Submissions/en
> > >
> > > *Any questions?* Please contact the Programme Committee at
> > > wikimania-program at wikimedia.org
> > >
> >
> >
> >
> > --
> > * I use this address for lists; send personal messages to phoebe.ayers
> <at>
> > gmail.com *
> > _______________________________________________
> > Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> > wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> > wiki/Wikimedia-l
> > New messages to: Wikimedia-l(a)lists.wikimedia.org
> > Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> > <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
>
>
>
>
> --
> Seddon
>
> *Advancement Associate (Community Engagement)*
> *Wikimedia Foundation*
> _______________________________________________
> Wikimedia-l mailing list, guidelines at: https://meta.wikimedia.org/
> wiki/Mailing_lists/Guidelines and https://meta.wikimedia.org/
> wiki/Wikimedia-l
> New messages to: Wikimedia-l(a)lists.wikimedia.org
> Unsubscribe: https://lists.wikimedia.org/mailman/listinfo/wikimedia-l,
> <mailto:wikimedia-l-request@lists.wikimedia.org?subject=unsubscribe>
--
* I use this address for lists; send personal messages to phoebe.ayers <at>
gmail.com *
Hello!
The analytics team would like to announce that legacy pagecounts are now
available programatically in an API.
"Pagecount" is the legacy definition of what we now call "pageview".
Pagecounts agreggated per project are available on API endpoint since
January 2008 to December 2016. The main difference among pagecounts and the
current pageview data is lack of filtering of self-reported bots, thus
automated and human traffic are reported together. You can access data
overall but also mobile/desktop split.
Note that -at this time- we still do not have pagecount data per article,
thus far we have loaded only per-project legacy data.
More info and examples of how to query the API can be found here:
https://wikitech.wikimedia.org/wiki/Analytics/AQS/Legacy_Pagecounts
Thanks to Thomas Steiner for promptly updating the pageviews.js node client
to be able to access pagecounts. Javascript client can be found here:
https://github.com/tomayac/pageviews.js
A glimpse of this data:
https://analytics.wikimedia.org/dashboards/reportcard/#pagecounts-dec-2007-…
Thanks,
Nuria
Hi all! I'm the main developer of the ProveIt gadget
<https://commons.wikimedia.org/wiki/Help:Gadget-ProveIt>, a reference
manager for Wikipedia. The code is tracked via Phabricator, reviewed via
Gerrit, and served to the various Wikipedias from Commons. Each wiki has a
unique initialization code
<https://en.wikipedia.org/wiki/MediaWiki:Gadget-ProveIt.js> that sets some
local config and then requests the main code from Commons (JavaScript, CSS
and JSON). Every time I merge a new change via Gerrit, I need to manually
update the Commons pages so that the Wikipedias have the latest code.
This is sub-optimal. Ideally, the Wikipedias should request the code
directly from Diffusion, so that when developers merge new changes, they
are immediately available (and we don't need interface rights or manual
work in Commons). However, when I go to the Diffusion of the gadget
<https://phabricator.wikimedia.org/diffusion/1884/>, click on the main
proveit.js file, and click on "View Raw File", I get to a URL like the
following:
https://phab.wmfusercontent.org/file/data/iapd7kogqo5x2naywwlq/PHID-FILE-dk…
The URL of the raw file changes with every click and doesn't have the
proper MIME type header, so it's useless for serving the code.
I think it would be very useful, for my case and others, to have a stable
URL that serves the latest code with the proper MIME type heading. In other
words, a CDN, which may or may not be integrated with Diffusion.
Thanks!
Sorry, I hit enter early by accident.
I realized the dump file for wikidata is no longer in the format wikidatawiki-2017XXXX-pages-articles.xml.bz2 anymore.
Now, it is split in to different dumps:
https://dumps.wikimedia.org/wikidatawiki/latest/wikidatawiki-latest-md5sums…
I am wondering when did this happen and the rationale behind it. Will it be permanent or we will switch back to the original format soon ?
Thank you,
Best regards,
Trung
On 4/5/17, 9:57 PM, "Wikitech-l on behalf of Trung Dinh" <wikitech-l-bounces(a)lists.wikimedia.org on behalf of trd(a)fb.com> wrote:
Hi everyone,
I realized the dump file for wikidata is no longer in the format wikidatawiki-2017XXXX-pages-articles.xml.bz2 anymore.
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Hello!
The Analytics team would like to announce that we have migrated the
reportcard to a new domain:
https://analytics.wikimedia.org/dashboards/reportcard/#
pageviews-july-2015-now
The migrated reportcard includes both legacy and current pageview data,
daily unique devices and new editors data. Pageview and devices data is
updated daily but editor data is still updated ad-hoc.
The team is working at this time on revamping the way we compute edit data
and we hope to be able to provide monthly updates for the main edit metrics
this quarter. Some of those will be visible in the reportcard but the new
wikistats will have more detailed reports.
You can follow the new wikistats project here: https://phabricator.
wikimedia.org/T130256
Thanks,
Nuria
The Parsing team at the Wikimedia Foundation that develops the Parsoid
service is deprecating support for node 0.1x. Parsoid is the service
that powers VisualEditor, Content Translation, and Flow. If you don't
run a MediaWiki install that uses VisualEditor, then this announcement
does not affect you.
Node 0.10 has reached end of life on October 31st, 2016 [1] and node
0.12 is scheduled to reach end of life December 31st, 2016 [1].
Yesterday, we released a 0.6.1 debian package [2] and a 0.6.1 npm
version of Parsoid [3]. This will be the last release that will have
node 0.1x support. We'll continue to provide any necessary critical bug
fixes and security fixes for the 0.6.1 release till March 31st 2017 and
will be completely dropping support for all node versions before node
v4.x starting April 2017.
If you are running a Parsoid service on your wiki and are still using
node 0.1x, please upgrade your node version by April 2017. The Wikimedia
cluster runs node v4.6 right now and will soon be upgraded to node v6.x
[4]. Parsoid has been tested with node 0.1x, node v4.x and node v6.x and
works with all these versions. However, we are dropping support for node
0.1x right away from the master branch of Parsoid. Going forward, the
Parsoid codebase will adopt ES6 features available in node v4.x and
higher which aren't supported in node 0.1x and will constitute a
breaking change.
Subramanya Sastry (Subbu),
Technical Lead and Manager,
Parsing Team,
Wikimedia Foundation.
[1] Node.js Long Term Support schedule @ https://github.com/nodejs/LTS
[2] https://www.mediawiki.org/wiki/Parsoid/Releases
[3] https://www.npmjs.com/package/parsoid
[4] https://phabricator.wikimedia.org/T149331
