 Bloomberg, as most enterprises, has been a consumer of open source for many, many years, but within the last few years it's become vitally important to us because the open source community is now producing software that's better than any other alternative. For many use cases, the best solution to the problem is actually an open source software product. So when we look to deploy new pieces of infrastructure or solve new problems, we actually now are searching for open source solutions before we look to find things or to build things of our own, and that as a result then we end up contributing back the improvements that we make since we have very unusual use cases in many scenarios. Even outside of just Bloomberg, an open source in general, the collaborative element allows people who care the most about the software's evolution to expend their energy on it. So that doesn't mean that people who are being paid don't also do a great job, but when you have people who are motivated by their own interest in the software being better, you end up with very, very good software that's produced at a very rapid pace. Recently the Bloomberg website was relaunched, a brand new version built on a bunch of new technologies including opensource, node.js and other things, and our web development team built a new JavaScript web application framework for that website and others, and was so successful at what they were doing with it that they decided to release it as an open source project of its own. So we've released that, it's called Briskit, and they've begun talking about it at JavaScript conferences and other places, and it's begun to gain some awareness as well. One of the things we began last year, which we think so far, we're the only company that's been doing this, we have sort of combined open source and our philanthropic efforts, and we've been running open source volunteer coding days where we have employees and students from universities and people from existing open source project communities come into Bloomberg for a day or a weekend and just sit there, work together on improving the project, which of course increases awareness inside our company, and we're giving back, of course, improvements to the code, and that's been extremely successful. We've done that for, I think, three or four open source projects now, and the demand is high enough that we'll probably try to do five or six of them in the coming year and see if we can even improve more after that.