Create esip-funding-friday-song-lyrics.md

[stefaniebutland]

Pull Request (PR) draft checklist - click to expand

• Please review our
  contributing documentation
  before getting started.
• Populate a descriptive title. For example, instead of "Updated README.md", use a
  title such as "Add testing details to the contributor section of the README".
  Example PRs: #763
• Populate the body of the pull request with:
  • A clear description of the change you are proposing.
  • Links to any issues resolved by this PR with text in the PR description, for
    example closes #1. See
    GitHub docs - Linking a pull request to an issue.
• Update CHANGELOG.md with details about your change in a section titled
  ## Unreleased. If such a section does not exist, please create one. Follow
  Common Changelog for your additions.
  Example PRs: #763
• Update the documentation and/or the README.md with details of changes to the
  earthaccess interface, if any. Consider new environment variables, function names,
  decorators, etc.

Click the "Ready for review" button at the bottom of the "Conversation" tab in GitHub
once these requirements are fulfilled. Don't worry if you see any test failures in
GitHub at this point!

Pull Request (PR) merge checklist - click to expand

Please do your best to complete these requirements! If you need help with any of these
requirements, you can ping the @nsidc/earthaccess-support team in a comment and we
will help you out!

• Add unit tests for any new features.
• Apply formatting and linting autofixes. You can add a GitHub comment in this Pull
  Request containing "pre-commit.ci autofix" to automate this.
• Ensure all automated PR checks (seen at the bottom of the "conversation" tab) pass.
• Get at least one approving review.

---

📚 Documentation preview 📚: https://earthaccess--1056.org.readthedocs.build/en/1056/

[github-actions]

👈 Launch a binder notebook on this branch for commit 115fc1f

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit 747216a

👈 Launch a binder notebook on this branch for commit b31a1e2

👈 Launch a binder notebook on this branch for commit 5fbf409

👈 Launch a binder notebook on this branch for commit 2d4eef9

👈 Launch a binder notebook on this branch for commit 2b72842

👈 Launch a binder notebook on this branch for commit 9147465

👈 Launch a binder notebook on this branch for commit eb18df8

👈 Launch a binder notebook on this branch for commit eb586c8

👈 Launch a binder notebook on this branch for commit f6b5aea

[stefaniebutland]

a visual timeline might be powerful to show just how short a time this took place in .... after the years of work and community that led to this

Wed July 23 at 10am, Julie types in NASA Openscapes Mentors doc:

What’s a small something/Earthaccess feature to pitch at ESIP :) Julie thinking of proposing: “piloting earthaccess with NOAA data”. Or other ideas?

Synchronous discussion ensued in Julie's absence and was quite technical focusing on datasets that could be used. Amy opened an earthaccess GitHub Discussion.

Thursday night poster-making. "lets's do a song". Powerful pivot to simplicity in the pitch song lyrics: we want to have NASA, NOAA, USGS, Copernicus data in our hands! (implicit: open science for all!).

Friday 15mins before Friday pitch time, Kate Wing, affiliation and singer, notices the stanzas of the song aren't quite right and she marks up the sheet and re-writes on bigger paper so all the "performers" can see.

Who is singing/ pitching? Boom!: 4 people, each from NASA, NOAA, Intertidal Agency, and Openscapes. Reflecting: this would absolutely not have happened without hours and years of prior connections, collaborations, trust- and community-building, and sync and async social interactions among these 4 and our collective web of humans. ("Want to build community? Go to other peoples' parties!" Analagous to: learn to understand and contribute to someone else's software before creating your own from scratch)

The Pitch (see what we did there?). Kate gives a "hummmmm" to start everyone on the right note then uses her finger like a bouncing lyric ball to guide the group. The fun song transitions to a crystal clear and emphatic ask from Julie: "We will use FUNDing Friday award to ....".

We win!

[jhkennedy]

I think we should also link the video here. @jules32, what do you think?

[jules32]

Great minds! Yes I have more edits to make, it's still a draft PR :)

[jules32]

OK I think it's all set as a PR; I put it in a folder but likely not the best place or name so please feel free to move/rename :)

Also linking to the discussion: #1054

[mfisher87]

I think this should live within the docs website. Nobody will see it if it's just in the repo! I think it's a good piece of evidence that this is a fun community to join. Maybe we should have a "this is a fun project"-type directory in the docs? Perhaps under "work with us"? Other ideas?

[jules32]

I like that idea @mfisher87 , I agree it needs visibility by being part of the website, not the GitHub repo. Wherever you think best! Thank you!

[mfisher87]

Any ideas for how we might name this page / potential future group of pages? "This is a fun project" under "work with us" may be fine, but I'd like to explore a bit more :)

[jules32]

I think framing it as sustainability+funding and growing the contributor community would be stronger (although indeed it was fun)