Separate repos for plugins, themes, and languages

[LeaVerou]

Given that our download page uses the Github API anyway and we already have a components.js to keep track of things, what do you think about having plugins etc in separate repos? That way their authors can update them without needing to send PRs to us and we don't need to keep track of authors, we can just use the repo owner.

It seems this is the way big projects with a plugin architecture are going, e.g. Atom. Thoughts?

[Golmote]

This sounds like a huge work to do...

I'm also afraid that it might get really hard to fix bugs related to using several components together, once they're all around on github and we don't have write rights on the repos. (I have in mind the recent issues regarding the use of the line-numbers plugin + normalize-whitespace plugin, and the ones about the line-numbers plugin + PHP component.)

That being said, I admit it would be great to let the maintaining work to the actual creators, sometimes...

[LeaVerou]

That's a very good point. Although once we don't host them anymore, our users won't hold us responsible for them, so perhaps we'll get out of fixing these compat issues altogether!