Railscamp lousy tshirt draft


Published on

A draft version of a talk following up on the advantages and disadvantages of possible improvements to Railscamp.

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Railscamp lousy tshirt draft

  1. 1. I went to Railscamp, and all I got was a lousy t-shirt How to improve Railscamp Andrew Grimm University of New South Wales
  2. 3. Aim of talk <ul><li>To vaguely summarize current (conflicting) thoughts about improving Railscamp
  3. 4. Speech bubbles represent heckling (zombie-chaser, zombie-heckler, hahahaha...) of new suggestions (some of them quotes) </li></ul>These proposals aren't half bad! No, they're ALL bad!
  4. 5. Reasons for attending Railscamp <ul><li>Boozecamp: A weekend away, werewolf, poker, Guitar Hero, stupid stunts, and beer
  5. 6. SmallTalkcamp: Chat with like-minded people, hear about the newest technologies
  6. 7. Rubycamp: Learning about ruby and Rails </li></ul>Our beer meetup group has a Rails problem! Railscamp? I thought this was for Javascript!
  7. 8. John West theory <ul><li>Rejecting people who are being sent in a group by a corporation is ok
  8. 9. Rejecting people who aren't already part of RORO is ok </li></ul>People who aren't active in the community … won't know about the camp or when to buy tickets. And that's fine...
  9. 10. Is there a shortage of tickets? <ul><li>Railscamp Canberra sold out within 4 hours of opening
  10. 11. If you joined RORO after they went on sale, you're SOL until the following one </li><ul><li>Unless you get a ticket from someone dropping out </li></ul></ul>Growing the community ≠ including more people in Railscamp
  11. 12. How to deal with the shortage <ul><li>Increase Railscamp size
  12. 13. More frequent Railscamps
  13. 14. Region-based Railscamps
  14. 15. Start having Rails conferences </li></ul><ul><li>Lotteries for tickets
  15. 16. Ticket quotas for newbies
  16. 17. Required breaks
  17. 18. Alternative topic camps
  18. 19. No booze </li></ul>
  19. 20. Increase Railscamp size <ul><li>Means not everyone knows everyone
  20. 21. Sufficiently large camp grounds may not exist
  21. 22. Hiring out a hotel might work, but then it'd be more of a conference </li></ul>
  22. 23. More frequent Railscamps <ul><li>Make each Railscamp less special </li></ul>
  23. 24. Region-based Railscamps <ul><li>Some states may be too small for their own camp
  24. 25. Merging states together (Barassi Line) might work better
  25. 26. Would mean not meeting up with people you know </li></ul>Mitosis doesn't work with communities.
  26. 27. Start having Rails conferences <ul><li>Australia has the most Railscamps, and yet has never had a conference </li><ul><li>Are Aussies a bunch of pissheads? </li></ul><li>Conference requires Big Deposit Up Front
  27. 28. Pay for speakers from overseas
  28. 29. Wouldn't have Guitar Hero </li></ul>
  29. 30. Lottories for tickets <ul><li>Allow people to reserve single or group tickets for a couple of weeks, and then determine at random who comes </li><ul><li>Means people missing out </li></ul></ul>
  30. 31. Quotas <ul><li>Reserve a number of tickets for first or second-timers, or those intending to mentor
  31. 32. Don't sell all tickets at once, but have two rounds of selling </li></ul>
  32. 33. Required breaks <ul><li>Have to give Railscamp a miss if you've been to the previous two, unless you're organizing it </li></ul>I keep missing Railscamp! Me too, but my aim is improving!
  33. 34. Alternative topic camps <ul><li>Maybe we need a miscellaneous camp </li></ul>
  34. 35. No booze <ul><li>Make Railscamp's appeal more selective
  35. 36. Crazy talk territory! </li></ul>
  36. 37. Making Railscamp affordable for all? <ul><li>Many people can easily afford railscamp, but not everyone </li><ul><li>Some choose camping over cabins to save money </li></ul><li>Subsidize students, unemployed, first-timers?
  37. 38. Corporate sponsorship could pay </li><ul><li>Banners out, but stubbies and acknowledgement ok </li></ul></ul>
  38. 39. Making Railscamp more productive <ul><li>Pitch sessions
  39. 40. Multiple talk venues
  40. 41. Get people mingling
  41. 42. Software for group projects
  42. 43. Internet ban
  43. 44. New Zealand </li></ul>Railscamp? Productive? Isn't that what conferences and hack nights are for?
  44. 45. Pitch sessions <ul><li>Already used at hack nights
  45. 46. Describe group projects </li></ul>
  46. 47. Multiple talk venues <ul><li>Talks going over time are a fact of life
  47. 48. Mainly a problem if the schedule is so jam-packed it forces other talks to be late
  48. 49. Multiple talk venues avoid tight scheduling </li></ul>Epic LOLs when they happen to be management methodology talks
  49. 50. Get people mingling <ul><li>People shouldn't work on their own stuff solo? </li><ul><li>People can casually join in on solo projects </li></ul><li>Werewolf and Guitar Hero are good at this? </li><ul><li>Even though the former seems anti-social
  50. 51. Werewolf criticised as cliquey </li></ul><li>Urban Terror and other first-person shooters aren't good, because they're not face to face? </li><ul><li>Disagreement on this too </li></ul></ul>
  51. 52. Software for group projects <ul><li>Let's do stuff
  52. 53. What
  53. 54. Boredjour
  54. 55. Somewhat under-utilised? </li></ul>
  55. 56. Internet ban <ul><li>Is it by design or by necessity?
  56. 57. Is it meaningful to partially ban the internet? </li></ul>No, but is that stopping the government?
  57. 58. New Zealand <ul><li>Let them manage their own Railscamps, even if Aussies attend </li></ul>No need for them to be sheepish about it!
  58. 59. Will someone please think of the newbies? <ul><li>Do we need to reach out to newbies?
  59. 60. Programming activities for Railscamp
  60. 61. Appropriate talk topics </li></ul>Yes, we've got them in our sights!
  61. 62. Do we need to reach out to newbies? <ul><li>Unlike RORO meetups, Railscamp attendees are committed to Rails/ruby </li></ul>Railscamp rocks as-is, and if we try to make it super-approachable for new attendees we'll probably just end up gimping it.
  62. 63. Programming activities for Railscamp <ul><li>Projects with instant gratification
  63. 64. Work better when installation done beforehand
  64. 65. Brains
  65. 66. RubyWarrior
  66. 67. Triaged Rails bug tickets </li></ul>
  67. 68. Appropriate talk topics <ul><li>Some RORO regulars feel they can only talk on ever more advanced topics
  68. 69. Talking about the advantages and disadvantages of competing gems (eg authentication) would be good
  69. 70. Lightning talks on useful gems people have come across
  70. 71. Bring back the analog blog! </li></ul>
  71. 72. Conclusion <ul><li>A few changes are generally seen as good, but most would be controversial </li></ul>