Editing in IE6!
Discussion article for the meetup : Melbourne, Friday 1st July 7pm WHEN: 01 July 2011 07:00:00PM (+1000) WHERE: 55 Walsh St, West Melbourne 3003 Directions: Enter the somewhat unfriendly building, climb the stairs to the top (2 floors), and turn left. If the front door is locked look for a...
Test
More Testing...
This is a test article
Cache should be cleared
Directions: Enter the somewhat unfriendly building, climb the stairs to the top (2 floors), and turn left. If the front door is locked look for a sign that includes my phone number ask me to let you in.
Discussion: http://groups.google.com/group/melbourne-less-wrong
We meet on the first Friday of each month. We formally start at 7pm, but I'll be here from 6pm and you're all welcome. You're all welcome to BYO liquid refreshments.
Ok, it has been reverted.
I've just deployed a fix that will apply to all new poll votes. Thanks jimrandomh for passing on the bug report and initial patch.
Please note that as of late last year the official development environment is now built with Vagrant. The primary repo contains a Vagrantfile and all the chef recipes (derived from our production recipes where possible) necessary to configure a base Ubuntu box for LW development.
The instructions for using this are at: Development-VM-Image.
Your fix for the incorrect median calculation has been deployed.
You're correct, John deliberately changed this as he thought it was a bug. I'll chat to some people to work out what the desired behaviour is.
John implemented the new feature, I just integrated it and deployed it.
This is actually a bug, not a feature. Some major changes to how karma is stored and passed around the application were made in order to implement the percentage tooltips. Scores are now passed around as an array containing the number of up votes and down votes, where previously it was the difference of the two. It appears the this array is being incorrectly rendered in the side bar, instead of the calculated score.
Great to hear you're interested in contributing Chris. The LW codebase takes a bit to get your head around so I'd certainly suggest starting with smaller bugs or small features before diving into big new features. You should definitely get in touch with us (TrikeApps) and Luke to discuss what you want to work on to make sure it's the best use of your time and your approach considers all angles.
For reference, Accepted issues are generally bugs. The Accepted status indicates they have been reviewed and acknowledged as a bug. Approved is used to indicate tickets that are approved for work (generally by Lucas). These are good candidates to work on but you should definitely coordinate with us to make sure they aren't being worked on already.
I received a lot of errors over the weekend relating to a performance regression introduced in the last set of changes. Eugine, you were one of the people affected by these errors. I released a fix for this yesterday and have not seen those errors since. Work is also underway to migrate to a new database server.
SiteMeter in the sidebar was the cause of this. It has been removed.