paul@20 | 1 | Licence Agreement for AcornElectronMainboard
|
paul@20 | 2 | --------------------------------------------
|
paul@20 | 3 |
|
paul@20 | 4 | Copyright (C) 2022, 2023 Paul Boddie <paul@boddie.org.uk>
|
paul@20 | 5 |
|
paul@20 | 6 | This program is free software; you can redistribute it and/or modify it under
|
paul@20 | 7 | the terms of the GNU General Public License as published by the Free Software
|
paul@20 | 8 | Foundation; either version 3 of the License, or (at your option) any later
|
paul@20 | 9 | version.
|
paul@20 | 10 |
|
paul@20 | 11 | This program is distributed in the hope that it will be useful, but WITHOUT
|
paul@20 | 12 | ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
paul@20 | 13 | FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
|
paul@20 | 14 | details.
|
paul@20 | 15 |
|
paul@20 | 16 | You should have received a copy of the GNU General Public License along with
|
paul@20 | 17 | this program. If not, see <http://www.gnu.org/licenses/>.
|
paul@20 | 18 |
|
paul@20 | 19 | Acknowledgements
|
paul@20 | 20 | ----------------
|
paul@20 | 21 |
|
paul@20 | 22 | The information provided in various forms within this distribution is based on
|
paul@20 | 23 | the circuit diagram previously published in the following book:
|
paul@20 | 24 |
|
paul@20 | 25 | Adrian C. Dickens, Mark A. Holmes, "The Advanced User Guide for the Acorn
|
paul@20 | 26 | Electron", Acornsoft/Adder Publishing, ISBN 0947929037
|
paul@20 | 27 |
|
paul@20 | 28 | Of specific relevance is the following statement from that publication:
|
paul@20 | 29 |
|
paul@20 | 30 | "The Authors gratefully acknowledge Acorn Computers Limited for their kind
|
paul@20 | 31 | permission to reproduce the complete Electron circuit diagram."
|
paul@20 | 32 |
|
paul@20 | 33 | The revised version of the Advanced User Guide undertaken by the community
|
paul@20 | 34 | also includes the following notes of relevance:
|
paul@20 | 35 |
|
paul@20 | 36 | "Third edition Jan 2019, by stardot.org.uk members. Revised diagrams based on
|
paul@20 | 37 | those drawn by C. Dewhurst."
|
paul@20 | 38 |
|
paul@20 | 39 | Thanks are also due to John Simpson for his continued work on revising the
|
paul@20 | 40 | Advanced User Guide, including the circuit diagram, over many years.
|
paul@20 | 41 |
|
paul@20 | 42 | Notes on the licence choice and its application to this work
|
paul@20 | 43 | ------------------------------------------------------------
|
paul@20 | 44 |
|
paul@20 | 45 | Although the above statement refers to a "program", the licence itself uses
|
paul@20 | 46 | this term to refer to "any copyrightable work". In this case, the work
|
paul@20 | 47 | consists of schematics, circuit layout details and other data, and the
|
paul@20 | 48 | application of this licence is intended to govern the further distribution of
|
paul@20 | 49 | these materials in addition to any programs or software that might also be
|
paul@20 | 50 | included in the work.
|
paul@20 | 51 |
|
paul@20 | 52 | When making hardware using the materials featured in this work, be sure to
|
paul@20 | 53 | provide corresponding sources (schematics, circuit layouts) or to make them
|
paul@20 | 54 | available on request, as indicated by the licence terms. Where a modified form
|
paul@20 | 55 | of the work is distributed, the relevant changes must be incorporated into the
|
paul@20 | 56 | source files that were actually edited to produce the desired, modified
|
paul@20 | 57 | result.
|
paul@20 | 58 |
|
paul@20 | 59 | It is not generally acceptable to provide only modified output files when
|
paul@20 | 60 | distributing modified forms of this work. For example, it is not acceptable to
|
paul@20 | 61 | change the circuit layout file in a PCB editing program and then withhold this
|
paul@20 | 62 | modified file from recipients by insisting that only the Gerber files were
|
paul@20 | 63 | edited directly. Only if the Gerber files were actually edited directly may
|
paul@20 | 64 | modified versions of such files be considered source-level changes. Even then,
|
paul@20 | 65 | such modifications on files that are the product of other, more abstract,
|
paul@20 | 66 | files are not recommended as they rarely uphold a sustainable development
|
paul@20 | 67 | approach.
|
paul@20 | 68 |
|
paul@20 | 69 | To conclude, when producing unmodified versions of this work, you should make
|
paul@20 | 70 | these materials available to recipients. When producing modified versions, you
|
paul@20 | 71 | should make the exact materials you used available to recipients.
|
paul@20 | 72 |
|
paul@20 | 73 | You should preserve the copyright and licensing notices present in this work
|
paul@20 | 74 | regardless of any modifications you make to the work. However, where a
|
paul@20 | 75 | copyright notice appears on the hardware itself (being analogous to a message
|
paul@20 | 76 | that a program might display to communicate such information to its users), you
|
paul@20 | 77 | may choose to extend the notice to take your modifications into account, or you
|
paul@20 | 78 | may choose to replace it with a reference to a resource providing all
|
paul@20 | 79 | applicable copyright and licensing information.
|