Which guides should we write next? | Software Sustainability Institute

Name: *

Which guide first?

We've written lots of guides about software and software projects. We've also received a lot of suggestions about which guides we should write next. But which ones should we write first?

You now have the opportunity to help us prioritise the next guides we write. Please take a look at the list of ideas below and indicate whether you'd be very interested, quite interested, or not interested in reading a guide about them. The most popular guides will get written first.

Can you do better than us?

If you are an expert on any of the ideas below and you'd like to write a guide (and have it widely distributed on our website), then just info [at] software [dot] ac [dot] uk (let us know).

New ideas

Is there a guide that you would like to see written? If we've missed something off the list of ideas, then info [at] software [dot] ac [dot] uk (let us know).

Ideas for guides:

	Very interested	Quite interested	Not interested
Writing press releases
Choosing a software licence
Using GitHub effectively
Handing over software from one develop/group to another
Understanding the role of software development in the research environment
Best practice in use of revision control
The most useful tools for PIs
Developing web services - DOs and DON'Ts
Lessons we've learned whilst working on research projects
Asking for help from the development community (how to write support queries)
Getting to know the TRAC issue tracking system
How (and why!) to do a post-project review
Lower-cost alternatives to running a Software Carpentry boot camp
When and how to optimise your code
How developers should talk to researchers
Open-source and closed-source funding models
How not to lose your data
Embedded documentation
How to describe the tests or profiling you've done with your code
Handling support requests from users of your software
Cloud best practice guide and top-tips
Reasons why you should allow your PhD/RA to help out at a Software Carpentry boot camp
How licensing works for university code repositories
Writing a Software Management Plan
Expanding your user community
Should you adopt open standards?
Reasons why you should help out at a Software Carpentry boot camp
How to set up a research software collaboration
Best practice for contributing code to other people's projects
Agile development
Moving from Sourceforge to Github
SubVersion advanced tips and tricks
How to run an un-conference event
The Model–view–controller (MVC) architecture
Why you should add a scientific software developer to your research group
Career progression for research software developers