This isn't really that related to #2511

We should probably emphasize that these two systems are more than content generators. They are also Koji plugins. I don't want other content generator implementors to think that this is part of being a content generator.

Added a comment there.

Here's the content generator for CoreOS. It's used for RH CoreOS, not Fedora CoreOS https://github.com/coreos/coreos-assembler/blob/master/src/cmd-koji-upload

Here's the Debian package content generator that I developed but never deployed to prod: https://github.com/red-hat-storage/misoctl

Here's "causeway", part of Project NewCastle (Java content generator): https://github.com/project-ncl/causeway. It calls Koji's CGImport RPC through kojiji (not sure how, it's a little hard for me to follow all the wrapping code.)

Let's rephrase "Pure CGs" to "Standalone CG utilities". "Pure" sounds like "perfect" or "ideal" to me, and these are not really that.

"Java package CG component"

Don't forget the most (in)famous content generator, MBS https://pagure.io/fm-orchestrator/blob/master/f/module_build_service/builder/KojiContentGenerator.py

Commit 39ab9fbb fixes this pull-request