@federicomena
If the W3C flattens (i.e. destroys) document SVG; then Inkscape will have no choice but to fork the standard.

The domination by Browsers and what they choose or fail to implement is a serious problem. That no SVG creators were involved in this discussion is damning and furthers the rift between SVG as a document standard and SVG as a CSS add-on.

Thanks for the at FMQ. 👍

@federicomena You can subscribe to the github repository issues.
github.com/w3c/svgwg/issues

There's also the public email list, www-svg@w3.org, but the only messages it gets most months are automated github issue summaries:
lists.w3.org/Archives/Public/

If you're interested in committing more time & energy you could apply to be an invited expert on the SVG working group.

But really, the reason for this one-off session was that all productive discussions on SVG standardization has stalled.

@doctormo

Issues · w3c/svgwg

SVG Working Group specifications. Contribute to w3c/svgwg development by creating an account on GitHub.

^GitHub

@doctormo Thanks, maybe indeed I should pay more attention to the repo's issues. I have looked at some of them in the past, but haven't really had anything to contribute.

My personal interest is in clarifying some things in the spec - but I'd have to trawl through librsvg's bug tracker to find places where we mention such things :)

(Also getting one or two features finalized, so librsvg can have parity with Inkscape - gradient meshes come to mind.)

@federicomena @doctormo It would certainly be helpful if you could file issues against the SVG spec whenever you run up against something that is unspecified, unclear, inconsistent, or just plain wrong.

However, do be aware that for a few years there really hasn't been anyone doing anything with those issues & it might be a while yet before that changes.

Also, apparently the build system is broken & editorial fixes that have been merged in the repo aren't showing up even on the Editor's Draft.

@federicomena @doctormo And to be clear, spec issues would still be useful despite all that because:

They provide a record for whenever someone is working on it again.

They provide evidence that there is still a demand for a better SVG spec, from devs working on all sorts of projects.

Not ideal, no, but yeah, if you have the time to at least post cross-links to your own bug tracker, it will hopefully make a difference eventually.