Writing snapcraft plugins is hard due to lack of API documentation

[Thomi Richards]

I find myself having to write a custom plugin, and it's really hard to know what I should be doing in each method of BasePlugin. It would be nice if there was comprehensive API documentation aimed at plugin authors, published online.

Ideally it would cover:

 * Which methods of BasePlugin can be overridded.
  * What plugin authors should do in each method.
  * which attributes are set on the BasePlugin, and what they're for (installdir, builddir etc).
 * When each method on BasePlugin will get called.
 * Functions, classes and methods from the rest of snapcraft that's considered a public, stable API.

[Leo Arias (elopio)]

As a first step, we will be publishing a sphinx doc in a website for all the classes and methods of snapcraft. This is not a stable API yet, so next step is to clean the API and agree on what will be the stable and supported API, remove all the internals and nicely document the remaining public parts.

[Kyle Fazzari (kyrofa)]

> This is not a stable API yet[...]

You're gonna scare people, Leo :P . To be clear, we do not intend to break the plugin API. I think what Leo is talking about here is the nebulous "other stuff" that is neither public nor clearly internal as of yet.