Commit 2fabf34e authored by Andrew Katz's avatar Andrew Katz

Update user_guides/cern_ohl_s_v2_user_guide.tex

parent 5aaabeea
......@@ -45,7 +45,147 @@ for the former and the word `suggestion' for the latter. Any perceived
contradiction between these guidelines and the licence text should of course be
resolved in favour of the licence text. \footnote{Lawyers among you may realise
that, technically, the CERN-OHL family of licences do not place any obligations
on Licensors at all (unless they are also licensees). However, if you if, as a
on Licensors at all (unless they are also licensees). However, if, as a
licensor, you do not comply with the "rules" you are not acting within the
spirit of the CERN-OHL, and you will almost certainly make it more difficult
for potential licensees to make use of the designs, something which contradicts
the most basic intention of the licence. Therefore, even as a Licensor,
please regard the rules as binding.}.
\section{How to apply CERN-OHL-S v2 to a hardware design}
\subsection{Pre-requisite}
Authorship/ownership of the design must be clear and undisputed. Only the legal
owner of the rights in the hardware design may decide under what conditions to
make it available. Generally, If ownership is vested in more than one
person/entity, there
must be an agreement among the owners (or a chain of compatible licences from
each of them) to release the hardware design as open hardware, and under the
CERN-OHL-S v2 in particular.
\documentclass[10pt, a4paper]{article}
\usepackage[utf8]{inputenc}
\usepackage[hidelinks, colorlinks=true, linkcolor=blue, urlcolor=blue,
citecolor=blue]{hyperref}
\usepackage{enumitem}
\usepackage{lmodern}
\usepackage[linewidth=1pt]{mdframed}
\usepackage{xcolor}
\usepackage{draftwatermark}
\SetWatermarkText{DRAFT}
%\SetWatermarkScale{5}
\title{CERN Open Hardware Licence Version 2 - Strongly Reciprocal \\ User
Guide}
\date{\today\\Guide version: 1.0}
\begin{document}
\maketitle
\section{Introduction}
This document contains guidelines on how to apply the CERN-OHL-S v2 to a given
hardware design, and on the use of hardware designs licensed under the
CERN-OHL-S v2. This means we will be talking to you sometimes as a licensor,
and
other times as a licensee.
As a licensor, there are many ways in which you can make it clear to your
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
can be done efficiently.
In order to help you distinguish between your obligations (mostly as a
licensee)
and our suggestions to you (mostly as a licensor), we will use the word `rule'
for the former and the word `suggestion' for the latter. Any perceived
contradiction between these guidelines and the licence text should of course be
resolved in favour of the licence text. \footnote{Lawyers among you may realise
that, technically, the CERN-OHL family of licences do not place any obligations
on Licensors at all (unless they are also licensees). However, if, as a
licensor, you do not comply with the "rules" you are not acting within the
spirit of the CERN-OHL, and you will almost certainly make it more difficult
for potential licensees to make use of the designs, something which contradicts
the most basic intention of the licence. Therefore, even as a Licensor,
please regard the rules as binding.}.
\section{How to apply CERN-OHL-S v2 to a hardware design}
\subsection{Pre-requisite}
Authorship/ownership of the design must be clear and undisputed. Only the legal
owner of the rights in the hardware design may decide under what conditions to
make it available. Generally, If ownership is vested in more than one
person/entity, there
must be an agreement among the owners (or a chain of compatible licences from
each of them) to release the hardware design as open hardware, and under the
CERN-OHL-S v2 in particular.
\subsection{Your sources}
\label{subsec:your-sources}
Nowadays most designers who intend to share their work do so by hosting their
design files (sources) in a publicly-accessible repository using
version-control
systems such as git. The sites hosting these repositories usually provide users
with the convenience of downloading a whole repository as a compressed (e.g.
\documentclass[10pt, a4paper]{article}
\usepackage[utf8]{inputenc}
\usepackage[hidelinks, colorlinks=true, linkcolor=blue, urlcolor=blue,
citecolor=blue]{hyperref}
\usepackage{enumitem}
\usepackage{lmodern}
\usepackage[linewidth=1pt]{mdframed}
\usepackage{xcolor}
\usepackage{draftwatermark}
\SetWatermarkText{DRAFT}
%\SetWatermarkScale{5}
\title{CERN Open Hardware Licence Version 2 - Strongly Reciprocal \\ User
Guide}
\date{\today\\Guide version: 1.0}
\begin{document}
\maketitle
\section{Introduction}
This document contains guidelines on how to apply the CERN-OHL-S v2 to a given
hardware design, and on the use of hardware designs licensed under the
CERN-OHL-S v2. This means we will be talking to you sometimes as a licensor,
and
other times as a licensee.
As a licensor, there are many ways in which you can make it clear to your
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
can be done efficiently.
In order to help you distinguish between your obligations (mostly as a
licensee)
and our suggestions to you (mostly as a licensor), we will use the word `rule'
for the former and the word `suggestion' for the latter. Any perceived
contradiction between these guidelines and the licence text should of course be
resolved in favour of the licence text. \footnote{Lawyers among you may realise
that, technically, the CERN-OHL family of licences do not place any obligations
on Licensors at all (unless they are also licensees). However, if, as a
licensor, you do not comply with the "rules" you are not acting within the
spirit of the CERN-OHL, and you will almost certainly make it more difficult
for potential licensees to make use of the designs, something which contradicts
......@@ -84,7 +224,7 @@ whole
whole project in one go.
\end{enumerate}
If you goal is to share, it makes sense to provide enough information to users
If your goal is to share, it makes sense to provide enough information to users
about the contents of the design package they download, and to make it easy for
them to browse that information. For example, if you have designed your
hardware using proprietary tools, maybe people who download the design files
......@@ -156,7 +296,7 @@ by including a placeholder file called CHANGES.txt in your sources.
You may write a few lines in the beginning of the file stating that anyone
modifying the design provide brief information about the modifications,
including the date they were made, and stating that information should be
added but never removed from that file (except you are
added but never removed from that file (except where you are
sure that the changes listed only apply to a part of the file you are not
using), and that, according to section 3.3.b of the licence, licensees should
provide a brief entry with a date and the nature of the modification for each
......@@ -297,28 +437,8 @@ the design is licensed to you.
If your design is modular, it may well be helpful to 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
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.
each of the sub-components (this makes is easier for people to reuse parts of
your design separately).
\section{How to deal with hardware designs licensed under CERN-OHL-S v2}
......@@ -408,5 +528,7 @@ must
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}.
You may also find that the answer has already been covered in the FAQ at\\
\href{https://www.ohwr.org/project/cernohl/wikis/faq}.
\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