Context Navigation

Changes between Initial Version and Version 1 of Ticket #49072, comment 3

initial	v1
7	7	I don’t think license.txt or readme.html are the kinds of files that make sense to handle dynamically like a favicon or robots file, but I also don’t think it makes sense to bundle them in the root of every single installation, especially when no commonly popular Apache or Nginx ruleset for WordPress have ever attempted to 404 them, redirect them, or anything else.
8	8
9		So step one in my mind is to find a way to simply remove these files~~. Step two is to make that way feel intentional, possibly as a~~n improvement.
	9	So step one in my mind is to find a way to simply remove these files from the project root. Step two is to include them in a way that feels intentional, possibly even as a fun improvement.
10	10
11	11	macOS [http://osxdaily.com/2014/08/20/famous-steve-jobs-speech-hidden-mac-easter-egg/ famously ships with] a not-so-hidden copy of the “Here’s to the crazy ones” speech. I do still think it would be fun if WordPress shipped with the GPL license as an Attachment that a User ''might'' read, as opposed to a raw file they never will. That’s just a single idea off the top of my head, to soften the blow of WordPress not shipping with a copy of the GPL license at all, which isn’t what I’m suggesting. Hopefully that clarifies somewhat?