Use this repository as a source of truth for federation members and their logos

[choldgraf]

Currently, the list of federation members exists in multiple places. From a deployment standpoint, we use this repository, but for documentation and public-facing purposes, we use the Binder user documentation. This is sub-optimal for a few reasons:

• When we add/remove federation members we have to remember to change two places. For example mybinder.org currently has different lists of federation members as mentioned in highlight past federation members, update some out of date supporters mybinder.org-user-guide#308
• The list of logos for federation members is hidden within the user documentation, which gets a lot less traffic than mybinder.org and thus isn't as much of an incentive for others to join the federation.

Suggested solution: use mybinder.org-deploy as a source of truth for federation members and list the logos on the Binder landing page

I suggest that we:

1. Use this repository as the source of truth for "who is contributing to the mybinder.org federation"
2. In the user docs, re-use this SOT for populating pages like https://mybinder.readthedocs.io/en/latest/about/federation.html (e.g. by reading a YAML file)
3. Put the list of federation members on mybinder.org at the bottom of the page (and ideally "above the fold")
4. Use the mybinder.org "announcement banner" only for announcements, and remove the persistent "thanks to XYZ for supporting Binder" message

[yuvipanda]

https://jupyter.zulipchat.com/#narrow/channel/469744-jupyterhub/topic/Binder.20UI.20Design.20and.20visibility.20of.20Federation.20members has context and prior conversation (I love how linkable zulip is). In there is one possible pathway that I'd love for us to take over time.