Update quick-start documentation to use new drupal.org URL

Trying these commands, I get the following:

~/Downloads/drupal $ php core/scripts/drupal quick-start
Could not open input file: core/scripts/drupal

~/Downloads/drupal $ ls core/scripts/
cron-curl.sh                 dump-database-d7.sh          js                           transliteration_data.php.txt
cron-lynx.sh                 dump-database-d8-mysql.php   password-hash.sh             update-countries.sh
db-tools.php                 generate-d6-content.sh       rebuild_token_calculator.sh
drupal.sh                    generate-d7-content.sh       run-tests.sh
dump-database-d6.sh          generate-proxy-class.php     test

It seems like those commands might require 8.6.x which is not yet released, so _technically_ this can't be fully tested.

One last note: I remember some discussion over using tar vs unzip in the issue which generated the quick-start command. I'll try to see if there were any caveats to switching.

Adding related issue.

And regarding unzip vs tar... this was because of Windows; a couple comments mentioned it's more likely to be available than tar in a Windows environment—most notably:

It defaulted to using unzip as that is more readily available on Windows.

From: #2911319-121: Provide a single command to install & run Drupal.

Is there a 'latest zipped archive' release URL as well?

I've picked this up at #uoe-d8-contribution

I've applied and tested this patch.
https://www.drupal.org/files/issues/2018-08-16/2992879-quick-start-docs-...
Install.txt has been updated with the appropriate MacOS/Linux and Windows commands.

Reviewed and and happy with this patch.

Not 100% sure if this should be RTBC yet; I think the main concern I have is this splits off the directions between Mac/Linux users and Windows users... which reverses course on the initial purpose of "one set of instructions no matter who you are".

It's nice to be optimized for the best use case, but this would be yet another example where those using Windows will end up being 2nd class citizens, in that their instructions are later in the README, and their instructions are not the same as the instructions the non-Windows users have (meaning fewer people would be using that set of instructions, it's less likely that someone who could quickly make an impact on fixing things would notice that the Windows download link isn't working vs. the one for Mac/Linux, etc.).

I'm not fully opposed to this patch... but I do think it's something we should get more input on, since we ended up spending significant energy (and helping a few first-time Windows-using contributors get their feet wet at the last DrupalCon) making sure the instructions worked on all major platforms, and not just the POSIX-centric ones.

The Needs Review Queue Bot tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

Downloading via a tarball is being removed. So, the instructions should be changed to using composer.

So, this hasn't been a response to the questions in #12 for 7 years. And @geerlingguy makes a valid point that having separate instructions for *nix family and Windows isn't ideal. However, we now only promoting installs via composer so this is now a won't fix. The wget commands are being removing in #3086655: Add composer instructions to INSTALL.txt and that is eligible for backport.

Therefor, I have updated credit and am closing this one.