Skip to content

[2018.10.9] Bi weekly Call

Jump to bottom
Stephan Hesse edited this page Nov 7, 2018 · 1 revision

Participants: John Bartos (JW), Rob Walch (JW), Fred, Michael Cunningham (Redspace), Stephan (Emliri), Oren (Kaltura)

Topics: Roadmap, current painpoints, rally around open issues, allocate resources where needed

Capacities? John has little availability atm, has some issues that need reviewing, help needed for that

John: Low-latency proposal, RFC proposal, LHLS proposal should gain more traction

Goals for today:

Stephan: Improve project organization, define milestones, determine common targets for releases, help collaboration

Rob: Create contributor guideline, Reboot process of collaborating, Specific things can be delivered in a fork, but it is important to contrib features back to upstream Is there a roadmap existing? Proposed process: Focus on specific features and release these as specific patch versions

Use project tool: Trello? Github?

Can we apply a process to determine what are the milestones

Where are we right now has to be determined. Looking at PRs already merged in this iteration.

Oren: Restrict scope of tickets/PRs. For example LHLS is a longer-term feature containing many smaller tasks. Not like a bug-fix. Maybe have a patch version every week? Every month a feature release. Major release? Oren: Need to consume from upstream releases, not using a fork

Discussion about Mocha HTML test runner.

Rob: Can there be issues we don't see in Karma but that come up in the regular webpack build(s)? Risk has to be considered.

Define scopes for 0.11.1 and 0.11.2 ->

Fred: Would like to contribute more, need for well-defined milestones, mostly concerned with live-streams

John: Memory-limitation per player in Chrome, related to multiple players on same page, could be an interesting topic to work on for Fred to get started with reviews (https://github.com/video-dev/hls.js/pull/1845)

Michael: Follows the project since long time. Would like to do more PR reviews.

Handling of discontinuities within same fragment or TS (without playlist discont tag) should not be necessary to handle

Descope tooling? Subtitle PRs can be removed from 0.11.1 scope

Actionables:

  • Look at various long-running issues/PRs (John/Fred)
  • Move functional testing to Browserstack (Stephan)
  • Get more into reviewing (Michael)
  • Progress on subtitle-stream-controller fixes for WebVTT (Oren/Stephan)
  • Re-define scopes for two next releases (eg. 0.11.1 and 0.11.2 or minor if API additions) (Rob/John/Oren/Stephan)
Clone this wiki locally