If Gmail proved anything, it was that people would, for the most part, accept any terms of service. Or at least not care enough to read the fine-print closely.
gpl does not prevent the owner from changing the licence later. (Unless it is also making use of someone else’s gpl components.)
For example, Qt has a free version which is under the GPL; and a paid version which is not. So if you were making software with Qt, if you were using the free version, you’d be compelled to also release your product under GPL. But you could then later switch to a paid subscription and rerelease under some other licience if you wanted to.
Not if the copyright owner changes the license. When you are the creator you can do what you please. With that being said you can not do that if the public writes code. That’s why you see CLAs (contributor license agreement)
gpl prevents you from doing that fyi
gpl does not prevent the owner from changing the licence later. (Unless it is also making use of someone else’s gpl components.)
For example, Qt has a free version which is under the GPL; and a paid version which is not. So if you were making software with Qt, if you were using the free version, you’d be compelled to also release your product under GPL. But you could then later switch to a paid subscription and rerelease under some other licience if you wanted to.
Actually it doesn’t
doesnt it require any modified versions of the code be shared, preventing a change to a non-copyleft liscence?
Not if the copyright owner changes the license. When you are the creator you can do what you please. With that being said you can not do that if the public writes code. That’s why you see CLAs (contributor license agreement)