on master help sign in
Add licensing guidelines
2e0a445Harendra Kumar
CONTRIBUTING.md+10
@@ -56,6 +56,8 @@ Here is a quick checklist for a PR, for details please see the next section:
56* Tutorial module, [README](README.md), and [guides](docs) are updated if
56* Tutorial module, [README](README.md), and [guides](docs) are updated if
57 necessary.
57 necessary.
58* [Changelog](Changelog.md) is updated if needed
58* [Changelog](Changelog.md) is updated if needed
59+* The code conforms to the license, it is not stolen, credit is given,
60+ copyright notices are retained, original license is included if needed.
59
61
60### Structuring Pull Requests
62### Structuring Pull Requests
61
63
@@ -170,6 +172,14 @@ of the library please indicate that in the `Changelog` as `Breaking Changes`
170and also write short notes regarding what the programmers need to do to adapt
172and also write short notes regarding what the programmers need to do to adapt
171their existing code to the new change.
173their existing code to the new change.
172
174
175+### Licensing
176+
177+If you have copied code from elsewhere you need to conform to the
178+licensing terms of the original code. Usually you would need to add a
179+copyright notice in the source header, and include the license of the
180+original code as per the terms of the license. If the code you are
181+copying does not have an associated license please do not use it.
182+
173## Developer documentation
183## Developer documentation
174
184
175To build haddock documentation for all modules, including the ones not exposed
185To build haddock documentation for all modules, including the ones not exposed