Add new validator tools subfolder and doc for building a command-line validator on Mac OS X

[pietergreyling]

Add new validator tools subfolder and doc for how to build the official AMP-HTML command-line AMP validator on Mac OS X.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[pietergreyling]

I signed it
On Jan 25, 2016 01:03, "googlebot" notifications@github.com wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project. Before we can look at your
pull request, you'll need to sign a Contributor License Agreement (CLA).

[image: 📝] Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll

verify. Thanks.

• If you've already signed a CLA, it's possible we don't have your
  GitHub username or you're using a different email address. Check your
  existing CLA data https://cla.developers.google.com/clas and verify
  that your email is set on your git commits
  https://help.github.com/articles/setting-your-email-in-git/.
• If you signed the CLA as a corporation, please let us know the
  company's name.

—
Reply to this email directly or view it on GitHub
#1554 (comment).

[cramforce]

You can probably avoid the -g here. If you have a package.json local installation should work.

[cramforce]

Could you also update and point to your new doc in https://github.com/ampproject/amphtml/blob/master/validator/README.md

[powdercloud]

Would it make sense to call this new directory docs instead of tools?
I have a hunch we'll want to add some more docs (e.g. about versioning), so it'd be a good precedent.

[pietergreyling]

Done:
renamed validator/{tools => docs}/building_a_command_line_amp_validator_for_mac_os_x.md
repointed: validator/README.md to refer to docs/..

[jridgewell]

I'd like to drop this section since it's not needed for the validator. We have a DEVELOPMENT.md with these instructions instead.

[powdercloud]

Sweet, thank you! I think this is good to go, except I see very many commits in this PR. Would you mind squashing these so the overall change history for the project is easier to read? You may already know how to do this, but in case not, this doc has helped me in the past:
https://github.com/ginatrapani/todo.txt-android/wiki/Squash-All-Commits-Related-to-a-Single-Issue-into-a-Single-Commit

[pietergreyling]

Squash done as follows (although authentication for terminal git push fails - 2 factor auth maybe?):

commit 63bedbb679e6ef6659bae5595a4d58d2a44df5b5
Author: Pieter Greyling pieter.greyling@gmail.com
Date: Mon Jan 25 00:43:28 2016 +0000

Created new docs folder.
Created building_a_command_line_amp_validator_for_mac_os_x.md.
Changed validator/build.py to allow experimental validator builds for Mac OS X systems.

[pietergreyling]

Forced push using 2F token over https:
To https://github.com/pietergreyling/amphtml.git

• 4ce49f1...0eba1d5 greyling-tools -> greyling-tools (forced update)

[powdercloud]

Hmm, I wonder whether something went wrong. Now I see a bunch of different files in there (https://github.com/ampproject/amphtml/pull/1554/files - 9 total). :-(

[pietergreyling]

Yep, only the last 3 are mine:
validator/docs/building_a_command_line_amp_validator_for_mac_os_x.md
validator/build.py
validator/README.md

[powdercloud]

Thank you! @jridgewell I think the comment about the /etc/hosts makes sense but a link to the development.md can go in as a follow up as well, so I think this one is fine as is.