From cd3baf1c67ba90e8693b4efc227b9e16569e8e90 Mon Sep 17 00:00:00 2001
From: Johan Thelin <jthelin@luxoft.com>
Date: Fri, 27 Apr 2018 11:02:45 +0200
Subject: [PATCH] Added ehumphries slides

---
 2018/slides/slides-mhumphries.pdf | 0
 2018/speakers-and-talks.html      | 1 +
 2 files changed, 1 insertion(+)
 create mode 100644 2018/slides/slides-mhumphries.pdf

diff --git a/2018/slides/slides-mhumphries.pdf b/2018/slides/slides-mhumphries.pdf
new file mode 100644
index 0000000..e69de29
diff --git a/2018/speakers-and-talks.html b/2018/speakers-and-talks.html
index 280cdee..dc243ff 100644
--- a/2018/speakers-and-talks.html
+++ b/2018/speakers-and-talks.html
@@ -360,6 +360,7 @@
             <div class="col-md-9">
                 <div class="name">Emma Humphries</div>
                 <div class="title">Avoiding the Petard: Triage at Scale in Firefox Quantum</div>
+                <div class="links"><a href="slides/slides-mhumphries.pdf">Slides</a></div>
 
                 <div class="abstract">
                     The bug that could had sabotaged a year of work on Firefox didn't slip into production because of the efforts of engineers, program managers, and management to triage bugs. But how do you triage 9,000 bugs over the course of a three month release cycle and not burn out? How do you measure hotspots? And how do you make it sustainable? The Firefox team's bugmaster, Emma Humphries, reports on what one of the largest and longest-lived open source projects learned while building this milestone version of the beloved web browser.