Use plugin specs repository and move plugins to their own repositories

[svenmuennich]

Since more and more plugins are added to Flashlight, it gets quite messy in the plugins directory. The main problem I see with this approach of storing all plugin code in the main repository is bug reporting. People file bug reports as issues in this repository, so they might not reach the responsible plugin developers. Hence I recon to split the code base as follows:

• A main app repository (this repository) that contains only the the code of the Mac app
• A Flashlight-specs repository, which serves the info.json files of all available plugins
• A repository for the website (now stored in flashlightplugins)
• One repository for each plugin (preferably owned by the respective developers)

Plugins can then be added (or updated) by sending a pull request to the Flashlight-specs repository. When a user installs a plugin, it is downloaded from the respective repository that is linked in the info.json.

I think these structural changes will be valuable for the future of this project. Depending on how much work this requires, I would be happy to help out.

[nate-parrott]

This is definitely a good idea — I'm pretty busy right now, but I'll give it a little more thought and start the project soon if it makes sense.

[svenmuennich]

Cool! As I said, if there's anything I can help you with, just reach out to me.