-
Notifications
You must be signed in to change notification settings - Fork 101
Sustainability of Clawpack
rjleveque edited this page Nov 12, 2014
·
16 revisions
- Publications
- Metrics
- Publications
- Downloads
- PyPI
- Github forks/clones
- Citations
See http://arxiv.org/pdf/1404.7414v2.pdf, especially the criteria on p. 19:
- Will the software continue to provide the same functionality in the future, even if the environment (other parts of the infrastructure) changes?
- Is the functionality and usability clearly explained to new users?
- Do users have a mechanism to ask questions and to learn about the software?
- Will the functionality be correct in the future, even if the environment changes?
- Does it provide the functionality that existing and future users want?
- Will it incorporate new science, theory, or tools as they develop?
- What parts of the code base are not deeply understood even by core developers?
- What parts are understood well by only one person?