11–20 of 23 posts
At least give us the option of using an email address, even if it may mean implementing this voting some other way.
First of all, great idea! But I think it would make for a fairer process if the current votes weren't displayed. I added a "display:none;" to the "baloon_counter" class via firebug so that my votes aren't influenced by other people.
I find it really cool to see what people like! The process is fair anyway imo :)
I find the page design and voting buttons a bit too distracting. Also considering the number of talks, some kind of tagging/categories would help.
Needing a GitHub account to vote is quite obnoxious. It's no different than those sites which require a Facebook login, for instance. At least give us the option of using an email address, even if it may mean implementing this voting some other way.
If you're crazy like me and constantly refresh the page to see if your favourite talk will make it to the next round, here is a simple Python script to do it for you: https://gist.github.com/4502077
Needing a GitHub account to vote is quite obnoxious. It's no different than those sites which require a Facebook login, for instance. At least give us the option of using an email address, even if it may mean implementing this voting some other way.
Needing a GitHub account to vote is quite obnoxious. It's no different than those sites which require a Facebook login, for instance. At least give us the option of using an email address, even if it may mean implementing this voting some other way.
Hey, thanks for your opinion. We try to keep it simple. We know that when someone has a Github account he's probably a programmer.
Needing a GitHub account to vote is quite obnoxious. It's no different than those sites which require a Facebook login, for instance. At least give us the option of using an email address, even if it may mean implementing this voting some other way.
Using GitHub seems like a pretty good way to try and filter out fraudulent votes (almost impossible with email address logins) - and it isn't really that much of a imposition given the nature of the conference - if you want to contribute pull requests to Django you need a GitHub account these days anyway.
technically, you don't.