session: An introduction to the pull-replication plugin

Change-Id: I86c8387a90cc0bd3ab61674531da3c719e82a727
diff --git a/schedule.md b/schedule.md
index 83ea3a4..aed6919 100644
--- a/schedule.md
+++ b/schedule.md
@@ -22,7 +22,7 @@
 |-----------------------|-----------------------------------------------------------------------------------------|
 |  8:00 PST / 17:00 CET | [How to survive with mono-repos in Gerrit](sessions/mono-repo-with-gerrit.md)           |
 |  8:30 PST / 17:30 CET | [Promoting Situational Awareness in Code Review Platforms](sessions/promoting-situational-awareness-in-code-review.md) |
-|  9:00 PST / 18:00 CET | Session 6 - __available for proposals__ (may include 1 poll)                            |
+|  9:00 PST / 18:00 CET | [An introduction to the pull-replication plugin](sessions/pull-replication-plugin.md)                              |
 |  9:30 PST / 18:30 CET | Q&A with the maintainers (may include 1-2 polls)                                        |
 | 10:30 PST / 19:30 CET | Lightning talk 6 - __available for proposals__                                          |
 | 10:40 PDT / 19:40 CET | Lightning talk 7 - __available for proposals__                                          |
diff --git a/sessions/pull-replication-plugin.md b/sessions/pull-replication-plugin.md
new file mode 100644
index 0000000..a9681e8
--- /dev/null
+++ b/sessions/pull-replication-plugin.md
@@ -0,0 +1,27 @@
+# An introduction to the pull-replication plugin
+
+Over the last year GerritForge took an effort to improve Gerrit replication
+performance by introducing the pull-replication plugin.
+
+This presentation will show the current state of the pull-replication plugin,
+introduce the main concepts behind it and explain how they can improve
+replication performance, provide more predictable behaviour and help to avoid
+split-brain scenario.
+
+I will also explain how the pull-replication plugin can be setup as a standalone
+solution or work together with the replication plugin.
+
+At the end of the talk I would like to show the pull-replication plugin in action.
+
+## Polls
+
+> ### What is your average replication execution time?
+> - around 1 second
+> - around 30 seconds
+> - around 1 minute
+> - around 5 minutes
+> - around 10 minutes
+> - around 30 minutes
+> - over 30 minutes
+
+*[Marcin Czech, GerritForge](../speakers.md#mczech)*
diff --git a/speakers.md b/speakers.md
index cef9891..e459f39 100644
--- a/speakers.md
+++ b/speakers.md
@@ -77,3 +77,13 @@
 His largest contributions to Gerrit so far were the Attention Set, the new
 Checks API/UI (see lightning talks) and heading large infrastrucutre migrations
 such as JavaScript->TypeScript and Polymer1->2->3->Lit.
+
+### Marcin Czech - GerritForge {#mczech}
+
+Marcin is a Senior Software Engineer at GerritForge where he contributes to the
+OpenSource Gerrit Code Review project.
+
+Over the last two years he has been involved in the design and development of
+numerous parts of the Gerrit ecosystem, such as: Gerrit core, multi-site,
+events-broker(Kafka and AWS Kinesis), pull-replication and external-ids
+online migration.