search

phuse-org / E2E-OS-Guidance

Collaboration area for PHUSE End-to-End Open-Source Guidance
https://phuse-org.github.io/E2E-OS-Guidance/
MIT License
7 stars 3 forks source link

Example clarification #15

Open TKQT opened 1 year ago

TKQT commented 1 year ago

https://github.com/phuse-org/E2E-OS-Guidance/blob/0891e63f439b09c84963c00890fa04962e793a3c/releasing.qmd#L55

I think this example needs more details. It writes "This function exists in another GPL-3 copy left licenced project" - does that imply that the project which copies the function and then goes open-source at a later point in time will also be released under GPLv3?

If that is the assumption, then they are not necessarily in the wrong as per my understanding (is the original project attributed and referenced explicitly?): https://fossa.com/blog/open-source-software-licenses-101-gpl-v3/ image

On the other hand, releasing the project, including a piece of code under GPLv3 and then marking the project as MIT would be an infringement, seeing as MIT is less strict than GPLv3 about permissions.

epijim commented 1 year ago

Thanks @TKQT, this is a great point. Would #25 be on track to tidy this up?

epijim commented 1 year ago

direct link to diff: https://github.com/phuse-org/E2E-OS-Guidance/pull/25/files