Migrate content from cf-infra-docs to conda-forge.org (maybe iteratively)

[jaimergp]

• cf-infra-docs: https://github.com/Quansight-Labs/cf-infra-docs
• conda-forge's infrastructure: https://conda-forge.org/docs/maintainer/infrastructure/

Merge and mix

Tasks

Preview Give feedback

1. Improve infrastructure repositories documentation conda-forge/conda-forge.github.io#2119
   Docs +1
2. Add description of feedstock infrastructure conda-forge/conda-forge.github.io#2139
   Docs +1
3. Add description of role of infrastructure in package building conda-forge/conda-forge.github.io#2150
   Docs +1
4. Add introduction to infrastructure page conda-forge/conda-forge.github.io#2158
   +0

[zklaus]

This is an overview of all the files to track handling.

docs

• getting-started.md (placeholder)
• index.md
• miniforge.md (placeholder)

fundamentals

• feedstocks.md
• index.mdx (technical)
• life-cycle.md
• publication.md (placeholder)
• staged-recipes.md

howto

• index.md

reference

• bot-commands.md
• feedstock-settings.md
• glossary.md
• index.mdx (technical)
• pinnings.md
• runners.md

infrastructure (Covered in conda-forge/conda-forge.github.io#2119)

• _events-triggers.md
• automated-maintenance.md
• diagrams.md (deferred to Improve infrastructure diagrams #42)
• feedstocks.md
• index.mdx (technical)
• services.md
• staged-recipes.md
• tooling-data.md
• website.md

advanced

• automation.md
• index.mdx (technical)
• security.md (placeholder)

tutorials

• index.mdx (technical)
• submit-a-recipe.md (placeholder)

[jaimergp]

What are the checkboxes here for? 🤔

[zklaus]

What are the checkboxes here for? 🤔

They get ticked when the file has been dealt with, meaning either determined to not need migration in its current form (e.g. purely technical or boilerplate contents), assigned to a different issue for tracking, or fully integrated into the migration branch at https://github.com/zklaus/conda-forge.github.io/tree/improve-infrastructure-documentation.

[jaimergp]

Ok, let's keep working on that branch until next week. Then we can start opening PRs, @goanpeca can help with the review(s) when time comes. To keep things scoped, let's open one PR per source (origin) page (e.g. "infrastructure docs revamp" discusses what happens with maintainer/infrastructure.md).

[zklaus]

We should also add https://github.com/regro/conda-forge-feedstock-check-solvable to the documented infrastructure.

[jaimergp]

Infra docs have migrated. Next in line: Diataxification of the docs via conda-forge/conda-forge.github.io#2164