Extras draft

extras/extras.tex

+\documentclass[slidestop]{beamer}
+
+\usepackage{framed}
+\usepackage{booktabs}
+
+\input{../shared/shared.tex}
+
+\author{Mihai Lefter}
+\title{\courseTitle}
+\providecommand{\mySubTitle}{Extras: GitLab, Markdown.}
+\providecommand{\myConference}{\courseTitle}
+\providecommand{\myGroup}{}
+\providecommand{\myDepartment}{Department of Human Genetics}
+\providecommand{\myCenter}{Center for Human and Clinical Genetics}
+
+\definecolor{cblack}{rgb}{0,0,0}
+\definecolor{cwhite}{rgb}{1,1,1}
+\definecolor{command-color}{rgb}{0,0.5,0}
+\definecolor{git-color}{rgb}{0.94,0.23,0.18}
+\definecolor{option-color}{rgb}{0.9,0.2,0.11}
+\definecolor{argument-color}{rgb}{0.11,0.27,0.7}
+\definecolor{pattern-color}{rgb}{0,0.5,0.5}
+\definecolor{wildcard-color}{rgb}{0.75,0.3,0}
+\definecolor{cli-text}{rgb}{0.15,0.15,0.15}
+\definecolor{important-note}{rgb}{0.69,0.13,0.13}
+\definecolor{redirection}{rgb}{0.99,0.13,0.13}
+\definecolor{shadecolor}{rgb}{0.9,0.9,0.9}
+\definecolor{one-dot}{rgb}{0.9,0.2,0.0}
+\definecolor{two-dots}{rgb}{0.11,0.11,0.8}
+\definecolor{slash}{rgb}{0.3,0.3,0.3}
+
+\definecolor{head}{HTML}{B22222}
+\definecolor{branch}{HTML}{20b2aa}
+\definecolor{commit-id}{HTML}{b8860b}
+
+\usetheme{lumc}
+
+\lstset{
+  basicstyle=\ttfamily,
+  language=none,
+  frame=none,
+  numbers=none,
+  numbersep=0
+}
+
+\AtBeginSection[]
+{
+  \begin{frame}
+    \frametitle{Table of contents}
+    \tableofcontents[currentsection, subsectionstyle=hide/hide]
+  \end{frame}
+}
+
+\begin{document}
+
+% This disables the \pause command, handy in the editing phase.
+%\renewcommand{\pause}{}
+
+% Make the title page.
+\makeTitleSlide{\includegraphics[width=3.5cm]{../shared/git_logo.pdf}}
+
+\section{GitLab}
+
+\subsection{Collaborative working environent}
+\begin{pframe}
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_00.pdf} 
+ \end{center}
+\end{pframe}
+
+\begin{pframe}
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_01.pdf} 
+ \end{center}
+\end{pframe}
+
+\begin{pframe}
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_02.pdf} 
+ \end{center}
+\end{pframe}
+
+\begin{pframe}
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_03.pdf} 
+ \end{center}
+\end{pframe}
+
+\subsection{Projects}
+\begin{pframe}
+ Every project belongs to a single namespace, either a:
+ \begin{itemize}
+  \item User: 
+  \begin{itemize}
+   \item The project owner has direct control over the project.
+  \end{itemize}
+  \item Group: 
+  \begin{itemize}
+   \item The group's user-level permissions will take effect.
+  \end{itemize}
+ \end{itemize}
+ \medskip
+ Every project has a visibility level:
+ \begin{itemize}
+  \item A way of controling who has \textbf{read} access to that project.
+  \item Note that this controls both git ``fetch'' access as well as access to the web UI for that project.
+ \end{itemize}
+\end{pframe}
+
+\subsection{Project visibility levels}
+\begin{pframe}
+  \begin{itemize}
+    \item Private projects:
+    \begin{itemize}
+      \item The project owner must explicitly grant access to specific users.
+      \item Are not listed on the public access directory.
+    \end{itemize}
+  \end{itemize}
+  
+  \begin{itemize}
+    \item Internal projects:
+    \begin{itemize}
+      \item Can be cloned by any logged in user.
+      \item Are listed on the public access directory for logged in users.
+      \item Logged in users have Guest permissions on the repository.
+    \end{itemize}
+  \end{itemize}
+  
+  \begin{itemize}
+    \item Public projects:
+    \begin{itemize}
+      \item Can be cloned without any authentication.
+      \item Are listed on the public access directory.
+      \item Logged in users have Guest permissions on the repository.
+    \end{itemize}
+  \end{itemize}
+\end{pframe}
+
+\subsection{Project permissions}
+\begin{pframe}
+  \vspace{-0.3cm}
+  \begin{table}[]
+    \centering
+    \label{my-label}
+    \scalebox{0.6}{
+    \begin{tabular}{lccccc}
+      \toprule
+      Action                  & Guest      & Reporter   & Developer  & Master     & Owner      \\
+      \midrule
+      Create new issue        & \checkmark & \checkmark & \checkmark & \checkmark & \checkmark \\
+      Leave comments          & \checkmark & \checkmark & \checkmark & \checkmark & \checkmark \\
+      View wiki pages         & \checkmark & \checkmark & \checkmark & \checkmark & \checkmark \\
+      Pull project code       &            & \checkmark & \checkmark & \checkmark & \checkmark \\
+      Download project        &            & \checkmark & \checkmark & \checkmark & \checkmark \\
+      Manage/Accept merge requests &       &            & \checkmark & \checkmark & \checkmark \\
+      Create new merge request &           &            & \checkmark & \checkmark & \checkmark \\
+      Push to non-protected branches &     &            & \checkmark & \checkmark & \checkmark \\
+      Write a wiki            &            &            & \checkmark & \checkmark & \checkmark \\
+      Create new milestones   &            &            &            & \checkmark & \checkmark \\
+      Add new team members    &            &            &            & \checkmark & \checkmark \\
+      Edit project            &            &            &            & \checkmark & \checkmark \\
+      Switch visibility level &            &            &            &            & \checkmark \\ 
+      Transfer project to another namespace &            &            &            &            & \checkmark \\
+      Remove project          &            &            &            &            & \checkmark \\
+      \bottomrule
+    \end{tabular}}
+  \end{table}
+  \vspace{-0.3cm}
+  \begin{itemize}
+   \item Check the entire list \textcolor{cyan}{\href{https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/user/permissions.md}{here}}.
+   \item On public and internal projects the Guest role is not enforced.
+   \item GitLab administrators receive all permissions.
+  \end{itemize}
+\end{pframe}
+
+\subsection{Group permissions}
+\begin{pframe}
+  \begin{table}[]
+    \centering
+%     \caption{My caption}
+    \label{my-label}
+    \scalebox{0.6}{
+    \begin{tabular}{lccccc}
+      \toprule
+      Action                  & Guest      & Reporter   & Developer  & Master     & Owner      \\
+      \midrule
+      Browse group            & \checkmark & \checkmark & \checkmark & \checkmark & \checkmark \\
+      Edit group              &            &            &            &            & \checkmark \\
+      Create project in group &            &            &            & \checkmark & \checkmark \\
+      Manage group members    &            &            &            &            & \checkmark \\
+      Remove group            &            &            &            &            & \checkmark \\
+      \bottomrule
+    \end{tabular}}
+  \end{table}
+  If a user is both in a group's project and the project itself, the highest permission level is used.
+\end{pframe}
+
+
+\subsection{Collaborative working environent}
+
+\begin{pframe}
+% issues
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_04.pdf} 
+ \end{center}
+\end{pframe}
+
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=0.7\textwidth]{images/issues.pdf}
+  \end{center}
+\end{pframe}
+
+\begin{pframe}
+% labels
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_06.pdf} 
+ \end{center}
+\end{pframe}
+
+\begin{pframe}
+% milestones
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_05.pdf} 
+ \end{center}
+\end{pframe}
+
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=\textwidth]{images/milestones.pdf}
+  \end{center}
+\end{pframe}
+
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=\textwidth]{images/issue_board.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Collaborative working environent}
+
+\begin{pframe}
+% to do
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_07.pdf} 
+ \end{center}
+\end{pframe}
+
+% \subsection{Todos}
+% \begin{pframe}
+%   A chronological list of things that are waiting for your input.
+%   \bigskip
+%   
+%   Todos allow you to see where:
+%   \begin{itemize}
+%    \item You should spend your time.
+%    \item Your team members need help.
+%    \item You need to take some action.
+%    \item You need to keep an eye on.
+%   \end{itemize}
+%   \bigskip
+%   
+%   Note that Todos are personal.
+% \end{pframe}
+% 
+% \subsection{Todos triggering}
+% \begin{pframe}
+%   A Todo is triggered when:
+%   \begin{itemize}
+%    \item An issue is assigned to you.
+%    \item You are @mentioned in an issue.
+%    \begin{itemize}
+%     \item Be it the description or in a comment.
+%    \end{itemize}
+%   \end{itemize}
+%   \bigskip
+% 
+%   You can also manually add an issue to your Todos list.
+%   \bigskip
+% 
+%   Note that there is just one Todo per issue.
+% \end{pframe}
+% 
+% \subsection{Todos dismissal}
+% \begin{pframe}
+%   Any of the following action to the corresponding issue will mark your Todo as Done:
+%   \begin{itemize}
+%     \item Changing the assignee.
+%     \item Changing the milestone.
+%     \item Adding/removing a label.
+%     \item Commenting on the issue.
+%   \end{itemize}
+%   \bigskip
+%   
+%   You can also manually mark the Todo as done.
+%   \bigskip
+% 
+%   Todos are only marked as Done if the action is coming from you.
+% \end{pframe}
+
+\subsection{Collaborative working environent}
+
+\begin{pframe}
+% wiki
+ \begin{center}
+  \includegraphics[width=1\textwidth]{images/gitlab_wrapper/gitlab_wrapper_08.pdf} 
+ \end{center}
+\end{pframe}
+
+% \subsection{Wiki}
+% \begin{pframe}
+%   Keep your project documentation using the built-in wiki system.
+%   \bigskip
+%   
+%   \begin{itemize}
+%    \item Available formats:
+%    \begin{itemize}
+%     \item Markdown.
+%     \item RDoc.
+%     \item AsciiDoc.
+%    \end{itemize}
+%   \end{itemize}
+% \end{pframe}
+
+\section{Markdown}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=0.5\textwidth]{images/markdown-slide.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{What is markdown?}
+\begin{pframe}
+  \begin{itemize}
+    \item A plain text format that makes any document easy-to-write and easy-to-read.
+    \item Various flavors exist:
+    \begin{itemize}
+     \item GitLab Flavored Markdown (GFM).
+    \end{itemize}
+    \item All ``.md'' files are automatically rendered in GitLab.
+    \item Ideally, every directory in the project has a README.md file.
+  \end{itemize}
+\end{pframe}
+
+\subsection{Used for}
+\begin{pframe}
+  \begin{itemize}
+   \item Comments.
+   \item Issues descriptions / comments.
+%    \item Merge requests.
+   \item Milestones descriptions.
+   \item Wiki pages.
+   \item Markdown documents inside the repository.
+  \end{itemize}
+\end{pframe}
+
+\subsection{Headers}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_01.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Emphasis}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_02.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Lists}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_03.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Links}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_04.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Images}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_05.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Line breaks}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_06.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Blockquotes}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_07.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Horizontal rule}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_08.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Tables}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_09.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Footnotes}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_10.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Task lists}
+\begin{pframe}
+  \begin{center}
+    \includegraphics[width=1\textwidth]{images/markdown_example/markdown_example_11.pdf}
+  \end{center}
+\end{pframe}
+
+\subsection{Further information}
+\begin{pframe}
+   \begin{itemize}
+    \item \url{https://docs.gitlab.com/ce/user/markdown.html}
+    \item \url{www.markdowntutorial.com}
+   \end{itemize}
+\end{pframe}
+
+
+\makeAcknowledgementsSlide{
+  \begin{tabular}{l}
+    \acknowledgements
+  \end{tabular}
+  \bigskip
+
+  \hfill\includegraphics[width=3.5cm]{../shared/git_logo.pdf}
+
+  \begin{tabular}{l}
+    \small\url{http://git-scm.com/book}\\
+    \small\url{https://www.atlassian.com/git}
+  \end{tabular}
+}
+
+\end{document}