Document existing infrastructure

[trallard]

Tasks to complete

Preview Give feedback

1. Initial Docusaurus setup + content structure
2. Create a "basic" inventory of conda-forge resources and owners #32
   funding: czi mission: infra 🛠 team: quansight-labs type: task +4
3. Create preliminar Infrastructure diagrams #34
   area: documentation 📖 funding: czi mission: infra 🛠 team: quansight-labs type: task +5

Resources

• PSF infra documentation: good example of how to structure the information and audit
• cabotage - PSF K8s cluster management app

[jaimergp]

Some comments (and ideas based on these comments) we've had on the last sync:

• Declarative Infrastructure as Code approaches are nice because there's an authoritary inventory of the resources.
• If conda-forge's infra can be expressed as Terraform state declarations, awesome, but simply documenting and inventorying the components is a HUGE step.
• Many of the infra tasks at conda-forge are procedural (list of actions to take to achieve a state), but they could benefit from being declarative (expressing the state we want to achieve, have magic ✨ figure out what actions need to be done). This is the whole idea behind Terraform, so if we can implement it with it, so be it, but if we can't, many of the design principles can / should be applied to CF's automation.

[trallard]

Current docs at https://conda-forge.org/docs/maintainer/infrastructure/

[jaimergp]

With the current docs at cf-infra-docs I'm quite ok with marking this as done and then iterating in conda-forge.org as part of the PR review process. @zklaus will be tackling that in #55