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

Update LICENSE to AGPL-3.0 #3

Merged
merged 1 commit into from
May 2, 2023
Merged

Update LICENSE to AGPL-3.0 #3

merged 1 commit into from
May 2, 2023

Conversation

glenn-jocher
Copy link
Member

@glenn-jocher glenn-jocher commented May 2, 2023

This pull request updates the license of the YOLOv8 project from GNU General Public License v3.0 (GPL-3.0) to GNU Affero General Public License v3.0 (AGPL-3.0).

We at Ultralytics have decided to make this change in order to better protect our intellectual property and ensure that any larger work that incorporates YOLOv8 and is provided as a service over a network will also be open-sourced under AGPL-3.0.

AGPL-3.0 is very similar to GPL-3.0, but with an additional clause to address the use of software over a network. This change ensures that if someone uses YOLOv8 as part of a larger work and provides that larger work as a service over a network (e.g., through a web application or API), they must make the source code of the larger work, including any YOLOv8 modifications, available to users of the service under the AGPL-3.0 license.

This update includes the following changes:

  • Replace the LICENSE file with the AGPL-3.0 license text
  • Update the license reference in the README.md file
  • Update the license headers in source code files

We believe that this change will promote a more collaborative environment and help drive further innovation within the YOLOv8 community.

copilot:all

🛠️ PR Summary

Made with ❤️ by Ultralytics Actions

🌟 Summary

Updated the project license from GNU General Public License v3 to the GNU Affero General Public License v3.

📊 Key Changes

  • Switched to the GNU Affero General Public License (AGPL) v3 from the GNU General Public License (GPL) v3.
  • Explicit integration with the community in the case of network server software is ensured.
  • Obligation for operators of network servers to provide the source code of the modified version.

🎯 Purpose & Impact

  • 🤝 Promotes cooperation by requiring that modifications of network server software be made available to the community.
  • 🔓 Enhances users' rights and freedom by ensuring access to the source code when interacting with the software over a network.
  • 🔧 Encourages societal and community benefits by compelling developers to share improvements to software.

This pull request updates the license of the YOLOv8 project from GNU General Public License v3.0 (GPL-3.0) to [GNU Affero General Public License v3.0](https://choosealicense.com/licenses/agpl-3.0/) (AGPL-3.0).

We at Ultralytics have decided to make this change in order to better protect our intellectual property and ensure that any larger work that incorporates YOLOv8 and is provided as a service over a network will also be open-sourced under AGPL-3.0.

AGPL-3.0 is very similar to GPL-3.0, but with an additional clause to address the use of software over a network. This change ensures that if someone uses YOLOv8 as part of a larger work and provides that larger work as a service over a network (e.g., through a web application or API), they must make the source code of the larger work, including any YOLOv8 modifications, available to users of the service under the AGPL-3.0 license.

This update includes the following changes:
- Replace the `LICENSE` file with the AGPL-3.0 license text
- Update the license reference in the `README.md` file
- Update the license headers in source code files

We believe that this change will promote a more collaborative environment and help drive further innovation within the YOLOv8 community.
@glenn-jocher glenn-jocher merged commit d99bbed into main May 2, 2023
@glenn-jocher glenn-jocher deleted the glenn-jocher-patch-1 branch May 2, 2023 16:29
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.

1 participant