Sustainability and Maintenance: Supportability

return to list
Feature 1 2 3 4 5 6 7 8 9
Above pages/windows/files describe, or link to, a description of “how to ask for help” e.g. cite version number, send transcript, error logs etc. 0.3 0.5 0.6 0.6
E-mail archives are publicly readable. 0.2 0.5 0.5 0.5
E-mail archives are searchable. 0.1 0.3 0.3
E-mail archives or ticketing system shows that queries are responded to within a week (not necessarily fixed, but at least looked at and a decision taken as to their priority). 0.1 0.2 0.4 0.6 0.8 1.0 1.0
E-mail lists or forums, if present, have regular posts. 0.2 0.4 0.8 0.8 0.8
E-mails are archived. 0.1 0.1 0.1 0.2 0.4 0.5 0.5
E-mails are read by more than one person. 0.1 0.2 0.3 0.4 0.4
If there is a blog, is it is regularly used. 0.1 0.3 0.4 0.6 0.8 0.8
Project e-mail address has project domain name. 0.1 0.2 0.2 0.2 0.3 0.4
Project has a ticketing system. 0.1 0.2 0.4 0.6 0.8 1.0 1.0 1.0 1.0
Project has an e-mail address. 0.1 0.2 0.4 0.5 0.7 0.9 1.0 1.0
Project resources are hosted externally to a single-organisation/institution in a sustainable third-party repository (e.g. SourceForge, GoogleCode, LaunchPad, GitHub) which will live beyond the lifetime of the current project. 0.1 0.1 0.1 0.3 0.3 0.3 0.5 0.5 0.5
Software describes how to get support (in a README for command-line tools or a Help=>About window in a GUI). 0.1 0.2 0.3 0.5 0.8 1.0 1.0
Ticketing system is publicly readable. 0.1 0.2 0.4 0.4 0.5 0.5
Ticketing system is searchable. 0.1 0.2 0.3 0.3 0.5
User doc has page describing how to get support. 0.1 0.2 0.3 0.3 0.5 0.8 1.0 1.0
Web site has page describing how to get support. 0.1 0.2 0.3 0.4 0.5 0.6 0.8 1.0 1.0
Web site has search facility. 0.1 0.2 0.3 0.5 0.5
Web site has site map or index. 0.1 0.1 0.2 0.2 0.3 0.3