Why are the plugins in single Git repository?

Dragooon

  • I can code! Really!
  • polygon.com has to be one of the best sites I've seen recently.
  • Posts: 1,841
Why are the plugins in single Git repository?
« on March 22nd, 2014, 08:25 AM »Last edited on March 22nd, 2014, 08:33 AM
There is no reason to, having individual repositories will allow for a much better development cycle since they'll maintain individual history and pull requests. Now I have to download all the plugins simply because I want to submit a PR for mass_upload...

PS: Use git subtree (like here) if you want to split the repositories.

PPS: I'm fairly sure I can't fork the repo without voiding the license :P
The way it's meant to be

Nao

  • Dadman with a boy
  • Posts: 16,061
Re: Why are the plugins in single Git repository?
« Reply #1, on March 27th, 2014, 08:46 PM »
They're in a single repo because they're sanctioned by the boss. That would be me.

Anyone's free to build their own plugins in their own repos, of course. If you want, I can 'link' to your plugins, either by adding a readme in the root and putting links to plugins, or by adding a submodule.

I've never used subtrees, and wouldn't know where to start. Apparently -- it's complicated.

As for the license, the January 20th version of it specifically adds a waiver for github forks!