Topic: website engine loicense

Posted under General

do you plan to keep the engine open source? will you make it agpl?

xruyi said:
do you plan to keep the engine open source? will you make it agpl?

The software we're using is e621ng, which has its own license, which already looks to be more permissive than GPL. It's not possible simple to change the existing license, so any work I produce on the project will remain licensed as it is now.

Personally I've always found GPL/AGPL to be far too restrictive.

I usually license my work with MIT whenever it's not possible to release it directly to the public domain.

I will set up a new repository in the coming days.

hinoserm said:
The software we're using is e621ng, which has its own license, which already looks to be more permissive than GPL. It's not possible simple to change the existing license, so any work I produce on the project will remain licensed as it is now.

Personally I've always found GPL/AGPL to be far too restrictive.

I usually license my work with MIT whenever it's not possible to release it directly to the public domain.

I will set up a new repository in the coming days.

my only concern is to have a license that makes it impossible to close the source, including forks