search

AR-Development / PersistentEmpires-OpenSourced

GNU Affero General Public License v3.0
1 stars 15 forks source link

Changing Licence From AGPL to MIT #57

Closed mentalrob closed 1 month ago

mentalrob commented 2 months ago

AGPL is very restrictive about distributing the code and enforces if any type of dependency to the PE should be open sourced. Thus making it hard to monetize and compete with others.

MIT allows you to basically do anything, you can create your own closed source copies, distribute them and make money on them.

I don't want to change the licencing on my own but i want your opinions @ianespana @Heavybob @Snah79 @lenggiauit @ErraynGit

mentalrob commented 2 months ago 
PR Comments:

Heavy Bob Using the AGPL-3 means that anyone who makes edits and redistributes it must publish their source. I think that's a fairly reasonable proposition that ultimately benefits everyone. It doesn't infringe on the ability for people to monetize OR make sub modules that interact with the base code that are are air gapped from the source. This still allows modifications that work along side PE to exist and still protects the rights of developers who want to make their own thing and still interact with PE. I think changing to MIT will mean that less people will be obligated to share their source code and will ultimately mean less people will want to contribute to this code base. I think the existing AGPL-3 license is good because it encourages cooperation. MIT doesn't do that.

mentalrob commented 2 months ago

There is another way that we can still enforce AGPL but also protect who they don't want to opensource their code. The way is actually creating another licence addition to AGPL and distribute this licence with money or other ways

haliliceylan commented 2 months ago

I do not agree with converting to MIT, as there are many people who have contributed significantly to this project. If it makes sense, the team can provide an alternative license connected to Patreon. However, if no payment is made and no Patreon tier is selected, developers/server owner must comply with the APGL license.

By supporting the project on Patreon, they can access a special license that allows for closed-source usage. There can be different Patreon tiers for different plans, so you can choose the one that best fits your needs. This way, you help sustain the project while getting the flexibility you need for your proprietary applications.

Examples: Minio, MongoDB

Heavybob commented 2 months ago

Don't change the license. If you want to offer a patreon MIT license, sure.