21 | 
215 |
216 | 
87 | 89 | An experiment that explores methods for visualizing NASA's open-source code projects using machine-learning generated keyword tags and clustering techniques. Exists as a live, editable, JavaScript + GUI notebook on ObservableHQ. 90 |
91 |
105 | 107 | One way to answer this question, is to tabulate Github statistics for forks, stars, clones, etc. This live, editable notebook on ObservableHQ lets you understand how the public is engaged with NASA code. 108 |
109 |
114 | 116 | It is hard to get an exact answer to how many labor hours went into an agency's open-source software. This short notebook acts as an explorable explaination. It lets a user ballpark a likely range given a few assumptions. 117 |
118 |
123 | 125 | There is an astronomy code sharing website that incorporates NASA astronomy related code into their collection. In order to make their job easier, this notebook lets them download all new code of a given license type updated since a certain date. 126 |
127 |Submit a request to release your project as Open Source to your center SRA (Software Release Authority) at https://softwarerelease.ndc.nasa.gov/. Check out a more detailed description of the SRA process at the bottom of this page.
147 |After going through the SRA process, receive approval from your center SRA to release as Open Source.
154 |Register on github.com/join using your NASA email address.
161 |Submit a NAMS request by filling out the HQ AGCY NASA GitHub Collaborator Form. This will request you be added as a member or collaborator to https://github.com/nasa. For new repo requests, you must include your SRA approval number into TEAMS & Repositories
168 |Reach out to us after submitting NAMs request. We can help you join NASA Org or answer any questions.
175 |Transfer or import your source code into the NASA Org on GitHub.
182 |Update the NASA Open Source Catalog via a pull request (repo here), or by our online form (behind NASA firewall) to register your project's meta-data. Be sure to provide good tags for your code project & follow this government-wide guidance on specific tags to use if your code involves machine-learning or artificial intelligence.
189 |After your request is approved, you can view your project on code.nasa.gov and socialize! Email opensource@lists.nasa.gov or view help.github.com/articles/be-social.
196 |Software release at NASA is governed by NPR 2210.1C. NPR 2210.1C establishes the roles, responsibilities, and procedures for reporting, reviewing, and releasing software under various conditions, including open source. Every center has a Software Release Authority (SRA). The SRA processes requests for software release and coordinates legal, export control, IT security, 508 compliance, and software engineering standards compliance reviews. Projects hoping to release software should contact their SRA early to discuss their goals and begin the reporting, review, and release process.
203 || Center | 213 |215 | | 216 | | 217 | | |
|---|---|---|---|---|
| [[item.Center]] | 221 |[[item.Email]] | 222 |[[item.Name]] | 223 |[[item.Title]] | 224 |[[item.Phone]] | 225 |
To release code, it must go through a process run by the Software Release Authority or SRA.
236 |One initiates the software review process by reporting the software as described in NPR 2210.1C (e.g., submitting a description of the software to be released, the individuals involved in its creation, development timeline, available documentation, and related topics). Depending on center procedures, this information may be captured through the NASA Technology Reporting System or standard form NF1679. Contact your SRA for the specific procedure used at your center.
237 |Each piece of software is unique, and must be reviewed on a case-by-case basis. Generally speaking, however, the review process will address the following considerations:
238 | 239 |Legal.
240 |
It is important to ensure that NASA has appropriate rights in software, including subcomponents, before NASA releases that material outside the agency. Software is rarely developed in isolation. If your project uses external dependencies, you must provide details about such packages or sources when you report your software. (See NPR 2210.1C, Chapter 2 for details on reporting software.) The terms and conditions governing external software impact NASA's right to use and release software, and must be thoroughly analyzed before NASA can release software incorporating that external software. NASA attorneys will also help identify the set of terms and conditions that should govern a particular piece of software when NASA releases it. Per current NASA policy, NASA releases open source software under the NASA Open Source Agreement (NOSA) unless external Open Source Software incorporated into the NASA Open Source Software requires use of a different open source license or unless approved by Center Patent or IP Counsel. Such determinations must be made by your center intellectual property counsel before NASA may release the software in question.
Export Control.
242 |
The Export Administration Regulations (EAR) and the International Traffic in Arms Regulations (ITAR), among other laws and policies, restrict which NASA technology may be publicly disclosed. Software falling within the scope of these laws or policies cannot be released open source, and may be subject to release restrictions. Your local export control staff can help you determine whether export control laws apply to your technology.
IT Security.
244 |
Generally speaking, released software should not contain any information peculiar to NASA, such as user names, passwords, database credentials, IP addresses, host names, firewall and network information, or any other data which would expose or create vulnerabilities. Your SRA and IT Security staff will help you understand the types of risks occasioned by software release, and will work with you to remove elements of your software which may give rise to a vulnerability prior to release.
508 Compliance.
246 |
When developing, procuring, maintaining, or using Electronic and Information Technology (EIT), Federal agencies must ensure that Federal employees with disabilities have access to and use of information and data that is comparable to that for other employees.
Software Engineering Requirements.
248 |
NASA has established formal software engineering requirements in NPR 7150.2A. These requirements govern all software development activities and must be followed throughout a project's development life cycle. As part of the software release process, your center SRA and Engineering Technical Authority for software will work with you to verify (or establish) your software classification and ensure compliance with the corresponding engineering requirements prior to release. For this area of inquiry in particular it is best to front-load compliance by adhering to the software engineering requirements with a documented compliance matrix from the outset. Otherwise, you may incur significant delay and expense in obtaining compliance prior to release.
Depending on the number of projects being assessed for release at any given time general workloads and backlogs, traversing the release process can take anywhere from 3 to 6 months. The process may take longer for complex or novel release requests. Be sure to factor these time tables (with consultation with your SRA) into your project schedules.
250 |
148 | 193 | 194 | [[_getProperty(item, 'Public Code Repo')]] 195 | 196 |
197 | 198 | 199 | 200 |[[item.Description]]
201 | 206 | 207 | 208 | 213 | 218 |92 | Not all releasable code is open-source code. NASA also has government source code that is only sharable with other US government agencies. If you don't find what you're looking for among the open-source on code.nasa.gov, check out Software.NASA.Gov, which is run by the Technology Transfer office and has government source code in addition to open source software. 93 |
94 |98 | DASHlink is a collaborative sharing network for researchers in the Data Mining and Systems Health fields. On DASHlink you can create a public member profile, share papers, algorithms, and datasets, and utilize tools like wikis and blogs to collaborate. 99 |
100 |104 | NASA has several programs for putting out data analysis and technology development contests and challenges to public. Centennial Challenge Program, NASA Tournament Lab, Challenge.gov, and NASA’s Center of Excellence for Collaborative Innovation are linked to from this page. 105 |
106 |120 | If you would like to interact with the data on this page through an API, we suggest you check out the code.gov API. You can programmatically interact with all NASA open-source projects & open-source code from every federal agency. 121 |
122 |126 | The projects page of code.nasa.gov is built from data in catalog.json, available on github. NASA projects on code.gov are harvested from code.JSON, also on github. You can interact with both here inside a live Observable code notebook editable in JavaScript. 127 |
128 |132 | If you find a mistake on this page, you can submit a change by contributing an issue or pull request to the public github repository that holds this page's source code. If you find any mistakes in the `A.I. generated tags` on this website's projects page, we'd like to know about it. 134 |
135 |83 | Thanks for your interest in sharing your code! If you are a developer employed by NASA or a 84 | NASA contractor and have open source code you wish to host on the NASA GitHub repository, check out the guide page or email us at opensource@lists.nasa.gov. 85 |
86 |91 | We encourage 92 | you to clone, fork, modify, break, and improve the code that we've released thus far. 93 | We're still working out the proper methods to take user contributions to our code and 94 | will provide information on how to do so as it develops. 95 |
96 |This notebook was created as an alternative way to interact with the data on
code.nasa.gov. It is an experiment!
Each of the code project's descriptions was run through a natural language processing model and higher-order concept tags predicted. Training data for this machine-learning model came from NASA's Science Technology and Information program database of published abstracts.
184 |This page explores how we might use those tags to quickly explore what code projects NASA has released to the public, without having to read through 500+ project descriptions.
185 |200 | Tag circles are scaled by number of times that concept tag was predicted by natural langauge processing (NLP) model as representative for a code project. Only tags found in the code project clusters highlighted below are shown in the tag bubbles. 201 |
202 | 203 |Limit tags by frequency
212 | 213 | 214 | 215 |Each line above represents a cluster of code projects that was tagged with similar concept tags. The tags on each line are the tags found to be most representative of each code project cluster. 222 | Select a cluster of code projects and both the bubble chart of tags above and list of code project names below will only reflect selected code projects.
223 |228 | Scroll to see all the Projects within selected cluster(s), click to learn more about a project: 229 |
230 |