Substance license?


I had this in my ToDo for a long time and recently I found time to take a look.

I’m just scratching the surface of the JATS’ universe (very chaotic one, by the way) and me neither want to reinvent the wheel, so the obvious first step was looking inside the PKP ecosystem…

I tested Open Typesetting Stack and looks really promising (congrats to @axfelix for the huge work) but some basic features (ie: table and image conversion to JATS) are still buggy… Any case, this is not the question (yet :stuck_out_tongue: ), the point is that I finally arrive to the substance project (PKP is member of the consortium) and I found the code is under a free but non formal license:

Does any body know why this was not GPLed as everything else in PKP?

Thanks for your time,

MIT: The MIT License | Open Source Initiative

1 Like

Isn’t that MIT?

Edit. too slow :smiley:

1 Like

Thanks @ajnyga and @WaDelma. :ok_hand:

You both are right, it’s a MIT license… but why not using a GPL like everything else?

I mean, MIT is a compliant license and this is good, but a GPL or an Apache would be better for a project as big as substance, don’t you think?


Hi Marc,

I spoke to them about this some months ago – they asked us if we needed them to commit to GPL and we said no, that wasn’t a fair expectation, and they would be fine going with Apache / MIT / BSD. If you’d be satisfied with Apache as an alternative to GPL, mindful of the tradeoffs, then I don’t think you’ll find MIT to be too much different.

1 Like

MIT it’s free and GPL compliant so it’s good enough for me.
Just been curious about the rationale.

Thanks for the explanations.