Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create preliminar Infrastructure diagrams #34

Closed
Tracked by #31
viniciusdc opened this issue Jan 30, 2023 · 6 comments · Fixed by Quansight-Labs/cf-infra-docs#5
Closed
Tracked by #31

Create preliminar Infrastructure diagrams #34

viniciusdc opened this issue Jan 30, 2023 · 6 comments · Fixed by Quansight-Labs/cf-infra-docs#5

Comments

@viniciusdc
Copy link

No description provided.

@viniciusdc viniciusdc changed the title Infrastructure diagrams @viniciusdc Create preliminar Infrastructure diagrams Jan 30, 2023
@viniciusdc
Copy link
Author

viniciusdc commented Jan 30, 2023

  • Started using diagrams to generate CF bot's components diagrams
    • a brief comparison using javascript-based diagram Mermaid tooling x a python-based one, Diagrams.
    • Adapt previous docs/graphs/diagrams into the new doc's structural design (Nan)

@viniciusdc
Copy link
Author

viniciusdc commented Feb 28, 2023

After pondering those two approaches, I've decided that Mermaid seems to be the best use case for our docs. The reason can be outlined into two main points:

  • The general graph coding experience (layout/classes) is similar to Diagrams, which makes its use quite simple to structure new graphs or add modifications to existing ones
  • Docssauros has a built-in (needs import) plugging for including mermaid diagrams direct in markdown files without much trouble. Compared with Diagrams, it is easier to handle, build (no need to run extra commands), and modify in the future.

@viniciusdc
Copy link
Author

As of now, to reduce the spent time on getting our diagram in the mermaid format, we will be using LucidCharts to generate the structure of these, for initial review and iterations, and later import into the docs with the proper formating/code

@viniciusdc
Copy link
Author

viniciusdc commented Feb 28, 2023

Current iteration
CZ Diagrams -- conda-forge docs - Page 2

@viniciusdc
Copy link
Author

viniciusdc commented Feb 28, 2023

Here we have come key concepts described using different colors:

  • Agents/actors (red)
  • Objects (greem)
  • Verbs (purple-ish)
    which still lack a proper definition, but its idea is to better organize the different situations and functionality of conda-forge infrastructure into classes of objects that sometimes interact with other resources (usually modifying some integral part of it), the agents/actors, or the object that receive such interactions "the objects."

Such classification helps outline the different scenarios with which the same object/actor might be involved and the extra level of coordination/management/authority that the same object controls.

  • Identified above the core concept is definitely the feedstock, wich in the next iteration will become the center part of the next diagrams in a more easy to read/follow representation

@jaimergp
Copy link
Contributor

jaimergp commented Jun 1, 2023

I merged the current status to get us going but we need to revisit the diagrams in the future. I'll create a separate issue for that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done all-time
Development

Successfully merging a pull request may close this issue.

2 participants