As you might know, WTM is currently short of a programmer to push things forward. Tliff had more urgent things to take care of so he had to stop working on WTM.
What we’re looking for: > reliable, friendly and enthusiastic folks who want to make WTM better (and by reliable you understand we dont want someone who start messing the all site and change everything his way of course, team work ^^) > people who are able to react fast in case of big problems and can have a frequent presence on the IRC chat > in this case also necessary: programming skills
Here’s our setup: > Framework: Ruby on Rails & Capistrano deployment > Database: Mysql and some Redis > Webserver: Nginx & Unicorn > VCS: Git on Github
Your main task: > Kill the errorgator (make WTM run more stable) > Squash some bugs > Implement new features
Unfortunately we can’t offer any cash for compensation. We are all working for free! Because someone lately raised the question about how the supporter money is spent: All the money which goes into the site is spent on server and domain costs (We have never taken any money out of this pot).
Apply with your programming portfolio (please show us some sample code, your github profile, etc) to contact Naut at quiz@whatthemovie.com Best is to also come on the IRC chat or to drop us a message (Chrisy, Misterzob or Asmodai) on our profile if you are interesting or if you know someone, to get things moving faster :)
We’re not necessarily looking for one single programmer, it can also be a small team of people. We are first looking for someone who is already member of the community and already knows how the site works but of course we are open to wider suggestions if this doesn't work out :)
Let's build up a great new team and improve the best quiz site on the net (it still is hey!!)
No, seriously, atm i'm studying RoR and stumbled upon the v2.2+ connection pooling. At my regular job i develop Java-based webapplications (JSP/JSF) with massiv SQL usage and using pools and caches helps a lot to improve the speed of a db-based website. I just want to know if you use these techniques already.
We're using rails 2.3.3 and we're preparing the website to switch to the v3. For the others things, i can't tell you, not because i don't want to but because i'm not sure exactly. We use the rails caching and some redis