Permalink
Browse files

Added presentation on Gerrit

Created for a workshop "Presenting for Impact" by Communication Edge.
  • Loading branch information...
1 parent 81611cb commit 3934533fa743d0178991114b387a3c8e32d7a018 @whiteinge committed Jun 27, 2012
View
BIN cars_2012-06-27_gerrit/central-simple.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
BIN cars_2012-06-27_gerrit/china-low-wage-factory-workers.jpg
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
BIN cars_2012-06-27_gerrit/gerrit-action.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
BIN cars_2012-06-27_gerrit/gerrit-simple.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
BIN cars_2012-06-27_gerrit/git-clones.png
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
View
BIN cars_2012-06-27_gerrit/presentation.pdf
Binary file not shown.
View
109 cars_2012-06-27_gerrit/presentation.rst
@@ -0,0 +1,109 @@
+======
+Gerrit
+======
+
+:Organization: Cars.com
+:Author: Seth House <shouse@cars.com>
+:Date: 2012-06-27
+
+.. include:: ../beamerdefs.txt
+
+.. Checklist:
+..
+ [X] When is the presentation?
+ [X] How long is the presentation?
+ Six minutes.
+ [ ] What is the fall-back plan if the presentation duration changes?
+ [X] How many will attend?
+ 1-15
+ [X] Who is the audience? Peers, coworkers, investors, superiors?
+ Peers & customers (QA)
+ [X] Who are the key audience members to influence?
+ Users -> managers
+ [X] What is the expected audience attention span?
+ Above avg.
+ [X] Why are these audience members in attendance?
+ Define future workflow.
+ [X] What does this audience expect?
+ High-level overview of workflow.
+ [ ] What will get the audience's attention?
+ [X] What is the audience's subject knowledge?
+ Light
+ [X] Will the audience understand jargon?
+ Some
+ [X] What is the expected reaction to the presentation and the presenter?
+ Hostile
+ [ ] What are likely audience questions?
+ [X] What are possible audience questions that will be hard to answer?
+ Q. Gerrit doesn't support feature branches.
+ Q. Why is Gerrit worth installing additional infrastructure?
+
+.. 1. Create a loose outline of ideas, references, and talking points.
+.. 2. Categorize into: must know, need to know, don't need to know (cut).
+.. 3. Restructure into the following sections:
+..
+ * Opening. Capture attention; avoid introductions and fluff.
+ * Current situation. Establish importance.
+ * Recommendation.
+ * Benefits. Personalize for the audience.
+ * Evidence. Support the recommendation; don't revisit current situation.
+ * Summary. Short!
+ * Action steps. Specific actions; specific time-frame.
+
+
+.. raw:: latex
+
+ {
+ \usebackgroundtemplate{\includegraphics[width=\paperwidth]{china-low-wage-factory-workers.jpg}}
+ \begin{frame}[plain]
+ \end{frame}
+ }
+
+Reptition & complexity
+======================
+
+* Slow
+* Error prone
+* Frustrating
+
+Subversion will be replaced
+===========================
+
+.. container:: r2b-note
+
+ * svn is being replaced (yay), but Git can be complex
+ * Central repo -> forks -> clones -> remotes.
+
+.. image:: central-simple.png
+ :width: 100%
+
+Git is not perfect
+==================
+
+.. image:: git-clones.png
+ :width: 100%
+
+Gerrit
+======
+
+.. image:: gerrit-simple.png
+ :scale: 80%
+
+Central, simple, automated
+==========================
+
+* Devs: One remote; control from Git
+* QA: Web interface; control
+* Bookeeping & automation
+
+Automation
+==========
+
+.. image:: gerrit-action.png
+ :width: 100%
+
+Adopt Gerrit
+============
+
+* Research Gerrit
+* Recommend Gerrit

0 comments on commit 3934533

Please sign in to comment.