On Fri, Oct 17, 2014 at 1:14 PM, Jens <[email protected]> wrote:
> How big is the VM image? >> > > I would guess at least 300 MB. > > Requiring a VM doesn't really make things simpler. Just imagine for a new > contributor that is used to the usual Github flow: > > - Sign up Gerrit + sign CLA (I guess that one is accepted nowadays among > developers) > - Download and install VirtualBox or activate Hyper-V in Win8.1+. Might > require a restart. > - Download image, 300MB+ > - Mount a directory from the VM so you can directly work on the git > repository inside the VM. > > If I imagine I would want to fix a small bug that maybe has a workaround > available I am not sure if I would go through the above. If I would plan to > contribute more often then the above might be acceptable for Windows users, > but for a one time contribution probably not. > …on the other hand, VirtualBox and/or boot2docker and/or Vagrant are reusable across projects, and I'd expect web developers to use VMs nowadays, if only for browser testing (e.g. testing in different versions of IE). What if we commit IDE configurations in the repository? (and make sure they're updated each time we change the build; that would be similar to today's situation, except that the IDE config could be generated from the build scripts) A new contributor could then work without a VM (for a small patch, running tests in the IDE should be enough), until he wants/needs to use a custom build of GWT in his projects; then he'd have to find a Linux or OS X machine (or VM) to actually build GWT. Would that be acceptable? -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAEayHEO%3Dg9F-NgukO%2Bm4_w7sZSRB7abzLHdec47c4myLD21reQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
