Replies: 1 comment
-
Hi Husled: We have a number of projects with USSF and USAF whereby we harden open-source software to military-grade specifications. What we do is instrument the software, observe it, and then remove the unused components. We have a number of open source initiatives whereby we are hardening open source software and suspect we can help NASA harden their open source projects to meet NPR 7150 guidelines, an example of the project is here: https://github.com/rapidfort/community-images there are also some Ironbank images that are hardened to USAF requirements, happy to talk you through the projects, so please email me at Russ@rapidfort.com and I will connect you internally with he right parties. |
Beta Was this translation helpful? Give feedback.
-
In my opinion, developing open source software at NASA is overly burdened by existing directives. The first major roadblock is NPR 7150, which requires a defined (and often laborious) process for software release. The second is the NOSA (and requirement for external contributors to sign a CLA), which is incredibly non-standard within the open-source software community and nobody external knows how to deal with.
Both of these make it difficult to work on research software, or even just release scripts underpinning your scientific analyses. I know there are reasons for these processes, and there are ways to deal with them, so I'm wondering what different perspectives there might be within TOPS, and how people deal with them efficiently.
I also am interested in what changes might be happening here (revised directives etc) to enable quicker release of research code.
Beta Was this translation helpful? Give feedback.
All reactions