Responding to the Controversy about YOLOv5
blog.roboflow.ai
Responding to the Controversy about YOLOv5
1–10 of 26 posts
Re: Responding to the Controversy about YOLOv5
#2> Is YOLOv5 the Correct Name?
> Candidly, the Roboflow team does not know.
It seems like, unless you can say with certainty that you have a legitimate claim to use an existing name, the right and safe thing to do would be to not use it. Just name your project something else. You lose the brand recognition of the existing name, but on the other hand you avoid the risk of your project getting dragged like this.
When in doubt, save yourself a headache and just use a different name.
Re: Responding to the Controversy about YOLOv5
#3> Is YOLOv5 the Correct Name? > Candidly, the Roboflow team does not know. It seems like, unless you can say with certainty that you have a legitimate claim to use an existing name, the right and safe thing to do would be to not use it. Just name your project something else. You lose the brand recognition of the existing name, but on the other hand you avoid the risk of your project getting dragged like this. When in…
Maybe I just misread this article but it really sounds like they don’t own YOLOv5. It’s someone else’s project they think is cool and are amplifying. If that’s right, then I think it’s reasonable to defer naming to whoever actually made the project!
Re: Responding to the Controversy about YOLOv5
#4> Is YOLOv5 the Correct Name? > Candidly, the Roboflow team does not know. It seems like, unless you can say with certainty that you have a legitimate claim to use an existing name, the right and safe thing to do would be to not use it. Just name your project something else. You lose the brand recognition of the existing name, but on the other hand you avoid the risk of your project getting dragged like this. When in…
YOLOv5 wasn't a Roboflow project, they just provided an implementation and used the name that the project creator used.
Re: Responding to the Controversy about YOLOv5
#5> Is YOLOv5 the Correct Name? > Candidly, the Roboflow team does not know. It seems like, unless you can say with certainty that you have a legitimate claim to use an existing name, the right and safe thing to do would be to not use it. Just name your project something else. You lose the brand recognition of the existing name, but on the other hand you avoid the risk of your project getting dragged like this. When in…
> When in doubt, save yourself a headache and just use a different name.
When you have no doubt, save yourself a headache and read the article. ;)
Re: Responding to the Controversy about YOLOv5
#6Is this article addressing a strawman? I certainly raised an eyebrow at their use of the name but is there actually a "controversy"? And if so, why not be similarly upset over YOLOv4? That edition confused me just as much as v5, given that neither one came from Reddie.
Re: Responding to the Controversy about YOLOv5
#7> Is YOLOv5 the Correct Name? > Candidly, the Roboflow team does not know. It seems like, unless you can say with certainty that you have a legitimate claim to use an existing name, the right and safe thing to do would be to not use it. Just name your project something else. You lose the brand recognition of the existing name, but on the other hand you avoid the risk of your project getting dragged like this. When in…
It seems like the researchers actually working on various versions and updates of this understand and are fine with the naming, the original creator of YOLO doesn’t seem to care, and the only people kicking up a fuss are random opinionated Internet commentators that are nothing to do with it.
I don’t see what the problem is with letting the community of people actually contributing to various forms of YOLO work it out between themselves. As, er, they seem to have done.
Re: Responding to the Controversy about YOLOv5
#8There's no controversy.
Re: Responding to the Controversy about YOLOv5
#9> Is YOLOv5 the Correct Name? > Candidly, the Roboflow team does not know. It seems like, unless you can say with certainty that you have a legitimate claim to use an existing name, the right and safe thing to do would be to not use it. Just name your project something else. You lose the brand recognition of the existing name, but on the other hand you avoid the risk of your project getting dragged like this. When in…
It seems like the researchers actually working on various versions and updates of this understand and are fine with the naming, the original creator of YOLO doesn’t seem to care, and the only people kicking up a fuss are random opinionated Internet commentators that are nothing to do with it. I don’t see what the problem is with letting the community of people actually contributing to various forms of YOLO work it ou…
What if there are two successors of YOLOv4 that both inherit large parts of YOLOv4, make different sets of changes, achieving different sets of improvements?
Do we call them YOLOv5.0 and YOLOv5.1? How do we nomenclate the graph? What if another one inherits from both YOLOv5.0 and YOLOv5.1? Is it YOLOv6 or YOLOv(5.0,5.1).0?
Re: Responding to the Controversy about YOLOv5
#10Earlier quoted context omitted.
It seems like the researchers actually working on various versions and updates of this understand and are fine with the naming, the original creator of YOLO doesn’t seem to care, and the only people kicking up a fuss are random opinionated Internet commentators that are nothing to do with it. I don’t see what the problem is with letting the community of people actually contributing to various forms of YOLO work it ou…
What if there are two successors of YOLOv4 that both inherit large parts of YOLOv4, make different sets of changes, achieving different sets of improvements? Do we call them YOLOv5.0 and YOLOv5.1? How do we nomenclate the graph? What if another one inherits from both YOLOv5.0 and YOLOv5.1? Is it YOLOv6 or YOLOv(5.0,5.1).0?
In the business world we have trademarks for this.
As models become brand names and franchises I wonder if academics will start trademarking them like many big open source projects do.