The 'only if no clear instructions were included in the readme' bit is the vital element here.

I spent more than 30 days out of the loop following my accident last November. I effectively lost the use of my 'dominant' hand for 6 weeks. If I had come back and found that my work had been considered 'community property' because I hadn't answered e-mails, I would have been FURIOUS. And trust me...when something like that happens, your first thought is not to check your e-mails.

The idea of this is to ensure that all modders are aware that their wishes with regard to their content are known and clearly stated. The more simple and straightforward that is, the better.

ALL releases should include a simple readme, stating:

1) The type of mod ( full conversion...stat change...map..whatever )
2) Installation instructions
3) Removal Instructions
4) Credits for contributors
5) Conditions of use.

Conditions of use can simply state whether the creators wish their content to be used in any other mod, can be modified in any way and under what conditions, and so on.

Ultimately, a 'standard' readme framework would be best. This was standard in the old Quake modding days. There was a standard readme framework, and you just put in the bits that related to your mod! All releases had it, and everyone knew about it. You can also paste this into your 'release' thread on the forum, for those who never read 'readme' files!

***************************
Mod Name:

This mod contains:
New Models
Mew Maps
New Textures
Stat Changes

Mod description:

Credits:

Install Instructions

Removal Instructions

Copyright Notice:
May not be used other than with the original mod
May not be used for other mods
May be used provided full credit given
May be used and modified provided credit given
Do what you want with it!