Benjamin Muskalla showed a better workflow to handle patches by OSS contributors using Eclipse Mylyn. See this video for an introduction to the idea.
After him, Alessandro Nadalin showed some advantages of using REST (and when not to use it). My criticism is that HTTP caching is brittle as it stands and can cause all kinds of problems. So, yes, if the caching works, REST is great. But if it breaks, all kinds of havoc can ensue. Worse, many problems simply don’t well with REST. Twitter and RSS feed downloads? Yes. Web conversations? No.
Lastly, we had Ivo Neskovic demonstrating Project FoX which allows to define mathematical rules to which some code has to comply. The demonstrated example (a buffer) was simple enough. As always, there was no telling how amount of work grows with code size. Most of these tools suffer from the problem that a) the effort grows exponentially (so you need 4 times the effort to handle twice as much code) and/or b) there is an explosion of test cases (so you might have all the tests but it would take years to run them).