Replying without the public GLAM list, this is a 'behind the scenes'
observation...
Though it is great that more data about downloads are available, examining
the Wikimedia Commons downloads of video, audio and images, is actually
disheartening for me personally as someone who has worked for years
uploading media from GLAM archives. The most popular videos and audios are
almost all about graphic sex, which I guess tell us what we already know
about what is the most popular types of media that the public wants to
consume. Sadly GLAM photographic archives and lovely upload projects like
the XenoCanto birdsongs, do not make it to the first couple of pages of
results. As for images, the most used are related to nationalism, as
national flags are the most heavily used images, presumably because of
their mass usage in templates and auto-created infoboxes on articles.
So, I guess the learning point, is that we would need to re-frame what this
data means for GLAM content creators and donors rather than judging things
like "impact" or "importance to open knowledge" could ever be judged by
being high or low by this metric.
Thanks,
Fae
On Fri, 3 Jan 2020 at 03:07, Mutegeki Cliff <mutegekicliff(a)gmail.com> wrote:
> This is very good news.
>
> On Fri, Jan 3, 2020, 05:31 Kerry Raymond <kerry.raymond(a)gmail.com> wrote:
>
>> Good news indeed! Does this include metrics for articles within a
>> category (thinking here specifically of the categories related to GLAM
>> content partners) or do we stick with BaGLAMa 2 for that?
>>
>>
>>
>> Kerry
>>
>>
>>
>> *From:* GLAM [mailto:glam-bounces@lists.wikimedia.org] *On Behalf Of *Pine
>> W
>> *Sent:* Friday, 3 January 2020 7:34 AM
>> *To:* Wikimedia Commons Discussion List <commons-l(a)lists.wikimedia.org>;
>> Wikimedia Foundation Multimedia Team <Multimedia(a)lists.wikimedia.org>;
>> Wikimedia & GLAM collaboration [Public] <glam(a)lists.wikimedia.org>
>> *Subject:* [GLAM] Fwd: [Analytics] Introducing statistics for media files
>>
>>
>>
>> Forwarding good news.
>>
>>
>>
>> Pine
>> ( https://meta.wikimedia.org/wiki/User:Pine )
>>
>>
>>
>> ---------- Forwarded message ---------
>> From: *Francisco Dans* <fdans(a)wikimedia.org>
>> Date: Mon, Dec 23, 2019 at 5:52 PM
>> Subject: [Analytics] Introducing statistics for media files
>> To: A mailing list for the Analytics Team at WMF and everybody who has an
>> interest in Wikipedia and analytics. <analytics(a)lists.wikimedia.org>
>>
>>
>>
>> Hi everybody,
>>
>>
>>
>> Just in time for the holidays, we're announcing the addition of Media
>> Requests to our metrics catalog. Over the last few months we've been
>> working on a dataset offering request numbers for every single image,
>> audio, video and document in the Wiki universe, since 2015.
>>
>>
>>
>> This means we have 3 new metrics available in the Analytics Query Service:
>>
>> - Media requests per referrer: e.g. how many images, audio, videos...
>> have been accessed from English Wikipedia in the last month? *73
>> billion for November
>> <http://stats.wikimedia.org/v2/#/en.wikipedia.org/content/total-mediarequest…>.*
>> - Media requests per file: e.g. how many hits did this cool painting
>> <https://en.wikipedia.org/wiki/Christmas_tree#/media/File:Yggdrasil.jpg>
>> get in November? The answer is 483,791 hits
>> <https://wikimedia.org/api/rest_v1/metrics/mediarequests/per-file/all-refere…>
>> .
>> - Top files by media requests: e.g. what was the most popular video
>> yesterday, December 22nd? Fred Rogers testifying before the Senate
>> Subcommittee on Communications
>> <http://stats.wikimedia.org/v2/#/en.wikipedia.org/content/top-mediarequests/…>.
>> Fun! You can check out the top 1000 media files for any month or day, for
>> any media type.
>>
>> Media requests is, in terms of absolute numbers, a huge dataset, so the
>> per file and top metrics are still being loaded with data all the way to
>> 2015. We expect this loading to finish in mid January.
>>
>>
>>
>> You can read more about this in Wikitech
>> <https://wikitech.wikimedia.org/wiki/Analytics/AQS/Mediarequests>. As
>> usual if you have any questions about the dataset or the new metrics please
>> send them our way here on the list or via Phabricator.
>>
>>
>>
>> Happy holidays!
>>
>> Francisco + the A team
>>
>> --
>>
>> *Francisco Dans **(él, he, **彼**)*
>>
>> Software Engineer, Analytics Team
>>
>> Wikimedia Foundation
>>
>> _______________________________________________
>> Analytics mailing list
>> Analytics(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/analytics
>> _______________________________________________
>> GLAM mailing list
>> GLAM(a)lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/glam
>>
> _______________________________________________
> GLAM mailing list
> GLAM(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/glam
>
--
faewik(a)gmail.com https://commons.wikimedia.org/wiki/User:Fae
Personal and confidential, please do not circulate or re-quote.
+1 to Kerry's request its import to be able to easily access such
information both a KPI for the those contributing and as a
demonstrable indicator for those being asked to contribute
On Fri, 3 Jan 2020 at 10:31, Kerry Raymond <kerry.raymond(a)gmail.com> wrote:
> Good news indeed! Does this include metrics for articles within a category
> (thinking here specifically of the categories related to GLAM content
> partners) or do we stick with BaGLAMa 2 for that?
>
>
>
> Kerry
>
>
>
> *From:* GLAM [mailto:glam-bounces@lists.wikimedia.org] *On Behalf Of *Pine
> W
> *Sent:* Friday, 3 January 2020 7:34 AM
> *To:* Wikimedia Commons Discussion List <commons-l(a)lists.wikimedia.org>;
> Wikimedia Foundation Multimedia Team <Multimedia(a)lists.wikimedia.org>;
> Wikimedia & GLAM collaboration [Public] <glam(a)lists.wikimedia.org>
> *Subject:* [GLAM] Fwd: [Analytics] Introducing statistics for media files
>
>
>
> Forwarding good news.
>
>
>
> Pine
> ( https://meta.wikimedia.org/wiki/User:Pine )
>
>
>
> ---------- Forwarded message ---------
> From: *Francisco Dans* <fdans(a)wikimedia.org>
> Date: Mon, Dec 23, 2019 at 5:52 PM
> Subject: [Analytics] Introducing statistics for media files
> To: A mailing list for the Analytics Team at WMF and everybody who has an
> interest in Wikipedia and analytics. <analytics(a)lists.wikimedia.org>
>
>
>
> Hi everybody,
>
>
>
> Just in time for the holidays, we're announcing the addition of Media
> Requests to our metrics catalog. Over the last few months we've been
> working on a dataset offering request numbers for every single image,
> audio, video and document in the Wiki universe, since 2015.
>
>
>
> This means we have 3 new metrics available in the Analytics Query Service:
>
> - Media requests per referrer: e.g. how many images, audio, videos...
> have been accessed from English Wikipedia in the last month? *73
> billion for November
> <http://stats.wikimedia.org/v2/#/en.wikipedia.org/content/total-mediarequest…>.*
> - Media requests per file: e.g. how many hits did this cool painting
> <https://en.wikipedia.org/wiki/Christmas_tree#/media/File:Yggdrasil.jpg>
> get in November? The answer is 483,791 hits
> <https://wikimedia.org/api/rest_v1/metrics/mediarequests/per-file/all-refere…>
> .
> - Top files by media requests: e.g. what was the most popular video
> yesterday, December 22nd? Fred Rogers testifying before the Senate
> Subcommittee on Communications
> <http://stats.wikimedia.org/v2/#/en.wikipedia.org/content/top-mediarequests/…>.
> Fun! You can check out the top 1000 media files for any month or day, for
> any media type.
>
> Media requests is, in terms of absolute numbers, a huge dataset, so the
> per file and top metrics are still being loaded with data all the way to
> 2015. We expect this loading to finish in mid January.
>
>
>
> You can read more about this in Wikitech
> <https://wikitech.wikimedia.org/wiki/Analytics/AQS/Mediarequests>. As
> usual if you have any questions about the dataset or the new metrics please
> send them our way here on the list or via Phabricator.
>
>
>
> Happy holidays!
>
> Francisco + the A team
>
> --
>
> *Francisco Dans **(él, he, **彼**)*
>
> Software Engineer, Analytics Team
>
> Wikimedia Foundation
>
> _______________________________________________
> Analytics mailing list
> Analytics(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/analytics
> _______________________________________________
> GLAM mailing list
> GLAM(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/glam
>
--
GN.
Noongarpedia: https://incubator.wikimedia.org/wiki/Wp/nys/Main_Page
Photo Gallery: http://gnangarra.redbubble.com
Out now: A.Gaynor, P. Newman and P. Jennings (eds.), *Never Again:
Reflections on Environmental Responsibility after Roe 8*, UWAP, 2017. Order
here
<https://uwap.uwa.edu.au/products/never-again-reflections-on-environmental-r…>
.
Forwarding good news.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Francisco Dans <fdans(a)wikimedia.org>
Date: Mon, Dec 23, 2019 at 5:52 PM
Subject: [Analytics] Introducing statistics for media files
To: A mailing list for the Analytics Team at WMF and everybody who has an
interest in Wikipedia and analytics. <analytics(a)lists.wikimedia.org>
Hi everybody,
Just in time for the holidays, we're announcing the addition of Media
Requests to our metrics catalog. Over the last few months we've been
working on a dataset offering request numbers for every single image,
audio, video and document in the Wiki universe, since 2015.
This means we have 3 new metrics available in the Analytics Query Service:
- Media requests per referrer: e.g. how many images, audio, videos...
have been accessed from English Wikipedia in the last month? *73 billion
for November
<http://stats.wikimedia.org/v2/#/en.wikipedia.org/content/total-mediarequest…>.*
- Media requests per file: e.g. how many hits did this cool painting
<https://en.wikipedia.org/wiki/Christmas_tree#/media/File:Yggdrasil.jpg>
get in November? The answer is 483,791 hits
<https://wikimedia.org/api/rest_v1/metrics/mediarequests/per-file/all-refere…>
.
- Top files by media requests: e.g. what was the most popular video
yesterday, December 22nd? Fred Rogers testifying before the Senate
Subcommittee on Communications
<http://stats.wikimedia.org/v2/#/en.wikipedia.org/content/top-mediarequests/…>.
Fun! You can check out the top 1000 media files for any month or day, for
any media type.
Media requests is, in terms of absolute numbers, a huge dataset, so the per
file and top metrics are still being loaded with data all the way to 2015.
We expect this loading to finish in mid January.
You can read more about this in Wikitech
<https://wikitech.wikimedia.org/wiki/Analytics/AQS/Mediarequests>. As usual
if you have any questions about the dataset or the new metrics please send
them our way here on the list or via Phabricator.
Happy holidays!
Francisco + the A team
--
*Francisco Dans (él, he, 彼)*
Software Engineer, Analytics Team
Wikimedia Foundation
_______________________________________________
Analytics mailing list
Analytics(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics
(Note: This is only an early heads-up, to be prepared. Google Code-in
has NOT been announced yet, but last year, GCI mentors asked for more
time in advance to identify tasks to mentor. Here you are. :)
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?
Google Code-in (GCI) is an annual contest for 13-17 year old students.
GCI 2019 has not yet been announced but usually takes place from late
October to December. It is not only about coding: We also need tasks
about design, docs, outreach/research, QA.
Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors , add
your name to the mentors table, and start tagging tasks in Wikimedia
Phabricator by adding the #gci-2019 project tag.
We will need MANY mentors and MANY tasks, otherwise we cannot make it.
Last year, 199 students successfully worked on 765 tasks supported by
39 mentors. For some achievements from the last round, see
https://wikimediafoundation.org/news/2019/02/20/partnerships-make-it-possib…
Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and replace 2 uses of
Linker::link() from the list in T223010" style).
We also have more than 400 unassigned open #good-first-bug tasks:
https://phabricator.wikimedia.org/maniphest/query/3YnDUWYJfXSo/#R
Can and would you mentor some of these tasks in your area?
Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2019#List_of_Wikimedia_mentors
Thanks (as we will not be able to run this without your help),
andre
--
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/
DATASET RELEASE
=======================================================================================
We are delighted to announce the release of the MA14KD (Movie Attraction
14K Dataset) Dataset: Visual Attraction of 14000 Movie Trailers
This dataset is intended to serve the community for research on Multimedia
Retrieval, Multimedia Recommender Systems, and Computer Vision.
SUMMARY
=======================================================================================
MA14KD provides a set of “Attractiveness" features extracted from 14000
movie and tv series trailers. The movie IDs are in agreement with the movie
IDs provided by a rating dataset, that contains millions of ratings and
thousands of tags.
INFORMATION
=======================================================================================
MA14KD dataset provides the following 10 VISUAL features:
f1: Sharpness
f2: Sharpness Variation
f3: Contrast
f4: RGB Contrast
f5: Saturation
f6: Saturation variation
f7: Brightness
f8: Colorfulness
f9: Entropy
f10: Naturalness
DOWNLOAD LINKS
==============================================================================
The MA14KD [ORIGINAL] Dataset can be downloaded at:
https://www.researchgate.net/publication/333579741_MA14KD_ORIGINAL_Dataset_…
The [AGGREGATED] features of this dataset can be downloaded at:
https://www.researchgate.net/publication/333579748_MA14KD_AGGREGATED_Datase…
COLLABORATORS
==============================================================================
The list of collaborators is the following:
Mehdi Elahi: http://www.linkedin.com/in/mehdielahi
Farshad B. Moghaddam: https://github.com/fmoghaddam
Reza Hosseini https://www.linkedin.com/in/reza-hoseini/
Christoph Trattner: https://www.christophtrattner.info
Marko Tkalčič: http://markotkalcic.com
Forwarding to other lists. :)
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: Léa Lacroix <lea.lacroix(a)wikimedia.de>
Date: Thu, Mar 14, 2019 at 8:05 PM
Subject: [Wikidata] New data type: musical notation with Lilypond format
To: Discussion list for the Wikidata project. <wikidata(a)lists.wikimedia.org>
Hello all,
Following a request from community members, we just deployed a new data
type called “Musical Notation” in order to store musical notation in
Wikidata. Property creators can now find this new data type in the list and
create new properties with it.
A property with musical notation data type will display the notation in
Lilypond <https://www.wikidata.org/wiki/Q195946> format, using the score
extension <https://www.mediawiki.org/wiki/Extension:Score>.
For example, if you enter this code as a value: \relative c' { c d e f | g2
g | a4 a a a | g1 |}, it will be displayed as a score:
[image: Screenshot musical notation Wikidata 1.png]
<https://commons.wikimedia.org/wiki/File:Screenshot_musical_notation_Wikidat…>
The score also appears on the diff pages.
[image: Screenshot musical notation Wikidata 2.png]
<https://commons.wikimedia.org/wiki/File:Screenshot_musical_notation_Wikidat…>
The existing property LilyPond notation (P5482)
<https://www.wikidata.org/wiki/Property:P5482> is used on around 300 items
<https://www.wikidata.org/w/index.php?title=Special%3AWhatLinksHere&target=P…>.
If you need any help from the developers to change the datatype of the the
property or to migrate the content, please let me know.
One bug is already known and we’re working on fixing it: if the score is
long, it gets out of the statement box and overlaps with the edit button.
If you encounter any issue, feel free to create a subtask of this ticket
<https://phabricator.wikimedia.org/T208489>.
Cheers,
--
Léa Lacroix
Project Manager Community Communication for Wikidata
Wikimedia Deutschland e.V.
Tempelhofer Ufer 23-24
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/029/42207.
_______________________________________________
Wikidata mailing list
Wikidata(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikidata
Forwarding to additional lists. I believe that in the past there has been
consideration of using automated image recognition to categorize images on
Commons.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---------- Forwarded message ---------
From: caip2019(a)unisa.it <caip2019(a)unisa.it>
Date: Tue, Mar 5, 2019 at 6:58 AM
Subject: [AI] Extended call for Workshops/Tutorials at CAIP 2019 in
Salerno, Italy
To: <ai(a)lists.wikimedia.org>
The CAIP2019 Organizing Committee invites proposals for workshops and
tutorials in conjunction with the 18th International Conference on Computer
Analysis of Images and Patterns. The workshops and tutorials will be held
as side events of the main conference.
*Proposals for Workshop*
The CAIP2019 workshops will provide forums where participants will have
opportunities to discuss technical topics and actively share ideas. The
topics of the workshops should be at the frontiers of academic research or
important applications in the domain of computer vision and pattern
recognition. Each proposal will be assessed for its scientific content,
structure and relevance. Cogently, good proposals would encourage
discussion and interaction between the participants, achievable in a
several ways, e.g., through presentations of submitted work, panel
discussions and hands-on sessions.
Download here the Call for Workshops
<http://caip2019.unisa.it/pages/submission/callcaip2019workshop.pdf>
*Proposals For Tutorials*
The CAIP 2019 Organizing Committee invites proposals for tutorials to be
held as side events of the main conference in Salerno, Italy. Tutorials
should serve one or more of the following objectives:
-
Introduce students and newcomers to major topics of CAIP research
-
Provide instruction on established practices and methodologies
-
Survey a mature area of CAIP research and/or practice
-
Motivate and explain a CAIP topic of emerging importance
-
Introduce expert non-specialists to a CAIP research area
Proposals should contain the following information:
-
The title and a brief description of the tutorial
-
A detailed outline of the tutorial, including preferred length of
tutorial: either 3 hours (half day) or 6 hours (full day). If it is a
full-day tutorial, please give a brief justification
-
Characterization of the potential target audience for the tutorial,
including prerequisite knowledge and estimated number of attendees
-
A description of why the tutorial topic would be of interest to a
substantial part of the CAIP audience
-
A brief resume of the presenter(s), which should include name, title,
affiliation, e-mail address, background in the tutorial area, example of
work in the area (e.g. publications and/or industrial work).
Download here the Call for Tutorials
<http://caip2019.unisa.it/pages/submission/callcaip2019tutorials.pdf>
*Submission*
Proposals should be submitted by electronic mail to the CAIP Organizing
Committee (caip2019(a)unisa.it)
*Important Dates*
Deadline for workshop proposal:
*March 11, 2019 *Notification of Acceptance: *March 15, 2019*
_______________________________________________
AI mailing list
AI(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/ai
A few months ago I switched our TimedMediaHandler's config to support the
newer, more bandwidth-efficient VP9/Opus variant of WebM and to use these
preferably over the older VP8/Vorbis version when creating scaled,
playback-ready derivatives.
(This does not affect upload support -- you may continue to upload video
files in WebM VP9, WebM VP8, or Ogg Theora formats, with either Vorbis or
Opus audio.)
Conversions of existing files on Commons ran in the background for some
weeks, finishing in November. I'm now running a final pass for
high-resolution files and any files on other wikis that didn't get a
conversion yet, in preparation for removing the VP8 derivatives in the next
couple of weeks to free storage space.
This should have relatively little visible effect for users, unless someone
is relying on the particular derivative files with extensions like
".360p.webm"; the new versions are named like ".360p.vp9.webm".
Note that IE 11 users using the "WebM Media Foundation Components for IE
<https://www.webmproject.org/ie/>" will not be able to play back the new
VP9/Opus files natively, as this driver has never been updated for VP9 or
Opus. IE 11 users will receive low-resolution, slow JavaScript-based video
playback instead. If you find this is troublesome, the recommended solution
is to switch to any other browser.
Third-party MediaWiki + TimedMediaHandler users should be aware that the
defaults are changing, and in future the VP8-specific support and code
paths may be removed. TimedMediaHandler will probably change a lot in the
coming months with upcoming WebVTT subtitle format, a streamlined
videojs-based player, and hopefully more!
-- brion
There's been some comments on some old tasks such as T27707
<https://phabricator.wikimedia.org/T27707> about problems with uploading
files that include text metadata that looks like HTML elements.
Years ago, we added security checks for IE 5/6/7 to work around IE's mime
type sniffing: if you went to view a .png file directly in IE (as opposed
to in an <img>) the browser would check the first few bytes of the file to
detect its type, overriding the HTTP Content-Type header. HTML would be
detected with a higher priority than the actual image formats, making it
possible to create an actual .png image which when viewed as an image
looked like an image, but when viewed as a web page was interpreted as
HTML, including any embedded JavaScript.
(This was defense in depth in addition to hosting files on a separate
domain; among other things, we sometimes serve files out from the main
domain when dealing with archived (deleted) versions, and third-party
installs are not guaranteed to have a second domain.)
Browsers have moved on, but the code remains and it trips up legitimate
files containing links in metadata, or sometimes just random compressed
data that looks like an element!
I've done a quick research check on feasibility:
* IE 6 and earlier can no longer access Wikimedia sites due to lack of SNI
and TLS 1.0 or later
* IE 7 on Windows XP can no longer access Wikimedia sites due to lack of SNI
* IE 7 on Windows Vista **can** access Wikimedia sites.
* IE 8 and higher support X-Content-Options: nosniff to disable sniffing,
which we already use on all MediaWiki requests.
At some point Microsoft dropped the sniffing, but I'm not sure if it was a
later IE version or an Edge version. No other browsers in reasonably
current versions seem to have this problem.
So the only remaining browser version that might be affected is IE 7 on
Windows Vista, which supports SNI and TLS 1.0. It might or might not still
work once we drop TLS 1.0 some time in the future. (Per our TLS dashboard
<https://grafana.wikimedia.org/d/000000458/tls-ciphersuite-explorer?orgId=1>
about
1.2% of our connections still use TLS 1.0, but this isn't broken down
between logged-in-user views and anon views.)
Open questions:
* Should we drop the anti-sniff checks on upload?
* If we do, should we forbid logins with IE 7, or something else to protect
the occasional IE 7 logged-in user from a hypothetical targeted drive-by
attack? (Is it actually worth doing work and testing it for this?)
* Should we add X-Content-Options: nosniff on files served from
upload.wikimedia.org too?
-- brion
Thanks for the news, Keegan. I'm cross-posting the info to other lists with
the date boldly corrected.
Pine
( https://meta.wikimedia.org/wiki/User:Pine )
---
Hi all, following up on last month's announcement... [0]
Multilingual file captions will be released this week, on either Wednesday,
9 January or Thursday, 10 January 2019. Captions are a feature to add
short, translatable descriptions to files. Here's some links you might want
to look follow before the release, if you haven't already:
* Read over the help page for using captions - I wrote the page on
mediawiki.org because captions are available for any MediaWiki user, feel
free to host/modify a copy of the page here on Commons. [1]
* Test out using captions on Beta Commons. [2]
* Leave feedback about the test on the captions test talk page, if you have
anything you'd like to say prior to release. [3]
Additionally, there will be an IRC office hour on Thursday, 10 January with
the Structured Data team to talk about file captions, as well as anything
else the community may be interested in. Date/time conversion, as well as a
link to join, are on Meta. [4]
Thanks for your time, I look forward to seeing those who can make it to the
IRC office hour on Thursday. I'll reply to this post once I confirm exactly
what day file captions will be released to Commons.
0.
https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump&oldid=…
1. https://www.mediawiki.org/wiki/Help:File_captions
2. https://commons.wikimedia.beta.wmflabs.org/
3.
https://commons.wikimedia.org/wiki/Commons_talk:Structured_data/Beta_captio…
4. https://meta.wikimedia.org/wiki/IRC_office_hours#Upcoming_office_hours
