WSSSPE 2015 - 3rd Workshop on Sustainable Software for Science: Practice and Experiences

WSSSPE3 will organize self-directed teams that will collaborate prior to and during the workshop to create vision documents, proposals, papers, and action plans that will help the scientific software community produce software that is more sustainable, including developing sustainable career paths for community members. These teams are intended to lead into working groups that will be active after the workshop, if appropriate, working collaboratively to achieve their goals, and seeking funding to do so if needed.
We now seek to collect additional ideas for teams to work on at WSSSPE3 (via email; see below.)
Initial ideas for WSSSPE3 team activities, based on the breakout groups in WSSSPE2, are:
Development and Community
Writing a white paper/review paper about best practices in developing sustainable software
Documenting successful models for funding specialist expertise in software collaborations
Creating and curating catalogs for software tools that aid sustainability (perhaps categorized by domain, programming languages, architectures, and/or functions, e.g., for code testing, documentation)
Documenting case studies for academia/industry interaction
Training
Writing a white paper on training for developing sustainable software, and coordinating multiple ongoing training-oriented projects
Developing curriculum for software sustainability, and ideas about where such curriculum would be presented, such as a summer training institute
Credit
Hacking the credit and citation ecosystem (making it work, or work better, for software)
Developing a taxonomy of contributorship/guidelines for including software contributions in tenure review
Documenting case studies of receiving credit for software contributions
Developing a system of awards and recognitions to encourage sustainable software
Publishing
Developing a categorization of journals that publish software papers (building on existing work), and case studies of alternative publishing mechanisms that have been shown to improve software discoverability/reuse e.g., popular blogs/websites
Determining what journals that publish software paper should provide to their reviewers (e.g., guidelines, mechanisms, metadata standards, etc.)
Reproducibility and testing
Building a toolkit that could allow conference organizers to easily add a reproducibility track
Documenting best practices for code testing and code review