Just to clarify - there are two places where we generate api docs.
The first is those published on the foreman website, e.g. Foreman :: API v2. Dropping additional languages from there will make building our site faster, as well as speed up the release process by a bit.
The second is generated during package build time and shipped with the packages. This will mean packages will build faster then they currently do, as generating api docs for all languages is one of the slowest steps in the build process.
In any case, users will still be able to generate all additional languages locally if they wish by running foreman-rake apipie:cache.
I feel for API docs English is enough, so I am pro dropping. But some will perhaps feel the need for there own language, so can we adjust the rake job to take a language as argument to create locally what you need and provide documentation somewhere a user can find this quite easily. Perhaps an installer option makes sense, with the installer now doing all rake jobs?
I believe the default when running foreman-rake apipie:cache is to generate the docs in all languages. You can add FOREMAN_APIPIE_LANGS env variable to specify which languages you wish to generate.
If the installer is now running the apipie:cache as well, should we drop it completely from the package build since the docs will be overwritten anyways once the installer runs? Also, should the installer by default only generate English docs, making the installation process shorter?