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
According to the GPL, every change in a forked project must be prominently tracked. For a project that exists only as source on GItHub, this is probably OK. However, any distribution of source code that doesn't include the full git history is out of compliance, unless we include some other file which lists the changes to be included in the distribution.
A ChangeLog.txt generated by "git log" is probably sufficient.
The text was updated successfully, but these errors were encountered:
franc6
added
the
GPL Compliance
Code that must be replaced, or files that must be modified/created in order to fully comply with GPL
label
Feb 8, 2019
According to the GPL, every change in a forked project must be prominently tracked. For a project that exists only as source on GItHub, this is probably OK. However, any distribution of source code that doesn't include the full git history is out of compliance, unless we include some other file which lists the changes to be included in the distribution.
A ChangeLog.txt generated by "git log" is probably sufficient.
The text was updated successfully, but these errors were encountered: