You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are no issues with cherry-picking commits to your fork, it's what open source and free software is about.
However, when doing so, you NEED to keep ownership and history. Indeed, the GPL (the license under which the code is in) grants copyright to each contributor for their code.
By breaking authorship, such as with this commit: 8081595 (Which is a copy of this Jellyfin commit: jellyfin/jellyfin@2c8592f ) you are essentially stealing the work of someone else and breaking their copyright.
In order to be GPL compliant, you need to properly cherry-pick whatever commits you wish to implement instead of redoing an identical commit with someone else's work.
There are no issues with cherry-picking commits to your fork, it's what open source and free software is about.
However, when doing so, you NEED to keep ownership and history. Indeed, the GPL (the license under which the code is in) grants copyright to each contributor for their code.
By breaking authorship, such as with this commit: 8081595 (Which is a copy of this Jellyfin commit: jellyfin/jellyfin@2c8592f ) you are essentially stealing the work of someone else and breaking their copyright.
In order to be GPL compliant, you need to properly cherry-pick whatever commits you wish to implement instead of redoing an identical commit with someone else's work.
If you need help, here's an article that explains what to do: https://www.previousnext.com.au/blog/intro-cherry-picking-git
The text was updated successfully, but these errors were encountered: