An optional centralized repository for simple packages

[ickc]

From #2 (comment):

...I'm considering providing repositories for centralized packages (totally optional). Because I see from pandocfilters/pandoc-templates pull request, there seems a need in this area. Sometimes for very simple filters/templates, a dedicated repository seems over kill, while a single file "repository" like gist might not be up to the job. e.g. One want to have at least 3 files: the package, the markdown source, and the native from them (for tests).

• Regarding native files for tests, they are not the standards (e.g. not in pandocfilters/panflute's example folders). But I think if we are to offer such centralize repositories for simple packages, I will require them to write a simple test, to minimize any extra workloads on us.

• there will be a standard organization structure to make the tests full automated.

• when tests fails on newer versions of pandocfilters/panflute/pandoc, the original author would be called to fix it. If no one is fixing it, it would be retired (say in an archive folder, meaning pandocpm install also wouldn't be able to install it to prevent problems. The corresponding YAML formula can be added a warning message for such cases.).

[ickc]

Just to note that this issue is kind of a place holder. The work should be done in a separate, yet to be created repository, which pandocpm will gives special permission as mentioned in #5.