Actually that's really what licenses are about. The day someone forks Joplin and creates a closed-source version of it, it will be too late to do something about the license.
I can agree that the chance of someone doing that is relatively low, but the cost of changing the license is also low (or at least that's what we're trying to establish here), so it seems like an acceptable thing to do.
But for example when someone created a commercial service based on Joplin Server, while it was still MIT (and well before Joplin Cloud was ready), it took me by surprise, so we can't always predict what's going to happen.
2 Likes
