Software guidance expansion

[RPaseka]

• [ ] List examples of journals for open source software (e.g. Software Heritage, ACL); similar to how we give suggestions for selecting external data repositories
• [ ] Examples of a software code of conduct 1,2 / contributing guide; guidance on what should be included in these
• [ ] add link to this reference
• [ ] review NIH best practices for sharing software for any areas not already addressed by the OSS Guidance

[nasacrawford]

@demitri here is the issue for you to review.

[jordanpadams]

JPL has been undergoing some efforts to develop some best practices, templates, and guides for developing open source software. It includes "starter kits" for users to get going with software, IT security scanning information, among many others. It is also open source and welcome to community contribution: https://nasa-ammos.github.io/slim/. I think it could definitely be integrated in some way with some of this software development / software management guidelines for Open Science and SPD-41a. @riverma is leading that effort at JPL and I'm sure would love more community input.

[riverma]

JPL has been undergoing some efforts to develop some best practices, templates, and guides for developing open source software. It includes "starter kits" for users to get going with software, IT security scanning information, among many others. It is also open source and welcome to community contribution: https://nasa-ammos.github.io/slim/. I think it could definitely be integrated in some way with some of this software development / software management guidelines for Open Science and SPD-41a. @riverma is leading that effort at JPL and I'm sure would love more community input.

Thanks for the inclusivity here @jordanpadams. Nice to meet you @RPaseka and @nasacrawford. Our project “Software Lifecycle Improvement & Modernization”, or SLIM for short, is definitely applicable here and could help out this ticket. Here’s some bullet-points about the project:

• SLIM is an open source collaborative effort to define and deploy software process improvements to NASA projects
• We’re focused on improving projects’ software lifecycle (write, build, test, deploy software), governance of software projects, and information sharing / documentation of software
• We treat software process improvements / best practices as code and as such we deploy improvements to projects via direct, automated patches that can be pushed or pulled from our codebase

Here’s a presentation I gave about our project (and the overall vision) at Linux’s Open Summit earlier this year: https://www.youtube.com/watch?v=eRc93r-CdAI

For some direct artifacts that might help out this ticket:

• Code of Conduct Guide: https://nasa-ammos.github.io/slim/docs/guides/governance/contributions/code-of-conduct/
• Contributing Guide: https://nasa-ammos.github.io/slim/docs/guides/governance/contributions/contributing-guide/

If SLIM sounds like something of interest to the folks here - I definitely encourage us to chat and help each other!