From a39d28f6d7fd977899076e7ea05ead7f8786e127 Mon Sep 17 00:00:00 2001 From: divVerent Date: Mon, 10 May 2010 04:58:00 +0000 Subject: [PATCH] (Commit created by redmine exporter script from page "Legal" version 7) --- Legal.textile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Legal.textile b/Legal.textile index d4e159f..c0725bb 100644 --- a/Legal.textile +++ b/Legal.textile @@ -27,11 +27,11 @@ You may also reuse the work of others, provided that this work is licensed under h3. Audio -It is required to provide sources for any audio files to be included. What your source is largely varies on the way you created this audio. If you created or edited your work in a computer program, you must provide the project files and any samples you used. The samples themselves may also be licensed under the CC-BY or CC-Sampling+ license, which by themselves do not require you to share the sources you used to create the sample. This means that you can use commercial programs to create a sample and include proprietary synths and effects, as the sample you create will be your work and you may choose to license it in every way you see fit. Especially: there is absolutely nothing wrong with using, for example, expensive VSTi plugins for your work, as long as you still share the project file containing the settings for that VSTi plugin. Even if the music is composed on a totally obscure platform (e.g. Mac OS 9, or Amiga), there is nothing wrong with providing whatever is the native format of that application (e.g. as a floppy disk image). +It is required to provide sources for any audio files to be included. What your source is largely varies on the way you created this audio. If you created or edited your work in a computer program, you must provide the project files and any samples you used. The samples themselves may also be licensed under the CC-BY license, which by themselves do not require you to share the sources you used to create the sample. This means that you can use commercial programs to create a sample and include proprietary synths and effects, as the sample you create will be your work and you may choose to license it in every way you see fit. Especially: there is absolutely nothing wrong with using, for example, expensive VSTi plugins for your work, as long as you still share the project file containing the settings for that VSTi plugin. Even if the music is composed on a totally obscure platform (e.g. Mac OS 9, or Amiga), there is nothing wrong with providing whatever is the native format of that application (e.g. as a floppy disk image). If you created the music in another way, let's say you just played it on the piano and recorded it, it may be unclear what your 'source' is. Commonly a musical score would be accepted, or if you completely improvised it may be accepted without any source at all. Generally many programs can export the musical score or provide a midi format. This makes it easier for others to work on what you created, and would be nice to be provided additionally to any project files. If you're unclear what your source is, ask yourself "What would I use if I wanted to modify it?", the answer is likely to be accepted as source. -You may also reuse samples created by others, +as long as they are licensed under the GPL, CC-BY, CC-Sampling+, Artistic License or the MIT License+ (note that ShareAlike and NonCommercial are NOT compatible). _(Provide a list of known legal resources here)._ +You may also reuse samples created by others, +as long as they are licensed under the GPL, CC-BY, Artistic License or the MIT License+ (note that ShareAlike and NonCommercial are NOT compatible). _(Provide a list of known legal resources here)._ h2. Xonotic name -- 2.39.2