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

Remove all AGPL licensed YOLO references from Frigate #10716

Merged
merged 5 commits into from
Mar 30, 2024

Conversation

blakeblackshear
Copy link
Owner

I have been made aware by Ultralytics that Frigate is in violation of the AGPL-3.0 license because it is MIT licensed.

Some public discussion unrelated to Frigate is here.

This project cannot include any reference to models, code, or content that are AGPL-3.0 licensed from Ultralytics. In my understanding, this even includes novel code written to interface with their models that does not utilize any source code published by Ultralytics. Their position is that the models are not considered an output, but rather an extension of the source code published under AGPL-3.0.

At this time, I am not interested in changing the license to AGPL-3.0. Unfortunately, I believe this means that Frigate will never be able to support Ultralytics models published under this license even if I was to obtain an Enterprise License. This pains me as I am obviously a big fan of open source projects with a business model that enables them to be self sustaining.

Copy link

netlify bot commented Mar 28, 2024

Deploy Preview for frigate-docs canceled.

Name Link
🔨 Latest commit d569ee6
🔍 Latest deploy log https://app.netlify.com/sites/frigate-docs/deploys/66057dfb3900ef00082be63e

@blakeblackshear blakeblackshear changed the title Remove all YOLO8 references from Frigate Remove all AGPL licensed YOLO references from Frigate Mar 28, 2024
@NickM-27
Copy link
Collaborator

@MarcA711

@MarcA711
Copy link
Contributor

That's a pity. I will use YOLOX models from now on.
Btw, does YOLOX only allow an input size of 640x640 or is there a way to change that to e.g. 320x320 (without rebuilding the whole model)?

@NickM-27
Copy link
Collaborator

I don't personally know about that, but I do know that the 300x300 size of the openvino implementation has worked fairly well for users

@blakeblackshear blakeblackshear merged commit b65aa64 into master Mar 30, 2024
12 of 13 checks passed
@blakeblackshear blakeblackshear deleted the remove-yolov8-master branch March 30, 2024 10:44
Repository owner locked as resolved and limited conversation to collaborators Mar 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants