Standardize license headers in Python files

[pderrenger]

This PR updates all Python file headers to use a standardized license format. 🔄

Changes:

• 📝 Standardized header: # Ultralytics 🚀 AGPL-3.0 License - https://ultralytics.com/license
• 🧹 Ensures consistent spacing after headers
• 🔍 Applies to all Python files except those in venv

Learn more about Ultralytics licensing 📚

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Minor updates to contribution documentation links for better navigation.

📊 Key Changes

• Updated URLs in the contribution guidelines to include trailing slashes (/) for consistency and improved navigation.

🎯 Purpose & Impact

• 🖇️ Improved User Experience: The adjusted URLs help avoid potential navigation issues and ensure smoother access to linked pages.
• 📚 Clarity & Consistency: Enhances the accessibility and professionalism of the documentation for contributors.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
handbook	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jan 15, 2025 1:16pm

[UltralyticsAssistant]

👋 Hello @pderrenger, thank you for submitting an ultralytics/handbook 🚀 PR! To ensure a smooth integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your changes in your PR description, linking any relevant issues where applicable. Ensure your commit messages are concise and follow the project's conventions.
• ✅ Synchronize with Source: Confirm your branch is up-to-date with the ultralytics/handbook main branch. If you need to pull the latest changes, click the 'Update branch' button or run git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify that all Continuous Integration (CI) checks have passed. If any checks fail, take time to resolve the issues.
• ✅ Update Documentation: Confirm you’ve updated any relevant documentation if your changes impact the user experience.
• ✅ Add Tests: If applicable, ensure your modifications include or update corresponding tests, and verify that all tests are successful.
• ✅ Sign the CLA: If this is your first PR, make sure to sign our Contributor License Agreement (CLA) by stating "I have read the CLA Document and I sign the CLA" in a comment below.
• ✅ Minimize Changes: Ensure your PR is focused on the minimum necessary updates to achieve the intended purpose. "Perfection is achieved not when there is nothing more to add, but when there is nothing left to take away." — Antoine de Saint-Exupéry

For additional guidance, please refer to our Contributing Guide. If you have questions, feel free to leave a comment, and an Ultralytics engineer will help you shortly. This is an automated response 🤖, but a team member will review and assist soon. Thank you for contributing to Ultralytics! 🎉

---

ℹ️ Summary of Your PR

Your updates to standardize license headers across Python files are much appreciated! 📝 Thank you for ensuring consistent and clear licensing information in the codebase.

Please make sure:

• Your PR description clearly outlines the scope and goal of the changes.
• You double-check CI status after pushing changes to ensure a green checkmark! ✅

Learn more about Ultralytics licensing 📚

Looking forward to your great contributions! 🙌

[UltralyticsAssistant]

✨ PR merged! Huge thanks to @pderrenger for the thoughtful updates and to @glenn-jocher for the collaborative support. These tweaks to the contribution docs ensure a smoother journey for future contributors—impacting navigation, clarity, and user experience in meaningful ways. 🌟

As Leonardo da Vinci once said, “Simplicity is the ultimate sophistication.” These small yet deliberate changes exemplify how thoughtful details can elevate the experience for everyone. Your work truly makes a difference—thank you! 🙌 🚀