Closed garciagenrique closed 2 months ago
A permissive free software license should be used (Apache License 2.0 seems a good choice)
A permissive free software license should be used (Apache License 2.0 seems a good choice)
Any scenario in where a copyleft license could be useful or needed ?
Also, are you familiarised with the re-licensing of a repository / project ? Please investigate under which circumstances this can be done and by whom.
Any scenario in where a copyleft license could be useful or needed ?
Permissive permits proprietary derivative works. If we want our project to be 100% free (and guarantee that anyone who uses this code to make their code open), we may use a copyleft license (e.g., GNU GPL).
Also, are you familiarised with the re-licensing of a repository / project ? Please investigate under which circumstances this can be done and by whom.
It depends on the original license and the final license. The original license of the extension template is BSD (permissive), so it could be done. With copyleft licenses this would be more difficult. In addition, when we use the copier
command in the tutorial, it creates the license with the "extension author name" (me), so I think I can modify the license.
It depends on the original license and the final license. The original license of the extension template is BSD (permissive), so it could be done. With copyleft licenses this would be more difficult. In addition, when we use the
copier
command in the tutorial, it creates the license with the "extension author name" (me), so I think I can modify the license.
In general, as far as the author + the maintainer and active collaborators agreed, a relicense can be performed under any situation.
Apache 2.0 is a very good choice, but I wanted you to go through the process of thinking about the different possibilities. Well Done @rubenperezm !
After having investigated and getting familiarised with