|
|
@@ -1,5 +1,7 @@
|
|
|
\documentclass{beamer}
|
|
|
+%\setbeamercovered{transparent}
|
|
|
\usetheme{poul}
|
|
|
+%\usetheme{Madrid}
|
|
|
\usepackage[utf8]{inputenc}
|
|
|
\usepackage[svgpath=images/]{svg}
|
|
|
\usepackage{graphicx}
|
|
|
@@ -259,7 +261,7 @@
|
|
|
\includegraphics[width=0.9\textwidth,height=0.5\textheight]{gitlab2}
|
|
|
\end{center}
|
|
|
\footnotetext{\url{https://docs.google.com/document/d/1GCK53YDcBWQveod9kfzW-VCxIABGiryG7_z_6jHdVik/pub}}
|
|
|
- \pause
|
|
|
+ %\pause
|
|
|
%\footnotesize{I don't want to put shame on GitLab for this incident, but only to use it as a case study.\\ In fact I think that the incident has been managed really well by the GitLab Team.\\
|
|
|
%Instead of starting blaming each other and finding silly excuses as usually happens in cases like this, they have been really open from the beginning about the problem and put as a priority the restore of the functionality of the service.}
|
|
|
|
