CW13 What people hope to gain from attending

Here is a list of what those who have registered hope to gain by attending the Collaborations Worskhop. Maybe their reasons resonate with you or you could help. If so, we hope to see you there !

  • To understand the current state of the software in research community.
  • To find out how we can continue to best work with the research community.
  • I would like to meet some developers and discuss how I view solutions to my problems, so that I can get opinions about possible software solutions.
  • New collaborators and ideas. A sense of how the community has evolved in the last year with regards to the push for open access.
  • Interesting ideas about how others are approaching issues. Good contacts. Fun!
  • Learning about the rest of the community, seeing my role as a software consumer and developer, talking about how best to train people who don't think of themselves as developers.
  • A better understanding of how people from other disciplines are creating and maintaining their software, as well as ways that people have been able to get academic credit for doing so.
  • Engagement in my role as an Institute Fellow.
  • Meet the Institute's Fellows to discuss areas of mutual interest. Identify topics for future collaboration with other delegates.
  • Meet other research software engineers and develop collaborations.
  • Learning what the community expects and needs from organisation like the Software Sustainability Institute. Meeting in person Institute Fellows. Discussing further work with them.
  • To understand code best practice; to learn about software novel approaches; to learn how to release code and network with the community.
  • Advice on improving the management of the highly used domain orientated software that I produce.
  • I hope to promote, expand and develop the RCUK-funded IT as a Utility Network and the rest of the wider RCUK Digital Economy theme.
  • New ideas; as a result of last year I ended up arranging the first Software Carpentry workshop at my University.
  • An understanding of the motivations, perspectives and constraints on researchers writing software.
  • A better understanding of what application area researchers need and want.
  • Networking.
  • As my programming skills develop, I'm getting increasingly interested in crafting good scientific software. Everything I've learned about software development has massively benefited my research and I'm really keen to learn more/share ideas/think about how to encourage other scientists to feel the same way.
  • Networking and understanding some of the current challenges in the community.
  • An idea of what EPSRC's strategic priorities should be for software funding.