Consider relicensing the tutorial under GNU FDL

[TravinDreek]

Hi, I'm a free software activist working on software licensing and free culture. After reading about your post (#68) on the license change of the tutorial from CC BY-SA to CC BY-ND-NC to ensure the promotion of free software, I believe there is a better way to do the trick.

The GNU Free Documentation License (GFDL) designed by the Free Software Foundation is a workaround to ensure the copyleft of the technical part of a manual while preventing the ideological part from being modified or wiped. One example using the GFDL is the GNU Emacs Manual, in which the technical sections are allowed to be changed while the GNU Manifesto is not.

In order to use the GFDL for this tutorial, you'll need to follow the steps below:

a) Assert copyright on the tutorial, and put in the documentation a license notice stating that this tutorial is licensed under the GFDL (see below for an example);

b) List, next to the license notice, the title of the sections that you do not wish to be changed as "Invariant Sections" of the document. (Invariant Sections, as defined in the GFDL, are parts of the document that expresses philosophical, ethical or political position etc. and are not allowed to be changed when a modified version of the doc is made.)

c) Include a copy of the GFDL in the tutorial, or point out where a copy of the license can be acquired (the former way is recommended);

Here is an example of a copyright and license notice:

Copyright (C) ArchLinuxStudio.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License, Version 1.3
or any later version published by the Free Software Foundation;
with the Invariant Sections being "前言", "后记" and "在这里列出更多标题";
with no Front-Cover Texts, and with no Back-Cover Texts.
A copy of the license is included in the section entitled "GNU
Free Documentation License". 

By completing the steps above, the tutorial should be licensed under the GFDL. If you have any additional questions, feel free to ask.

Happy Hacking.

[ryosukeeeeee]

Thank you very much for your suggestion, it looks like a good way to modify it. We will consider making changes in the future.