Write up and maintain a guide (and guidelines) for plugin developers

[dmikurube]

Embulk has had very few documents, especially for plugin developers, because of we have had no bandwidths for writing documents.

We wanted to have someone who is/are willing to contribute in documenting for plugin developers.

If you're interested in it, please let us know in this Discussion at first.

[kakoni]

@dmikurube Perhaps I could help.

[hiroyuki-sato]

Anyway, Thank you @kakoni

[dmikurube]

So, In my opinion, we need a new plugin template generation mechanism before writing developer guide.

Why not we go for them in parallel? ;)

(Half joking, but half serious. While we write a draft document, we may find a good feedback for the template. We'll be able to think about both at the same time.)

[dmikurube]

It's true that the SPI had some changes between v0.9 -> v0.11, but the core concept is still the same. I believe that the difference would not impact the rough direction of the documents so much.

[hiroyuki-sato]

That's Right, We can run parallel in three 😄
It's stress job for convert v0.9 to v0.11. so I want (un-official) template generator for that for myself.

[dmikurube]

Sounds good. By the way, any un-official template generator can be a good starting point to be promoted to an official. ;)