Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Standardize license headers in Python files #114

Merged
merged 2 commits into from
Jan 15, 2025
Merged

Conversation

pderrenger
Copy link
Member

@pderrenger pderrenger commented Jan 15, 2025

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

Added licensing information to multiple Python scripts in the JSON2YOLO repository to ensure compliance and clarity on usage rights.

📊 Key Changes

  • Inserted the Ultralytics AGPL-3.0 license header at the top of the following files:
    • general_json2yolo.py
    • labelbox_json2yolo.py
    • utils.py

🎯 Purpose & Impact

  • 🛡 Clarity on Licensing: Clearly specifies the repository's licensing terms, ensuring users understand the legal framework for using and distributing the code.
  • ✅ Compliance: Aligns with open-source best practices by prominently including the license in all source files.
  • 📢 Transparency: Helps users and contributors quickly identify the license type, fostering better collaboration and adherence to usage rights.

@UltralyticsAssistant UltralyticsAssistant added the documentation Improvements or additions to documentation label Jan 15, 2025
@UltralyticsAssistant
Copy link
Member

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

  • Define a Purpose: Clearly explain the purpose of your changes 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/JSON2YOLO 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. As Bruce Lee said, "It is not daily increase but daily decrease, hack away the unessential." 🎯

🛠 Need Assistance?

If your changes involve a bug fix or unexpected behavior, please provide a Minimum Reproducible Example (MRE) or steps to reproduce the issue. This helps us expedite the verification and review process.

For more guidance, please refer to our Contributing Guide.

🚀 Your contribution improves the JSON2YOLO project for everyone. Thank you for your hard work and dedication. An Ultralytics engineer will assist with your PR soon! 😊

@pderrenger pderrenger merged commit 9aa4595 into main Jan 15, 2025
2 checks passed
@pderrenger pderrenger deleted the refactor-20250115140854 branch January 15, 2025 13:13
@UltralyticsAssistant
Copy link
Member

🎉 Exciting news: The PR is now merged! Thank you, @pderrenger, for your hard work and @glenn-jocher for your thoughtful contributions. By adding clear and prominent licensing to the JSON2YOLO repository, you've both taken an important step toward fostering transparency, trust, and collaboration in the open-source world. 🌐✨

As Marcus Aurelius once said, "What we do now echoes in eternity." Your efforts here not only set a standard for clarity and compliance but also empower the greater community to build and create with confidence.

Here's to building a brighter, more open future—one contribution at a time! 🚀❤️

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.

3 participants