Sessions at Open Source Bridge 2010 about Social with notes

Your current filters are…


Wednesday 2nd June 2010

  • SELECT * FROM Internet Using YQL

    by Jonathan LeBlanc

    The Yahoo! Query Language provides a rich and dynamic method for obtaining and manipulating data from any source or API on the internet – with YQL the internet becomes your database. Using the simplified SQL syntax that YQL is based in, YQL seeks to open all data on the web into a standardized format. Manipulating and mashing up sources as if they were tables, YQL becomes a repository for exploring government, event, social and API data on the web.

    This talk will cover the core techniques within YQL, including server-side JavaScript with native E4X support for manipulating data, key / value pair data storage and the process of creating your own YQL tables for accessing web based content. Going further with the integration of the open authentication standards defined by OAuth, we’ll delve into advanced authentication techniques using this standard within YQL.

    At 2:30pm to 3:15pm, Wednesday 2nd June

  • How To Report A Bug

    by Michael Schwern

    The process of reporting a bug starts off with two strikes against it. The user is angry; they're taking time away from doing their work to report a bug. The developers are annoyed; some freeloader is telling them they made a mistake and they have to take time to fix it. Accusations fly. Tempers get heated. Nobody is happy. Nobody wants to help anyone.

    Developers often treat bug reports like the user dumped a bag of crap on their doorstep, rang the bell and told them to clean it up. That's not what they are. A bug report is a user walking up to your door, stepping in crap, pointing out maybe it should be cleaned up.

    Nobody likes stepping in crap. And nobody likes cleaning it up. So the whole interaction starts off on the wrong foot, perhaps the one covered in crap. Your job, as developer or as reporter, is to deliberately steer it back to being a positive one where the developer wants to fix your bug and the reporter wants to continue to report bugs.

    As a user, and as a developer, some simple social hacks will turn bug reporting from a hateful shoutfest into a pleasant collaboration. We'll look at some dos and don'ts when reporting and receiving a bug, how to provide enough information, avoid a hostile tone, make it easy to report and track bugs, and how to keep your head when all you really want to do is bash someone's in.

    As a developer, you'll encourage more and better quality feedback from your users and even pick up new developers in the process. As a user, developers will find your reports so delightful they'll enjoy patching it. And you'll both improve the software you use and love.

    At 3:45pm to 4:30pm, Wednesday 2nd June