1 % Intended LaTeX compiler: pdflatex
2 \documentclass[presentation]{beamer}
3 \usepackage[utf8]{inputenc}
4 \usepackage[T1]{fontenc}
10 \usepackage[normalem]{ulem}
16 \pgfdeclareimage[height=0.185\textheight]{debian_logo.png}{debian_logo.png}\logo{\pgfuseimage{debian_logo.png}}
17 \setbeamercolor{background canvas}{bg=}
18 \usepackage{subfigure}
19 \definecolor{DebianMagenta}{RGB}{215,10,83}
20 \usecolortheme[named=DebianMagenta]{structure}
21 \setbeamercolor{alerted text}{fg=red}
22 \setbeamertemplate{footline}[slide number]
23 \definecolor{string}{rgb}{0,0.6,0} \definecolor{shadow}{rgb}{0.5,0.5,0.5} \definecolor{keyword}{rgb}{0.58,0,0.82} \definecolor{identifier}{rgb}{0,0,0.7}
24 \setbeamerfont{author}{size=\footnotesize}
28 \title{Meet the Debian Technical Committee}
31 pdftitle={Meet the Debian Technical Committee},
40 \section{What is tech-ctte}
41 \label{sec:org4a428e5}
43 \begin{frame}[fragile,label={sec:orgc1d7055}]{Current tech-ctte members}
45 \item \alert{David Bremner} (\texttt{bremner})
46 \item \alert{Tollef Fog Heen} (\texttt{tfheen})
47 \item Philip Hands (\texttt{philh})
48 \item \alert{Margarita Manterola} (\texttt{marga}, chair)
49 \item Simon McVittie (\texttt{smcv})
50 \item Didier Raboud (\texttt{odyx})
51 \item Niko Tyni (\texttt{ntyni})
52 \item \alert{Gunnar Wolf} (\texttt{gwolf})
56 (Red \(\Rightarrow\) present at DC19)
60 \begin{frame}[label={sec:org8eb153d}]{Past tech-ctte members — Thanks!}
61 \small \begin{columns} \begin{column}{0.5\textwidth}
63 \item Sam Hartman (2015-03-08–2017-11-09)
64 \item Keith Packard (2013-11-29–2017-12-31)
65 \item Don Armstrong (2009-01-11–2016-12-31)
66 \item Andreas Barth (2006-01-05–2016-12-31)
67 \item Steve Langasek (2006-01-05–2015-12-31)
68 \item Bdale Garbee (–2015-12-31)
69 \item Colin Watson (2011-08-24–2015-03-05)
70 \item Ian Jackson (–2014-11-19)
72 \end{column} \begin{column}{0.5\textwidth}
74 \item Russ Allbery (2009-01-11–2014-11-16)
75 \item Manoj Srivasta (–2012-08-12)
76 \item Anthony Towns (2006-01-04–2009-01-05)
77 \item Raul Miller (–2007-04-30)
78 \item Wichert Akkerman (–2006-01-05)
79 \item Jason Gunthorpe (–2006-01-05)
80 \item Guy Maor (–2006-01-05)
81 \item Dale Scheetz (–2002-09-02)
82 \item Klee Dienes (–2001-05-21)
84 \end{column} \end{columns}
87 \begin{frame}[label={sec:orgdab8194}]{What is the Debian Technical Committee?}
89 Debian Constitution §6.1
91 The Technical Committe may:
94 \item §6.1.1 Decide on any matter of technical policy
95 \item §6.1.2 \& 6.1.3 Decide any technical matter where Developers' jurisdictions overlap
96 \item Make a decision when asked to do so
100 \item §6.1.4 Overrule a Developer
102 \item Requires a 3:1 majority
105 \item §6.1.5 Offer advice
109 \begin{frame}[label={sec:org2cbcda9}]{Constraints}
111 \item §6.3.3 Public discussion and decision-making
112 \item §6.3.5 No detailed design work
113 \item §6.3.6 TC makes decisions only as last resort
117 \begin{frame}{What this means}
121 \item Constitutionally, we are asked to \emph{break ties} amongst available
124 \item After all efforts to solve it via consensus have been \emph{tried and
128 Offer advice and make our views known
130 \item We can offer advice at any point, but it's just advice.
135 \begin{frame}[label={sec:org9fed62f}]{The Debian Technical Committee is a\ldots{}}
140 \item Conflict resolution and advice-providing body
146 \section{Recent activity (FSVO)}
147 \label{sec:org8ef7e2e}
149 \begin{frame}[fragile,label={sec:orgcd00434}]{Issues in front of the TC since DebConf18 (\url{https://bugs.debian.org/tech-ctte})}
155 \item \texttt{\#904302} Whether vendor-specific patch series should be permitted in the archive
157 \item Use of dpkg's vendor-specific patch series feature is a bug
160 \item \texttt{\#914897} Should debootstrap disable merged /usr by default?
162 \item We declined to override the debootstrap maintainers.
163 \item We were tied for the other part of our decision, so a casting vote was necessary.
164 \item We decided the desired state for bullseye should be that both directory schemes are allowed, and
165 packages (including official packages) can be built on hosts with either classical or "merged /usr schemes.
171 \begin{frame}[fragile,label={sec:org5491b73}]{Issues in front of the TC since DebConf18 (\url{https://bugs.debian.org/tech-ctte})}
173 Closed without a formal resolution
177 \item \texttt{\#904558} What should happen when maintscripts fail to restart a service
179 \item We declined to rule. Recommended that a new notification method gets developed
182 \item \texttt{\#911225} Advice on stale libraries in a higher-precedence path entry
184 \item Advice was given.
187 \item \texttt{\#919951} ocaml builder must not be called `dune' or provide /usr/bin/dune
189 \item The issue was resolved without our intervention.
192 \item \texttt{\#923450} requirements for being pre-dependency of bin:init
194 \item We declined to rule. Agreed that the maintainers of the init-system-helpers package
195 have a gatekeeper role for this.
201 \begin{frame}[fragile,label={sec:org13d88a5}]{Issues in front of the TC since DebConf18 (\url{https://bugs.debian.org/tech-ctte})}
206 \item \texttt{\#932795} How to handle FTBFS bugs in release architectures
210 \section{Fresh blood wanted}
211 \label{sec:orgb562a1f}
212 \begin{frame}[label={sec:orge4537ce}]{Term expiry §6.2.7}
214 On January 1st of each year the term of any Committee member who has
215 served more than 42 months (3.5 years) \emph{and} who is one of the two
216 most senior members is set to expire on December 31st of that year.
219 §6.2.1: The Technical Committee consists of up to 8 Developers, and
220 should usually have at least 4 members.
222 We are roughly looking for 1-2 new members per year.
226 \begin{frame}[label={sec:org2d763d0}]{Term expiry (maybe)}
228 Last year we got this wrong. Maybe this time we get it right...
233 \item Didier Raboud (2015-03-08)
234 \item Tollef Fog Heen (2015-03-08)
238 \item Phil Hands (2016-04-15)
242 \item Margarita Manterola (2016-07-07)
243 \item David Bremner (2017-04-13)
247 \item Niko Tyni (2017-06-21)
248 \item Gunnar Wolf (2018-01-02)
252 \item Simon McVittie (2018-03-16)
259 \section{Problems with the TC}
261 \begin{frame}{Reality Check}
264 \large{Things aren't going too well}
270 \begin{frame}{Problems with the current process}
274 \item Escalations need to be done as last resort, which means that discussions have turned into a flamewar by the time they reach us.
276 \item Some developers resent the TC and will straight away refuse to talk to us.
278 \item Our main power is to overrule and as such people fear or dislike us.
280 \item It can take months until we make a decision, sometimes this means it's already too late.
282 \item Having a discussion in the open leads to exhausting flamewars.
288 \begin{frame}{We keep declining to rule}
289 We may decline to rule because:
291 \item The escalation was done too quickly, not all avenues were exhausted.
293 \item We're being asked to overrule a delegate (release team, ftp master team, etc) which we can't do.
295 \item We can't do design work and the only answer is to design something.
300 \begin{frame}{How could we make this better?}
302 \item Changing how the TC works will probably require a constitutional change.
304 \item Is there a way we could keep the purpose (solving disagreement) but avoid the flamewars and broken relationships?
306 \item What can we do to ensure we can discuss matters without people shutting down?
312 %\begin{frame}[label={sec:org1013a0e}]{TC work is}
314 %\item Often more \emph{social} than technical
315 %\item About \emph{disagreements} and conflicts
316 %\item At the \emph{broad} technical level
317 %\item \emph{Listening} to what people have to say
318 %\item Sometimes taking hard decisions
319 %\item Essentially political
323 %\begin{frame}[label={sec:org2a77929}]{Required skillset}
326 %\item Technical agility
328 %\item Responsiveness
329 %\item Social sensitivity
334 %\begin{frame}[label={sec:orgccc87c0}]{Talk to us}
336 %\Large Come talk to us if you have worries, questions or else!
338 %\tiny We are just developers.
344 \label{sec:org28d85df}
345 \begin{frame}[label={sec:orged404fd}]{Q\&A}
347 \Large Time for Q \& A! \vfill
351 \small debian-ctte@lists.debian.org
353 %\footnotesize \url{https://people.debian.org/\~gwolf/talks/2018/tech-ctte.pdf}