paul@3 | 1 | Licence Agreement for CommonPIC32_VGA
|
paul@3 | 2 | -------------------------------------
|
paul@3 | 3 |
|
paul@3 | 4 | Copyright (C) 2021, 2022 Paul Boddie <paul@boddie.org.uk>
|
paul@3 | 5 |
|
paul@3 | 6 | This program is free software; you can redistribute it and/or modify it under
|
paul@3 | 7 | the terms of the GNU General Public License as published by the Free Software
|
paul@3 | 8 | Foundation; either version 3 of the License, or (at your option) any later
|
paul@3 | 9 | version.
|
paul@3 | 10 |
|
paul@3 | 11 | This program is distributed in the hope that it will be useful, but WITHOUT
|
paul@3 | 12 | ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
|
paul@3 | 13 | FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
|
paul@3 | 14 | details.
|
paul@3 | 15 |
|
paul@3 | 16 | You should have received a copy of the GNU General Public License along with
|
paul@3 | 17 | this program. If not, see <http://www.gnu.org/licenses/>.
|
paul@3 | 18 |
|
paul@3 | 19 | Notes on the licence choice and its application to this work
|
paul@3 | 20 | ------------------------------------------------------------
|
paul@3 | 21 |
|
paul@3 | 22 | Although the above statement refers to a "program", the licence itself uses
|
paul@3 | 23 | this term to refer to "any copyrightable work". In this case, the work
|
paul@3 | 24 | consists of schematics, circuit layout details and other data, and the
|
paul@3 | 25 | application of this licence is intended to govern the further distribution of
|
paul@3 | 26 | these materials in addition to any programs or software that might also be
|
paul@3 | 27 | included in the work.
|
paul@3 | 28 |
|
paul@3 | 29 | When making hardware using the materials featured in this work, be sure to
|
paul@3 | 30 | provide corresponding sources (schematics, circuit layouts) or to make them
|
paul@3 | 31 | available on request, as indicated by the licence terms. Where a modified form
|
paul@3 | 32 | of the work is distributed, the relevant changes must be incorporated into the
|
paul@3 | 33 | source files that were actually edited to produce the desired, modified
|
paul@3 | 34 | result.
|
paul@3 | 35 |
|
paul@3 | 36 | It is not generally acceptable to provide only modified output files when
|
paul@3 | 37 | distributing modified forms of this work. For example, it is not acceptable to
|
paul@3 | 38 | change the circuit layout file in a PCB editing program and then withhold this
|
paul@3 | 39 | modified file from recipients by insisting that only the Gerber files were
|
paul@3 | 40 | edited directly. Only if the Gerber files were actually edited directly may
|
paul@3 | 41 | modified versions of such files be considered source-level changes. Even then,
|
paul@3 | 42 | such modifications on files that are the product of other, more abstract,
|
paul@3 | 43 | files are not recommended as they rarely uphold a sustainable development
|
paul@3 | 44 | approach.
|
paul@3 | 45 |
|
paul@3 | 46 | To conclude, when producing unmodified versions of this work, you should make
|
paul@3 | 47 | these materials available to recipients. When producing modified versions, you
|
paul@3 | 48 | should make the exact materials you used available to recipients.
|
paul@3 | 49 |
|
paul@3 | 50 | You should preserve the copyright and licensing notices present in this work
|
paul@3 | 51 | regardless of any modifications you make to the work. However, where a
|
paul@3 | 52 | copyright notice appears on the hardware itself (being analogous to a message
|
paul@3 | 53 | that a program might display to communicate such information to its users), you
|
paul@3 | 54 | may choose to extend the notice to take your modifications into account, or you
|
paul@3 | 55 | may choose to replace it with a reference to a resource providing all
|
paul@3 | 56 | applicable copyright and licensing information.
|