Agenda for the call 5/14 (Yes, two weeks from now)

On the last call we've discussed alternatives to accelerate getting updated PR and eventually REC sooner rather than later and resolved on the following plan of action:


  *   Fork the current specification into "shipping" and "forward-looking" branches
  *   Focus "shipping" branch on getting to updated PR and REC by removing features at risk
  *   Unblock removing in the "shipping" branch at-risk features to use currently available status of the features and the implementation plans
  *   Do not require new feature tests for this determination, limit tests to basic feature detection and do not block removal on the tests for known at-risk features
  *   Focus test creation on the "shipping" branch new features (new in SVG 2.0 over SVG 1.1)
  *   Keep existing text and features in "forward-looking"
  *   (Optional) Update svgwg.org to have two links - SVG 2.0 shipping and forward-looking (SVG next?)

We believe this is the most pragmatic way to accelerate progress, while striking the balance between preserving existing work and getting to REC faster.

With this in mind we'd like to send (almost) two weeks in advance notice on the agenda to:


  *   discuss and confirm features at risk
  *   assign editors to do the changes.

The criteria we're planning to use didn't change - we need two implementations with at least one browser and one non-browser for every non-trivial change. The change is that we want to move faster on the actual editorial changes to allow more focused testing effort.

Please attend if you'd like to discuss any of the features at risk.

We hope to move fast on those changes, do a focused testing effort for the not-at-risk changes and push for an updated PR soon after that.

Thank you and hope to see you on the call!

P.S There is no change planned to the regular call scheduled on 5/7. As usual I'll try to send an agenda based on GitHub issues labelled with "Agenda+" on Thursday (5/3) before the call.