1$MirOS: src/share/doc/legal/LICENCE-GNU,v 1.11 2009/01/15 22:19:44 tg Exp $ 2 3Special rules for GNU and similar less free software 4==================================================== 5 6Non-GNU software 7---------------- 8 9Some software comes under GPL (lynx, mkisofs, perl) or 10different licences (sendmail, perl). For GPL software, 11the "Obtaining source code" section below applies. For 12sendmail, it applies similarily. 13 14GNU software 15------------ 16 17Some software comes under GPL with documentation under 18either GPL or GFDL, and requires copyright assignment, 19namely: autotools, binutils, cvs, gcc, rcs, texinfo 20 21The section "Obtaining source code" below applies. The 22GNU software parts are however not covered by the col- 23lective copyright on MirOS asserted by the founder. We 24also ask any contributor to this part of the source to 25assign back the US style copyright to the FSF. Europe- 26an droit d'auteur rights are retained. 27 28 29GNU FDL 30------- 31 32The MirOS project goals forbid distributing code - this does 33not exclude documentation - which we cannot modify. 34 35The GNU Free Documentation License has been deemed non-free, 36unless neither cover texts nor invariant sections are speci- 37fied - this is, however, not the case with the documents in- 38cluded, thus we have decided to delete them. 39 40Update: even in the case neither front nor back cover texts, 41nor invariant sections are specified, the GFDL is considered 42non-free: http://home.twcny.rr.com/nerode/neroden/fdl.html 43 44cf. http://people.debian.org/%7Esrivasta/Position_Statement.xhtml 45 46If you don't like the fact, contact your local FSF represen- 47tative, or the FSF Europe or USA. 48 49Compromise 50---------- 51 52Currently, we are delivering GNU software bundled with MirOS 53and, for a few key components (gcc and binutils), do not ex- 54clude documentation (for others, we either base our documen- 55tation on an older non-GFDL version (this worked for cvs) or 56do not install it, e.g. texinfo). RMS has assured we can re- 57distribute the GFDL-licenced parts in our CVS repository and 58on CDs, via SSH, in a non-world-readable or encrypted direc- 59tory, according to http://marc.info/?m=113699292525210 60 61All copyright on the changes is assigned back to the FSF, so 62there is not much we can do about it. In order to fulfil the 63licence's requirements, there is always the original version 64available at the CVSweb of "sources.redhat.com", and the mo- 65dified and original versions are visible via MirOS CVSweb as 66shown below. 67 68We urge people to not licence their work under GNU FDL, pre- 69vent people from relicencing our own documentation under it, 70e.g. in the website licence, when possible, and ask them not 71to do it otherwise. We must live with the FSF documentation, 72but we do not allow committers to modify them unless changes 73are assigned back to the FSF, to prevent additional require- 74ments to burden us. 75 76 77GNU GPL 78------- 79 80http://groups.google.com/group/comp.lang.python/msg/29c7588fbecd8289 81and at http://www.symlink.ch/articles/06/12/18/1515227.shtml (German) 82 83Despite FSF propaganda (FUD), the GNU GPL is not a viral li- 84cence if you do not redistribute the end product of combina- 85ting some work with a GPL licenced work. Dynamic linking and 86dlopen(3) are not combining, as they are brought together at 87run time only. GPLv2 section 0 says the act of running isn't 88restricted. Mere aggregation of GPL and non-GPL work on some 89medium (e.g. our installation sets) don't "infect" either. 90 91The ChangeLog requirement is met by CVS logs (both the files 92and the logs within the ,v files themselves). The source can 93be obtained for free from our CVSweb unless distributed with 94the MirOS release/snapshot you obtained. Note that the bina- 95ries you receive need not correspond to the source code (for 96non-GPL binaries only). 97 98Opinions 99-- -- -- 100 101>I believe if you include all of the sources in the exact state you 102>used to build the binary that includes tinyirc as a part of it, as far 103>as I'm concerned you've satisfied the license. 104 -- Nathan Laredo 105 106This was regarding crunchgen(1) and tinyirc. The solution was 107to add tinyirc to a source tarball as usual, and link it only 108against unmodified stock MirOS source from CVS, which is made 109available via AnonCVS regularily and long-livingly. 110 111GPLv3 112----- 113 114We do not yet have a stance on the GPLv3. No work covered by 115that licence will be included in the MirOS base system, gcc, 116and X11 modules. Ports should not be a problem, but for set- 117ting the PERMIT_* flags, we will have to evaluate it first. 118 119 120Obtaining source code 121--------------------- 122 123On your MirOS Release CD, source code for the base system is 124at /v{version}/source{version}.ngz and xfree{version}.ngz; a 125link is placed in the machine-dependent subdirectories to be 126able to easily install them. 127 128Third-party sources for Release, Snapshot or Live CDs can be 129obtained from /v{version}/[Dd]istfiles, or /[Dd]istfiles, or 130/v{version}/[Dd]ist, or /[Dd]ist, if existent. Live CDs come 131with the source code of packages pre-installed, unless these 132have distfiles placed on the HTTP mirror(s), see below. 133 134Source code for less free software that comes with MirOS, as 135listed above, is available via CVSweb, anonCVS, or anonRSYNC 136as described below. 137 138Distfiles not on the distribution media 139--------------------------------------- 140 141According to the GNU General Public License (Version 2), Section 1423b, we hereby guarantee that, unless the required source code is 143available on the same media (as per Section 3a), it shall be ac- 144cessible to the general public on our HTTP download mirrors, for 145at least three years after the initial release date of the media 146and at no cost other than the expense of physically distributing 147these files. Because HTTP mirrors is the medium customarily used 148for software interchange, when it comes to "distfiles" of ports, 149we do not offer any other means, unless the mirrors are not wor- 150king. However, if you want the complete material downloadable at 151our mirrors on fixed media, contact us and we'll send them, at a 152little extra fee, to you, as an additional service going further 153than what the GPL requires. 154 155Distfiles covered by other licences shall be treated similarily. 156 157Mirror list 158----------- 159 160anonymous cvs access with ssh: 161 CVSROOT=_anoncvs@anoncvs.mirbsd.org:/cvs 162 Port: 22 163 passwordless 164 165 CVSROOT=anoncvs@1.anoncvs.mirbsd.org:/cvs 166 Port: 22 167 password: anoncvs 168 169 CVSROOT=anoncvs-mirbsd@anoncvs.allbsd.org:/??? 170 Port: 2022 171 empty password 172 173anonymous rsync access: 174 - via rsync protocol 175 rsync://rsync.allbsd.org/miros-cvs/ 176 - via SSH 177 _anoncvs@anoncvs.mirbsd.org:/cvs/ 178 179cvsweb access with http: 180 http://cvs.mirbsd.de/ (generic redirection to one of below) 181 http://cvsweb.allbsd.org/cvsweb.cgi/?cvsroot=mirbsd 182 http://www.mirbsd.org/cvs.cgi/?cvsroot=miros 183 184direct access to changelog files: 185 http://www.mirbsd.org/clogs/ 186 187access to files' changelogs from upstream: 188 http://www.openbsd.org/ 189 http://www.openbsd.org/anoncvs.html 190 http://www.openbsd.org/cgi-bin/cvsweb/ 191 http://www.netbsd.org/ 192 http://www.gnu.org/ 193 http://sources.redhat.com/projects.html 194 195access to distfiles, ISOs, CVS repository tarballs ("HTTP mirrors"): 196 rsync://rsync.allbsd.org/miros-ftp/ 197 http://www.mirbsd.org/MirOS/ 198 http://pub.allbsd.org/MirOS/ 199 ftp://ftp.allbsd.org/pub/MirOS/ 200