Reorganize documentation to be more modular and cleanly grouped

[choldgraf]

I was looking into where information for the mybinder.org cloud credit information could go, and found that it was a bit hard for me to figure out the "natural" grouping of information. We have:

• About our team, which as a list of team members below the fold, as well as information about team structure
• Team resources, which is a combination of team policy, information, and helpful guides
• Governance, which is about decision-making, but also includes a milestones section even though these aren't really "binding" from a decision-making standpoint
• Contribute, which is more like a general contribution guide for newcomers

So, this PR tries to do a few things with the goal of making information easier to find, more naturally grouped, and easier to decide where to update or add new information. Here's a summary:

• Our About the team page is now just a list of our current team members, and it links to a Team information parent page for information about the team structure.
• Our Team resources page is now broken down into sub-sections. One for Governance and structure, one for Team guides, that describes some common processes and policy we follow, and one for Team coordination, which has information about accounts and shared infrastructure + planning.
  • I created a dedicated page about mybinder.org infrastructure, since that's a special-case within the team.
• I've moved Governance to the Team resources page, so we have our policy all defined in one place.
• I've explicitly labeled Contribute as New contributors guide so that it's clear what kind of information belongs there (we might consider moving this somewhere else depending on Sketching ideas for the content of a Community Handbook #572 )
• Also some housekeeping: I've updated conf.py to use the latest pydata configuration, and also removed a bunch of sphinx-quickstart cruft so that it is simpler

I don't believe any of the content has changed, this is just rearranging

Questions I have

• Is it actually helpful to collapse "governance" into "team information"?
• Should we instead have a separate section for "governance and policy" and differentiate this from "team information and guides?"
• Should the contributing guide be combined into two sub-sections, one for the team and one for other contributors?

[choldgraf]

Another ping for @consideRatio since I'm on a roll w/ documentation today :-D and maybe @sgibson91 who might have thoughts via her CSL role

[sgibson91]

One nitpick over word choice but shouldn't be a blocker. (Which I have just realised that I forgot to add... 🤦🏻‍♀️ )

[choldgraf]

Thanks for the feedback y'all - will take another quick pass and resolve these

[choldgraf]

OK I just took another pass after @consideRatio's feedback, and made a few other significant changes:

• Top-level sections now cleanly delineate what are Team policies and practices from What are team guides and information. I hope this makes it clearer that are expectations vs. just helpful information.
• I've renamed and moved a couple of files / folders to make this easier to navigate and maintain. There is now a practices/ folder (for expected practicies/standards) and a resources/ folder (for helpful information).
• I've consolidated and removed a few redundant sections so it's clearer what information is the "source of truth" / what should be updated.

cc @minrk - I saw that you Approved while I was making these edits, so just FYI to make sure you notice this

[consideRatio]

These kinds of lists are unsustainable to maintain overall I think, where its better to link to the configuration where one can see what repositories its active for.

No change requested though as its not unproblematic in this case to not be mistaken about the current state sometime in the future when this is outdated.

[choldgraf]

I agree w you. If there's a place where this is configured I'm happy to link it in this PR. If it's more complex then let's open an issue for a future fix?

[consideRatio]

I was thinking it was you who had written these lines now, but it was just relocated - let's not add an action point for such a trivial thing!

[consideRatio]

I'll go ahead and push some commits as I wanted to ensure that existing links redirect instead of break, so I'll be adding the sphinx extension rediraffe.

[consideRatio]

I added three commits, this LGTM to me.

@choldgraf can you review the added commits?

Also, could I be added to https://readthedocs.org/projects/jupyterhub-team-compass/ as well?

[choldgraf]

Thanks - the redirects look great to me. Also I appreciate you added the date for them, so we can decide if we want to delete them after some time has passed.

I added you as a maintainer for this repo on RTD.

[consideRatio]

Wieeee!!! Great improvements!