Summary of Questions and Responses from the PESO Planning Input Google Form
Background: The PESO Project is collecting community input on important topics that influence plans for post-ECP software-ecosystem sustainment. Results from the first 50 responses are summarized in the following documents, organized by question.
- What activities are you undertaking to grow the contributor base for your tool, and how could a sustainability organization help?
- What factors do you think should be considered when selecting and assessing a software product as part of a software sustainability organization portfolio?
- What are the top 3 things that your software project should do to improve its sustainability that a software sustainability organization could provide support for in some way?
- How does the user base for your package grow over time, and how could a sustainability organization help?
- What kind of outreach activities are you doing to grow your user base, and how could a sustainability organization help?
- What level of annual funding is needed for incremental development, delivery, and user support of your product?
- What are the critical factors that determine whether you will use an open-source library or tool?
- What are the most common impediments to you using more open-source libraries and tools?
- What factors do you (facilities staff) think should be considered when selecting and assessing a software product as part of a software sustainability organization portfolio?
- How can your facility staff contribute to a software sustainment effort?
- Which kinds of libraries and tools in the DOE software stack have the greatest potential for broader adoption and use by your (facilities) customers?
- What barriers to adoption might be addressed, at least in part, by a software sustainability effort?
- What are ways that you (facilities staff) can contribute to the ongoing sustainment of DOE software packages?
- How can you (facilities staff) help to broaden the contributor base for DOE software packages?
- What are the top things a software sustainability organization should (or should not) do to be a successful steward of DOE software?