Skip to content

Commit aa28ee9

Browse files
mfisher87jhkennedydanielfromearthasteikerJessicaS11
committed
WIP context and problem statement
Co-authored-by: Joseph H Kennedy <[email protected]> Co-authored-by: danielfromearth <[email protected]> Co-authored-by: Amy Steiker <[email protected]> Co-authored-by: Jessica Scheick <[email protected]>
1 parent 160a6ac commit aa28ee9

File tree

1 file changed

+45
-1
lines changed

1 file changed

+45
-1
lines changed

docs/governance/decisions/929-move-repository.md

Lines changed: 45 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,50 @@ Technical Story: [#929 Move or fork to independent organization](https://github.
99

1010
## Context and Problem Statement
1111

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+
1256

1357
## Considered Options
1458

@@ -30,4 +74,4 @@ Move to an independent org, e.g. `earthaccess-dev`.
3074

3175
### Option 3
3276

33-
Move to a sponsor / incubator org, e.g. `pangeo`.
77+
Move to a sponsor / incubator org, e.g. `pangeo`.

0 commit comments

Comments
 (0)