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
I would really like to use some of the code in the dump repository for free software projects, particularly the code in "how-to-receive-a-packet".
Closed issue #1 has relevant information, as well as pull request 16. In PR 16 you state, "Code that are reused from somwhere are... well under some license. Code authored by me are either "public domain" or MIT. When in doubt use MIT as suggested in issue 1" I think that this is difficult for users to find. It also does not propagate to forks of the repository.
I can't tell whether code in a particular directory is written by you or not, as I don't see statements in the files crediting the author of the code.
As an example of why an obvious license statement is important, user unixlab has forked the code in "how-to-receive-a-packet", but unixlab's code has no license statement. unixlab probably didn't know what license to apply to it. I was about to use the code, checked the license and found myself unable to use it without knowing what license terms to announce and comply with for my fork of the code.
Thanks for your contributions to free software and the computing industry.
The text was updated successfully, but these errors were encountered:
Norse-Harold
changed the title
No license statement
License statement - not easily found and incomplete
Dec 23, 2023
Norse-Harold
changed the title
License statement - not easily found and incomplete
License statement - incomplete and difficult to find
Dec 23, 2023
Hello,
I would really like to use some of the code in the dump repository for free software projects, particularly the code in "how-to-receive-a-packet".
Closed issue #1 has relevant information, as well as pull request 16. In PR 16 you state, "Code that are reused from somwhere are... well under some license. Code authored by me are either "public domain" or MIT. When in doubt use MIT as suggested in issue 1" I think that this is difficult for users to find. It also does not propagate to forks of the repository.
I can't tell whether code in a particular directory is written by you or not, as I don't see statements in the files crediting the author of the code.
As an example of why an obvious license statement is important, user unixlab has forked the code in "how-to-receive-a-packet", but unixlab's code has no license statement. unixlab probably didn't know what license to apply to it. I was about to use the code, checked the license and found myself unable to use it without knowing what license terms to announce and comply with for my fork of the code.
Thanks for your contributions to free software and the computing industry.
The text was updated successfully, but these errors were encountered: