Skip to content

O
OHR Meta Project
Commit 0767641a authored by Javier Serrano's avatar Javier Serrano
Browse files
Options

First version based on OctConf 2017 slides

parent adc5e710
Hide whitespace changes
Inline Side-by-side
Showing with 433 additions and 0 deletions
presentations/icud_09_2017/Makefile 0 → 100644
View file @ 0767641a
all : js_icud_2017.pdf
.PHONY : all clean
js_icud_2017.pdf : js_icud_2017.tex
pdflatex $^; \
pdflatex $^
clean :
rm -f *.eps *.pdf *.dat *.log *.out *.aux *.dvi *.ps *.toc *.snm *.nav *~
presentations/icud_09_2017/js_icud_2017.tex 0 → 100644
View file @ 0767641a
\documentclass[compress,red]{beamer}
%\documentclass[compress,red, handout]{beamer}
\mode<presentation>
\setbeamertemplate{navigation symbols}{}
\usetheme{Warsaw}
%\hypersetup{pdfpagemode=FullScreen} % makes your presentation go automatically to full screen
% define your own colors:
\definecolor{Red}{rgb}{1,0,0}
\definecolor{Blue}{rgb}{0,0,1}
\definecolor{Green}{rgb}{0,1,0}
\definecolor{magenta}{rgb}{1,0,.6}
\definecolor{lightblue}{rgb}{0,.5,1}
\definecolor{lightpurple}{rgb}{.6,.4,1}
\definecolor{gold}{rgb}{.6,.5,0}
\definecolor{orange}{rgb}{1,0.4,0}
\definecolor{hotpink}{rgb}{1,0,0.5}
\definecolor{newcolor2}{rgb}{.5,.3,.5}
\definecolor{newcolor}{rgb}{0,.3,1}
\definecolor{newcolor3}{rgb}{1,0,.35}
\definecolor{darkgreen1}{rgb}{0, .35, 0}
\definecolor{darkgreen}{rgb}{0, .6, 0}
\definecolor{darkred}{rgb}{.75,0,0}
\xdefinecolor{olive}{cmyk}{0.64,0,0.95,0.4}
\xdefinecolor{purpleish}{cmyk}{0.75,0.75,0,0}
\useoutertheme[subsection=false]{smoothbars}
% include packages
\usepackage{subfigure}
\usepackage{multicol}
\usepackage{amsmath}
% \usepackage{epsfig} % Erik: didn't work with Miktex
\usepackage{graphicx}
\usepackage[all,knot]{xy}
\xyoption{arc}
\usepackage{url}
\usepackage{multimedia}
\usepackage{hyperref}
\usepackage{helvet}
\usepackage[polish,english]{babel}
\usepackage[utf8]{inputenc}
\usepackage{multirow}
%%%%%%%%%%%%5
%\usepackage{geometry}
%\geometry{verbose,letterpaper}
%\usepackage{movie15}
%\usepackage{hyperref}
\graphicspath{ {../../figures/} }
\title[Collaboration and Open Source \hspace{10em}\insertframenumber/\inserttotalframenumber]
{Collaboration and Open Source}
\subtitle{A CERN perspective}
\author
{Javier Serrano}
% - Give the names in the same order as the appear in the paper.
% - Use the \inst{?} command only if the authors have different
% affiliation.
\institute%[Universities of Somewhere and Elsewhere] % (optional, but mostly needed)
{
%\inst{1}%
% BE-CO Hardware and Timing section\\
CERN, Geneva, Switzerland
%\and
%\inst{2}%
%Department of Theoretical Philosophy\\
%University of Elsewhere
}
% - Use the \inst command only if there are several affiliations.
% - Keep it simple, no one is interested in your street address.
\date[ICUD 2017] %(optional, should be abbreviation of conference name)
{ICUD 2017\\
Prague, Czech Republic, 12 September 2017
}
% - Either use conference name or its abbreviation.
% - Not really informative to the audience, more for people (including
% yourself) who are reading the slides online
%\subject{Theoretical Computer Science}
% This is only inserted into the PDF information catalog. Can be left
% out.
% If you have a file called "university-logo-filename.xxx", where xxx
% is a graphic format that can be processed by latex or pdflatex,
% resp., then you can add a logo as follows:
%\pgfdeclareimage[height=1cm]{ohr-logo}{ohr_logo.jpg}
%\logo{\pgfuseimage{ohr-logo}}
% Delete this, if you do not want the table of contents to pop up at
% the beginning of each subsection:
\AtBeginSection[]
{
\begin{frame}<beamer>{Outline}
\tableofcontents[currentsection]
\end{frame}
}
% If you wish to uncover everything in a step-wise fashion, uncomment
% the following command:
%\beamerdefaultoverlayspecification{<+->}
\begin{document}
\begin{frame}
\titlepage
\end{frame}
\begin{frame}{Outline}
\tableofcontents
% You might wish to add the option [pausesections]
\end{frame}
% Structuring a talk is a difficult task and the following structure
% may not be suitable. Here are some rules that apply for this
% solution:
% - Exactly two or three sections (other than the summary).
% - At *most* three subsections per section.
% - Talk about 30s to 2min per frame. So there should be between about
% 15 and 30 frames, all told.
% - A conference audience is likely to know very little of what you
% are going to talk about. So *simplify*!
% - In a 20min talk, getting the main ideas across is hard
% enough. Leave out details, even if it means being less precise than
% you think necessary.
% - If you omit details that are vital to the proof/implementation,
% just say so once. Everybody will be happy with that.
\section[Introduction to OSHW]{Introduction to Open Source Hardware}
\subsection{}
\begin{frame}{A basic question}
Could hardware design be as easy to share as software?
\end{frame}
\begin{frame}{A basic question}
Why is this important?
\end{frame}
\begin{frame}{Empowerment}
\begin{center}
\includegraphics[height=0.85\textheight]{misc/fwatch-full-side.jpg}
\end{center}
\end{frame}
\begin{frame}{Empowerment}
\begin{center}
\includegraphics[height=0.85\textheight]{misc/ben_with_talon_beast.jpg}
\end{center}
\end{frame}
\begin{frame}{Empowerment}
\begin{center}
\includegraphics[height=0.85\textheight]{misc/momo-installation.jpg}
\end{center}
\end{frame}
\begin{frame}{Empowerment}
\begin{center}
\includegraphics[height=0.85\textheight]{misc/safecast.jpg}
\end{center}
\end{frame}
\begin{frame}{There is an OSHW definition!}
\begin{block}{Check out \href{http://www.oshwa.org/definition/}{http://www.oshwa.org/definition/}}
\begin{itemize}
\item Inspired by the Open Source definition for software.
\item Focuses on ensuring freedom to study, modify, distribute, make
and sell designs or hardware based on those designs.
\item Now we know exactly what we mean when we say OSHW!
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{CERN Open Hardware License \href{http://ohwr.org/cernohl}{-- ohwr.org/cernohl}}
\begin{block}{Provides a solid legal basis}
\begin{itemize}
\item Developed in collaboration with Knowledge Transfer Group at CERN.
\item Better suited than non-HW licenses (GNU GPL, Creative Commons\dots)
\item Defines conditions for using and modifying licensed material.
\end{itemize}
\end{block}
\pause
\begin{block}{Provides a clear legal environment}
\begin{itemize}
\item Written in a clear, concise style.
\item Easy for licensors to evaluate if it is good for them.
\end{itemize}
\end{block}
\end{frame}
\section[OSHW in practice]{Open Source Hardware in practice}
\subsection{}
\begin{frame}{Example of a project in the Open Hardware Repository
\href{http://ohwr.org}{-- ohwr.org}}
\begin{center}
\includegraphics[height=6cm]{../pictures/ohwr/ohr_spec_top.jpg}
\end{center}
\end{frame}
\begin{frame}{Open source and the unexpected}
\begin{center}
\includegraphics[width=\textwidth]{../../figures/applications/wr_other_apps.jpg}
\end{center}
\end{frame}
\begin{frame}{Business models}{Dispelling the commercial vs open myth}
\begin{center}
\includegraphics[width=\textwidth]{../pictures/ohwr/commercial_and_open.pdf}
\end{center}
\end{frame}
\begin{frame}{SPEC: Simple PCI Express FMC carrier}
{Made in Spain, The Netherlands \& Poland}
\begin{center}
\includegraphics[height=6.5cm]{../pictures/ohwr/SPEC_top_high_res.jpg}
\end{center}
\end{frame}
\begin{frame}{Where the rubber meets the road}{Seven years
of experience at CERN}
\begin{center}
\includegraphics[height=6.5cm]{../pictures/ohwr/ohr_companies.png}
\end{center}
\end{frame}
\begin{frame}{Free-as-in-freedom design tools}{The last hurdle to
efficient sharing}
\begin{center}
\includegraphics[width=\textwidth]{misc/kicad_screenshot.png}
\end{center}
\end{frame}
% \begin{frame}{Other perceived benefits}
% \begin{block}{Motivation and recognition}
% \begin{itemize}
% \item Designers prefer collaboration rather than work in isolation.
% \item Easy to gain a reputation based on one's work.
% \item Easier hiring.
% \item Part of the commercial strategy of many companies.
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{For small and medium-size companies}
% \begin{itemize}
% \item Lower barriers to market.
% \item Easier to bring in extra talent, even from the client!
% \end{itemize}
% \end{block}
% \end{frame}
% \begin{frame}{Perceived issues}
% \begin{block}{Where does this stop?}
% \begin{itemize}
% \item Layers of openness.
% \item ASIC design slowly becoming more accessible (e.g. lowRISC).
% \item Commodity hardware not so critical.
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{Will I find providers if I specify OSHW?}
% \begin{itemize}
% \item For better or worse, it's a free market out there.
% \item Nothing specific to OSHW.
% \end{itemize}
% \end{block}
% \end{frame}
% \begin{frame}{Perceived issues}
% \begin{block}{The expectation management department}
% \begin{itemize}
% \item Can I really control all manufacturing and distribution
% of an OSHW design I release?
% \item Comparing apples-to-apples: how much has been invested
% in a given OSHW solution?
% \item I published and I did not get any bug fix!
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{Will people steal my design and make money off it?}
% \begin{itemize}
% \item Yes, even if it's not OSHW (unless it's very complicated
% and you have a large legal department).
% \item But hey, Arduino survives! Why?
% \end{itemize}
% \end{block}
% \end{frame}
% \begin{frame}{Perceived issues}
% \begin{block}{I can't afford the initial investment}
% \begin{itemize}
% \item OSHW designs are often a show case for a group,
% institution or company.
% \item Can't cut corners on quality. Should not be bad in principle.
% \item May not be adequate given the context. OSHW is not for
% everyone all the time.
% \end{itemize}
% \end{block}
% \end{frame}
% \begin{frame}{Recipes for success}
% \begin{block}{Common sense!}
% \begin{itemize}
% \item Identify the problem that needs solving, prepare plan,
% get good team, track progress, document\ldots
% \item Nothing OSHW-specific here.
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{Enlarge your scope}
% \begin{itemize}
% \item Use standards.
% \item Be flexible if you want to attract talent.
% \end{itemize}
% \end{block}
% \pause
% \begin{block}{Choose good partners}
% Your interests do not need to align completely, just enough
% to walk a part of the path together.
% \end{block}
% \end{frame}
\section[Public institutions]{Public Institutions}
\subsection{}
\begin{frame}{Public institutions}
\begin{block}{They serve the interests of a whole society}
\begin{itemize}
\item Try to maximize 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.
\item Liaising with other public institutions to reach
critical mass.
\item Also with their procurement hat.
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{Dissemination}
\begin{center}
\includegraphics[height=0.8\textheight]{misc/cern_council.jpg}
\end{center}
\end{frame}
\begin{frame}{How to interpret one's dissemination mandate in the 21\textsuperscript{st}
century}
\begin{center}
\includegraphics[height=0.8\textheight]{misc/cern_and_openness.jpg}
\end{center}
\end{frame}
\begin{frame}{The funding agencies conundrum}
\begin{center}
\includegraphics[height=0.8\textheight]{misc/flags.jpg}
\end{center}
\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}
\section{Outlook}
\subsection{}
\begin{frame}{KiCad plans}
\begin{block}{Give it a try in CERN's drawing office}
\begin{itemize}
\item Have PCB layout professionals provide UX feedback.
\item Fix KiCad and iterate.
\end{itemize}
\end{block}
\pause
\begin{block}{Propose purchase of a KiCad support contract}
\begin{itemize}
\item Including provision for new developments.
\item A paid supporting entity is a requirement of potential
users and helps sustain the project.
\end{itemize}
\end{block}
\end{frame}
\begin{frame}{So, can all this apply to other cases?}
\begin{center}
\includegraphics[height=6.5cm]{misc/Tuxoid_OHWR-logo_RC_V1.png}
\end{center}
\end{frame}
\end{document}
\ No newline at end of file
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