Just a quick note for everyone (that either didn't attend LGM or didn't
hear the results of the conversation I had with Joao and Jehan)...
After some back and forth we are currently considering managing our own
infrastructure to host plugins/scripts.
We had a chance to speak (loudly in my case) at LGM and I will ping the
list again when we have fleshed out some ideas a little further and start
soliciting some feedback/ideas.
On Tue, Apr 12, 2016 at 1:13 PM Jason van Gumster <fw...@monsterjavaguns.com>
> Akkana Peck <akk...@shallowsky.com> wrote:
> > I'm still not clear what the advantage would be of one repo per
> > file.
> Not to kick a week-old hornet's nest, but I'd like to point out that as a
> looking for extensions/add-ons/scripts/etc, I find it much more convenient
> download/clone a single script without being required to pull down a bunch
> unrelated scripts as part of the same repository. This is even more the
> case if
> I happen to want to contribute code to that script.
> Granted, perhaps there's a frontend that's developed which obfuscates or
> otherwise diminishes the need to get all of the undesired scripts. But
> the hassle (I have a few one-off scripts/add-ons for Blender on GitHub in
> own repos), there are definitely some advantages for the people who aren't
> primary developers.
> gimp-developer-list mailing list
> List address: email@example.com
> List membership:
> List archives: https://mail.gnome.org/archives/gimp-developer-list
gimp-developer-list mailing list
List address: firstname.lastname@example.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list