hone · August 29, 2015 13:57 · Mar 31, 2014 · Mar 31, 2014 · Feb 5, 2014 · Feb 5, 2014
diff --git a/speaker.md b/speaker.md
@@ -1,4 +1,3 @@
-
 # Terence Lee
 
 ## Contact details

diff --git a/talk.md b/talk.md
@@ -4,7 +4,7 @@
 
 ## Abstract
 
-On November 22, 2013, a devastating security exploit was publicized to the Ruby community: Heap Overflow in Floating Point Parsing (CVE-2013-4164)[https://www.ruby-lang.org/en/news/2013/11/22/heap-overflow-in-floating-point-parsing-cve-2013-4164/]. There was no fixes provided for Ruby 1.9.2. In fact, Ruby 1.9.2 has never had a formal end of life announcement. At Heroku we realized this impacted our ability to provide reliable runtime support. Not wanting to leave our customers high and dry, Heroku released Ruby 1.8.7 and 1.9.2 security patches on our runtimes and pushed to get them upstream. This situation paved the way for me to join ruby-core to help [maintain security fixes for 1.8.7 and 1.9.2](https://www.ruby-lang.org/en/news/2013/12/17/maintenance-of-1-8-7-and-1-9-2/).
+On November 22, 2013, a devastating security exploit was publicized to the Ruby community: Heap Overflow in Floating Point Parsing [CVE-2013-4164](https://www.ruby-lang.org/en/news/2013/11/22/heap-overflow-in-floating-point-parsing-cve-2013-4164/). There was no fixes provided for Ruby 1.9.2. In fact, Ruby 1.9.2 has never had a formal end of life announcement. At Heroku we realized this impacted our ability to provide reliable runtime support. Not wanting to leave our customers high and dry, Heroku released Ruby 1.8.7 and 1.9.2 security patches on our runtimes and pushed to get them upstream. This situation paved the way for me to join ruby-core to help [maintain security fixes for 1.8.7 and 1.9.2](https://www.ruby-lang.org/en/news/2013/12/17/maintenance-of-1-8-7-and-1-9-2/).
 
 Over the course of the year with help from [zzak](https://twitter.com/_zzak), I’ve been figuring out how to work with ruby core as well as proposing policy changes for more transparency. This talk, goes through the steps and mistakes that I learned on how to interact with members of ruby core as well as telling war stories of my experience on core. We’ll remove the opacity around getting contributions upstreamed and how you can have meaningful discussions with the implementers about the language we all know and love. Help us make Ruby better.
 

diff --git a/speaker.md b/speaker.md
@@ -1,13 +1,14 @@
-# [Speaker Name]
 
-## Contact details
+# Terence Lee
 
-* Twitter: @example
-* Website or Blog: <http://example.net>
-* Company: Example Ltd. <http://example.com>
+## Contact details
 
-[Feel free to add more details if you wish…]
+* Twitter: @hone02
+* Website or Blog: <http://hone.heroku.com>
+* Company: Example Ltd. <http://www.heroku.com>
 
 ## Speaker bio
 
-[ Your bio here. 50-100 words is enough for us. ]
+Terence leads Heroku's Ruby Task Force curating the Ruby experience on the platform. He also works some OSS projects such as Ruby (the language), Bundler, as well as helping with the Rails Girls movement. When he's not going to an awesome Heroku or Ruby event, he lives in Austin, TX, the taco capital of America.
+
+(Terence loves Friday hugs, EVERY DAY OF THE WEEK! Give him a big one when you see him!)
diff --git a/talk.md b/talk.md
@@ -1,14 +1,13 @@
-# Talk title
+# Ruby & You
 
-* Desired talk duration: 30/45 minutes
+* Desired talk duration: 30 minutes
 
 ## Abstract
 
-[ Your talk abstract. Whether you make your proposal gist private or public is entirely up to you: we don't mind one way or another. You can, of course, edit your proposal right up until the deadline. ]
-
-For an example of a good proposal, see [this proposal by Jeff Casimir](https://gist.github.com/1780670) and [“How to write a conference proposal” by Mike Moore](http://blowmage.com/2013/01/24/writing-conf-proposals)
+On November 22, 2013, a devastating security exploit was publicized to the Ruby community: Heap Overflow in Floating Point Parsing (CVE-2013-4164)[https://www.ruby-lang.org/en/news/2013/11/22/heap-overflow-in-floating-point-parsing-cve-2013-4164/]. There was no fixes provided for Ruby 1.9.2. In fact, Ruby 1.9.2 has never had a formal end of life announcement. At Heroku we realized this impacted our ability to provide reliable runtime support. Not wanting to leave our customers high and dry, Heroku released Ruby 1.8.7 and 1.9.2 security patches on our runtimes and pushed to get them upstream. This situation paved the way for me to join ruby-core to help [maintain security fixes for 1.8.7 and 1.9.2](https://www.ruby-lang.org/en/news/2013/12/17/maintenance-of-1-8-7-and-1-9-2/).
 
+Over the course of the year with help from [zzak](https://twitter.com/_zzak), I’ve been figuring out how to work with ruby core as well as proposing policy changes for more transparency. This talk, goes through the steps and mistakes that I learned on how to interact with members of ruby core as well as telling war stories of my experience on core. We’ll remove the opacity around getting contributions upstreamed and how you can have meaningful discussions with the implementers about the language we all know and love. Help us make Ruby better.
 
 ## Notes
 
-[ Have you given this talk before? Anything else you'd like to mention... ]
+I'm going to be giving this talk at Ancient City Ruby this year. I've been focused this year and working on ruby-core to get us to a better place for supporting applications. zzak and I have a goal to pave the way to get as many ruby developers to be active with the development of Ruby. Showing people it isn't a black box is an important part of that.
diff --git a/speaker.md b/speaker.md
@@ -3,9 +3,8 @@
 ## Contact details
 
 * Twitter: @example
-* Website or Blog: <http://example.com>
-* Company: Example Ltd.
-* Company website: <http://example.com>
+* Website or Blog: <http://example.net>
+* Company: Example Ltd. <http://example.com>
 
 [Feel free to add more details if you wish…]
 

diff --git a/speaker.md b/speaker.md
@@ -2,11 +2,13 @@
 
 ## Contact details
 
-* Email: <me@example.com>
 * Twitter: @example
 * Website or Blog: <http://example.com>
 * Company: Example Ltd.
+* Company website: <http://example.com>
+
+[Feel free to add more details if you wish…]
 
 ## Speaker bio
 
-[ Your bio here. 50-100 words is enough for us. ]
+[ Your bio here. 50-100 words is enough for us. ]
diff --git a/talk.md b/talk.md
@@ -1,12 +1,12 @@
 # Talk title
 
-* Desired talk duration: 15/30/45 minutes
+* Desired talk duration: 30/45 minutes
 
 ## Abstract
 
 [ Your talk abstract. Whether you make your proposal gist private or public is entirely up to you: we don't mind one way or another. You can, of course, edit your proposal right up until the deadline. ]
 
-For an example of a good proposal, see [this proposal by Jeff Casimir](https://gist.github.com/1780670).
+For an example of a good proposal, see [this proposal by Jeff Casimir](https://gist.github.com/1780670) and [“How to write a conference proposal” by Mike Moore](http://blowmage.com/2013/01/24/writing-conf-proposals)
 
 
 ## Notes

diff --git a/talk.md b/talk.md
@@ -4,7 +4,7 @@
 
 ## Abstract
 
-[ Your talk abstract. Whether you make your proposal gist private or public is entirely up to you: we don't mind one way or another. ]
+[ Your talk abstract. Whether you make your proposal gist private or public is entirely up to you: we don't mind one way or another. You can, of course, edit your proposal right up until the deadline. ]
 
 For an example of a good proposal, see [this proposal by Jeff Casimir](https://gist.github.com/1780670).
 

diff --git a/talk.md b/talk.md
@@ -4,7 +4,7 @@
 
 ## Abstract
 
-[ Your talk abstract ]
+[ Your talk abstract. Whether you make your proposal gist private or public is entirely up to you: we don't mind one way or another. ]
 
 For an example of a good proposal, see [this proposal by Jeff Casimir](https://gist.github.com/1780670).
 

diff --git a/talk.md b/talk.md
@@ -1,5 +1,7 @@
 # Talk title
 
+* Desired talk duration: 15/30/45 minutes
+
 ## Abstract
 
 [ Your talk abstract ]

diff --git a/speaker.md b/speaker.md
@@ -9,4 +9,4 @@
 
 ## Speaker bio
 
-[ Your bio here. 80-100 words is enough for us. ]
+[ Your bio here. 50-100 words is enough for us. ]
diff --git a/speaker.md b/speaker.md
@@ -9,4 +9,4 @@
 
 ## Speaker bio
 
-[ Your bio here ]
+[ Your bio here. 80-100 words is enough for us. ]
diff --git a/speaker.md b/speaker.md
@@ -3,9 +3,9 @@
 ## Contact details
 
 * Email: <me@example.com>
-* Twitter: 
+* Twitter: @example
 * Website or Blog: <http://example.com>
-* Company: 
+* Company: Example Ltd.
 
 ## Speaker bio
 

diff --git a/speaker.md b/speaker.md
@@ -2,11 +2,10 @@
 
 ## Contact details
 
-* Name: 
-* Company: 
 * Email: <me@example.com>
 * Twitter: 
 * Website or Blog: <http://example.com>
+* Company: 
 
 ## Speaker bio
 

diff --git a/speaker.md b/speaker.md
@@ -4,9 +4,9 @@
 
 * Name: 
 * Company: 
-* Email: 
+* Email: <me@example.com>
 * Twitter: 
-* Website or Blog: 
+* Website or Blog: <http://example.com>
 
 ## Speaker bio
 

diff --git a/talk.md b/talk.md
@@ -4,6 +4,8 @@
 
 [ Your talk abstract ]
 
+For an example of a good proposal, see [this proposal by Jeff Casimir](https://gist.github.com/1780670).
+
 
 ## Notes
 

diff --git a/speaker.md b/speaker.md
@@ -4,7 +4,6 @@
 
 * Name: 
 * Company: 
-* Phone number: 
 * Email: 
 * Twitter: 
 * Website or Blog: 

diff --git a/speaker.md b/speaker.md
@@ -0,0 +1,14 @@
+# [Speaker Name]
+
+## Contact details
+
+* Name: 
+* Company: 
+* Phone number: 
+* Email: 
+* Twitter: 
+* Website or Blog: 
+
+## Speaker bio
+
+[ Your bio here ]
diff --git a/gistfile1.md → talk.md b/gistfile1.md → talk.md
@@ -1,9 +1,4 @@
-# Proposal title
-
-## Speaker bio
-
-[ Your bio here ]
-
+# Talk title
 
 ## Abstract
 

diff --git a/gistfile1.md b/gistfile1.md
@@ -0,0 +1,15 @@
+# Proposal title
+
+## Speaker bio
+
+[ Your bio here ]
+
+
+## Abstract
+
+[ Your talk abstract ]
+
+
+## Notes
+
+[ Have you given this talk before? Anything else you'd like to mention... ]
No results found