[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 pento):

 @nbachiyski: I'm absolutely in favour of supporting web-based development
 environments, as well as investigating their use for new contributors.
 They're a long way from being full solutions, however, for a few reasons:

 - They require a continuous, reasonably stable internet connection.
 - Adding config for popular editors is a good idea. Mandating the editor
 is not.
 - Storing GitHub/SVN/whatever credentials in the cloud is... less than
 ideal. 🙃 Requiring re-authentication for every commit is a terrible UX.

 There are other services that are more focussed on providing the shared
 development stack (eg, [https://www.koding.com/ Koding]), but they have
 their own set of issues.

 So as to not get too far ahead of ourselves, the focus of this ticket is
 to create a development environment that:

 - Fits existing uses. Primarily, core development, Gutenberg development
 (as a model for future core development), and can be easily setup at
 contributor days.
 - Is built with future uses in mind. Either container or full VM
 configurations can be relatively easily translated to online development
 environments, or to testing environments like calypso.live.

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