[Fyren]

The discussion with caesium brought this up, but I'd like to ask just to be totally explicit. As far as the developers are concerned, since SM is GPL'd, the fact that plugins use the SM API means that plugins are derivative works and so must be licensed under the GPL or are infringing upon the SM copyright? (This is assuming it's impossible to write code that would be considered a "SM plugin" without using something from the API SM provides.)

[msleeper]

http://forums.alliedmods.net/showthr...t=57142&page=2

FlyingMongoose's response at the bottom of the page answers this I think, though I'm not sure how official that may be.

[pRED*]

The GPL v3 no longer uses the term 'derivative work', but instead 'work based upon'.

So yes, plugins must be released under GPL v3.

[BAILOPAN]

Indeed, and I'm glad we chose the GPL3 on those grounds alone. "Derivative works" was confusing. "Works based on" is clear-cut, it's hard to argue plugins are not based on their host, even if they manage to not use the supplied headers.

(The reason behind the choice of the GPL at all is an entirely different discussion, but I don't think it's really been a problem.)

[bl4nk]

It's pretty simple. If you're giving out your plugin, you HAVE to give the source with it as well. You are allowed to sell your plugins to other people, but they have every right to hand it out to anybody they like once you've given it to them.