Move voodoo to OCaml.org or ocaml-docs-ci

[tmattio]

OCaml.org is split into three repositories:

• OCaml.org
• Voodoo
• ocaml-docs-ci

This makes maintenance more complicated than it needs to be and increases the entry bar for new contributors for seemingly no added value. While the docs pipeline should probably remain separated from OCaml.org, we can merge voodoo with one of the other repositories. I'm in favour of moving it to the ocaml-docs-ci repository as it is essentially defining the behaviour of the pipeline, so it seems like a better separation of concerns.

[sabine]

IMO, the most confusing thing about voodoo as a newcomer is the name. It doesn't give any hints on what this actually does. So I would be in favor of renaming voodoo to something more descriptive, e.g. like package-docs-gen

We have here:

• ocaml.org: the webserver. It looks up data, then renders HTML pages. In ocaml.org's repository also lives the data-generator ood-gen which generates HTML for various data items on ocaml.org.
• voodoo: the package documentation generator. Given a package, it generates data in a format that ocaml.org consumes.
• ocaml-docs-ci: the system that creates tasks that run the package documentation generator. Since the data is dynamically changing all the time, as people publish new packages and versions, it makes sense that this is separate from ocaml.org, so that the substantial complexity of building package documentation in the background is insulated from ocaml.org.

I would argue that changes to voodoo and ocaml.org often go hand-in-hand, so I think that your earlier idea of co-locating voodoo within ocaml.org's repository would be fine. Newcomers to ocaml.org development need to easily find where the package documentation data is generated, when they need to make changes to the package documentation webpages. They don't need to see all the complexities of the pipeline for that.

However, to move voodoo somewhere else, we first need a solid plan for how to handle upgrades of voodoo.

[tmattio]

Moving to either OCaml.org or ocaml-docs-ci would simplify the whole setup, so I'm fine with anything you prefer!

[sabine]

Move into ocaml.org and expose voodoo via Dockerfile with opam-repository pin sounds sane to me.

[shonfeder]

This relocation will help us with our centralization efforts. I've provisionally re-assigned this to @cuihtlauac, thinking that his experience with ocaml.org may provide useful context. But we should talk about how to move forward here and whether it is a good fit synchronously.