[IDEA] Add GitHub/Channel History Plugin to OIE Repository

[pacmano1]

Is your feature request related to a problem? Please describe.
@kayyagari 's GH plugin should be moved and incorporated into the OIE effort

Describe your use case
I need this feature so I can include this valuable plugin for the community.

Describe the solution you'd like
Add new repo for this plugin, compile and sign as needed

Describe alternatives you've considered
Using other vendor's plugin.

Additional context
N/A

[jonbartels]

@pacmano1 - This should be in governance

After moving the issue update it to describe how we will organize the code. I think maybe an extras or plugins repo with the sub projects under it would be good. IDK if GH supports organizing repos into something like groups or folders.

Finally Kiran and any other contributor to those repos should comment on the issue saying he's assigning copyright to OIE for these repos, then we can move them.

EDIT - It looks like we have smaller repos for other plugins that are, or may be, donated to OIE. I think split the work, get control of the repos first then we can reorganize to plugins or extras later

[pacmano1]

For now, I'd suggest putting it where the other plugins have been started.

[mgaffigan]

There's a lot of value in a single repo, with a single build script. I agree that a separate subproject may be called for, and there might be some plugins so substantial or dependency heavy that they should be in a separate repo/deploy.

I think the rule should be:

• If it is in the release artifact, it should be in the main repo
• If it is separately installable/versioned (not in the release artifact), it should be in a separate repo

[tonygermano]

Eventually I would like all plugins to be separately installable and versioned. Multiple people have expressed interest in a minimal core where plugins are selected a la carte. But for now I don't care where they go.