Maybe we should support wild backbones/models ?

Describe the feature Add a wild_backbones folders that stores the backbones directly copied from the original papers/repositories. They are just about to work and could be maintained by any contributors.

Motivation I personally have sucessfully run the I3D, X3D, MViT, MViT2, VideoMAE as the backbones with the mmaction2 by intergrating the codes from the original repos. I want to share my codes because I was once eager to these backbones. But my implementations is just about to work, and defitenly do NOT meet the mmaction code requirement.

Therefore, I think it would be very meaningful to have wild_backbones that allow contributors to easily share their implementations without the need of following the strict code requirement.

[makecent]

@hukkai I am in favor of the option1 because it’s simple. Furthermore, in some cases it may be NOT good to put a trhid party codes in a single py file. The dependency subfolder could also be put in the contrib folder.

For instance, we can implement ALL slowfast models by adding a slowfast package under the models/contrib. This slowfast pacakage only contains necessary py files to build slowfast models, and the slowfast config files. After that, we can easily build any slow models with mmaction2.

I will create a demo PR for this.

[hukkai]

@makecent I think we can begin with the MViT model and make the inference available. I will work on this in the following two days.