Some remarks:

There are very useful examples files, such as for the Data Transfer Modifier.

Some examples are very simple and/or duplicated by screenshot or video, and can be removed.

And also there are old blend-files that don't work in new Blender versions, for example in the Physics section. There should be an opportunity to update them, if they remain in the manual.

I would like if we keep downloads and write some rules:

• Must be CC-BY-SA 4.0 Int
• Must be under 10mb for a zip
• Files should be properly named with the blender version they were last updated for
• Files are stored in the svn repo
• A page should try limit itself to 1 example
• blend-file should include a txt-file (opened in blender text editor) that describes the example and steps on how to use it.
• All files should be stored as a zip
• No py-files or other executable code (security reasons)

Anyone have any thoughts or concerns here?

Hi Aaron, I couldn't find this task when I searched for an existing one.

Replying to your questions:

I propose to put media files in the SVN repo for the manual under a new folder files/ in the root directory. Not in the new developer wiki.

• Must be CC-BY-SA 4.0 Int

The files on the archived wiki were uploaded under the Open Content License or the Blender Artistic License.
The Blender Manual switched from OCL to CC-BY-SA 4.0.
I also wonder if the files should be re-uploaded with this license or keep one of the above?

• Must be under 10mb for a zip.

I think we can recommend a maximum size, but I wouldn't strictly enforce it. 10MB seems low for media.

• Files should be properly named with the blender version they were last updated for

Renaming would break links, I would not put the Blender version on the file name.
We could ask for .blend files to have a text buffer with the version, besides the license, but this would also mean bumping all binary files on every blender release.
Since the manual is now versioned, I think there is no need to manually add versions to the files. They still should be checked periodically, but that can be part of the release process checklist.

• Files are stored in the svn repo

Yes.

• A page should try limit itself to 1 example

I don't see the reason for this limitation.

• blend-file should include a txt-file (opened in blender text editor) that describes the example and steps on how to use it.

A blend file (or a zip), should always have a text with the license and readme. However, I'd keep text to a minimum and refer to the manual page.

• All files should be stored as a zip

I also don't see a reason for this limitation.

• No py-files or other executable code (security reasons)

Python code may be needed as a demo, although most python examples are already shipped with Blender.
I wouldn't limit this either.