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
Many places will not even consider using modules that do not include a clear & easy to find license and the standard practice is to have a file in the root directory of the project called either LICENSE or COPYING.
Ideally you would have a permissive license such as MIT, etc., but without such a file it is impossible to tell what your intended license conditions are. Many companies are reluctant to use GPL/LGPL code but some packages are dual licensed.
Ideally also including a brief license statement in the Docs (ideally near to the start of the first page).
The text was updated successfully, but these errors were encountered:
Many places will not even consider using modules that do not include a clear & easy to find license and the standard practice is to have a file in the root directory of the project called either LICENSE or COPYING.
Ideally you would have a permissive license such as MIT, etc., but without such a file it is impossible to tell what your intended license conditions are. Many companies are reluctant to use GPL/LGPL code but some packages are dual licensed.
Ideally also including a brief license statement in the Docs (ideally near to the start of the first page).
The text was updated successfully, but these errors were encountered: