Re: Agenda for the call on 5/7

Minutes for this week's call: https://www.w3.org/2018/05/07-svg-minutes.html

And a reminder to all working group members, particularly implementation
teams, that next week's call is about reviewing features at risk to decide
what to remove from SVG Level 2.

If you can't be on the telcon, it would help to send an email listing which
features are in progress or "intent to implement", but aren't shipping yet.

~ABR

On 3 May 2018 at 17:42, Bogdan Brinza <bbrinza@microsoft.com> wrote:

> Hello,
>
>
>
> Below is the list of GitHub issues labelled with “Agenda+” we hope to
> discuss on the call next Monday:
>
>
>
>    - Clarify hit testing behavior of <foreignObject>:
>    https://github.com/w3c/svgwg/issues/427
>    <https://github.com/w3c/svgwg/issues/427>
>    - Do we really need not to reflect additional enum values in SVG 2:
>    https://github.com/w3c/svgwg/issues/424
>    <https://github.com/w3c/svgwg/issues/424>
>    - What should happen if you try to set an out of range value on an
>    enum in the DOM: https://github.com/w3c/svgwg/issues/423
>    - Clarify relation of isPointInFill and pointer-events:
>    https://github.com/w3c/svgwg/issues/416
>    <https://github.com/w3c/svgwg/issues/416>
>    - dur attribute should permit leading .: https://github.com/w3c/svgwg/
>    issues/394
>
>
>
> Hope to see everybody on the call!
>
>
>
> I’ll use this opportunity to remind about the next call after that and
> reiterate the plan to discuss and remove features at risk. Please see
> attached message sent earlier.
>
>
> ---------- Forwarded message ----------
> From: Bogdan Brinza <bbrinza@microsoft.com>
> To: www-svg <www-svg@w3.org>
> Cc:
> Bcc:
> Date: Tue, 1 May 2018 23:01:29 +0000
> Subject: 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.
>
>