Speaker notes improvements

Dependencies

• [2] 5JGZ5VE7 Add unrecord to Pijul demo
• [3] 7RVMAQLP Final major additions to the slide deck
• [4] S55XICBM Fix speaker notes
• [5] 4AZS4L6B Add chapters
• [6] BZTIJPUB Finish the predictions
• [7] UH3YXOLF Start the slide deck
• [8] UXLO2KVD Introduce fragments
• [9] QEKU5M3O Preface
• [10] LDVTVP2G All TODOs are gone now
• [11] JSFDZRYK Add the famous Bill Gates quote
• [12] I3EH5ASI Improve speaker notes
• [13] CBUCBYTV Progress
• [14] 73PQOETU Update slides to 2021 situation
• [15] KPHR32IR Progress
• [16] W7EIQGVR Progress
• [17] D7QXCWGA Progress
• [18] WYULWETJ Reorganize
• [19] SQWPGFUE Finish the demos
• [20] QUG3TDX3 Update to reveal.js 4.1 and a few small fixes
• [21] ENHNSR4Q Add a Fossil vs. Git comparison
• [22] PMBAMPBI Finish the title slide
• [23] 5LKTNB6O LOTS of progress
• [*] ARAFRHKU Create the outline of the talk

Change contents

• edit in index.html at line 102
  [4.4444]

  [4.4444]
  +

  + <section>

  + <h2>Now what?</h2>

  + <ul>

  + <li class="fragment">A lot of projects are nothing like the Linux kernel. <strong>So try Fossil for a change!</strong></li>

  + <li class="fragment">Git's snapshotting might be too technical for the average Git user. <strong>So try Pijul for a change!</strong></li>

  + </ul>

  +

  + <aside class="notes">

  + <strong>Time Elapsed: 45 min.</strong>

  + OK, so now what?

  +

  + Well, of all the things I learned by doing research on this topic, two of them really struck me as important.

  +

  + 1. Git was intended for global open-source development with thousands of contributors.

  + 2. A lot of students in my "Git for developers" course are managers, test specialists, requirements engineers, Scrum Masters. And they struggle with Git's snapshot-based approach. Perhaps a patch-based approach like Pijul will suit them better.

  + </section>
• replacement in index.html at line 137
  [4.5322]→[4.5322:5503](∅→∅)
  − href="https://nest.pijul.com/hannotify/will-git-be-around-forever-slides">https://nest.pijul.com/hannotify/will-git-be-around-forever-slides</a>
  [4.5322]

  [4.5503]
  + href="https://bit.do/utrechtjug-successor-of-git">bit.do/utrechtjug-successor-of-git</a>
• replacement in index.html at line 144
  [4.5862]→[4.5862:5970](∅→∅)
  − href="https://hannotify.github.io">https://hannotify.github.io</a></td>
  [4.5862]

  [4.5970]
  + href="https://hanno.codes">hanno.codes</a></td>
• edit in sections/0-welcome.md at line 27
  [4.192]→[4.259:302](∅→∅)
  − * Niet te snel praten!! Er is tijd genoeg!
• replacement in sections/0-welcome.md at line 35
  [4.8447]→[4.8447:8481](∅→∅)
  − ## Version Control 'By USB Stick'
  [4.8447]

  [4.8481]
  + ## Version Control 'By USB Stick' <!-- .element: class="fragment" -->
• replacement in sections/0-welcome.md at line 42
  [4.8618]→[4.8618:8720](∅→∅)
  − And at my first job, about 14 years ago, we did a revolutionary thing with regard to version control.
  [4.8618]

  [4.8720]
  + And at my first job, about 14 years ago, we did a revolutionary thing regarding version control.

  + I was really eager to learn it, because at college we did version control by sending each other emails with zip files in it.

  + Surely my employer would teach me something more sophisticated?

  +

  + [slide]

  +
• edit in sections/0-welcome.md at line 49
  [4.8757]→[4.8757:8815](∅→∅)
  − And at the first job I had, we did a revolutionary thing.
• replacement in sections/1-preface.md at line 11
  [4.8868]→[4.8868:8945](∅→∅)
  − At Info Support, besides doing consultancy work, I also teach a few courses.
  [4.8868]

  [4.8945]
  + I've gained some experience with real Version Control Systems like Subversion and Git.

  +

  + Now at Info Support, besides doing consultancy work, I also teach a few courses.
• replacement in sections/1-preface.md at line 35
  [4.119386]→[4.38812:38877](∅→∅)
  − So, for example, Subversion relates to the Nokia 3210. (*point*)
  [4.119386]

  [4.119451]
  + So, for example, Subversion relates to the Nokia 3210. (point)

  + Which are both *undestructable*.
• replacement in sections/1-preface.md at line 40
  [4.119502]→[4.4218691:4218806](∅→∅)
  − Now, when I talk about this slide during the Git course, I tend to focus on the events of the year 2005. (*point*)
  [4.119502]

  [4.4218806]
  + Now, when I talk about this slide during the Git course, I tend to focus on the events of the year 2005. (point)
• replacement in sections/1-preface.md at line 121
  [4.95657]→[4.54180:54263](∅→∅)
  − Which he probably didn't say exactly like this, it is very plausible that he added
  [4.95657]

  [4.54263]
  + Which he probably didn't say **exactly** like this, it is very plausible that he added
• edit in sections/1-preface.md at line 147
  [4.54473]→[4.8980:9658](∅→∅)
  −

  −

  − <!-- .slide: data-background="img/background/problem-encountered.jpg" data-background-color="black" data-background-opacity="0.5" --->

  −

  − ## One problem though.

  −

  − <blockquote class="explanation">

  − We haven't included <em>any</em> new products!

  − </blockquote>

  −

  − <https://www.pexels.com/photo/man-in-black-shirt-and-gray-denim-pants-sitting-on-gray-padded-bench-1134204> <!-- .element: class="attribution" -->

  −

  − note:

  − Yeah, one problem though.

  − We haven't included *any* new products.

  − This 'first prediction' is based entirely on existing products.

  − But a lot can happen in ten years!

  − What if a brand-new, feature-packed version control system appears and takes the market by storm?
• edit in sections/2-git.md at line 325
  [4.4230226]
  +

  + note:

  + So, there you have it - Git will stay on top.

  + Thanks for attending everyone, until next time.

  +

  + Just kidding.

  +

  + ---

  +

  + <!-- .slide: data-background="img/background/problem-encountered.jpg" data-background-color="black" data-background-opacity="0.5" --->

  +

  + ## One problem though.

  +

  + <blockquote class="explanation">

  + We haven't included <em>any</em> new products!

  + </blockquote>

  +

  + <https://www.pexels.com/photo/man-in-black-shirt-and-gray-denim-pants-sitting-on-gray-padded-bench-1134204> <!-- .element: class="attribution" -->

  +

  + note:

  + Yeah, one problem though.

  + We haven't included *any* new products.

  + This 'first prediction' is based entirely on existing products.

  + But a lot can happen in ten years!

  + What if a brand-new, feature-packed version control system appears and takes the market by storm?

  +
• edit in sections/5-fossil.md at line 118
  [4.56883]→[4.56883:56884](∅→∅)
  −
• edit in sections/5-fossil.md at line 119
  [4.56911]→[4.56911:56912](∅→∅)
  −
• edit in sections/5-fossil.md at line 187
  [4.1340]→[3.688799:688894](∅→∅)
  −

  − ---

  −

  − # Fossil for Git users

  −

  − <https://www.fossil-scm.org/home/doc/trunk/www/fossil-v-git.wiki>
• edit in sections/6-pijul.md at line 123
  [4.2140]→[4.57050:57051](∅→∅)
  −
• edit in sections/6-pijul.md at line 126
  [4.2313]→[4.57107:57108](∅→∅)
  −
• edit in sections/6-pijul.md at line 128
  [4.2357]→[4.57109:57110](∅→∅)
  −
• edit in sections/6-pijul.md at line 131
  [4.2543]→[4.57170:57171](∅→∅)
  −
• edit in sections/6-pijul.md at line 133
  [2.19]→[2.19:20](∅→∅)
  −
• replacement in sections/6-pijul.md at line 192
  [3.692034]→[3.692034:692095](∅→∅)
  − Which look sa bit like the interactive rebase screen in Git.
  [3.692034]

  [3.692095]
  + Which looks a bit like the interactive rebase screen in Git.
• replacement in sections/7-predictions.md at line 204
  [4.1765]→[4.57781:57840](∅→∅)
  − So Pijul will be the third version control system in 2030!
  [4.1765]

  [4.1824]
  + So Pijul might be the third version control system in 2030!