README.md in hirefire-0.1.2 vs README.md in hirefire-0.1.3

@@ -107,10 +107,56 @@
 
 - [Resque](https://github.com/defunkt/resque)
   - [Redis](https://github.com/ezmobius/redis-rb)
 
 
+Suggestions, Bugs, Requests, Questions
+--------------------------------------
+
+View the [issue log](https://github.com/meskyanichi/hirefire/issues) and post them there.
+
+
+Contributors
+------------
+
+<table>
+  <tr>
+    <th>Contributor</th>
+    <th>Contribution</th>
+  </tr>
+  <tr>
+    <td><a href="https://github.com/dirk" target="_blank">Dirk Gadsden ( dirk )</a></td>
+    <td>Implementing a more functional job/worker ratio notation using Lambda</td>
+  </tr>
+  <tr>
+    <td><a href="https://github.com/michelson" target="_blank">Miguel Michelson Martinez ( michelson )</a></td>
+    <td>Allowing HireFire to initialize in non-Ruby on Rails environments</td>
+  </tr>
+  <tr>
+    <td><a href="https://github.com/nbibler" target="_blank">Nathaniel Bibler ( nbibler )</a></td>
+    <td>Ensures that HireFire gracefully handles RestClient exceptions</td>
+  </tr>
+  <tr>
+    <td><a href="https://github.com/samoli" target="_blank">Sam Oliver ( samoli )</a></td>
+    <td>Adding the ability to specify a minimum amount of workers</td>
+  </tr>
+</table>
+
+
+Want to contribute?
+-------------------
+
+- Fork/Clone the **develop** branch
+- Write RSpec tests, and test against:
+  - Ruby 1.9.2
+  - Ruby 1.8.7
+  - Ruby Enterprise Edition 1.8.7
+- Try to keep the overall *structure / design* of the gem the same
+
+I can't guarantee I'll pull every pull request. Also, I may accept your pull request and drastically change parts to improve readability/maintainability. Feel free to discuss about improvements, new functionality/features in the [issue log](https://github.com/meskyanichi/hirefire/issues) before contributing if you need/want more information.
+
+
 Frequently Asked Questions
 --------------------------
 
 - **Question:** *Does it start workers immediately after a job gets queued?*
   - **Answer:** Yes, once a new job gets queued it'll immediately calculate the amount of workers that are required and hire them accordingly.
@@ -135,10 +181,9 @@
 - **Question:** *Will running jobs concurrently (with multiple Worker) cost more?*
   - **Answer:** Actually, no. Since worker's are pro-rated to the second, the moment you hire 3 workers, it costs 3 times more, but it also processes 3 times faster. You could also let 1 worker process all the jobs rather than 3, but that means it'll still cost the same amount as when you hire 3 workers, since it takes 3 times longer to process.
 
 - **Question:** *Can I process jobs faster with HireFire?*
   - **Answer:** When you run multiple jobs concurrently, you can speed up your processing dramatically. *Normally you wouldn't set the workers to 10 for example, but with HireFire you can tell it to Hire 10 workers when there are 50 jobs (would normally be overkill and cost you A LOT of money) but since (see Q/A above) Workers are pro-rated to the second, and HireFire immediately fires all workers once all the jobs in the queue have been processed, it makes no different whether you have a single worker processing 50 jobs, or 5 workers, or even 10 workers. It processes 10 times faster, but costs the same.*
-
 
 
 Other potentially interesting gems
 ----------------------------------
 
\ No newline at end of file