[Reelin]

This is all really disappointing - they ought to mention it up front in their FAQ. I hope they (or someone else) submits a v3 with tighter definitions that can close the SaaS proprietary source code loophole without introducing a compromising level of overreach or ambiguity.

> the fact that they haven't switched over by now signals to me that they're not yet confident in the newer version of the license; if they're not, I can't say I am either.

Agreed; I wouldn't want to make use of it either until the dust is well settled.

[bradrydzewski]

I recommend taking a look at the API Copyleft License https://github.com/kemitchell/api-copyleft-license/blob/mast...

[karmakaze]

> overreach or ambiguity

Specifically overreach ambiguity and as mentioned compatibility with other popular copyleft licenses are valid reasons for me.

It seems reasonable for anyone that cares to switch to AGPL now and to an compatible stronger successor, perhaps SSPLv2 but it will take a bit of time. It's great that some are starting to test this.

Remember when there was a ban on any type of open source? We now have to take another step to the left together. The only ones that would truly miss out are the ones serving proprietized and not just using community software.