Skip to content

Add License section to README - #79

Merged
glenn-jocher merged 2 commits into
mainfrom
readme-branding-pass2
Aug 2, 2026
Merged

Add License section to README#79
glenn-jocher merged 2 commits into
mainfrom
readme-branding-pass2

Conversation

@glenn-jocher

@glenn-jocher glenn-jocher commented Aug 2, 2026

Copy link
Copy Markdown
Member

This repo ships an AGPL-3.0 LICENSE file, but the README never mentioned or linked it. Added the canonical two-option ## 📄 License section between Feedback and Contributions and Contact, matching the section order used across Ultralytics repos.

Note: LICENSE and README.md are this repo's own files and are not inherited as org-wide defaults, so this changes nothing for other repositories.

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

📄 Adds clear licensing information to the .github repository README.

📊 Key Changes

🎯 Purpose & Impact

  • ✅ Makes the repository’s licensing terms easier to find and understand.
  • ⚖️ Helps users distinguish between the open-source AGPL-3.0 license and commercial licensing options.
  • 🤝 Improves transparency for developers and organizations evaluating Ultralytics projects for personal, open-source, or commercial use.

@UltralyticsAssistant UltralyticsAssistant added the documentation Improvements or additions to documentation label Aug 2, 2026
@UltralyticsAssistant

Copy link
Copy Markdown
Member

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/.github 🚀 PR! This is an automated review message, and an engineer will assist with any questions. To ensure a seamless integration of your work, please review the following checklist:

  • Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
  • Synchronize with Source: Confirm your PR is synchronized with the ultralytics/.github main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
  • Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
  • Update Documentation: Update the relevant documentation for any new or modified features.
  • Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
  • Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
  • Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee
    For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

@UltralyticsAssistant UltralyticsAssistant left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

🔍 PR Review

Made with ❤️ by Ultralytics Actions

The new section is well placed and links the repository license, but it conflates this .github repository's AGPL-3.0 license with the separate Enterprise licensing terms for Ultralytics software and models.

💬 Posted 1 inline comment

Comment thread README.md Outdated

## 📄 License

Ultralytics offers two licensing options to accommodate diverse needs:

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

💡 MEDIUM: This repository contains only community-health resources, and its LICENSE is the AGPL-3.0 license for those repository contents. Presenting it as a two-option license suggests that an Enterprise License also governs this repository, but the linked Enterprise terms cover Ultralytics software/models instead. Please scope this section to the .github repository's AGPL-3.0 license (or remove the Enterprise option) to avoid giving contributors incorrect licensing guidance.

@glenn-jocher

Copy link
Copy Markdown
Member Author

Addressed the review finding in aad0466: the section no longer presents a two-option license for this repository. It now states plainly that this repo's contents are AGPL-3.0, and mentions the Enterprise License only as separately covering Ultralytics software and AI models.

@glenn-jocher
glenn-jocher merged commit fcc2837 into main Aug 2, 2026
4 checks passed
@glenn-jocher
glenn-jocher deleted the readme-branding-pass2 branch August 2, 2026 19:00
@UltralyticsAssistant

Copy link
Copy Markdown
Member

🎉 Thank you, @glenn-jocher, for this valuable contribution!

“Honesty is the first chapter in the book of wisdom.” — Thomas Jefferson

Adding clear AGPL-3.0 and Enterprise License information makes the .github repository more transparent and helps developers and organizations understand their licensing options. This is a meaningful improvement for the Ultralytics community—thank you for helping make our projects easier to evaluate and use responsibly!

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

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants