Commit 51c6e905 authored by Javier Serrano's avatar Javier Serrano

Design modifications and hardware production

parent 024eddbf
...@@ -16,6 +16,7 @@ citecolor=blue]{hyperref} ...@@ -16,6 +16,7 @@ citecolor=blue]{hyperref}
\title{CERN Open Hardware Licence Version 2 - Strongly Reciprocal \\ User Guide} \title{CERN Open Hardware Licence Version 2 - Strongly Reciprocal \\ User Guide}
\date{\today\\Guide version: 1.0}
\begin{document} \begin{document}
...@@ -33,11 +34,11 @@ licensees that you are sharing your designs under the licence. These guidelines ...@@ -33,11 +34,11 @@ licensees that you are sharing your designs under the licence. These guidelines
are only to be taken as advice, illustrating some ways in which we think this are only to be taken as advice, illustrating some ways in which we think this
can be done efficiently. can be done efficiently.
In order to help you distinguish between your obligations as a licensee and our In order to help you distinguish between your obligations (mostly as a licensee)
suggestions to you as a licensor, we will use the word `rule' for the former and and our suggestions to you (mostly as a licensor), we will use the word `rule'
the word `suggestion' for the latter. Any perceived contradiction between these for the former and the word `suggestion' for the latter. Any perceived
guidelines and the licence text should of course be resolved in favour of the contradiction between these guidelines and the licence text should of course be
licence text. resolved in favour of the licence text.
\section{How to apply CERN-OHL-S v2 to a hardware design} \section{How to apply CERN-OHL-S v2 to a hardware design}
...@@ -144,7 +145,8 @@ licensing information. ...@@ -144,7 +145,8 @@ licensing information.
\item a notice that the hardware design source is licensed under the \item a notice that the hardware design source is licensed under the
CERN-OHL-S v2, possibly with a link to CERN-OHL-S v2, possibly with a link to
\href{https://cern.ch/cern-ohl}{https://cern.ch/cern-ohl}: \href{https://ohwr.org/cern\_ohl\_s\_v2.txt}
{https://ohwr.org/cern\_ohl\_s\_v2.txt}:
\begin{enumerate} \begin{enumerate}
\item ``Licensed under CERN-OHL-S v2 or later'' or \item ``Licensed under CERN-OHL-S v2 or later'' or
\item ``Licensed under CERN-OHL-S v2''; \item ``Licensed under CERN-OHL-S v2'';
...@@ -175,7 +177,7 @@ called Gizmo at https://example\_url: ...@@ -175,7 +177,7 @@ called Gizmo at https://example\_url:
\\ \\
As per CERN-OHL-S v2 section 4, should You produce hardware based on this As per CERN-OHL-S v2 section 4, should You produce hardware based on this
source, You must maintain the Source Location visible on the external case of source, You must maintain the Source Location visible on the external case of
the Gizmo or other product you make using this documentation. the Gizmo or other products you make using this source.
\end{mdframed} \end{mdframed}
The first three lines in the example above, containing copyright and licence The first three lines in the example above, containing copyright and licence
...@@ -194,11 +196,27 @@ SPDX-License-Identifier: CERN-OHL-S-2.0+ ...@@ -194,11 +196,27 @@ SPDX-License-Identifier: CERN-OHL-S-2.0+
your choice of licence is easy to understand by humans and computers alike. your choice of licence is easy to understand by humans and computers alike.
\end{enumerate} \end{enumerate}
Why would you license your design under `CERN-OHL-S v2 or later'? Imagine we
discovered a shortcoming of the licence which made us write a new version, let's
say version 3.0, to fix it. Let us further imagine that we decided to make v3
incompatible with v2 (this actually happened with the GPL). If you licensed your
design under `v2 only' that means it could not be combined with new designs
licensed under v3. If, on the other hand, you license your design under `v2 or
later', you give future licensees the option of interpreting the design as
licensed under the hypothetical v3, and there would be no compatibility issues.
This is quite an important decision to take when you use a reciprocal licence,
so we thought we'd mention it in this guide.
\begin{enumerate}[label=\textbf{\ref*{subsec:your-sources}.8}]
\item \textbf{Suggestion: } give some thought to the `or later' option before
publishing your design under CERN-OHL-S v2.
\end{enumerate}
We are going to assume that you, as a licensor, want people who receive a product We are going to assume that you, as a licensor, want people who receive a product
based on your design to know that it is Open Hardware and where they can find based on your design to know that it is Open Hardware and where they can find
the design files for that product, hence: the design files for that product, hence:
\begin{enumerate}[label=\textbf{\ref*{subsec:your-sources}.8}] \begin{enumerate}[label=\textbf{\ref*{subsec:your-sources}.9}]
\item \textbf{Rule: } include in a part of the Source corresponding to a visible \item \textbf{Rule: } include in a part of the Source corresponding to a visible
part of the Product (e.g. silkscreen or top copper for a Printed Circuit part of the Product (e.g. silkscreen or top copper for a Printed Circuit
Board): Board):
...@@ -232,7 +250,64 @@ to: ...@@ -232,7 +250,64 @@ to:
\end{enumerate} \end{enumerate}
\subsection{Design modifications and publication} \subsection{Design modifications and publication}
\label{subsec:modify-designs}
If you modify a hardware design licensed by someone else under CERN-OHL-S v2,
and you want to publish your modified design, or you need to publish it e.g. as
a result of the obligations attached to the production and distribution of
products, you must:
\begin{enumerate}[label=\textbf{\ref*{subsec:modify-designs}.1}]
\item \textbf{Rule: } keep intact all the notices referred to above, although
you may remove notices that are no longer relevant to your design (for
example, if the design you are using contains a power supply and a processor
board, and you are only using the processor board in your own design, you can
remove the notices relating to the power supply, so long as you are sure they
only relate to the power supply).
\end{enumerate}
\begin{enumerate}[label=\textbf{\ref*{subsec:modify-designs}.2}]
\item \textbf{Rule: } include notices stating that you have modified the
hardware designs, giving a date and information about the modifications you
have made (e.g. in a CHANGES.TXT file).
\end{enumerate}
\begin{enumerate}[label=\textbf{\ref*{subsec:modify-designs}.3}]
\item \textbf{Rule: } add the appropriate copyright notice and Source Location
to the modifications that were made.
\end{enumerate}
\begin{enumerate}[label=\textbf{\ref*{subsec:modify-designs}.4}]
\item \textbf{Rule: } license the modifications under the `CERN-OHL-S v2' or
`CERN-OHL-S v2 or later' as decided by the original licensor.
\end{enumerate}
\subsection{Hardware production and distribution} \subsection{Hardware production and distribution}
\label{subsec:make-hardware}
If, as a licensee, you want to produce hardware based on a design licensed under
CERN-OHL-S v2 and/or distribute that hardware, you need to:
\begin{enumerate}[label=\textbf{\ref*{subsec:make-hardware}.1}]
\item \textbf{Rule: } either provide each recipient with a copy of the Complete
Source or ensure that each recipient is notified of the Source Location of the
Complete Source.
\end{enumerate}
By Complete Source, we mean all files needed to make the hardware. Please see
the licence text for details. You also need to respect, if applicable, the will
expressed by the licensor to have a clear visual indication of the Source
Location on the hardware:
\begin{enumerate}[label=\textbf{\ref*{subsec:make-hardware}.1}]
\item \textbf{Rule: } if specified in a Notice by the licensor, the Product must
visibly and securely display the Source Location on it or its packaging or
documentation in the manner specified in that Notice.
\end{enumerate}
\section{Asking for help}
If there is something unclear in this guide, or you have any question on how to
apply the licence, the best place to ask is the CERN OHL forum at\\
\href{https://forums.ohwr.org/c/cernohl}{https://forums.ohwr.org/c/cernohl}.
\end{document} \end{document}
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment