[wp-trac] [WordPress Trac] #43711: Let's create a standard development setup for WordPress core.

[WordPress Trac]

#43711: Let's create a standard development setup for WordPress core.
------------------------------+------------------------------
 Reporter:  omarreiss         |       Owner:  (none)
     Type:  enhancement       |      Status:  new
 Priority:  normal            |   Milestone:  Awaiting Review
Component:  Build/Test Tools  |     Version:  trunk
 Severity:  normal            |  Resolution:
 Keywords:                    |     Focuses:
------------------------------+------------------------------

Comment (by Mte90):

 I am a huge fan of VVV, so I will try to be not from a side and be
 impartial.

 One of the problems that has VVV right now is that require a lot of time
 on first start because of installation (and download of a lot of things)
 but the plan for version 3 (https://github.com/Varying-Vagrant-
 Vagrants/VVV/issues/1469) with a box that contain everything and also the
 parallel for the provision will improve a lot this point.

 The other problems that often at contributor day we have is Windows.
 Install virtualbox, vagrant, git on Windows is a big step because people
 do't know anything of them.
 Often the problems on VVV is because there are different versions of
 powershell on the system (don't ask me why) and Vagrant or Virtualbox
 works with issue based on the version of ps.

 With docker we will have more problems on Windows because we need a
 virtual machine so (virtualbox and git will be required in any case) so
 the only advantage that we don't have anymore the easy vagrant to use but
 docker (that is not so entry level).

 Sure, there is the VVV USB Generator that prepare all the executables for
 download (maybe also the latest image) but we need to think that at
 contributor day not everyone has an OS dev friendly for *nix stuff.
 We have already a lot of issues with vagrant I can image with Docker
 virtualized...

 From the other side VVV has the cool part to be used also for not
 contribute and very easy with vagrant up/halt and db backup so usually
 people are interested in that then contribute.

 So probably the better way is to start to work on VVV at least for the GUI
 side, so we can gather feedback because the technical problems are from
 both the side.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/43711#comment:4>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform