Good morning from San Francisco, Multimedians!
The Multimedia team just finished their weekly planning meeting, and we decided it would be a fantastic first step to write a quick email each week describing what sorts of things we're working on and what you can expect out of us in the coming weeks and months.
== Release-level ==
On the release level, we've made a few plans in our most recent meeting. We intend to push back our planned release of MultimediaViewer [0] a few weeks, pending a better view of how well we're doing with estimating our velocity and keeping it up. If we do really well, we may release it to MediaWiki.org as the default for logged-in users as soon as March 13th. Other releases will follow in a staggered manner.
== Last week ==
As this release is focused 100% on finishing MultimediaViewer so we can release it to wider audiences, last week's accepted cards [1] are no surprise:
* Several bugfixes to CSS and JavaScript alike, including a nasty bug involving keyup event handlers [2], a stubborn bug having to do with foreign database image repositories [3], and a bug arising out of our lazy-loading patch from the prior week [4]. Also a fix for a race condition when loading many images quickly. [5] * Work on technical debt, in particular consolidating the spaghetti code strung between two class systems into our single "mmv" module set. [6] * Showing permissions that are more complicated to the user, instead of just the license name [7] [8] - this is a big win for Commons, where file permissions can sometimes be...well, a little hairy. :) * Loading a fuzzy thumbnail of the image while the bigger image is loading in the interface [9] - gives you a more consistent viewing experience that doesn't seem as choppy.
== This week ==
Notable cards we've scheduled or continued working on this week include [10]:
* Share [11] and embed [12] features for the lightbox, using oojs-ui that is newly in core. We'll be giving you wikitext and HTML code that you can copy and have images on-wiki or off. Also we'll have an easy link to the image that you can share on whatever Flitter or Macebook site your heart desires. I'll be sending a separate mail about this shortly to update you and be a little more verbose. * Metrics for MultimediaViewer [13] - we've put this off long enough, it's high time we had dashboards! These will show you things like how many times the close button is used, how many times people go into fullscreen, and also load times for images, metadata, and more. * Download interface for files [14] - this will use the same panel as share and embed, but will be slightly differently organized.
== Future ==
If you have any questions or suggestions for the Multimedia team regarding this release, or any of the work we're doing, feel free to contact us on- or off-list. We'll try to be better about using this list in coming weeks, and we hope you'll enjoy the updates :)
You can also find us in #wikimedia-multimedia on irc.freenode.net, and you can leave feedback about our various products on the subpages of our team page on MediaWiki.org [15].
[0] https://www.mediawiki.org/wiki/Extension:MultimediaViewer [1] http://ur1.ca/gpp1a [2] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/236 [3] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/217 [4] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/254 [5] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/242 [6] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/177 [7] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/118 [8] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/197 [9] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/146 [10] http://ur1.ca/gpp39 [11] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/147 [12] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/148 [13] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/54 [14] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/79 [15] https://www.mediawiki.org/wiki/Multimedia
Thanks for reading, and have a good week!
On Thu, Feb 27, 2014 at 11:17:45AM -0800, Mark Holmquist wrote:
On the release level, we've made a few plans in our most recent meeting. We intend to push back our planned release of MultimediaViewer [0] a few weeks, pending a better view of how well we're doing with estimating our velocity and keeping it up. If we do really well, we may release it to MediaWiki.org as the default for logged-in users as soon as March 13th.
I lied! Our earliest option is March 20th. Sorry about the slight miscommunication.
And just a note from QA to say "thanks" for not using those data URI strings! -Chris
On Thu, Feb 27, 2014 at 12:17 PM, Mark Holmquist mtraceur@member.fsf.orgwrote:
Good morning from San Francisco, Multimedians!
The Multimedia team just finished their weekly planning meeting, and we decided it would be a fantastic first step to write a quick email each week describing what sorts of things we're working on and what you can expect out of us in the coming weeks and months.
== Release-level ==
On the release level, we've made a few plans in our most recent meeting. We intend to push back our planned release of MultimediaViewer [0] a few weeks, pending a better view of how well we're doing with estimating our velocity and keeping it up. If we do really well, we may release it to MediaWiki.org as the default for logged-in users as soon as March 13th. Other releases will follow in a staggered manner.
== Last week ==
As this release is focused 100% on finishing MultimediaViewer so we can release it to wider audiences, last week's accepted cards [1] are no surprise:
- Several bugfixes to CSS and JavaScript alike, including a nasty bug involving keyup event handlers [2], a stubborn bug having to do with foreign database image repositories [3], and a bug arising out of our lazy-loading patch from the prior week [4]. Also a fix for a race
condition when loading many images quickly. [5]
- Work on technical debt, in particular consolidating the spaghetti code strung between two class systems into our single "mmv" module set. [6]
- Showing permissions that are more complicated to the user, instead of just the license name [7] [8] - this is a big win for Commons, where file permissions can sometimes be...well, a little hairy. :)
- Loading a fuzzy thumbnail of the image while the bigger image is loading in the interface [9] - gives you a more consistent viewing experience that doesn't seem as choppy.
== This week ==
Notable cards we've scheduled or continued working on this week include [10]:
- Share [11] and embed [12] features for the lightbox, using oojs-ui that is newly in core. We'll be giving you wikitext and HTML code that you can copy and have images on-wiki or off. Also we'll have an easy link to the image that you can share on whatever Flitter or Macebook site your heart desires. I'll be sending a separate mail about this shortly to update you and be a little more verbose.
- Metrics for MultimediaViewer [13] - we've put this off long enough, it's high time we had dashboards! These will show you things like how many times the close button is used, how many times people go into fullscreen, and also load times for images, metadata, and more.
- Download interface for files [14] - this will use the same panel as share and embed, but will be slightly differently organized.
== Future ==
If you have any questions or suggestions for the Multimedia team regarding this release, or any of the work we're doing, feel free to contact us on- or off-list. We'll try to be better about using this list in coming weeks, and we hope you'll enjoy the updates :)
You can also find us in #wikimedia-multimedia on irc.freenode.net, and you can leave feedback about our various products on the subpages of our team page on MediaWiki.org [15].
[0] https://www.mediawiki.org/wiki/Extension:MultimediaViewer [1] http://ur1.ca/gpp1a [2] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/236 [3] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/217 [4] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/254 [5] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/242 [6] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/177 [7] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/118 [8] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/197 [9] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/146 [10] http://ur1.ca/gpp39 [11] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/147 [12] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/148 [13] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/54 [14] https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/79 [15] https://www.mediawiki.org/wiki/Multimedia
Thanks for reading, and have a good week!
-- Mark Holmquist Software Engineer, Multimedia Wikimedia Foundation mtraceur@member.fsf.org https://wikimediafoundation.org/wiki/User:MHolmquist
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBAgAGBQJTD49ZAAoJEEPl+wghkjzxIMMQAOMQk0jA4RpzW2qNunsKV0Jq SvlBh7vh/+M+sZkvFjSQqwH7z4hb/YwEwIDRsKtZRyYV90UzDpKLIC+m/UgKbSmz FFjOyWQZ8EULekAm1wrY91qP+QqdUZHVZ9xo+LPihWvRSz4lsCJZ3QhiaFtgqmOB gKM+Ly/TMWYEpUlG8Y5WjFw+qpQSI9VoVXN6RDUXXqEPJSav2DG/Pwd23xDNYlhq f5rEb6tgDKVxLH5XGJpkDljiWsmQMq1AaOD6IQxrj8Zi3MK5uO2NakrKHxnMEVgb ek2UDSo/iRdgfSskpqzovIuW4Poz+71BtAUDFFA+frZ56vmxH1KjbteT7oXvK63Q mluQQye5f+PqSaRXCgOmygeFmF5nVH8TOJKNDgm2AZQ+ZK20oto+PID4bpCShoCP jQZyxvB98Hb9TcDHCioNVjturhYByfF++p6WCH79iEaEzxt+E3hkSwARxLrVGSqU NhUJry0EAlQdpEPzwsvom7Bdoe0VxBos6Ja5y4gckEVS86HdOzOE1lCavZmyB5To W/7dIdIMeIdgUjIUG5uF+crmUDZ9tAbL/oN2tKkwGq+AI3j2rKqdzWOE/lRQSkVq HpFarUx+rd/rPqhf/3agcTE6sBO7xotbYqCjzi3hrupfukDwv8WW9ZUazAzDPyAP Cv2EULJ9+36g70IfkiR0 =cPDa -----END PGP SIGNATURE-----
Multimedia mailing list Multimedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/multimedia
Hey Mark and team,
Excellent first step! Please keep the Multimedia news coming, this is great :)
* Metrics for MultimediaViewer [13] - we've put this off long enough, it's
high time we had dashboards! These will show you things like how many times the close button is used, how many times people go into fullscreen, and also load times for images, metadata, and more.
I'd have questions on this.
1/ The user story says this is for " manager or community member" does that mean that every user (logged in or not) can query the dashboard ?
2/ My understanding is that these metrics will be at a global, site-level - correct ? Would there be a possiblity to have fancy stats at a finer level? Like, how many times File:Example.jpg was enlarged ? (awesome for GLAM partners) Or How many times any thumb in article [[Barack Obama]] was clicked through (might be intersting for article writers)? etc.
3/ When implemented, will the "Share", "Embed" and "Download" feed the dashboard as well ?
Thanks!
On Thu, Feb 27, 2014 at 08:49:37PM +0100, Jean-Fr?d?ric wrote:
1/ The user story says this is for " manager or community member" does that mean that every user (logged in or not) can query the dashboard ?
The dashboard will be on our metrics site [0], so yes, it will be public.
2/ My understanding is that these metrics will be at a global, site-level - correct ?
Currently it's global, but we could as easily generate data for projects.
Would there be a possiblity to have fancy stats at a finer level? Like, how many times File:Example.jpg was enlarged ? (awesome for GLAM partners) Or How many times any thumb in article [[Barack Obama]] was clicked through (might be intersting for article writers)? etc.
We specifically don't store information like what image was loaded, because with a little magic we could use that information in conjunction with others to determine what a user was looking at at any given time. We were unhappy with this idea, so we deleted [1] loads of information from the schema we're using [2].
3/ When implemented, will the "Share", "Embed" and "Download" feed the dashboard as well ?
We could add clicks on the "use this file" link, but clicks between the "share"/"embed"/"download" tabs may not be super useful. We have no way of determining what information the user actually winds up copying to their clipboard, so it'd be pretty random-looking data IMO.
Hope that helps!
[0] http://multimedia-metrics.wmflabs.org [1] https://meta.wikimedia.org/w/index.php?title=Schema%3AMediaViewer&diff=6... [2] https://meta.wikimedia.org/wiki/Schema:MediaViewer
On Thu, Feb 27, 2014 at 1:26 PM, Mark Holmquist mtraceur@member.fsf.orgwrote:
We could add clicks on the "use this file" link, but clicks between the "share"/"embed"/"download" tabs may not be super useful. We have no way of determining what information the user actually winds up copying to their clipboard, so it'd be pretty random-looking data IMO
We could use the clipboard API (on modern browsers) to detect when someone copies text from a given textfield. That sounds like a pretty good metric actually, I've created a ticket for it (#269https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/269 ).
Cool.
What a nice surprise :)
I crossed-linked this ticket with card #54 and included it in this release for now.
We’ll have to discuss how quickly all this can be implemented, but at least these features are now on our radar.
Onward!
Fabrice
On Feb 27, 2014, at 2:20 PM, Gergo Tisza gtisza@wikimedia.org wrote:
On Thu, Feb 27, 2014 at 1:26 PM, Mark Holmquist mtraceur@member.fsf.org wrote: We could add clicks on the "use this file" link, but clicks between the "share"/"embed"/"download" tabs may not be super useful. We have no way of determining what information the user actually winds up copying to their clipboard, so it'd be pretty random-looking data IMO
We could use the clipboard API (on modern browsers) to detect when someone copies text from a given textfield. That sounds like a pretty good metric actually, I've created a ticket for it (#269). _______________________________________________ Multimedia mailing list Multimedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/multimedia
_______________________________
Fabrice Florin Product Manager Wikimedia Foundation
Thanks, Jean-Fred,
Glad our updates work for you — we really appreciate your good suggestions and thoughtful questions, as always :)
See my notes below, to complement Mark’s responses.
Cheers,
Fabrice
On Feb 27, 2014, at 1:26 PM, Mark Holmquist mtraceur@member.fsf.org wrote:
On Thu, Feb 27, 2014 at 08:49:37PM +0100, Jean-Fr?d?ric wrote:
1/ The user story says this is for " manager or community member" does that mean that every user (logged in or not) can query the dashboard ?
The dashboard will be on our metrics site [0], so yes, it will be public.
Our public dashboards are likely to be similar in look and feel to these dashboards we created for Echo Notifications:
http://ee-dashboard.wmflabs.org/dashboards/enwiki-features
2/ My understanding is that these metrics will be at a global, site-level - correct ?
Currently it's global, but we could as easily generate data for projects.
We are hoping to generate a few dashboards for individual projects, as recommended in this Mingle card #54:
https://wikimedia.mingle.thoughtworks.com/projects/multimedia/cards/54
We would like to initially track this data for these sites:
• MediaWiki.org (first pilot site - non-Wikipedia) • Hungarian Wikipedia (or other Wikipedia pilot site TBD) • Wikimedia Commons (large non-Wikipedia site) • English Wikipedia (large Wikipedia site) • French Wikipedia (or other Wikipedia site TBD)
However, it is not practical at this time to implement dashboards for all sites, so we may not go much further than this initially.
Would there be a possiblity to have fancy stats at a finer level? Like, how many times File:Example.jpg was enlarged ? (awesome for GLAM partners) Or How many times any thumb in article [[Barack Obama]] was clicked through (might be intersting for article writers)? etc.
We specifically don't store information like what image was loaded, because with a little magic we could use that information in conjunction with others to determine what a user was looking at at any given time. We were unhappy with this idea, so we deleted [1] loads of information from the schema we're using [2].
3/ When implemented, will the "Share", "Embed" and "Download" feed the dashboard as well ?
We could add clicks on the "use this file" link, but clicks between the "share"/"embed"/"download" tabs may not be super useful. We have no way of determining what information the user actually winds up copying to their clipboard, so it'd be pretty random-looking data IMO.
Jean-Fred: good point!
I just added ‘Use This File’ clicks to the proposed specification on Mingle, so we can count the number of times a user clicked on that button.
I agree with Mark that we cannot track how often they actually share or embed a file, but at least we can find out if users seem interested in this feature.
Hope that helps!
[0] http://multimedia-metrics.wmflabs.org [1] https://meta.wikimedia.org/w/index.php?title=Schema%3AMediaViewer&diff=6... [2] https://meta.wikimedia.org/wiki/Schema:MediaViewer
-- Mark Holmquist Software Engineer, Multimedia Wikimedia Foundation mtraceur@member.fsf.org https://wikimediafoundation.org/wiki/User:MHolmquist _______________________________________________ Multimedia mailing list Multimedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/multimedia
_______________________________
Fabrice Florin Product Manager Wikimedia Foundation
On Thu, Feb 27, 2014 at 2:29 PM, Fabrice Florin fflorin@wikimedia.orgwrote:
However, it is not practical at this time to implement dashboards for all sites, so we may not go much further than this initially.
We could probably share the data though?
As I understand, Mark has some scripts running from a cronjob to aggregate data from the event logs (which cannot be public for privacy reasons) into CSV files, and those CSV files are fed to Limn. Building those CSVs for every wiki and making them downloadable should be simple, I imagine?
On Thu, Feb 27, 2014 at 02:49:28PM -0800, Gergo Tisza wrote:
As I understand, Mark has some scripts running from a cronjob to aggregate data from the event logs (which cannot be public for privacy reasons) into CSV files, and those CSV files are fed to Limn. Building those CSVs for every wiki and making them downloadable should be simple, I imagine?
My favorite answer: "Yes".
Once I have a first-pass script that does this for one wiki, it should be "trivial" to replace the places that call a specific wiki with variables that get replaced and saved into multiple scripts, then run all the scripts.
But, this is a wishlist thing that I'm not super interested in worrying about right now - I want to do the metrics we need, not the ones we might later.
But, I'll leave it open to do later. :)
You can see the scripts I'm running at Gitorious [0]. There are some leftovers from my first shitty implementation and the cronjobs aren't there, but you can get a good picture.
[0] https://gitorious.org/analytics/multimedia
Thanks Mark, Gergo & Fabrice for the answers ! This helps a lot.
I'd like to develop this point :
Would there be a possiblity to have fancy stats at a finer level? Like,
how many times File:Example.jpg was enlarged ? (awesome for GLAM partners)
Currently, though I do not think it is widely used, it is possible to see
how popular a file is based on the page-views of its file description - using Henrik's service [1]. (And as usual, Magnus made an awesome tool to query that data for an entire media collection ^_^). It can be interesting especially for use cases like GLAM partnerships.
With MediaViewer, I expect that these figures will go down a lot - users just wanting to view the file in a higher resolution will have what they want without needing to browse to the file description page on Wikimedia Commons.
So as a media contributor to Wikimedia Commons, I want to know how much my file is viewed through MediaViewer ;-)
Also, here is a long wanted dream-feature request - being able to track how much a file/media collection is reused outside of Commons. Having data on MediaViewer usage of "Download" or "Reuse" would be incomplete but could provide a nice approximation.
We specifically don't store information like what image was loaded, because
with a little magic we could use that information in conjunction with others to determine what a user was looking at at any given time. We were unhappy with this idea, so we deleted [1] loads of information from the schema we're using [2].
These are serious concerns indeed... Any chance data could be anonymised or the magic exorcized so we could have both privacy-repect and awesome data?
I agree with Mark that we cannot track how often they actually share or
embed a file, but at least we can find out if users seem interested in this feature.
And if we can track it, I suppose we could A/B test to see which formulations seem to make more sense to users ? ;-)
Thanks a lot for engaging in this discussion - I appreciate it a lot!
[1] Eg. < http://stats.grok.se/commons.m/201402/File:Fran%C3%A7ois_Hollande_%28Journ%C...
Hi
I totally agree with Jean-Frédéric: these data are precious for the GLAM movement.
Benoît Le 27 févr. 2014 23:51, "Jean-Frédéric Berthelot" < jeanfrederic.berthelot@gmail.com> a écrit :
Thanks Mark, Gergo & Fabrice for the answers ! This helps a lot.
I'd like to develop this point :
Would there be a possiblity to have fancy stats at a finer level? Like,
how many times File:Example.jpg was enlarged ? (awesome for GLAM partners)
Currently, though I do not think it is widely used, it is possible to
see how popular a file is based on the page-views of its file description - using Henrik's service [1]. (And as usual, Magnus made an awesome tool to query that data for an entire media collection ^_^). It can be interesting especially for use cases like GLAM partnerships.
With MediaViewer, I expect that these figures will go down a lot - users just wanting to view the file in a higher resolution will have what they want without needing to browse to the file description page on Wikimedia Commons.
So as a media contributor to Wikimedia Commons, I want to know how much my file is viewed through MediaViewer ;-)
Also, here is a long wanted dream-feature request - being able to track how much a file/media collection is reused outside of Commons. Having data on MediaViewer usage of "Download" or "Reuse" would be incomplete but could provide a nice approximation.
We specifically don't store information like what image was loaded,
because with a little magic we could use that information in conjunction with others to determine what a user was looking at at any given time. We were unhappy with this idea, so we deleted [1] loads of information from the schema we're using [2].
These are serious concerns indeed... Any chance data could be anonymised or the magic exorcized so we could have both privacy-repect and awesome data?
I agree with Mark that we cannot track how often they actually share or
embed a file, but at least we can find out if users seem interested in this feature.
And if we can track it, I suppose we could A/B test to see which formulations seem to make more sense to users ? ;-)
Thanks a lot for engaging in this discussion - I appreciate it a lot!
[1] Eg. < http://stats.grok.se/commons.m/201402/File:Fran%C3%A7ois_Hollande_%28Journ%C...
-- Jean-Frédéric
Multimedia mailing list Multimedia@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/multimedia
multimedia@lists.wikimedia.org