Skip to content

Add practical license compliance guide - #1358

Open
Tarekchehahde wants to merge 1 commit into
github:gh-pagesfrom
Tarekchehahde:fix/compliance-requirements-646
Open

Tarekchehahde wants to merge 1 commit into
github:gh-pagesfrom
Tarekchehahde:fix/compliance-requirements-646

Conversation

@Tarekchehahde

Copy link
Copy Markdown

Summary

  • Adds /compliance/ with practical checklists grouped by license rule types (include-copyright, disclose-source, same-license, network-use-disclose, document-changes).
  • Includes a not-legal-advice disclaimer and links from the site footer.

Fixes #646

Test plan

  • Verify /compliance/ renders with checklists
  • Confirm footer Compliance link works
  • Spot-check links to license pages and related guides

Made with Cursor

Fixes github#646. Checklists for common license condition rule types.

Co-authored-by: Cursor <cursoragent@cursor.com>
Comment thread compliance.md

- [ ] Keep original copyright headers in source files you redistribute.
- [ ] Include the full license text in source distributions (for example, a `LICENSE` file in the repo or release tarball).
- [ ] For **binary** or app store releases, provide notices in an **About**, **Legal**, or **Third-party notices** screen or file, as required by the license.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would be useful to provide an example screenshots of what these disclosures look like as well as what a third-party notice file looks like.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add information on compliance requirements

2 participants