You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/governance/decisions/929-move-repository.md
+45-1Lines changed: 45 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,6 +9,50 @@ Technical Story: [#929 Move or fork to independent organization](https://github.
9
9
10
10
## Context and Problem Statement
11
11
12
+
`earthaccess` currently lives under the `nsidc` organization.
13
+
14
+
While the `earthaccess` community lives under the ownership of a private
15
+
organization, GitHub's design prevents us from administrating our project
16
+
independently.
17
+
For example, we require organization owner permission for certain actions, teams are managed at the organization level, and our project is mixed with a large number of other projects (making it less discoverable).
18
+
19
+
Moving the `earthaccess` repo to another GitHub organization will:
20
+
21
+
* Reduce friction to collaboration by allowing us to self-determine our
22
+
community members' access and privileges.
23
+
* Improve discoverability by reducing the amount of irrelevant items
24
+
when browsing for related projects.
25
+
* Enable bundling related repositories (e.g. the R earthdatalogin project, other
26
+
dependency libraries) under the same org, for example to cross-document project.
27
+
* Preserve community's ability to make its own decisions independent of
28
+
institutional structure and policy.
29
+
30
+
Overall: enhance collaboration, efficiency, and longevity
31
+
In order to strengthen the community engagement of earthaccess and lower participation barriers, moving to a
32
+
33
+
Bullets from presentation to ESDIS on 2/11/2025:
34
+
- Accelerate development via broader participation
35
+
- Lower the cost:value even further for ESDIS
36
+
- Promote NASA’s partners
37
+
38
+
* Co-location with other similar projects (including similar resources in other languages, e.g. R and Julia)
39
+
* Meeting users where they are
40
+
* Increase visibility, ability to promote, bring awareness to a broader community (e.g. Pangeo showcase)
41
+
* Meets NASA Open Source Science goals
42
+
* Leveraging NUMFocus sponsorship could allow for Google Summer of Code mentorship and other funding/effort contributions
43
+
* Promotes NASA’s partnerships with other community members based on shared goals, by actively recognizing the critical * contributions of those members.
44
+
* From some Googling:
45
+
* Flexibility
46
+
* Rapid innovation
47
+
* Improved security through rapid bug fixes
48
+
* Transparency and trust
49
+
* Cost efficiency
50
+
* Development driver by the user community
51
+
* While inter-community support reduces ESDIS/NASA required support, we acknowledge that increased ESDIS funding will also help us sustain the library
52
+
hips with other community members based on shared goals
53
+
- Increase sustainability
54
+
55
+
12
56
13
57
## Considered Options
14
58
@@ -30,4 +74,4 @@ Move to an independent org, e.g. `earthaccess-dev`.
0 commit comments