hone · July 1, 2012 19:21 · Jul 1, 2012 · Jul 1, 2012 · Jul 1, 2012 · Jul 1, 2012
diff --git a/talk.md b/talk.md
@@ -6,7 +6,7 @@
 
 Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backward incompatible changes. Also due to this inactivity, other queueing libraries like Sidekiq have come up to fill the void with new features.
 
-This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help with making Resque one of the best queueing libraries for Ruby.
+This talk will journey through the takeover of Resque and the balancing act of solving the old bugs while moving the project forward. On the topic of old bugs, we'll cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help with making Resque one of the best queueing libraries for Ruby.
 
 ## Notes
 

diff --git a/talk.md b/talk.md
@@ -11,3 +11,5 @@ This is a talk about the journey of taking over Resque and balancing the act of
 ## Notes
 
 Hihih! I would like to work in bacon and saunas into my talk but not exactly sure how! I have never given this talk before.
+
+People should walk away from this talk with a better understanding of the new changes introduced in Resque 2 and how that works with Rails 4 as well as what is helpful when participating in the community as a user.
diff --git a/talk.md b/talk.md
@@ -6,7 +6,7 @@
 
 Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backward incompatible changes. Also due to this inactivity, other queueing libraries like Sidekiq have come up to fill the void with new features.
 
-This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help.
+This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help with making Resque one of the best queueing libraries for Ruby.
 
 ## Notes
 

diff --git a/talk.md b/talk.md
@@ -6,7 +6,7 @@
 
 Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backward incompatible changes. Also due to this inactivity, other queueing libraries like Sidekiq have come up to fill the void with new features.
 
-This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help with things going forward.
+This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help.
 
 ## Notes
 

diff --git a/talk.md b/talk.md
@@ -6,7 +6,7 @@
 
 Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backward incompatible changes. Also due to this inactivity, other queueing libraries like Sidekiq have come up to fill the void with new features.
 
-This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward with new features. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help with things going forward.
+This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help with things going forward.
 
 ## Notes
 

diff --git a/talk.md b/talk.md
@@ -10,4 +10,4 @@ This is a talk about the journey of taking over Resque and balancing the act of
 
 ## Notes
 
-Hihih! I would like to work in bacon and saunas into my talk! I have never given this talk before.
+Hihih! I would like to work in bacon and saunas into my talk but not exactly sure how! I have never given this talk before.
diff --git a/talk.md b/talk.md
@@ -6,7 +6,7 @@
 
 Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backward incompatible changes. Also due to this inactivity, other queueing libraries like Sidekiq have come up to fill the void with new features.
 
-This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward with new features. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll end with how the community can help with things going forward.
+This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward with new features. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll close with how the community can help with things going forward.
 
 ## Notes
 

diff --git a/talk.md b/talk.md
@@ -4,7 +4,7 @@
 
 ## Abstract
 
-Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backtward incompatible changes.
+Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backward incompatible changes. Also due to this inactivity, other queueing libraries like Sidekiq have come up to fill the void with new features.
 
 This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward with new features. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll end with how the community can help with things going forward.
 

diff --git a/talk.md b/talk.md
@@ -6,13 +6,8 @@
 
 Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backtward incompatible changes.
 
-This is a talk about the journey of taking over Resque and we'll cover the work being done as well as the discussion of balancing the two parts:
-
-1. Maintaining legacy software in the 1.x branch
-2. Building Resque 2
-
-For the 1.x series, we'll go over the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll end with how the community can help with things going forward.
+This is a talk about the journey of taking over Resque and balancing the act of solving the old bugs and moving the project forward with new features. On the topic of old bugs, we'll go cover the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll end with how the community can help with things going forward.
 
 ## Notes
 
-Hihih! I would like to work in bacon and saunas into my talk! I have never given this talk before.
+Hihih! I would like to work in bacon and saunas into my talk! I have never given this talk before.
diff --git a/speaker.md b/speaker.md
@@ -1,12 +1,15 @@
-# [Speaker Name]
+# Terence Lee
 
 ## Contact details
 
-* Email: <me@example.com>
-* Twitter: @example
-* Website or Blog: <http://example.com>
-* Company: Example Ltd.
+* Email: <hone02@gmail.com>
+* Twitter: @hone02
+* Website or Blog: <http://hone.heroku.com>
+* Company: Heroku
 
 ## Speaker bio
 
-[ Your bio here. 50-100 words is enough for us. ]
+
+Terence works at Heroku maintaining the Ruby stack and a slew of OSS projects such as Bundler and Resque, 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, where everything is three times bigger!
+
+(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,18 @@
-# Talk title
+# Rescuing Resque
 
-* Desired talk duration: 15/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. ]
+Resque has been plagued by issues over the past half a year due to inactivity on the project. For instance, resque doesn't handle the cleaning up workers on distributed systems like Heroku. This issue ([#319](https://github.com/defunkt/resque/issues/319)) has been open for over a year. redis.rb 3.0.0 came out on May 23rd which brings improved performance and backtward incompatible changes.
 
-For an example of a good proposal, see [this proposal by Jeff Casimir](https://gist.github.com/1780670).
+This is a talk about the journey of taking over Resque and we'll cover the work being done as well as the discussion of balancing the two parts:
 
+1. Maintaining legacy software in the 1.x branch
+2. Building Resque 2
+
+For the 1.x series, we'll go over the challenges of getting a stale project in order and into a solid state. Next up will be the work on Resque 2. Rails 4 introduces ActiveQueue and Resque is going to be a first class citizen in the Rails Queueing ecosystem. In order for this to happen, there will be a new Queue interface similar to stdlib's Queue class. We'll walk through reworking the Worker class so it supports both the current jailboxed Forked Consumer as well as a Threaded Consumer for heavy I/O jobs. We'll end with how the community can help with things going forward.
 
 ## Notes
 
-[ Have you given this talk before? Anything else you'd like to mention... ]
+Hihih! I would like to work in bacon and saunas into my talk! I have never given this talk before.
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