Thank you for your proposal, @brion!

I guess this proposal aims to be pre-scheduled in relation to the main topic Handling wiki content beyond plaintext? Please follow the instructions at https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/Call_for_participation to clarify these and other details.

@brion, regarding "need good infrastructure in the wiki for storing large files and making derivitives that may be slow", what's the class of thing that may be slow?

If I may say so, I feel like this "cross-functional support for rich media" topic is worth a 50-90 minute slot of its own to kick off its discussion. In terms of ordering, perhaps this "cross-functional support for rich media" topic should precede the "handling wiki content beyond plaintext" kickoff.

In T147604#2722541, @dr0ptp4kt wrote:

@brion, regarding "need good infrastructure in the wiki for storing large files and making derivitives that may be slow", what's the class of thing that may be slow?

The creation of the derivative file -- for instance encoding video at high resolutions may be slower than real-time, so a 1-hour conference video might take a good several hours to completely process at several output resolutions, especially as we move towards newer codecs that compress better (VP9 -- half the bitrate but up to several times the encode time vs VP8).

We already have problems with the job queue when creating the faster Theora and VP8 derivatives, with timeouts causing additional jobs to be fired off before the first job completes, overloading the video scaler machines.

Large video files are also a moderate problem for operations that need to re-fetch the files from the SWIFT backend, such as purging and rebuilding metadata, which can take a while on a 1gig+ video file.

There are similarly some issues with streaming/caching large files between the Varnish frontend and the SWIFT backend, which sometimes causes delays when loading files. (I haven't fully quantified this problem, needs further investigation.)

Thanks, @brion!

Please remember the next deadline in the selection process:

2016-11-14: Deadline for defining a good problem statement, expectations, and links to relevant resources.

That is next Monday.

In T147604#2722541, @dr0ptp4kt wrote:

If I may say so, I feel like this "cross-functional support for rich media" topic is worth a 50-90 minute slot of its own to kick off its discussion.

There is nothing stopping this discussion to be kicked off here, before the Summit, right? That is the point.

I am moving this proposal to "on track" not because there has been significant discussion here so far, neither because it has received a large support. I am keeping it on track because the topic seems relevant and there are no other proposals discussing this area (?). Also because I assume that the Architecture Committee thinks it is important, since Brion is pushing for it?

In any case, unless this proposal receives more explicit support and kicks off a real discussion, it is very likely that it will be moved to the Unconference.

I'm proposing to include this in a merged session: T151952: Media, Visualizations, and Layout at Wikidev'17.

@brion Hey! As developer summit is less than four weeks from now, we are working on a plan to incorporate the ‘unconference sessions’ that have been proposed so far and would be generated on the spot. Thus, could you confirm if you plan to facilitate this session at the summit? Also, if your answer is 'YES,' I would like to encourage you to update/ arrange the task description fields to appear in the following format:

Session title
Main topic
Type of activity
Description Move ‘The Problem,' ‘Expected Outcome,' ‘Current status of the discussion’ and ‘Links’ to this section
Proposed by Your name linked to your MediaWiki URL, or profile elsewhere on the internet
Preferred group size
Any supplies that you would need to run the session e.g. post-its
Interested attendees (sign up below)

1. Add your name here

We will be reaching out to the summit participants next week asking them to express their interest in unconference sessions by signing up.

To maintain the consistency, please consider referring to the template of the following task description: https://phabricator.wikimedia.org/T149564.

As a Summit proposal, this topic will be part of T151952: Media, Visualizations, and Layout at Wikidev'17.

This task has a live of its own though, so I am just removing it from the Summit workboard.

@brion, can you come up with no-more-than-ten slides to introduce & overview this topic?

From my understanding, it seems like this is just related to Wikimedia Video's stuff, so I'm removing Video extension since the name indicates otherwise, and the tag I mentioned is for an extension different from what Wikimedia uses to my knowledge. At the time this tag was included it was named Video, so I recently renamed it although I forgot to mention it here - hope that clears up the confusion, sorry about that! Social-Tools was auto-added only because Video extension is an extension under the Social-Tools extension umbrella.

(Although if this is related to even media that includes third-party stuff, then feel free to re-add it - sorry for all the mess!)

Closing as there is nothing actionable in this task about a session at a physical event many years ago; see T147604#2889159
If there were actionable tasks, please create separate dedicated engineering tickets instead. Thanks.