Figure out plugin development workflow

[oubiwann]

The development workflow outlined [here]() is rather cumbersome. Once we move to lfetool written in LFE, this should get much simpler. We should design, from the start, with a simple process in mind.

[oubiwann]

I think this is pretty figured out by now. It should be documented (in detail!), but that can go in a separate ticket.

There are a few unknowns:

• what do we do about common files? do we just overwrite? do we have a "common" plugin? (abstract plugins are a conceptual oddity ...)
• we haven't actually implemented any plugins other than a very, very simple one that takes a single command, so there could be lots of tuning still left to do.

Despite these, though, I am guessing that the overall development workflow is pretty solid, if the details to have to change a bit.

[oubiwann]

Issue #70 tracks the documentation of the plugin development process.

[oubiwann]

Despite the open questions, I'm going to close this. As the other plugins are migrated, the answers to these will emerge.