On Mon, Sep 28, 2015 at 11:22 AM, Ofnuts <ofnuts@xxxxxxx> wrote: > > Plenty of UIs and desktop managers, and plenty of development tastes... > I'm myself on KDE, but if your VM was running Gnome or Unity, it would be > useless to me. I do use a VM for some development that can only be done on > Windows, but using a Linux VM over my existing Linux install is a bit > wasteful? In this case, it is not wasteful. Consider the goals of this project (and development from the perspective of a newcomer). NEWCOMER PERSPECTIVE: * Must assemble over 100 dependency packages from Debian (for Debian GNU/Linux alone; not including other platforms). * Must clone two additional projects (GEGL and BABL). * Must compile projects in the correct order: 1) BABL 2) GEGL 3) GIMP. * On the mailing list there's a lot of "works for me, so it must be something wrong with what you're doing" The point of a bootstrapped development environment is to avoid even having to answer most of the above questions before they're even asked. PRIMARY GOALS: * Lower the barrier to entry for contributing to GIMP source code. * Repeatable and consistent configuration between someone who is new and someone who can verify if issues experienced by the new contributor is with the development environment or with GIMP itself. FUTURE: Even when I maintain the build system at build.gimp.org there's regularly a "works for me" statement when the build system fails but it passes on a developers laptop. These challenges hinder progress when having a repeatable build environment would solve these issues. Future-looking action items for me that will come out of this: * Containerize (via docker) a build environment based off of the vagrant bootstrap development environment. This means build.gimp.org will run the same code and dependencies as the development environment. Avoids the "works for me" syndrome between core developers and the build system. * Create a Windows-based development environment based on https://atlas.hashicorp.com/modernIE and https://dev.modern.ie/ (free Windows VMs provided by Microsoft). CONCLUSION: By settling on a convention for how we build the GIMP software we'll: * speed up development velocity * be more consistent * have a lower barrier to entry for new contributors SAM -- I prefer to encrypt my email GPG FINGERPRINT 4096 KEY 8D8B F0E2 42D8 A068 572E BF3C E8F7 3234 7257 E65F https://keybase.io/samrocketman Learn how to encrypt your email with the Email Self Defense guide: https://emailselfdefense.fsf.org/en/ _______________________________________________ gimp-developer-list mailing list List address: gimp-developer-list@xxxxxxxxx List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
