Software Sustainability Institute's Collaborations Workshop 2015

This post originally appeared on the Software Carpentry website.

The Software Sustainability Institute's Collaborations Workshop 2015 (CW15), which will be held on March 25-27, 2015 in Oxford, UK, focusses on software, best practice and the social side of working past the boundaries of traditional disciplines and roles to accelerate research outcomes—or put differently, interdisciplinarity done right!

What will you learn by attending:

  • The social and technical sides of interdisciplinary working.
  • Examples of best practice of when it's been effective - and horror stories of when it has not.
  • Examples of techniques and technologies that could be applied from one discipline to another - discipline hopping.

CW15 brings together researchers, software developers, managers, funders, publishers and more to share practice, explore ideas, highlight problems and establish a community based understanding of the state of interdisciplinarity, collaboration and software.

This will also be your chance to meet many of the Institute's 2015 Fellows: ambassadors for software in their varied research domains, including physics, digital history, genetics, glaciology, addiction studies, systems biology, to programming languages and high performance computing.

CW15 is an 'unconference' event and this interdisciplinarity theme will run through the schedule, which includes keynotes,lightning talks, demos, collaboration and discussion sessions, and concludes with this year's CW Hackday. The CW Hackday will focus on topics related to effective interdisciplinarity—reproducible research, data/code sharing, and data science—so you are free to bring your own data. There will be prizes for the best team efforts. The Hackday will start on the evening of March 26th after the main CW15 event. Please note attending the Hackday only is free but still requires registration.

Register for CW15 and/or CW Hackday at We look forward to seeing you!

Dialogue & Discussion

Comments must follow our Code of Conduct.

Edit this page on Github