Re: SVG style and contributing barrier to entry

2020-04-19 Thread lilypond . wayne
> LilyPond […] is a community-driven process where there’s no > distinction whatsoever between users and contributors […] > (In this regard however, Patrice’s referring to messages from the bug > list as `spam’ does make me feel a bit uncomfortable.) By “spam” I thought it was clear from the

Re: SVG style and contributing barrier to entry

2020-04-19 Thread Valentin Villenave
On 4/16/20, Werner LEMBERG wrote: > Well, you just *did* submit a patch, and I'm going it to apply soon. Indeed; initiating, or taking part in, discussions on some of our mailing lists (or forums) is a pretty easily-achievable first step. LilyPond (like most Free Software projects, and perhaps

Re: SVG style and contributing barrier to entry

2020-04-16 Thread Werner LEMBERG
> In any case, I'm subscribed so I'll cross-post and CC James so > that the patch (which looks correct to me) is not lost. I've just applied it to staging. Werner

Re: SVG style and contributing barrier to entry

2020-04-16 Thread Werner LEMBERG
> I just discovered that the “style” tag created inside svg output > uses the wrong syntax, [...] > > A trivial one-line patch to fix this (based on git master): [...] Thanks. > Wanting to submit this patch, I've looked at the LilyPond > Contributor's guide¹, and frankly, I'm amazed by the

Re: SVG style and contributing barrier to entry

2020-04-16 Thread Patrice Levesque
> I'll cross-post and CC James so that the patch (which looks correct to > me) is not lost. Thank you very much. Cheers, -- · Patrice Levesque · http://ptaff.ca/ · lilypond.wa...@ptaff.ca -- signature.asc Description: Digital signature

Re: SVG style and contributing barrier to entry

2020-04-16 Thread Jonas Hahnfeld
Am Donnerstag, den 16.04.2020, 05:00 -0400 schrieb Patrice Levesque: > Hi! > > I just discovered that the “style” tag created inside svg output uses the > wrong syntax, e.g. > >

SVG style and contributing barrier to entry

2020-04-16 Thread Patrice Levesque
Hi! I just discovered that the “style” tag created inside svg output uses the wrong syntax, e.g. ```