I never would claim that as my original work! But installation and UI
is a necessary step to use SAGE, (thankfully) predetermined by the
creators (or part of the features of implemantation or the underlying
language). I never would just copy and paste complete passages of a
manual, but such a description of fundamental concepts (installation and
UI) do have a degree of (creative) freedom close to zero!
My question: What is the proper way to describe such (necessary) basic,
predefined sage-components without breaking copyright and giving proper
credit?
For sure any doc/tutorial etc. must give reference to SAGE home on
different places of the SAGE document, so my request is just to avoid
trouble and to hear your attitude regarding this point.
Regards BB
Sage code and its documentation are licensed under open-source
licenses, so feel free to copy+paste. In fact, it is encouraged.
Just please license your documentation under the same
open source license.
Further license information:
* Documentation: http://creativecommons.org/licenses/by-sa/3.0/
* Sage code: Type license() at the Sage command line.
>
> My question: What is the proper way to describe such (necessary) basic,
> predefined sage-components without breaking copyright and giving proper
> credit?
>
> For sure any doc/tutorial etc. must give reference to SAGE home on different
> places of the SAGE document, so my request is just to avoid trouble and to
> hear your attitude regarding this point.
>
> Regards BB
>
>
>
>
>
>
> --
> To post to this group, send email to sage-s...@googlegroups.com
> To unsubscribe from this group, send email to
> sage-support...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/sage-support
> URL: http://www.sagemath.org
>
> To unsubscribe from this group, send email to
> sage-support+unsubscribegooglegroups.com or reply to this email with the
> words "REMOVE ME" as the subject.
>
to my regret the copy paste option and
creativecommons.org/licenses/by-sa/3.0/ does not help. The simple reason
is it would not enjoy readers of a german text to find an english
installation manual. creativecommons.org/licenses/by-sa/3.0/ is
compatible with Debian Free Software Guidelines (DFSG), it is allowed
"to Remix � to adapt the work".
The problem is, that a translation is not just a remix but an act of
creative originality and therefore with an own copyright. So I (and may
be others) need a (written) permission to translate the installation
manual. Better for sage to "spread the world" would be a general
allowance to translate the installation manual.
I am only speaking of the installation manual! Because, as I pointed out
in another mail, such a description of installation steps do have a
degree of (creative) freedom close to zero!
Regards BB
I do not agree. Can you show me exactly where in
http://creativecommons.org/licenses/by-sa/3.0/legalcode
it prevents you from translating the work? (See section "3. License Grant.")
>
> The problem is, that a translation is not just a remix but an act of
> creative originality and therefore with an own copyright. So I (and may be
Let us assume this is true. Secondly, you are allowed to add creative
content! (Read the license.) You must relicense your work under
the same license.
> others) need a (written) permission to translate the installation manual.
> Better for sage to "spread the world" would be a general allowance to
> translate the installation manual.
>
> I am only speaking of the installation manual! Because, as I pointed out in
> another mail, such a description of installation steps do have a degree of
> (creative) freedom close to zero!
>
> Regards BB
>
*3. License Grant.* Subject to the terms and conditions of this License,
Licensor hereby grants You a worldwide, royalty-free, non-exclusive,
perpetual (for the duration of the applicable copyright) license to
exercise the rights in the Work as stated below:
a. ...
b. to create and Reproduce Adaptations provided that any such
Adaptation, including any translation in any medium, takes reasonable
steps to clearly label, demarcate or otherwise identify that changes
were made to the original Work. For example, a translation could be
marked "The original work was translated from English to Spanish," or a
modification could indicate "The original work has been modified.";
In a first browsing my attention just was focused on "any translation in
any medium", translation to another language is just in the next sentence.
So I think I have understood this topic and I do not see a problem for a
translation or an adaption.
Tnx for your kind and patient help!
Regards BB
> David Joyner schrieb:
>> On Thu, Mar 18, 2010 at 5:53 PM, bb <bbl...@arcor.de> wrote:
>>
>>> If I try to write a math-tutorial ...
>>>
>>
>>
>> Sage code and its documentation are licensed under open-source
>> licenses, so feel free to copy+paste. In fact, it is encouraged.
>> Just please license your documentation under the same
>> open source license.
>>
>> Further license information:
>> * Documentation: http://creativecommons.org/licenses/by-sa/3.0/
>> * Sage code: Type license() at the Sage command line.
>>
>>
> Thank you for your answer,
>
> to my regret the copy paste option and creativecommons.org/licenses/
> by-sa/3.0/ does not help. The simple reason is it would not enjoy
> readers of a german text to find an english installation manual.
> creativecommons.org/licenses/by-sa/3.0/ is compatible with Debian
> Free Software Guidelines (DFSG), it is allowed "to Remix — to adapt
> the work".
>
> The problem is, that a translation is not just a remix but an act of
> creative originality and therefore with an own copyright. So I (and
> may be others) need a (written) permission to translate the
> installation manual. Better for sage to "spread the world" would be
> a general allowance to translate the installation manual.
CC gives you the right, among other things, to translate as long as
you release under a compatible license. You then are a joint copyright
holder of the translated work (which I would consider to be an
adaption, though one that requires significant creative input).
> I am only speaking of the installation manual! Because, as I pointed
> out in another mail, such a description of installation steps do
> have a degree of (creative) freedom close to zero!
If it's a list of steps, I could totally see that falling under "fair
use."
- Robert