Commit 3300f4898f2 by Georges Racinet

Rewrote with LaTeX + Beamer

parent b3f06f155dc
syntax: glob
hovercraftenv/
generated/
*~
.\#*
\#*
*.pdf
*.dvi
*.aux
*.out
*.toc
*.vrb
*.log
*.snm
*.orig
*.nav
\documentclass{beamer}
\usepackage[utf8]{inputenc}
\usetheme{Warsaw}
\usepackage{minted}
\title{Heptapod}
\author{Georges Racinet}
\institute{Octobus, \url{https://octobus.net}}
\pgfdeclareimage[height=14.5mm,width=8.3mm]{octobus-logo}{octobus-logo-min}
\logo{\pgfuseimage{octobus-logo}}
\date{Mercurial Conference – Paris 2019, Hosting mini track}
\begin{document}
\begin{frame}
\titlepage
\begin{itemize}
\item This presentation:
\begin{itemize}
\item slides: \url{https://slides.racinet.fr/2019/hg-paris}
\item source: \url{https://dev.heptapod.net/slides/2019-hg-paris}
\end{itemize}
\item Heptapod:
\begin{itemize}
\item Docker: \url{https://hub.docker.com/r/octobus/heptapod}
\item source: \url{https://dev.heptapod.net/heptapod}
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}{What is Heptapod ?}{Heptapod = GitLab CE + Mercurial}
\begin{itemize}
\item<2-> A friendly fork
\item<3-> Excellent relationship with GitLab
\item<4-> Featuring modern Mercurial workflows: evolve, topic\\
One should never had to force-push
\end{itemize}
\end{frame}
\begin{frame}{Heptapod history}
\begin{itemize}
\item First commit: november 2017
\item First prototype: december 2017
\item February 2018: demo to GitLab developers at FOSDEM
\item Blog post: september 2018
\item Fully self hosted: april 2019
\item Official Docker images: april 2019
\end{itemize}
\end{frame}
\begin{frame}{Topics in Heptapod}{Reminder: \emph{topics}}
\uncover<2->{Topics}
\begin{itemize}
\item<2-> are lightweight short-lived branches
\item<3-> disappear upon \emph{publication} of their changesets
\item<4-> suited for features or bugfixes
\end{itemize}
\uncover<5->{while \emph{named} (classical) Mercurial branches are…}
\begin{itemize}
\item<6-> permanent
\item<6-> global
\item<6-> suited for support branches, stable/default etc
\end{itemize}
\end{frame}
\begin{frame}[fragile]{Topics in Heptapod}{Heptapod is meant for topics}
From GitLab point of view, both topics and named branches are… just branches.
\uncover<2->{GitLab branch mappings:}
\begin{description}
\item<3->[named branch]
\begin{verbatim}
branch/BRANCH_NAME
\end{verbatim}
\item<4->[topic]
\begin{verbatim}
topic/TARGET_BRANCH_NAME/TOPIC_NAME
\end{verbatim}
\end{description}
\end{frame}
\begin{frame}[fragile]{Topics in Heptapod}{Topic examples}
\begin{itemize}
\item
\begin{verbatim}
branch/default/my-cool-feature
\end{verbatim}
\item
\begin{verbatim}
branch/stable/fix435
\end{verbatim}
\item
\begin{verbatim}
branch/1.0.x/fix435
\end{verbatim}
\end{itemize}
\end{frame}
\begin{frame}{Topics and Merge Requests}
\begin{itemize}
\item Creation, diff, review, discussions: just normal GitLab
\item Merge: rebase + publish
\end{itemize}
\end{frame}
\begin{frame}{Heptapod in action}
\begin{center}
time for a live demo…
\end{center}
\end{frame}
\begin{frame}{Heptapod now}{Don't call it a prototype any more}
\begin{itemize}
\item<2-> Many stabilisation actions in 2019:
\begin{itemize}
\item<2-> Better concurrency support
\item<2-> More streamlined Docker deployment
\item<3-> Yet, still internally based on hg-git
\end{itemize}
\item<4-> Self hosted
\item<5-> In regular use at Octobus and some of our partners
\item<6-> Support available through Octobus
\end{itemize}
\end{frame}
\begin{frame}{Current developments}{On the current code base}
\begin{itemize}
\item stabilisation/publication of Gitlab CI\\
currently running at Logilab
\item Work on importing large projects
\item Finer permission control (publication)
\item Basic documentation (install instructions)
\end{itemize}
\end{frame}
\begin{frame}{Caveats}{Not a prototype, yet still…}
\begin{itemize}
\item<1-> no SSH support
\item<1-> forking is disabled
\item<1-> no Git support (!)
\item<1-> base GitLab version now quite old
\end{itemize}
Some of these will be solved on the current code base according to needs,
but in the long run we better jump to…
\end{frame}
\begin{frame}{The Next Phase}{Starting now!}
Hg + Gitaly
\begin{itemize}
\item Gitaly: abstraction layer for internal Git access
\item Development of a Mercurial version
\item No more hg-git
\item much faster
\item catching up onto current GitLab
\end{itemize}
\end{frame}
\begin{frame}{How you can help}
\begin{itemize}
\item<2-> Contributing
\begin{itemize}
\item code
\item documentation
\item bug reports
\end{itemize}
\item<3-> Sponsoring
\begin{itemize}
\item missing features on the current version
\item long term developments
\end{itemize}
\end{itemize}
\end{frame}
\begin{frame}{Current sponsors}
\begin{itemize}
\item Octobus
\item Notile
\item Logilab \url{https://logilab.fr}
\item Pythonian \url{https://pythonian.fr}
\end{itemize}
\end{frame}
\begin{frame}{Thank you}
\begin{center}
Any questions?
\end{center}
\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