Related Issues:

• WongKinYiu/yolov9#82
• WongKinYiu/yolov9#10

I envision that all required changes should be tracked, potentially using GitHub Projects.

That way, people can come and go from active development and get involved, and only a small number (1-2 people) will need to actively keep track of everything:

• I think the first part of this is finding all files with code that will need to be changed.
• Then this information can be split into two categories: "trivial" and "component". Trivial changes would be things that are easily re-written, where as "component" would be something that needs a bigger overhaul
• After that, the process is legal. AGPL is a complicated license, and the community would need to try and get some answers on how to make sure we do this properly.

Note that I am not a lawyer, but I think it would be good if we make sure we cite exactly the information we have collected for all our new code.

Thanks!

First Draft

• #2
• #1
• architectures and loss functions (WongKinYiu/yolov9#82 (comment))

I think it is important we mark that this is a WIP and use of the code is at the degression of the owner until further notice?

@WongKinYiu mentioned that help is requested in building out DDP-compatible training infrastructure. Let's start that discussion here.

@WongKinYiu has mentioned that help is needed with datasets and dataloaders. Let's kick off the discussion of that work here.