Skip to content

O
OHR Meta Project
Commit 1190c412 authored by Javier Serrano's avatar Javier Serrano
Browse files
Options

Streamlined presentation

parent 0bb63a5e
Hide whitespace changes
Inline Side-by-side
Showing with 122 additions and 152 deletions
presentations/openuk_2021/js_openuk_2021.tex
View file @ 1190c412
......@@ -56,7 +56,7 @@
\graphicspath{ {../../figures/} }
\title[Open Hardware at CERN\hspace{9em}\insertframenumber/\inserttotalframenumber]
\title[Open Hardware at CERN\hspace{11em}\insertframenumber/\inserttotalframenumber]
{Open Hardware at CERN}
%\subtitle{An Introduction}
......@@ -80,8 +80,8 @@
% - Use the \inst command only if there are several affiliations.
% - Keep it simple, no one is interested in your street address.
\date[Future Leaders' training] %(optional, should be abbreviation of conference name)
{OpenUK's Future Leaders' training\\
\date[Future Leaders training] %(optional, should be abbreviation of conference name)
{OpenUK's Future Leaders training\\
5 February 2021
}
% - Either use conference name or its abbreviation.
......@@ -121,7 +121,6 @@
\end{frame}
\begin{frame}{Outline}
\tableofcontents
% You might wish to add the option [pausesections]
......@@ -177,7 +176,7 @@
\end{block}
\end{frame}
\begin{frame}{Challenges in Open Hardware}
\begin{frame}{Challenges we saw in Open Hardware ten years ago}
\begin{itemize}
\item Curated repositories of \textbf{high-quality designs} with version control and
forums
......@@ -195,6 +194,97 @@
\end{center}
\end{frame}
\section{Open Hardware Licensing}
\subsection{}
\begin{frame}{Software licensing: our starting point}
\begin{block}{Mostly copyright licences}
\begin{itemize}
\item Very uniform legal landscape worldwide
\item Modern licences also deal with patents
\end{itemize}
\end{block}
\pause
\begin{block}{Three licensing regimes}
\begin{itemize}
\item Permissive (BSD, MIT, Apache v2)
\item Weakly reciprocal (MPL v2, LGPL v3)
\item Strongly reciprocal (GPL v3, AGPL v3)
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{Challenges in hardware licensing}
\begin{block}{Rights for hardware}
Copyright does not generally apply to physical objects
\end{block}
\pause
\begin{block}{Patents}
Much more prevalent in hardware than in software
\end{block}
\pause
\begin{block}{Reciprocity}
What should a reciprocal licence do for a hardware design? What is the scope
of reciprocity?
\end{block}
\pause
\begin{block}{The hardware design ecosystem}
Dominated by proprietary tools, parts of which sometimes go into the design itself
\end{block}
\end{frame}
\begin{frame}{The CERN Open Hardware Licence v2}
\begin{itemize}
\item Based on rights mainly applying to the design sources (e.g. circuit
schematics or CAD drawings)
\pause
\item Specifies conditions for:
\begin{itemize}
\item Copying designs
\item Modifying designs
\item Distributing modified or unmodified designs
\item Making hardware out of those designs
\item Distributing that hardware
\end{itemize}
\pause
\item Drafted by Myriam Ayass, Andrew Katz and Javier Serrano
\pause
\item Comes in three variants:
\begin{itemize}
\item CERN-OHL-P-2.0 (permissive)
\item CERN-OHL-W-2.0 (weakly reciprocal)
\item CERN-OHL-S-2.0 (strongly reciprocal)
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}{Challenges in hardware licensing}{How CERN OHL v2 deals with them}
\begin{block}{Rights for hardware}
CERN OHL v2 makes no assumption about rights
\end{block}
\pause
\begin{block}{Patents}
Two-way patent licensing clauses
\end{block}
\pause
\begin{block}{Reciprocity}
Have URL travel with object and use concepts of Product and Available
Component to establish limits of reciprocal obligations
\end{block}
\pause
\begin{block}{The hardware design ecosystem}
Components which are shipped with design tools qualify as Available Components
\end{block}
\end{frame}
\begin{frame}{CERN OHL v2 for PCB designs}
\begin{center}
\includegraphics[width=\textwidth]{misc/cern_ohl_variants_pcb.jpg}
\end{center}
\end{frame}
\section[White Rabbit]{White Rabbit}
\subsection{}
......@@ -225,7 +315,7 @@
\end{columns}
\end{frame}
\begin{frame}{The need for synchronisation in a particle accelerator}
\begin{frame}{How do you make two distant places agree on time?}
\begin{center}
\includegraphics[height=6.5cm]{protocol/ptp_exchange.pdf}
\end{center}
......@@ -313,175 +403,55 @@
reciprocal open source licences
\end{itemize}
\end{block}
\pause
\end{frame}
\section{Open Hardware Licensing}
\subsection{}
\begin{frame}{Software licensing: our starting point}
\begin{block}{Mostly copyright licences}
\begin{itemize}
\item Very uniform legal landscape worldwide
\item Modern licences also deal with patents
\end{itemize}
\end{block}
\pause
\begin{block}{Three licensing regimes}
\begin{itemize}
\item Permissive (BSD, MIT, Apache v2)
\item Weakly reciprocal (MPL v2, LGPL v3)
\item Strongly reciprocal (GPL v3, AGPL v3)
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{Challenges in hardware licensing}
\begin{block}{Rights for hardware}
Copyright does not generally apply to physical objects
\end{block}
\pause
\begin{block}{Patents}
Much more prevalent in hardware than in software
\end{block}
\pause
\begin{block}{Reciprocity}
What should a reciprocal licence do for a hardware design? What is the scope
of reciprocity?
\end{block}
\pause
\begin{block}{The hardware design ecosystem}
Dominated by proprietary tools, parts of which sometimes go into the design itself
\end{block}
\end{frame}
\begin{frame}{The CERN Open Hardware Licence v2}
\begin{itemize}
\item Based on rights mainly applying to the design sources (e.g. circuit
schematics or CAD drawings)
\pause
\item Specifies conditions for:
\begin{itemize}
\item Copying designs
\item Modifying designs
\item Distributing modified or unmodified designs
\item Making hardware out of those designs
\item Distributing that hardware
\end{itemize}
\pause
\item Drafted by Myriam Ayass, Andrew Katz and Javier Serrano
\pause
\item Comes in three variants:
\begin{itemize}
\item CERN-OHL-P-2.0 (permissive)
\item CERN-OHL-W-2.0 (weakly reciprocal)
\item CERN-OHL-S-2.0 (strongly reciprocal)
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}{Challenges in hardware licensing}{How CERN OHL v2 deals with them}
\begin{block}{Rights for hardware}
CERN OHL v2 makes no assumption about rights
\end{block}
\pause
\begin{block}{Patents}
Two-way patent licensing clauses
\end{block}
\pause
\begin{block}{Reciprocity}
Have URL travel with object and use concepts of Product and Available
Component to establish limits of reciprocal obligations
\end{block}
\pause
\begin{block}{The hardware design ecosystem}
Components which are shipped with design tools qualify as Available Components
\end{block}
\end{frame}
\begin{frame}{CERN OHL v2 for PCB designs}
\begin{center}
\includegraphics[width=\textwidth]{misc/cern_ohl_variants_pcb.jpg}
\end{center}
\end{frame}
\begin{frame}{CERN OHL v2 for HDL/FPGA/ASIC designs}
\begin{center}
\includegraphics[width=\textwidth]{misc/cern_ohl_variants_hdl.jpg}
\end{center}
\end{frame}
\section{Public institutions}
\subsection{}
\begin{frame}{Public institutions}
\begin{block}{They serve the interests of a whole society}
\begin{itemize}
\item Try to maximise positive impact of decisions.
\item Not always easy.
\item Try to maximise positive impact of decisions
\item Not always easy
\end{itemize}
\end{block}
\pause
\begin{block}{Can be ``tractor'' institutions}
\begin{itemize}
\item To help take projects to a mature state where they can
be sustained commercially.
be sustained commercially
\item Liaising with other public institutions to reach
critical mass.
\item Also with their procurement hat.
critical mass
\item Also with their procurement hat
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{Issues with ``coopetition''}
Research groups sometimes (often?) end up behaving as private
companies (but with public money!) because of wrong incentives by
funding agencies.
\end{frame}
\begin{frame}{The funding agencies conundrum}
\begin{center}
\includegraphics[height=0.8\textheight]{misc/flags.jpg}
\end{center}
\end{frame}
\begin{frame}{Things I believe we did right in the White Rabbit
project}
\begin{block}{For the WR community}
\begin{itemize}
\item Open source
\item Lively welcoming environment via mailing list and periodic workshops
\end{itemize}
\end{block}
\pause
\begin{block}{For companies}
\begin{itemize}
\item Growing open source core
\item Space in the periphery for proprietary innovation
\end{itemize}
\end{block}
\begin{frame}{Public institutions}
\begin{block}{They often have it in their mandates to contribute to the commons}
\begin{itemize}
\item Pressure to self-finance can sometimes lead to proprietary
developments with less impact
\item It would help if somebody solved the impact tracking and retribution issues in
open-source
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{Things I believe we did right in the White Rabbit
project}
\begin{block}{For tax payers}
\begin{itemize}
\item Enlarge the scope of our original project
\item Use standard technologies and standardise our enhancements
under IEEE 1588
\item Open source
\end{itemize}
\end{block}
And, in general, ensuring a coordinating and facilitating role to
make sure the whole project runs smoothly.
\begin{frame}{Public institutions}
\begin{block}{Introducing ``Public Core'' (and seeking feedback!)}
\begin{itemize}
\item Incentives in ``Open Core'' are not always conducive to an
ever-expanding open-source core
\item The actors in charge of the core must have an interest in seeing
it grow
\item Public institutions are natural candidates for such a role
\item Private companies can develop proprietary innovations at the
periphery and move further out as the core expands
\end{itemize}
\end{block}
\end{frame}
\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