\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
Board):
part of the Product (e.g. silkscreen or top copper for a printed circuit
board):
\begin{enumerate}
\item the licence notice: “Licensed under CERN-OHL-S v2”;
\item the Source Location.
\end{enumerate}
Do \emph{not} include the CERN logo in there. Only include the CERN copyright
\item\textbf{Suggestion: }You can optionally include a copyright notice to be printed on the Product (remember you must keep intact any Notices in the source, though), but do \emph{not} include the CERN logo (you may optionally include the CERN copyright
notice if your design includes portions of a design from CERN which contains
that CERN copyright notice (in which case, you will be required to reproduce it
as part of your obligations as a licensee under terms of the CERN-OHL under which
the design is licensed to you.
{\color{red} discuss this}
that CERN copyright notice. If you do include a copyright notice on the Product, any it includes part of other designs, you should at least acknowledge the work is not all your own by using Copyright \textcopyright 2020 Sam Smith and others.
\end{enumerate}
\subsection{A Note on Components}
\label{subsec:note-components}
If your design is modular, it may well be helpful to consider licensing each of
If your design is modular, consider licensing each of
the components you have designed separately, and then having an overarching
design, also licensed under an appropriate variant of CERN-OHL which contains
the each of the sub-components.
Why? It will make life easier for licensees who only want to make use of one
the each of the sub-components. This will
make life easier for licensees who only want to make use of one
component of
your design: they will not have to extract the relevant component from your
design and then work out which parts of Notices they are allowed to delete.
You may also want to attach different notice requirements to different
components. For example, if you have a processor and a power supply in your
design, you may want to ensure that the source location for the design files
for the processor are printed on the outside casing of anything using the
processor,but you are less concerned about this when people use the design for
the power
supply. Or, to take a more extreme example, you may want to license the design
for a hydraulic press, and you also include your recipe for hydraulic fluid.
Both can be incorporated into the same design, but it becomes very difficult to
see how a general obligation in the notice file to place the source location
URL on the press can be followed if a licensee only wants to manufacture and
use the hydraulic fluid. This issue can be addressed if the hydraulic fluid is
licensed separately, and there is either has no NOTICE obligation to place the
url on the design, or simply one to place it on the first container in which
the fluid is shipped.
your design.
\section{How to deal with hardware designs licensed under CERN-OHL-S v2}
\label{sec:receive-designs}
Generally speaking, you must always comply with any obligations applying to a
particular design (detailed in a contract or accompanying licence). If you
receive hardware designs licensed under the CERN-OHL-S v2, the obligations are
Generally speaking, you must comply with the requirements applying to a
particular design detailed in the accompanying licence. If you
receive hardware designs licensed under the CERN-OHL-S v2, the requirements are
\href{https://forums.ohwr.org/c/cernohl}{https://forums.ohwr.org/c/cernohl}. You may also find useful information in the FAQs at \href{https://www.ohwr.org/project/cernohl/wikis/faq}{https://www.ohwr.org/project/cernohl/wikis/faq}.
