My concern would mostly be maintenance. It adds to an already very complex build. It only assists developers who are a small audience. What does this provide, concretely? On Jan 21, 2015 12:14 AM, "Nicholas Chammas" <nicholas.cham...@gmail.com> wrote:
> What do y'all think of creating a standardized Spark development > environment, perhaps encoded as a Vagrantfile, and publishing it under > `dev/`? > > The goal would be to make it easier for new developers to get started with > all the right configs and tools pre-installed. > > If we use something like Vagrant, we may even be able to make it so that a > single Vagrantfile creates equivalent development environments across OS X, > Linux, and Windows, without having to do much (or any) OS-specific work. > > I imagine for committers and regular contributors, this exercise may seem > pointless, since y'all are probably already very comfortable with your > workflow. > > I wonder, though, if any of you think this would be worthwhile as a > improvement to the "new Spark developer" experience. > > Nick >
