Warning, /coresoftware/generators/JEWEL/GUIDELINES is written in an unsupported language. File is not indexed.
0001
0002 MCNET GUIDELINES
0003
0004 for Event Generator Authors and Users
0005
0006
0007 PREAMBLE
0008
0009 This generator has been developed as part of an academic research
0010 project and is the result of many years of work by the authors.
0011 Proper academic recognition is a requirement for its continued
0012 development.
0013
0014 The components of the program have been developed to work together
0015 as a coherent physics framework. We believe that the creation of
0016 separately maintained forks or piecewise distribution of individual
0017 parts would diminish their scientific value.
0018
0019 The authors are convinced that software development in a scientific
0020 context requires full availability of all source code, to further
0021 progress and to allow local modifications to meet the specific
0022 requirements of the individual user.
0023
0024 Therefore we have decided to release this program under the
0025 GNU General Public License (GPL) version 2. This ensures
0026 that the source code will be available to you and grants you the
0027 freedom to use and modify the program. You can redistribute your
0028 modified versions as long as you retain the GPL and respect existing
0029 copyright notices (see the file 'COPYING' for details).
0030
0031 By using the GPL, we entrust you with considerable freedom and expect
0032 you to use it wisely, since the GPL does not address the issues in
0033 the first two paragraphs. To remedy this shortcoming, we have
0034 formulated the following guidelines relevant for the distribution
0035 and usage of event generator software in an academic setting.
0036
0037
0038 GUIDELINES
0039
0040 1) The integrity of the program should be respected.
0041 -------------------------------------------------
0042
0043 1.1) Suspected bugs and proposed fixes should be reported back to the
0044 original authors to be considered for inclusion in the standard
0045 distribution. No independently developed and maintained forks
0046 should be created as long as the original authors actively work on
0047 the program.
0048
0049 1.2) The program should normally be redistributed in its entirety.
0050 When there are special reasons, an agreement should be sought with
0051 the original authors to redistribute only specific parts. This
0052 should be arranged such that the redistributed parts remain
0053 updated in step with the standard distribution.
0054
0055 1.3) Any changes in the code must be clearly marked in the source
0056 (reason, author, date) and documented. If any modified version is
0057 redistributed it should be stated at the point of distribution
0058 (download link) that it has been modified and why.
0059
0060 1.4) If a significant part of the code is used by another program,
0061 this should be clearly specified in that program's documentation and
0062 stated at its point of distribution.
0063
0064 1.5) Copyright information and references may not be removed.
0065 Copyright-related program messages may not be altered and must be
0066 printed even if only a part of the program is used. Adding further
0067 messages specifying any modifications is encouraged.
0068
0069
0070 2) The program and its physics should be properly cited when used for
0071 academic publications
0072 ------------------------------------------------------------------
0073
0074 2.1) The main software reference as designated by the program authors
0075 should always be cited.
0076
0077 2.2) In addition, the original literature on which the program is based
0078 should be cited to the extent that it is of relevance for a study,
0079 applying the same threshold criteria as for other literature.
0080
0081 2.3) When several programs are combined, they should all be mentioned,
0082 commensurate with their importance for the physics study at hand.
0083
0084 2.4) To make published results reproducible, the exact versions of the
0085 codes that were used and any relevant program and parameter
0086 modifications should be spelled out.
0087
0088
0089 POSTSCRIPT
0090
0091 The copyright license of the software is the GPL v2 alone, therefore
0092 the above guidelines are not legally binding. However, we reserve the
0093 right to criticize offenders. The guidelines should always be combined
0094 with common sense, for interpretation and for issues not covered.
0095 Enquiries regarding the guidelines and related issues are encouraged
0096 and should be directed to the authors of the program.
0097
0098 Please note that the program, including all its code and documentation,
0099 is intended for academic use and is delivered "as is" to be used at
0100 your own risk, without any guarantees.
0101
0102 ----------------------------------------------------------------------
0103
0104 These guidelines were edited by Nils Lavesson and David Grellscheid
0105 for the MCnet collaboration, which has approved and agreed to respect
0106 them. MCnet is a Marie Curie Research Training Network funded under
0107 Framework Programme 6 contract MRTN-CT-2006-035606.
0108
