First Workshop on Maintainable Software Practices in e-Science

This post originally appeared on the Software Carpentry website.

First Workshop on Maintainable Software Practices in e-Science

9 October 2012
Co-located with 8th IEEE International Conference on eScience, Chicago

This workshop will focus on the issues relating to the development and maintenance of software that can endure past the limited periods of defined project durations and project funding, and go beyond software engineering best practice to address aspects of cultural, organisational and policy change. By bringing together all those with an interest in ensuring the longer term development and use of software for research, including researchers, developers, research computing specialists, software engineers, infrastructure providers, facilitators, and funders, the goal of this workshop is to understand what software practices can be successfully applied and which lead to long-term improvements in the development of software for e-Science.

As part of the workshop we will also be running a panel on the topic of culture change in software management for research, featuring invited speakers from a variety of disciplines who have experienced or instigated these changes, to talk about their real life experiences of scientists of what worked and didn't work for them.

Topics of Interest

We invite the submission of work that is related to the topics below. The papers can be either short (4 pages) position/experiences abstracts, or full (8 pages) research papers featuring original, unpublished work.

Topics of interest include:

  • software engineering and software product management best practice as applied to e-Science and computational science;
  • community development, collaborative development, and widening adoption;
  • licensing, funding, and business models for eScience and research software;
  • managing governance and organisational change during the software lifecycle;
  • measuring and analysing the impact of software and software processes;
  • software attribution, citation, and credit;
  • interaction between researchers, developers and stakeholders;
  • transferable software practices from industry.

Dialogue & Discussion

Comments must follow our Code of Conduct.

Edit this page on Github