Drafted session schedules
diff --git a/index.md b/index.md
index 5162d0d..a4a24b8 100644
--- a/index.md
+++ b/index.md
@@ -10,59 +10,24 @@
*** promo
## Registration
-Conference registration is free, but by invite only.
-Please complete the [invite form](https://goo.gl/forms/fifi2YQTc7)
-to request an invite to this event.
+Registration closed on October 1st.
***
|||---|||
----
+|||---||| 7,4
+
+## Schedule
+
+<iframe
+ src="https://docs.google.com/spreadsheets/d/1k3Q_Jx-iSPlHzfeTmrYYuMrebripvkD98vknhhOth50/pubhtml?gid=811932605&widget=true&headers=false"
+ width="510px"
+ height="480px"
+ frameborder="0"></iframe>
+
## Sessions
-### Impact of Modern Code Review Practices on Software Quality
+[Saturday](sat.md) | [Sunday](sun.md)
-Software teams that use modern code reviewing tools like Gerrit are
-quickly accumulating data about their code reviewing processes. In
-our research, we mine this code review data, connecting it with data
-from other software repositories (e.g., version control, bug trackers)
-to produce rich datasets. We then analyze these datasets to study the
-impact that code reviewing has on: (a) software release quality
-(approximated using occurrences of post-release bugs) and (b) software
-design quality (approximated using occurrences of design
-anti-patterns). In this talk, I will describe our approach to Gerrit
-mining code review data and the results of some of our recent
-empirical studies of the code reviewing processes of large open source
-systems, such as Qt and OpenStack.
-
-[more](http://shanemcintosh.org/tags/code-review.html)
-
-*Shane McIntosh, McGill University*
-
-### GerritHub: 2 years in
-
-[GerritHub](http://gerrithub.io/) launched 2 years ago, bringing
-Gerrit to GitHub repositories. Learn more about how this is going.
-
-*Luca Milanesio, GerritForge*
-
-### How I implemented SAML for Gerrit in one weekend
-
-Most enterprises already have a single sign-on solution.
-And Gerrit doesn't support SAML out of the box.
-
-*Nadav S Samet, TrueAccord*
-
-### Scaling Gerrit: active-active masters in a cluster
-
-What does it take to get geographically distributed Gerrit masters?
-
-*TBD, Google*
-
-### Docker-ization of Gerrit
-
-Packaging and Docker-ization for faster enterprise deployment.
-
-*Luca Milanesio, GerritForge*
-
-**More coming soon!**
+|||---|||
diff --git a/navbar.md b/navbar.md
index e88ce93..fc5fc39 100644
--- a/navbar.md
+++ b/navbar.md
@@ -1,7 +1,11 @@
# Gerrit User Summit 2015
-* [Request Invite](https://goo.gl/forms/fifi2YQTc7)
* [Conduct Policy](/conduct-policy.md)
+* [Attendee Information][private]
+* Agenda
+* [Saturday](/sat.md)
+* [Sunday](/sun.md)
[home]: /index.md
[logo]: images/diffy45.png
+[private]: https://www.google.com/a/SelectSession?service=gerritcodereview&continue=https://gerrit.googlesource.com/login/summit/2015/%2B/private/welcome.md
diff --git a/sat.md b/sat.md
new file mode 100644
index 0000000..58d9271
--- /dev/null
+++ b/sat.md
@@ -0,0 +1,114 @@
+# Saturday Agenda
+
+|||---||| 7,5
+
+#### Schedule
+<iframe
+ src="https://docs.google.com/spreadsheets/d/1k3Q_Jx-iSPlHzfeTmrYYuMrebripvkD98vknhhOth50/pubhtml?gid=811932605&widget=true&headers=false"
+ width="510px"
+ height="480px"
+ frameborder="0"></iframe>
+
+#### Sessions
+[TOC]
+
+|||---|||
+
+## 8:45 am Registration and Breakfast
+
+Coffee and breakfast in breakout area.
+
+## 9:30 am Welcome
+## 9:45 am What's new in 2.11
+
+*David Pursehouse, Sony Mobile*
+
+## 10:15 am Gertty: Console Interface to Gerrit
+
+Gertty is a console-based interface to Gerrit implementing using
+Gerrit's comprehensive REST API. Gertt's author will discuss his
+experience using the API, demonstrate the unique capabilities afforded
+by a secondary interface, and show some ASCII art.
+
+*James Blair, OpenStack / IBM*
+
+## 10:35 am Break
+
+Coffee in the breakout area.
+
+## 11:00 am Impact of Modern Code Review Practices
+
+Software teams that use modern code reviewing tools like Gerrit are
+quickly accumulating data about their code reviewing processes. In
+our research, we mine this code review data, connecting it with data
+from other software repositories (e.g., version control, bug trackers)
+to produce rich datasets. We then analyze these datasets to study the
+impact that code reviewing has on: (a) software release quality
+(approximated using occurrences of post-release bugs) and (b) software
+design quality (approximated using occurrences of design
+anti-patterns). In this talk, I will describe our approach to Gerrit
+mining code review data and the results of some of our recent
+empirical studies of the code reviewing processes of large open source
+systems, such as Qt and OpenStack.
+
+[more](http://shanemcintosh.org/tags/code-review.html)
+
+*Shane McIntosh, McGill University*
+
+## 12:00 pm Lunch
+
+Buffet served in breakout area.
+
+## 1:00 pm GerritHub: 2 years in
+
+[GerritHub](http://gerrithub.io/) launched 2 years ago, bringing
+Gerrit to GitHub repositories. Learn more about how this is going.
+
+*Luca Milanesio, GerritForge*
+
+## 1:30 pm SAML in a weekend
+
+How I implemented SAML for Gerrit in one weekend. Most enterprises
+already have a single sign-on solution. And Gerrit doesn't support
+SAML out of the box.
+
+*Nadav S Samet, TrueAccord*
+
+## 1:30 pm Gerrit in a Windows world
+
+Managing Gerrit in a mostly-Windows environment, and how we've helped
+simplify and improve the new employee setup process by automating many
+of the Git and Gerrit configuration steps.
+
+*Doug Kelly, Garmin*
+
+## 2:00 pm Ericsson's migration to Gerrit
+
+*Frank Stockmans, Ericsson*
+
+## 2:30 pm Break and snack
+
+Coffee and snacks served in breakout area.
+
+## 3:00 pm Gerrit at Yahoo, a 2-year Journey
+
+Sharing our experience in these 2 years on Gerrit's growth in Yahoo
+from a single team pilot to the company wide recommended code review
+solution.
+
+We will talk about the reason why we chose Gerrit and how we move
+forward the adoption along with Git and GitHub, Chef based
+deployments, submit rules customizations, and a few metrics we created
+to facilitate better use of Gerrit and code reviews in general, also
+the critical role Gerrit played in the landscape of continuous
+delivery.
+
+*Shanbin Wang, Yahoo*
+
+## 3:30 pm Gerrit at Google
+
+*TBD, Google*
+
+## End
+
+See you on [Sunday](/sun.md) between 8:45 and 9:30!
diff --git a/sun.md b/sun.md
new file mode 100644
index 0000000..0ae8e51
--- /dev/null
+++ b/sun.md
@@ -0,0 +1,122 @@
+# Sunday Agenda
+
+|||---||| 7,5
+
+#### Schedule
+<iframe
+ src="https://docs.google.com/spreadsheets/d/1k3Q_Jx-iSPlHzfeTmrYYuMrebripvkD98vknhhOth50/pubhtml?gid=811932605&widget=true&headers=false"
+ width="510px"
+ height="480px"
+ frameborder="0"></iframe>
+
+#### Sessions
+[TOC]
+
+|||---|||
+
+## 8:45 am Breakfast
+
+Coffee and breakfast in breakout area.
+
+## 9:30 am Scaling Gerrit at Ericsson
+
+*Vladimir Cantiru, Ericsson*
+
+## 10:00 am Scaling Gerrit: active-active masters
+
+*TBD, Google*
+
+## 10:30 am Break
+## 11:00 am Tuning Gerrit
+
+How to Properly Tune and Size your Gerrit Backend
+
+So you decided to host your Git repositories yourself - great! How
+many servers will you need? Which cloning protocols to offer? How
+many CPUs and how much RAM will you need? What the heck is pack
+size? How often should you run garbage collection? Does it
+make any difference whether you go with a native Git or JGit
+based backend? How do you handle hundreds of polling CI users
+without compromising performance for your human end users? What
+about clustering and replication? This talk will provide you with
+background knowledge to better answer those questions (and some
+more). It is based on the scaling and tuning experience of many
+companies with 10k+ Git repositories and users, dozens of servers,
+terabytes of source code, and millions of fetch requests per day.
+
+Every participant will get a Gerrit Performance Tuning Cheat Sheet
+which summarizes the most important factors, gerrit.config options
+and formula.
+
+*Johannes Nicolai, CollabNet*
+
+## 12:00 pm Lunch
+
+Buffet served in breakout area.
+
+## 1:00 pm Continuous Delivery in Big Data
+
+BigData is now everywhere, from mobile media analytics, banking,
+industry, avionics and even in medicine to monitor expansion of
+epidemics.
+
+We are showing how Code Review can be integrated with Continuous
+Integration and Continuous Delivery in a Big Data scenario that poses
+new challenges to the existing Jenkins framework. We are going to
+describe how we managed to implement our agile build and deployment
+process working with distributed teams in BigData Software Development
+Projects for media and financial organizations in London. The talk
+will start with a presentation of our workflow and then will explain
+how we leveraged Gerrit and Jenkins and how we integrated with Docker,
+Mesos and the Hadoop ecosystem.
+
+*Stefano Galarraga, GerritForge Ltd*
+
+## 1:30 pm Prolog file-level whitelists
+
+How I use Prolog to implement file-level whitelist and blacklist if
+there are any interests. (I am a Prolog novice myself!)
+[15 min]
+
+*Kenny Ho, AMD*
+
+## 2:00 pm Non-Prolog submit rules
+
+You shall not pass – Control your code quality gates with a wizard.
+
+For those of us who does not speak Prolog, there is an easier way
+to configure your submit rules. The quality gate wizard lets you
+to set up your submit rules in less than 3 minutes.
+
+This presentation is about a gerrit plugin that provides an
+alternative to writing submit rules in Prolog.
+
+*Eryk Szymanski, CollabNet*
+
+## 2:30 pm Break and snack
+
+Coffee and snacks served in breakout area.
+
+## 3:00 pm notedb: Code reviews in Git
+
+*Dave Borowitz, Google*
+
+## 3:30 pm Docker-ization of Gerrit
+
+Packaging and Docker-ization for faster enterprise deployment.
+
+*Luca Milanesio, GerritForge*
+
+## 4:00 pm Jenkins & Gerrit
+
+CloudBees has a fully integrated & Dockerized Gerrit/Jenkins
+demonstration. This is based on the real-world use case of a mobile
+development team using repo to manage multiple repositories in Gerrit.
+It illustrates how Jenkins workflow can be tied into Gerrit processes
+to simplify a complex review/build/test pipeline.
+
+This builds on and uses the Dockerized Gerrit image that is being
+presented by GerritForge, and I will discuss some of the challenges &
+solutions, with an eye towards integrated solutions in Docker.
+
+*Sam Van Oort, CloudBees, Inc.*
diff --git a/welcome.md b/welcome.md
new file mode 100644
index 0000000..6ca7b76
--- /dev/null
+++ b/welcome.md
@@ -0,0 +1,57 @@
+# Welcome
+
+Welcome to the 2015 Gerrit User Summit, November 7 and 8
+
+Google’s Open Source Programs Office is pleased you could join us.
+This sheet will provide you with information about Google’s facilities
+and a schedule of events for the Summit.
+
+## Location
+
+The Gerrit Summit will take place on the Google Main Campus at
+[1395 Charleston Road, Mountain View, California][maps],
+Saturday November 7 and Sunday November 8. Parking is readily
+available and adjacent to the building.
+
+Please use the entrance to the building facing North Shoreline Blvd.
+
+[maps]: https://www.google.com/maps/place/Google+MTV+1395,+1395+Charleston+Rd,+Mountain+View,+CA+94043/@37.4198393,-122.0769082,17z/data=!3m1!4b1!4m2!3m1!1s0x808fb9fdcb4cbb63:0xa07f4c5d6bf298e5
+
+## Food & Drink
+
+Google will provide all food, beverages and snacks while you are on
+the Google campus. We promise you will NOT go hungry! Vegetarian
+options will be available.
+
+## Internet
+
+You can get online using the **GoogleGuest** wireless network. No
+password is required. Please do not plug into any network jacks.
+
+## Badges
+
+Please ensure you wear your conference name badge at all times while
+on the Google campus.
+
+## Photos
+
+Photographs are limited to areas outside of the building or in the
+building lobby *only*. Please refrain from snapping photos indoors,
+including in the conference room. Also, please make sure you have
+your colleagues’ permission to photograph them and to publish said
+photos, if applicable.
+
+## Contact Information
+
+If you have any problems while attending the Summit, please feel free
+to reach out to:
+
+* Shawn Pearce, 347-443-8767, sop@google.com
+
+## Conduct Policy
+
+Google reserves the right to refuse admittance to, or remove any
+person from Google premises (including future events) at any time in
+its sole discretion. This includes but is not limited to attendees
+behaving in a disorderly manner or failing to abide by our
+[anti-harassment policy](http://www.google.com/events/policy/anti-harassmentpolicy.html).
