Recommendations to clarify NASA open source requirements

by   John D. Haiducek, et al.

The software community has specific definitions for terms such as "open source software," "free software," and "permissive license," but scientists proposing software development efforts to NASA are not always knowledgeable about these definitions. Misunderstandings about the meaning of these terms can result in problems of fairness with solicitations, because scientists who interpret the terms differently than NASA intends may either needlessly limit the scope of their proposed work, or unwittingly propose work that does not comply with software licensing requirements. It is therefore recommended that NASA adopt definitions of the above terms that are in line with software community usage, that these definitions be communicated as part of solicitations to ensure a common understanding, and that proposals be required to identify what software licenses the proposers expect to use.


page 1

page 2

page 3


Tamil Open-Source Landscape - Opportunities and Challenges

We report in this paper, Tamil open-source software community is a vibra...

Towards Utility-based Prioritization of Requirements in Open Source Environments

Requirements Engineering in open source projects such as Eclipse faces t...

The Anatomy of Requirements

Requirements engineering is crucial to software development but lacks a ...

Forking Without Clicking: on How to Identify Software Repository Forks

The notion of software ”fork” has been shifting over time from the (nega...

From Seed AI to Technological Singularity via Recursively Self-Improving Software

Software capable of improving itself has been a dream of computer scient...

Please Don't Go – Increasing Women's Participation in Open Source Software

Women represent less than 24 from various types of prejudice and biases....

State of the Practice for GIS Software

We present a reproducible method to analyze the state of software develo...