Guides

The Institute gathers many contributions from external authors to our blog and news. If you're planning on writing a text for us, here are some tips of what we're looking for in a blog post or news item.
Photo by Aaron Burden.

Whether you're writing a blog post, a news item, or a speed blog post (at one of our events), these guides are aimed at anyone writing for the Software Sustainability Institute.

Niall Beard, from the University of Manchester, has written a guide for the Software Sustainability Institute on "Adding schema.org to a GitHub Pages site." 

By Mike Jackson, Software Architect

By Will Usher, Senior Researcher: Infrastructure Systems Modeller, University of Oxford

By Aleksandra Nenadic, Training Lead

By Neil Chue Hong, Director.

This guide explains how software fits with the EPSRC policy framework for research data.

By Neil Chue Hong, Director of the Software Sustainability Institute.

Google announced today that their open source project hosting site, Google Code, is to close. The site has disabled the creation of new projects, will turn read-only on 24 August 2015, and will close on 25 January 2016. In the announcement.

Google's Director of Open Source Chris DiBona cited the move of projects away from Google Code to other services such as GitHub and BitBucket - indeed Google itself has moved thousands of its projects to GitHub.

The first thing to stress is: don't panic.…

By Mike Jackson, Software Architect.

This is a guide on using Git and GitHub within a VMWare virtual machine (VM) which, for whatever reason (e.g. organisational security policies), cannot be connected to a network.

Why write this guide?

This guide arose from our open call collaboration with the Distance project at the University of St. Andrews. They use Windows XP virtual machines for developing their Distance for Windows software. Their interface code, implemented in Visual Basic, is not held under revision control and institutional security policies…

Much research software starts its life thanks to a research grant. But what happens when your code proves useful and you want to extend it or ruggedise it for release to the wider community? Research grants generally can't help because they focus on solving research problems, not improving code. Who should you turn to?

We're putting together a list of funders and funding calls who can help with the costs of improving code. This list is not comprehensive, but we'd like it to be. If you know of other sources for this type of funding, please let us know and we'll add them to the list…

Subscribe to Guides