Reviewing Your RailsConf Proposal

An aborted RailsConf Lightning talk I really wanted to share with attendees to encourage them to submit a proposal for RailsConf, RubyConf and any other conference really.

Transcript

1. Reviewing your RailsConf Proposal
2. Lots of proposals.
7. One month to submit.
8. It’s hard to chose.
10. But we had to.
12. 15.95%
13. Those odds aren’t that bad.
14. CFP-App
16. It’s a Rails app.
17. It’s open source.
18. You can contribute.
19. https://github.com/ rubycentral/cfp-app
21. So use it for your conf.
22. Make it better.
23. CFP-App helps.
24. A lot.
25. This is what CFP-App looks like.
27. title
28. tracks
33. And this is what we don’t see:
34. Who the speaker is.
35. Other reviewer’s rating.
36. Helps protect us from our own bias.
37. We only see other ratings after we rate.
39. It helps when:
40. You’re being too harsh.
41. You’re being too nice.
42. It’s helps achieve consensus.
43. We can also send comments to the candidate.
45. We help you improve your proposal.
46. Does it work?
49. That’s not good enough.
50. But we’ll do better next time.
51. We focus on good writers first.
52. But it doesn't stop there.
53. We later move beyond anonymous reviewing.
54. Because who you are does sometime matter.
55. Or your experience is relevant.
56. Or you’ve taught workshops before.
57. I only reviewed 180 proposals.
58. They reviewed a lot more.
59. Akira Matsuda
60. Marty Haught
61. Kinsey Ann Durham
62. Sarah Mei
63. Coraline Ehmke
64. Hug these people.
65. Submit a proposal!
66. RubyConf 2015
67. RailsConf 2016
68. TurbolinksConf 2017
69. EveryConf
70. HomeConf
71. Come talk to us if you need help.
72. We need your voice.
73. ❤ @olivierlacan