kojiweb does not currently support plugins, so there is nothing to document

which is a big problem. so perhaps reword that, support plugins and document how to do so

kojiweb is not organized in a way that facilitates a plugin being able to do much, which is one big reason that we haven't done this before. This RFE might effectively amount to "rewrite kojiweb from scratch."

OTOH, maybe there are some small ways in which a web plugin could be useful.

Can you give me some examples if things you might want plugins to be able to do in kojiweb?

well my thought is that if we add functionality to the hub/builder/cli via a plugin, we need to have a matching change to the web interface to ensure the display of the new artifact type. say ostree, install dvd, anything else new. maybe we want to write and enable a plugin that allows people to submit new builds via the web interface. or possibly any other number of actions.

Related: #193 [RFE] Extend CLI for plugins

There are basically two places where web plugins would benefit now. First is listing of taskmethods in filters and second is formatting of task details pages. Possible third place would be adding xmlrpc calls - but I don't know about any plugin which needs this now.

Related: #258

Let's close this one. Web plugins are not on the horizon for now. /First we have to move from cheetah to jinja templating and after/with this change, plugins can be revisited/

Dropped PR: #377