So far, we've had no problems related to this, which is also why there are no solid agreements on the subject. With that in mind, I would prefer we have a decent permission declaration before some kind of disagreement crops up.
With that in mind, I think we should sticky a general-purpose guideline in the assets dev forums which touches on the following subjects:
- Usage of Tamriel_Data objects by other affiliated projects. Tamriel_Data is a joint asset repository for several related projects (P:C, SHOTN, TR, etc.) Any asset made or donated to one project should therefore be implicitly usable by other projects. Give the cooperative nature of Tamriel_Data, we cannot accept files that are exclusive to one project alone.
- Usage of Tamriel_Data objects by the community. Tamriel_Data is built as a repository for high-quality resources that can be used by other modders in the community, either by making their mods dependent on Tamriel_Data.esm, or by unpacking the files and repackaging them in their own mods. We ask that all third-party modders acknowledge the origin of repackaged assets, and give credits in their readme files. Any PT modder who does not wish for his work to be used outside of Tamriel_Data should mention this explicitly alongside his contribution: otherwise, it will be assumed that the modder agrees to share his work with the community.
- Usage of Tamriel_Data objects for other games. Occasionally, it happens that we are contacted by third-party modders who work on projects for Oblivion or Skyrim. Not quite sure if we can make a general rule for this? Thoughts? Of course, any asset that is partially based on a vanilla asset cannot be used for other games in any way.
- Pre-arrangement assets: obviously, this agreement cannot work retroactively. For assets that are currently in data, the best course of action would probably be to track down the original modder, if they are still active, and ask for permission directly. If anybody currently active has qualms about sharing one or more of his assets, it would be best if they note this somewhere so that we can include this in a permissions file.
- Maybe a general reminder that assets have to be either wholly original or based on resources that themselves offer full permission for usage and modifications.
- Related to this, I think it might be a good idea to include a "no take-backs" rule: once an asset is donated, you cannot arbitrarily demand that it is removed from data. Maybe a bit paranoid, but I think it might pay to write this down somewhere.