-
Notifications
You must be signed in to change notification settings - Fork 57
/
index.html
359 lines (336 loc) · 18.1 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8"/>
<meta name="viewport" content="width=device-width, initial-scale=1.0"/>
<meta name="description" content="NASA's Public Github Organization">
<link rel="stylesheet" href="index.css"/>
<link
rel="preload"
as="style"
href="https://fonts.googleapis.com/css2?family=DM+Sans:ital,wght@0,400;0,500;0,700;1,400;1,500;1,700&display=swap"
onload="this.rel='stylesheet';"
/>
<link
rel="preload"
as="style"
href="https://fonts.googleapis.com/css2?family=DM+Mono:ital,wght@0,400;0,500;0,700;1,400;1,500;1,700&display=swap"
onload="this.rel='stylesheet';"
/>
<noscript>
<!-- To support older browser with JS disabled, we load the fonts the old way: -->
<link
rel="stylesheet"
href="https://fonts.googleapis.com/css2?family=DM+Sans:ital,wght@0,400;0,500;0,700;1,400;1,500;1,700&display=swap"
/>
<link
rel="stylesheet"
href="https://fonts.googleapis.com/css2?family=DM+Mono:ital,wght@0,400;0,500;0,700;1,400;1,500;1,700&display=swap"
/>
</noscript>
<title>NASA's Public Github Organization</title>
<link rel="shortcut icon" href="assets/NASA_logo.svg" type="image/x-icon">
</head>
<body>
<header>
<div style="display:inline-block">
<img alt="NASA" style="height:4.5rem;" src="assets/NASA_logo.svg"/>
<div style="display:inline-block">
<span style="display:block">NASA's Public</span>
<span style="display:block">GitHub Organization</span>
</div>
</div>
<div>
<a href="#purpose">Purpose</a>
<a href="#instructions">Instructions</a>
<a href="#related">Related Sites</a>
<a href="#questions">Questions</a>
</div>
</header>
<div class="container">
<h2 id="purpose">Purpose</h2>
<p>
This GitHub organization is intended to publicly host NASA code that has
been
SRA-approved for open source.
You can review the SRA (software release authority) process for
getting
open-source approval on
<a href="https://code.nasa.gov/#/guide">https://code.nasa.gov/#/guide</a>.
</p>
<h2 id="Who">Instructions: Who Can Be a Member</h2>
<p>
<b>Only NASA staff can be a member of the NASA org on github.com and
release code in
<a href="https://github.com/nasa">github.com/nasa</a> org.</b>
</p>
<p>
If you are a NASA civil servant or contractor and would like to be added to the Public
NASA
GitHub Org, you will need to
submit the <strong>AGCY NASA Github Collaborator Form</strong> NAMS
request
(<a href="https://nams.nasa.gov">https://nams.nasa.gov</a>).
This requires you to be behind the NASA firewall.
If you were a member several years ago and recently found you are no
longer a member, please see this
<a href="https://github.com/nasa/nasa.github.io/issues/2">note</a>.
</p>
<p>
Only members have rights to directly edit code in a github.com/nasa
repository. Everyone else will need
to submit a pull request. <strong class="highlight-red">We highly encourage
pull requests from the public!!!</strong>
However, please note that not all repositories are actively
maintained.</p>
<p>Members of the public can not attain and do not need collaborator
status.
You don't need any special status to submit pull requests or add
issues.</p>
<h3 id="How">How</h3>
<p>
For information on how to become a member of the NASA Org (you need
to be
a NASA civil servant or
contractor with access to systems inside the NASA firewall), please
see
the instructions on
<a href="https://code.nasa.gov/#/guide">code.nasa.gov/#/guide</a>.
</p>
<!-- <p>
Employees or contractors of another federal agency that are working closely on a code project and absolutely
need collaborator status can get collaborator status by attaining a <a href="https://guest.nasa.gov/">NASA guest account</a>.
Please use your gov piv identity if possible. Your NASA contact can than request collaborator status for you in the NAMs system.</p>
-->
<h2 id="instructions" style="margin-top:2em;">Instructions: Once
You Are a Member</h2>
<p>
To ensure mandatory policies are followed, NASA org members are not
given
the full admin rights you might be used
to on your personal github.com accounts. However, by using teams,
team
owners, collaborators, and outside collaborators
roles we can make the experience pretty quick and easy.
</p>
<h3 id="owners">Org Owners</h3>
<p>Only org owners have the ability to create new repositories and bring
new
users in as members of the NASA github org. </p>
<p>We currently have two active owners in the org:</p>
<ul>
<li>Taylor Yates (<a href="mailto:[email protected]">[email protected]</a>)</li>
<li>Justin Gosses (<a href="mailto:[email protected]">[email protected]</a>)</li>
</ul>
<h3 id="repos">Repos</h3>
<p>
We do not give out admin rights on any NASA Github repos for reasons
stated above. If you want a new repo created or
want to edit settings on an existing repo that require admin access,
please contact one of our org owners. Without admin
rights on a repository, you'll still be able to make any code
changes
yourself as long as you're a collaborator on that
repository or a member of a team whose participants are
collaborators by
default.
</p>
<p>
If you need for a new repository (and it has gotten SRA approval)
please
either submit a modification to your NAMs request
or email one of the Org Owners with the follwing information:
</p>
<ul>
<li>Name of the repository</li>
<li>SRA number</li>
<li>Team name for managing the repository</li>
<li>Usernames of people for that team if it doesn't already exist.
Usernames must be from the list of existing NASA org members.</li>
</ul>
<p>
If you are joining for the first time and need a repository created,
you
can also include the same information in your NAMs request
for access inside the more information box.
</p>
<p>
You can learn more about the software release authority process on
the Guide page of
<a href="https://code.nasa.gov/#/guide"> code.nasa.gov</a>.
</p>
<h3 id="teams">Teams</h3>
<p>
Teams are effective ways of managing repository access privileges
for
an entire group of users. Only org owners can create and
remove teams, but we now allow users to be team maintainers. Team
maintainers have permissions to add and remove users to their
teams from the population of people who are already NASA org
members.
</p>
<p><strong>Note</strong>: Team maintainers are <em>technically</em> able
to add a user who was once in the NASA org back onto their team
(thus
reinstating the user in the org). However, we <strong>do not allow
this</strong> and will remove maintainers who are found in
violation. If you need a past member to be reinstated in the org,
contact an org owner and request to be added as an outside
collaborator.</p>
<h3 id="collaborators">Collaborators</h3>
<p>Github also has a role called "collaborator". This is someone who
doesn't have repository ownership or admin rights but can push edits
to code directly without doing a pull request.</p>
<p>If you would like to add a NASA staff member who is a member of the
NASA org as a collaborator on a single repository, we still suggest
you contact the NASA org owners mentioned above about setting up a
TEAM for that single repository instead of adding people one by one.
Teams result in less requestes (and therefore waiting) on NASA org
owners for actions. We are sorry you don't have normal full
ownership
rights. It is because everyone with write access needs to be
approved
NASA user. If you had normal repository owner right, you could add
any
github user.</p>
<h3 id="outsidecollaborators">Outside Collaborators</h3>
<p>Only on a rare case-by-case basis we will allow non-NASA users to be
added to the org as Outside Collaborators. You can collaborate
without
this status via forks, branches, and pull-requests. If you fork a
repository, you can make changes and then submit back a
pull-request.
A repository maintainer can then approve those changes. You do not
need formal outside-collaborator status for this!</p>
<p>Please reach out to us if you have any questions.</p>
<h3 id="common">Common Request & Process Combinations</h3>
<p><b>Need:</b> If you need to be added to the NASA org on github.com</p>
<p><b>Process:</b> Create a personal github account and then request to
be added as a Github Collaborator via a new or modified <a
href="https://idmax.nasa.gov/nams/asset/227756">NAMs request</a>.
Please include your github id in the request.</p>
<p><b>Need:</b> If you need to add a new open-sourced repository to
github.com/nasa that has already been approved via the <a
href="https://code.nasa.gov/#/guide">software release authority
process</a>.</p>
<p><b>Process:</b> Make or modify a request to start a new repository in
github.com/nasa via the <a
href="https://idmax.nasa.gov/nams/asset/227756">NAMs request</a>.
Please give it a useful name and good documentation! We'll create a
blank repository for you to put the code into.</p>
<p><b>Need:</b> If you need to create a new team for managing who has
access to make changes on a particular repository or group of
repositories.</p>
<p><b>Process:</b> Modify your <a
href="https://idmax.nasa.gov/nams/asset/227756">NAMs request</a>
to
request the team creation or email the two owners above. Give team
name and which repositories team members should be given access to.</p>
<p><b>Need:</b> If you need to add a new member to an already
established team.</p>
<p><b>Process:</b> Send an email to the Team owner, modify your NAMs
request, or email the Github Owners in that order of preference.</p>
<h2 style="margin-top:2em;">Related Sites</h2>
<h3 id="related">Organizationally Related Sites</h3>
<b>In addition to github.com/nasa, NASA OCIO's Transformation and Data Division Open-Innovation staff also run:</b>
<ul>
<li><a href="https://code.nasa.gov">code.nasa.gov</a></li>
<li><a href="https://data.nasa.gov">data.nasa.gov</a></li>
<li><a href="https://api.nasa.gov">api.nasa.gov</a></li>
<li><a href="https://open.nasa.gov">open.nasa.gov</a></li>
<li><a href="https://nasa.gov/data">nasa.gov/data</a></li>
</ul>
<h3> Why is NASA's Open Source Code in multiple locations?</h3>
<p>The reason for NASA open source code existing in different places
boils down to different requirements, both requirements of those
writing the code and requirements from above.</p>
<h4>Other NASA orgs on github.com or gitlab.com or bitbucket</h4>
<p>Although NASA staff are highly encouraged to release open source
software on github.com/nasa as that is where most people look so it
ensures higher potential reuse, they are not absolutely required to
use that org account. A common reason code may exist under other orgs
is that the software is jointly maintained by non-NASA persons or
the
code was developed by non-NASA persons through a NASA grant.</p>
<p>To encourage disoverability, please use the <a
href="https://github.com/search?q=nasa&type=topics">#NASA topic
tag</a>
on any GitHub or GitLab repositories not under github.com/nasa.</p>
<h4>Discovering useful NASA Open-Source Code via metadata catalogs</h4>
<p>There are several hundred NASA open-source code repositories and as previously noted, not everything is on github.com/nasa.
To improve your chance of finding something useful to you,
we suggest you use code.nasa.gov and software.nasa.gov.
These sites host metadata descriptions
for nearly all of the officially open-sourced code.</p>
<h4><a href="https://code.nasa.gov">Code.nasa.gov</a></h4>
<p>Code.nasa.gov feeds into https://code.gov, which holds open source
code from across all federal government agencies. It is mandated by
Congress and only holds standardized metadata about the code.</p>
<p>Code.nasa.gov only shows open-source software. For government-source
and patented software, see software.nasa.gov</p>
<p class="highlight-red"><strong>Please make sure any repos added to github.com/nasa
are also tracked in code.nasa.gov!</strong></p>
<p>Code.nasa.gov uses both human and A.I. generated tags to help users find NASA open source that is useful for their goals.</p>
<img class="content_image" src="assets/code_demo.png" alt="Screenshot of NASA's project OPEN MCT" style="display: block;margin-left: auto;margin-right: auto;">
<h4><a href="https://software.nasa.gov">Software.nasa.gov</a></h4>
<p>Software.nasa.gov is part of the larger <a
href="https://technology.nasa.gov/">https://technology.nasa.gov/</a>
that also covers patents and spinoffs. The NASA's Technology
Transfer
Program ensures that innovations developed for exploration and
discovery are broadly available to the public, maximizing the
benefit
to the Nation. Whether you're looking to start a new company,
enhance
an existing product, or create a new product line, you can gain a
competitive edge in the marketplace by putting NASA technology to
work
for you.</p>
<p>The information on software.nasa.gov is presented in a way that
leverages NASA's technology taxonomy, so if you want to see an
aggregate view of NASA software categories, it is a good place to
visit.</p>
<p>It also includes some older software products that are only available
as downloadable zip files as well as software that must be requested
individually as they are only open to US persons or are tied to a
patent.</p>
<a href="https://software.nasa.gov"><img class="content_image" src="assets/software.png" alt="Screenshot of NASA's software categories"style="display: block;margin-left: auto;margin-right: auto;"></img></a>
<h1 id="questions" style="margin-top:2em;">Questions?</h1>
<p>In addition to the emails listed above, you may leave an <a
href="https://github.com/nasa/instructions/issues">issue</a>
on
this repository. We will use those questions & answers to
eventually
make a FAQ section on this page.</p>
<br>
<hr>
<div id="ember16" class="ember-view"><div id="footer">
<div id="footer-info">
<a class="logo" href="assets/NASA_logo.svg">
<img src="assets/NASA_logo.svg" alt="NASA logo">
</a>
<div id="status">
<span>National Aeronautics and Space Administration</span>
<span>Page Last Updated: March 12, 2021</span>
<span>NASA Official: Jason Duley</span>
</div>
</div>
<ul id="footer-links">
<li><a href="https://www.nasa.gov/offices/odeo/no-fear-act">No Fear Act</a></li>
<li><a href="https://www.nasa.gov/FOIA">FOIA</a></li>
<li><a href="https://www.nasa.gov/about/highlights/HP_Privacy.html">Privacy</a></li>
<li><a href="https://oig.nasa.gov/">Office of Inspector General</a></li>
<li><a href="https://osc.gov/">Office of Special Counsel</a></li>
<li><a href="https://www.nasa.gov/news/budget/index.html">Agency Financial Reports</a></li>
<li><a href="https://www.nasa.gov/about/contact/index.html">Contact NASA</a></li>
</ul>
</div>
</div>
</div>
<script>
if(window.location.href == "https://nasa.github.io/instructions" || window.location.href == "https://nasa.github.io/instructions"){
window.location.replace("https://github.com/nasa/instructions/blob/master/docs/INSTRUCTIONS.md");
}
</script>
</body>
</html>