Incorporate feedback

bd5af2f1 · Javier Serrano · 2cb95aa9 · bd5af2f1
Commit bd5af2f1 authored Nov 30, 2020 by Javier Serrano
Hide whitespace changes
Inline Side-by-side

Showing with 46 additions and 13 deletions

js_cernohl_12_2020.tex presentations/ch_open_cernohl_12_2020/js_cernohl_12_2020.tex +46 -13

No files found.
--- a/presentations/ch_open_cernohl_12_2020/js_cernohl_12_2020.tex
+++ b/presentations/ch_open_cernohl_12_2020/js_cernohl_12_2020.tex
@@ -81,7 +81,7 @@
 % - Keep it simple, no one is interested in your street address.

 \date[Open Science Monitor Webinar] %(optional, should be abbreviation of conference name)
-{CH Open and why! Computing online presentation\\
+{\emph{CH Open} and \emph{why! Computing} online presentation\\
 1 December 2020
 }
 % - Either use conference name or its abbreviation.
@@ -169,12 +169,12 @@
 \begin{frame}{Challenges in Open Hardware}
  \begin{itemize}
   \item Curated repositories of high-quality designs with version control and
-     forums.
-   \item Discussions with commercial companies on business models.
+     forums
+   \item Discussions with commercial companies on business models
   \item Free and Open Source Software tools to design hardware and easily share
-     those designs.
+     those designs
   \item A sound legal basis for sharing in the form of a good set of \textbf{Open
-     Hardware Licences}.
+     Hardware Licences}
  \end{itemize}
 \end{frame}

@@ -185,15 +185,15 @@
 \begin{frame}{The Holy Trinity of ``Intellectual Property''}

 \begin{block}{Copyright}
-deals with the right to make copies.
+generally deals with the right to make copies
 \end{block}
 \pause
 \begin{block}{Trademarks}
-define under what circumstances you can use a recognisable brand or logo.
+define under what circumstances you can use a recognisable brand or logo
 \end{block}
 \pause
 \begin{block}{Patents}
-allow an inventor to exclude others from making, using or selling an invention.
+allow an inventor to exclude others from making, using or selling an invention
 \end{block}

 \end{frame}
@@ -226,11 +226,11 @@ allow an inventor to exclude others from making, using or selling an invention.

 \begin{frame}{Challenges in hardware licensing}
  \begin{block}{Rights for hardware}
-   Copyright does not apply in principle to physical objects
+   Copyright does not generally apply to physical objects
  \end{block}
  \pause
  \begin{block}{Patents}
-   Much more prevalent than in software
+   Much more prevalent in hardware than in software
  \end{block}
  \pause
  \begin{block}{Reciprocity}
@@ -310,19 +310,52 @@ allow an inventor to exclude others from making, using or selling an invention.

 \begin{frame}{What should I do with the software embedded in my hardware
    projects?}
-
+Feel free to use your favourite software licence. You can use CERN OHL v2 for
+``non-gateware'' software (with the different variants behaving as expected) but
+we don't encourage it because:
+\begin{itemize}
+  \item there are already very good software licences out there
+  \item for reciprocal variants there can be compatibility issues (licence
+    proliferation is a well-known problem in the reciprocal space)
+\end{itemize}
 \end{frame}

 \begin{frame}{Are there cases in which the reciprocity provisions will be less effective?}
-
+Yes. Most of the time, CERN OHL v2 will rely on rights associated with the
+design files (drawings, HDL\ldots) such as copyright. Projects in which these
+design files do not play an important role will be missing this essential
+ingredient. E.g. object modifications which do not rely on modifications of the
+design files will not be subject to the same obligations.
 \end{frame}

 \begin{frame}{Are the reciprocal variants of CERN OHL v2 compatible with GPL?}
-
+No. This was a tough decision, but making the W and S variants compatible with
+GPL would have offered licensees an easy way to escape certain obligations, such
+as the need to keep a visible URL on an object at which to find the design
+files from which the object was created.
 \end{frame}

 \section{Conclusion}
 \subsection{}
+\begin{frame}{Short recap}
+  \begin{itemize}
+    \item CERN OHL v2 provides designers with a sound legal basis to share
+      Open Hardware designs effectively
+    \item Three licensing regimes:
+      \begin{itemize}
+      \item Permissive
+      \item Weakly reciprocal
+      \item Strongly reciprocal
+      \end{itemize}
+      \item Strong effort on solving some issues in reciprocal licensing for
+        hardware, including HDL/FPGA/ASIC
+      \item A community project itself, get in touch if you have questions or suggestions!
+  \end{itemize}

+  \begin{center}
+    Licence texts, rationale, FAQs and forum at
+    \href{https://ohwr.org/cernohl}{https://ohwr.org/cernohl}    
+  \end{center}
+\end{frame}

 \end{document}