I was suggesting using your own binhost as an alternative to distcc.
If someone’s considering distcc, presumably they’ve already decided not to use the public Gentoo binaries, and want to do the compilation themselves

I think that’s more for when you have multiple machines (that would use the same USE flags) and you only want to have to compile once.

One issue with distcc is some of the build operations can’t be delegated. If you want to minimise resource usage as much as possible (e.g. on old hardware) and want to compile yourself, then running your own binhost makes sense.

Or set up your own binhost

Where’s the pickle?!

I know very little about GIMP or other OS design software, but does this software have a plugin system that designers could use to extend the software so they can use it how they want?
That would be another thing to look into

a platform that enables designers to relatively easily contribute to open source projects without learning git

Reading this made me a bit sad.
On the one hand, I understand how tools like this could be a hurdle for someone who isn’t heavily invested in their use. And on the other, as someone who has tinkered with open source projects, I know that as hurdles go, git is the first of very many hurdles that must be cleared when contributing to a large, mature GUI program like this, and it’s a pretty low one at that.

It would be great if more people could contribute to and help develop open-source versions of tools they themselves use, but I can certainly see how tough it can be starting out

I wanted to play around with a project that uses Nix… it seemed really cool but I couldn’t get it working, I guess I was throwing myself in at the deep end with it

It looks like a fantastic way of sharing a dev environment across a team