I went trough this thing and it's huge, with very distinct stuff in it.
I propose adding at least:
Renaming the existing extension to just TimedMediaHandler could be considered as well.
A showing of hands in support for the names would be appreciated, alternatives, objections etc.
I'd love to see the Multimedia team providing input / opinions here (e.g. a TMH umbrella project?), plus who would be supposed to triage this to set/add these projects.
The old Multimedia team did not have the resources to support TMH apart from putting out fires and sometimes helping with code review. Not sure about the new one but I imagine they are in a similar situation. IMO whatever the de facto maintainers find helpful should be fine. From the gerrit queues, those seem to be TheDJ, @brion and @Paladox.
Are you proposing actually splitting the extension, or just having separate phab projects for the components?
Creating separate phab projects sounds fine to me (And the names also sound fine). Actually separating the extensions also sounds like an ok idea to me, particularly if I don't have to be the one to do it ;)
Having several projects. Where the actual code lies, will probably change at some point in the future as well, but that's a longer story and would be different tickets :)
If there is consensus among the people working on TMH, feel free to create these projects.
I've done some presorting on the TMH board and I think the following projects should be added.
Name: TimedMediaHandler-Player
Description: Issues relating to the HTML5 playback of A/V assets using the JS enriched web player. A subproject of TimedMediaHandler.
Type: Briefcase+Blue.
Policy: Default
Name: TimedMediaHandler-TimedText
Description: Issues relating to the addition, management and playback of subtitles, captions and other forms of Timed Text. A subproject of TimedMediaHandler.
Type: Briefcase+Blue.
Policy: Default
Name: TimedMediaHandler-Transcode
Description: Issues relating to transcoding pipelines (the creation of derivative files) and the management of these files. A subproject of TimedMediaHandler.
Type: Briefcase+Blue.
Policy: Default
We will have an assortment of remaining tickets (format support, originals management, alternative playback interfaces [mobile], metadata parsing) that can be left in the main TimedMediaHandler.
Where are people supposed to put their tasks? Into both TimedMediaHandler and TimedMediaHandler-something, or just into one?
Does someone plan to triage the open 162 tasks?
@Aklapper I already triaged most of them this weekend on the workboard. That way i can easily do a batch move.
The question of having tickets on both or not is interesting indeed... Is there a convention that most projects follow ?