Add community calendar to "How to collaborate" page

[mfisher87]

Resolves #1049

I feel like the title of this page doesn't quite match the name in the sidebar or the filename. So I'm putting info in the doc based on the title. We need to reorg our docs 😁

I'd especially like your thoughts @saberbrasher !

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--1202.org.readthedocs.build/en/1202/

[github-actions]

👈 Launch a binder notebook on this branch for commit d6fefc4

I will automatically update this comment whenever this PR is modified

👈 Launch a binder notebook on this branch for commit 776b4ed

👈 Launch a binder notebook on this branch for commit af2ee72

👈 Launch a binder notebook on this branch for commit d943359

👈 Launch a binder notebook on this branch for commit 8f71dc8

👈 Launch a binder notebook on this branch for commit e2082d7

👈 Launch a binder notebook on this branch for commit f5d5376

[mfisher87]

Readthedocs build status is "triggered" but it's not making any progress.

[saberbrasher]

Thanks for making this, @mfisher87 ! Just a couple of small suggestions. :-)

[saberbrasher]

Looks good to me! I think the change from Hackday to Collaboration Café is cute and seems a bit more inclusive to non-code-based collaborations, but Hackday may have more widespread understanding (or not? I'm actually not sure). Either way, I'm good with it!

[mfisher87]

@asteiker @ateucher thoughts on going forward with the new "Collaboration Cafe" terminology? Inspired by the Turing Way:

https://book.the-turing-way.org/community-handbook/community-calls/community-calls-collabcafe/

I figured now, as we're recreating the calendar invite, would be the best time to reconsider what we're naming this event and just went for it.

[chuckwondo]

@asteiker @ateucher thoughts on going forward with the new "Collaboration Cafe" terminology? Inspired by the Turing Way:

https://book.the-turing-way.org/community-handbook/community-calls/community-calls-collabcafe/

I figured now, as we're recreating the calendar invite, would be the best time to reconsider what we're naming this event and just went for it.

Thanks @mfisher87! I love the idea of a fresh name that is hopefully more inclusive and less intimidating/misleading.

I like "Collaboration Cafe". If others would like to bat around other names, I'm open to that as well, but perfectly happy with this one.

[mfisher87]

Dope. Let's merge and update the name later if we want!