[License of FDclone3] (NOTICE: The official license is written in Japanese language. This document is only a translation of the original license, so is NOT VALID LEGALLY.) <0. Introduction> This document describes the permission to use FDclone. FDclone is a free software and there is no restriction on using this software. This document hereby describes the details based on each example, including the wishful desire of the author. <1. Definition> First of all, some terms used in this document are defined here. If the following terms are used in this document without any specific notice, they are used in the meanings written below. source A set of source program, or a set of packages containing such source program, documents and something else. binary An executable binary generated by compiling a set of source program, or a set of packages containing such binary, documents and something else. distribution In the broad sense, to create a duplicate of sources or binaries (if modified or not), and to give it to others. In the narrow sense, to give such duplicate to a few speficic persons. circulation One form of distribution in the broad sense. To give a duplicate of sources or binaries to someone widely in public. primary distribution, primary circulation distribution (or circulation) of files by the author of the files himself. secondary distribution, secondary circulation distribution (or circulation) of files by someone except the author of the files which were primarily distributed or circulated. The subsequent distribution (or circulation) is called as tertiary or quaternary distribution (or circulation) and so on. redistribution, recirculation A general term for secondary and higher order of distribution (or circulation) modification To make changes on a part of the original sources or the binaries. secondary use To include a part of the original sources into other software and use it. <2. Redistribution> You may freely, at any purpose if at a profit or not, redistribute the sources and the binaries, if modified or not, in the narrow sense. Similarly, tertiary and higher order of redistribution can be done freely. However, the author won't take any responsibility for redistributed files. If a person to redistribute files needs a guarantee that the files are not modified or that the files work normally, the person to redistribute files must guarantee it by himself. <3.Recirculation> You can freely, at any purpose, like distribution in the narrow sense, recirculate the sources and the binaries, if modified or not. Note that the author of this software establishes a system for circulation registration for some forms of circulation so that the author takes some responsibility for recirculated files. Similarly to redistribution, the author won't take any responsibility for recirculated files without circulation registration. The author takes responsibility for and gives a guarantee on recirculated files with circulation registration equal to primarily circulated files. You don't have to make circulation registration if you don't need such responsibility or guarantee taken by the author. When recirculated files already with circulation registration are redistributed tertiarily or in higher order, the author takes responsibility for those files equal to recirculated files, provided that the package form and the contents of the redistributed files are not modified compared to recirculated files with circulation registration. If some modification is made to the package, the circulation registration gets invalid at the moment and the authour won't take any responsibility for the package without another circulation registration. However, if a secondary circulator adds some license conditions on the secondarily circulated files with circulation registration, the condition for tertiary and higher order of redistribution follows those conditions. A secondary circulator can freely establish the condition of tertiary or higher order of recirculation as far as it won't break the license condition of primary circulation, provided that circulation registration is made. You should contact the secondary circulator when you consider to recirculate the secondarily circulated files. The author won't interfere tertiary or higher order of redistribution as far as recirculation registration is made. <4. Responsibility on the author> The author takes some responsibility for the primarily distributed files and recirculated files with circulation registration. Concretely speaking, the author will reply to questions and requests from users and make changes on the program if needed. Also the author guarantees that the author won't insert some malicious function out of the specifications to the program and that the program works normally. The author will accept to change the program if it doesn't follow the specifications written in the documents. The author won't take any responsibility for recirculated files not with recirculation registration and won't reply to any questions or requests from the users of those files. The author expects that the recirculator accepts such contacts from those users and cope with them with responsibility. However the author won't compensate for any damages brought by the use of this program and so each user must use it at his own risk. <5. About source circulation registration> The author takes some responsibility for recirculation of the sources even without circulation registration, provided that no changes are made compared to the contents of the primarily circulated package. The author takes files with some changes on its contents in the same way as the ones without any changes, provided that there is no modification on the part of program sources and only some documents or programs are added. In these cases, the change of package format, in other words the change of compression format, package name and so on will not be counted. If modifications are made on the files which are directly related to the executable binaries, including the part of program sources or Makefiles, the author takes some responsibility for the recirculated files provided source recirculation registration is made. You can make circulation registration according to the procedure written below. <6. About binary circulation registration> The author won't take any responsibility for recirculation without circulation registration with regard to the circulation of binaries, even if no changes are made compared to the primarily circulated binaries. You have to make circulation registration following the procedure described below, if modified or not, if you need a guarantee made by the author. The author suggests to make circulation registration for the circulation of binaries without fail, because the circulation of binaries is especially risky. <7. Modification of the program> When a user modifies a part of the program and uses it, it is regarded as secondary use regardless of the number of the modified parts if it is regarded as a product different from the program before changes. Modifications not being regarded as secondary use will follow the redistribution rules described above, however you may treat the files for secondary use freely as a work by a secondary copyright holder. <8.Carrying on books> It is regarded as recirculation to attach (the program) on books to be published via media such as CD-ROM. If a guarantee by the author is required you must make source or binary circulation registration according to whether the attached files are sources or binaries. (The registration) is treated in the same way as for other recirculation. Note that you don't have to make another circulation registration for attachments of recirculated files which are already with circulation registration, and you should follow the condition formulated by the circulator who made circulation registration. If you are going to introduce (the program) in an article, not attaching it, no registration is needed because neither a guarantee nor responsibility will be generated. No need to contact the author. The author appreciate it if you would contact the author or give the author the book when you attach or introduce the program. Especially if you show the author a manuscript of the introduction article in advance, the author may check if any inappropriate parts are included in its contents. Those who want to carry the program should consider this. <9. Procedure for circulation registration> Ciculation registration may be proceeded as below. 1. define the person in charge of circulation 2. replace the string "NULL" in the part containing "distributor" valuable in version.h with the e-mail address of the persion in charge. Example: char *distributor = "shirai@unixusers.net (Takashi SHIRAI)"; 3. Make the differential from the source package primarily circulated. Additional attachments must also be included in the differential if any. 4. Create a package for circulation. 5. Examine and take a note of MD5 checksum of the package for circulation. The checksum of FDClone executable binary must also be examined in the case of binary circulation. If you have no way to examine them, you can make use of "checkid" command built-in FDClone (binary). Compile and execute FDclone, hit "h" key and type "checkid " after the prompt of EXECUTE_SH command, then the MD5 checksum of the file is displayed. 6. Send the author a E-mail for circulation registration including the differential and the MD5 checksum of the package for circulation. The enrironment where the executable binaries are executed, including the operation system and the type of the machine, and the MD5 checksum of the exectutable binary must also be included in the case of binary circulation. 7. Tell the author that you want to change the license condition for the package to be recirculated in the letter if you want. It must be clarified whether you want to make source or binary circulation registration in the registration letter. You can make both source and binary circulation registration in one registration letter. With regard to binary circulation registration, in the case of recircutation on multiple environments using the same differential, you can make the registration for all environments in once in one registration provides those environments are listed. You should contact the author if you have some questions about the detailed procedure before registration.