I think it's time for AGPL
Forum rules
This forum houses many years of development, tracing back to some of the earliest posts that exist on the board.
Its current use is for the continued development of the server and game it has always served: TMW Classic.
I think it's time for AGPL
Recently, this issue has come up again: it is perfectly legal for someone to take TMW's server code and content, modify them, and run a public server without releasing their changes, because users do not actually receive the server, the only talk to it over the network.
This exact problem is the reason that the AGPL was created: http://www.gnu.org/licenses/agpl-3.0.html
Therefore, I propose that new work on TMWA be licensed under the AGPL. This is an explicitly permitted use of the license.
This exact problem is the reason that the AGPL was created: http://www.gnu.org/licenses/agpl-3.0.html
Therefore, I propose that new work on TMWA be licensed under the AGPL. This is an explicitly permitted use of the license.
Former programmer for the TMWA server.
Re: I think it's time for AGPL
Disadvantange of AGPL what you must publish all. If scripts AGPL too and exists some event with secret questions, it must be public too.o11c wrote:Recently, this issue has come up again: it is perfectly legal for someone to take TMW's server code and content, modify them, and run a public server without releasing their changes, because users do not actually receive the server, the only talk to it over the network.
This exact problem is the reason that the AGPL was created: http://www.gnu.org/licenses/agpl-3.0.html
Therefore, I propose that new work on TMWA be licensed under the AGPL. This is an explicitly permitted use of the license.
Also for server code to change license need ask all contributors, this mean all people from old eathena, and all who contributed to tmw server code.
Re: I think it's time for AGPL
GNU Affero General Public License (AGPL) version 3 wrote:This is a free software, copyleft license. Its terms effectively consist of the terms of GPLv3, with an additional paragraph in section 13 to allow users who interact with the licensed software over a network to receive the source for that program. We recommend that developers consider using the GNU AGPL for any software which will commonly be run over a network.
Please note that the GNU AGPL is not compatible with GPLv2. It is also technically not compatible with GPLv3 in a strict sense: you cannot take code released under the GNU AGPL and convey or modify it however you like under the terms of GPLv3, or vice versa. However, you are allowed to combine separate modules or source files released under both of those licenses in a single project, which will provide many programmers with all the permission they need to make the programs they want. See section 13 of both licenses for details.
"The language of everyday life is clogged with sentiment, and the science of human nature has not advanced so far that we can describe individual sentiment in a clear way." Lancelot Hogben, Mathematics for the Million.
“There are two motives for reading a book; one, that you enjoy it; the other, that you can boast about it.” Bertrand Russell, Conquest of Happiness.
"If you optimize everything, you will always be unhappy." Donald Knuth.
“There are two motives for reading a book; one, that you enjoy it; the other, that you can boast about it.” Bertrand Russell, Conquest of Happiness.
"If you optimize everything, you will always be unhappy." Donald Knuth.
Re: I think it's time for AGPL
That's acceptable if it comes to that, but I'm not sure if we actually need to.4144 wrote:Disadvantange of AGPL what you must publish all. If scripts AGPL too and exists some event with secret questions, it must be public too.
No, it is explicitly permitted to link AGPL and GPL code into one executable ...4144 wrote:Also for server code to change license need ask all contributors, this mean all people from old eathena, and all who contributed to tmw server code.
... and I have written enough brand new files in TMWA that I can relicense them.AGPL wrote: Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the work with which it is combined will remain governed by version 3 of the GNU General Public License.
TMWA is already GPL3+ (because it was previously GPL2+), so this is not an issue.Nard wrote:GNU Affero General Public License (AGPL) version 3 wrote:Please note that the GNU AGPL is not compatible with GPLv2. It is also technically not compatible with GPLv3 in a strict sense: you cannot take code released under the GNU AGPL and convey or modify it however you like under the terms of GPLv3, or vice versa.
Former programmer for the TMWA server.
Re: I think it's time for AGPL
If link at same time AGPL and GPL look like it works like GPL, this mean all AGPL additions removed or not?o11c wrote:No, it is explicitly permitted to link AGPL and GPL code into one executable ...4144 wrote:Also for server code to change license need ask all contributors, this mean all people from old eathena, and all who contributed to tmw server code.
http://en.wikipedia.org/wiki/Affero_Gen ... th_the_GPL
Re: I think it's time for AGPL
GPL and AGPL are incompatible. You can't take a work licensed under GPL and turn it into a AGPL project. So when you want an AGPL client- or server you need to rewrite from scratch. Unless, of course, you get the permission from all past contributors (and you won't get mine).
- former Manasource Programmer
- former TMW Pixel artist
- NOT a game master
Please do not send me any inquiries regarding player accounts on TMW.
You might have heard a certain rumor about me. This rumor is completely false. You might also have heard the other rumor about me. This rumor is 100% accurate.
Re: I think it's time for AGPL
I would not be doing that. I would be relicensing the code *I* wrote, which includes several complete files.Crush wrote:GPL and AGPL are incompatible. You can't take a work licensed under GPL and turn it into a AGPL project.
The boundary between GPL3 and AGPL3 licensed source is allowed to happen at file granularity.
Former programmer for the TMWA server.
Good idea
IMO this idea sounds nice: "usual" GPL does not really handles cases where someone takes source, modifies it, puts on their own server but never distributes server binaries. In this case they also do not have to distribute source. So GPL does not really works well for server software if you care about private installations (which is somethint to consider for MMORPGs, obviously). AGPL on other hand takes care about this case.
Btw, same issue applies to server-side files, etc. So AGPL could be interesting option to consider to encourage sharing instead of private forks with closed server code, scripts, etc. Sounds reasonable, if you can sort out issues about licenses compatibility, old code, etc.
Btw, same issue applies to server-side files, etc. So AGPL could be interesting option to consider to encourage sharing instead of private forks with closed server code, scripts, etc. Sounds reasonable, if you can sort out issues about licenses compatibility, old code, etc.
Re: I think it's time for AGPL
I'm in the minority here, but after some thought I'm actually completely ok with people running closed-source servers. I just wish there were some BSD-like accreditation clause.
My thinking here is that TMW and TMWA are under constant development. Rather than coding themselves into a corner it'd be in the best interest of competantly managed downstream projects to push the best changes they've made upstream. Even if they do not do this it's still good exposure for TMW in the end, as it's unlikely they will be writing their own client from scratch. Keeping it GPL will help encourage forks, and forks are good.
Also, haven't we had enough licencing issues already?
My thinking here is that TMW and TMWA are under constant development. Rather than coding themselves into a corner it'd be in the best interest of competantly managed downstream projects to push the best changes they've made upstream. Even if they do not do this it's still good exposure for TMW in the end, as it's unlikely they will be writing their own client from scratch. Keeping it GPL will help encourage forks, and forks are good.
Also, haven't we had enough licencing issues already?
Head of the TMW Illuminati
- wushin
- TMW Adviser
- Posts: 1759
- Joined: 18 Dec 2012, 05:56
- Location: RiverBest, Brew City, Merica
- Contact:
Re: I think it's time for AGPL
well it would make everyone have to post their changes. which it would be nice to see what other forks are doing so we don't step on each others toes.
AGPL sounds even a bit more share and share alike. I can see how this would keep all of us more honest.
AGPL sounds even a bit more share and share alike. I can see how this would keep all of us more honest.
The secret to getting all the important stuff done is doing nothing.