On Tue, Jul 21, 2015 at 6:52 PM, Ryan Kaldari <[email protected]> wrote:
> If the MultimediaViewer extension is transferred to Editing (i.e. > Multimedia), TimedMediaHandler should probably go with it, as they are both > mainly for presenting media within pages. > I agree with Jon that MMV should belong to Reading Web (especially since they already own the mobile media viewer and the plan is to merge the two), but the comparison does not really stand up. TMH is about a whole lot of things: it adds and manages a new page content type (TimedText), it integrates the file upload with machinery to run and control video transcoding jobs, it is deeply entangled with WMF infrastructure (it has its own server cluster), it provides its own file metadata API (although it probably shouldn't <https://phabricator.wikimedia.org/T89971>). And it also presents media within pages. It could go to any number of teams - Reading Infrastructure is IMO a practical decision for now because all the recent TMH breakage I can remember was MW core or devops related (mostly because those have more interdependencies and a higher rate of change than frontend code), and the other potential teams focus on frontend. And while frontend is the part of TMH in the biggest need of a rewrite (TheDJ actually started that and anyone from the frontend teams helping out by reviewing his code would be great), extension responsibility is explicitly not about improvements but about reacting to breakage.
_______________________________________________ Mobile-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/mobile-l
