Utilizing plugins built during hackathon

[mr-loop-1]

Hi @jawache @russelltrow @adamj89 and others, I made an application which is at this issue #148 and it revolves around making a plugin library and utilizing that in the pipeline builder.

I wanted to expand the number of plugins available in the application, and was thinking about adding the plugins made under "Best plugin" or plug-in-project label into my app. I have a "community" tag for exact same use-case and these plugins will be added under that tag.

The benefit would be that they can also test out their plugins very easily as well as the maintainers can also see how interoperable different plugins built in this hackathon are.

I would only require the following information

pluginName:
description:
repoUrl:
inputParams:
outputParams:

and if there are some params outside the canonical ones, then their information in this format

name:
description:
unit:optional
aggregation: optional

I haven't had the time to create a registration page, and hence this information can be given as comment under issue etc.