Skip to content

O
OHR Meta Project
Commit 494d43be authored by Javier Serrano's avatar Javier Serrano
Browse files
Options

Conclusions and logo

parent 6c7bde03
Hide whitespace changes
Inline Side-by-side
Showing with 78 additions and 3 deletions
presentations/cern_ospo_2023/cern_ospo_2023_11.tex
View file @ 494d43be
......@@ -183,7 +183,18 @@
\end{frame}
\begin{frame}{Other things the OSPO will do:}
\begin{itemize}
\item Maintain a catalogue of open-source software and hardware published by
CERN.
\item Organise courses in collaboration with HR-LD.
\item Liaise with IPT-PI in matters regarding the procurement of open-source
products.
\item Define metrics for Open Source adoption at CERN and publish a yearly
report.
\end{itemize}
\end{frame}
\section[Why]{Why an OSPO}
\subsection{}
......@@ -274,17 +285,81 @@ is the position of CERN on issue xyz related to Open Source?''
\begin{center}
\includegraphics[height=0.8\textheight]{misc/hpm7177_praise.png}
\end{center}
\end{frame}
\section[How]{How the OSPO will operate}
\subsection{}
\begin{frame}{The main use case: ``I want to open-source my project''}
\begin{block}{Software}
Get in touch by writing to Open.Source@cern.ch
\end{block}
\begin{block}{Hardware}
The entry point for dissemination in this case is KT. Contact them for advice
and the OSPO will be involved if you decide to open-source the designs.
\end{block}
\end{frame}
\begin{frame}{Most common questions will hopefully be answered in:}
\begin{block}{The OSPO website (\href{https://opensource.cern}{https://opensource.cern})}
This site contains information about the OSPO itself and is more
``outreachy'' in nature.
\end{block}
\begin{block}{The documentation website (\href{https://ospo.docs.cern.ch}{https://ospo.docs.cern.ch})}
This site will contain best practices for open-sourcing your software, gateware
and hardware projects, including tools, community management and legal aspects.
It will also cover how to participate in externally-managed (i.e. non-CERN)
projects and how to integrate external open-source components in your projects.
\end{block}
\end{frame}
\begin{frame}{``My question is not answered in any of the above''}
\begin{block}{For questions which you feel at ease discussing in public:}
Ask in the forum ({\color{blue}
\href{https://ospo.web.cern.ch/}{https://ospo.web.cern.ch/}}). In that
way, others will also benefit from the discussion.
\end{block}
\begin{block}{For any other question:}
Write to Open.Source@cern.ch or get in touch directly with any member of the
OSPO.\\See the list at {\color{blue}
\href{https://opensource.cern/who_we_are}{https://opensource.cern/who\_we\_are}}.
\end{block}
\end{frame}
\section[How]{How the OSPO will operate}
\section[Who]{The team}
\subsection{}
\section[Who]{The team}
\begin{frame}{The team}
The CERN OSPO is a community endeavour. We want many people to participate.
This is the current list of members: Matthias Bonora (TE), Hamza Boukabache
(HSE), Andriy Boychenko (HSE), Sunje Dallmeier-Tiessen (RCS-SIS), Han Dols
(KT), Philip Elson (BE), Axel Naumann (EP, Chair), Giacomo Tenaglia (IT),
Javier Serrano (BE) and Alexander Yohei Huss (TH), with the precious help of
Victoria Huisman Sigcha (IT-CA) Hafsa Saboor (RCS-SIS) and Antonia Winkler
(RCS-SIS).
\end{frame}
\section*{}
\subsection{}
\begin{frame}{Links and further discussion}
\begin{center}
\includegraphics[height=0.3\textheight]{misc/cern_ospo_logo.png}
\end{center}
OSPO website: {\color{blue}
\href{https://opensource.cern}{https://opensource.cern}}\\
Documentation website: {\color{blue}
\href{https://ospo.docs.cern.ch}{https://ospo.docs.cern.ch}}\\
OSPO forum: {\color{blue}
\href{https://ospo.web.cern.ch/}{https://ospo.web.cern.ch/}}\\
OSPO email address: {\color{blue}
\href{mailto:Open.Source@cern.ch}{Open.Source@cern.ch}} \\ \vspace{20px}
Join us for more in-depth discussion tomorrow at 14:00 in the Main Auditorium:
{\color{blue} \href{https://indico.cern.ch/event/1327563/}{https://indico.cern.ch/event/1327563/}}.
\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