Lots of documentation cleanup

docs/LanguageSpecification.md

-# GYP (Generate Your Projects) Language Specification
+# Language Specification
 
-Status: Draft (as of 2009-01-30)
-
-Mark Mentovai <mark@chromium.org> _et al._
-
-Modified: 2009-02-10
-
 [TOC]
 
 ## Objective
 
 Create a tool for the Chromium project that generates native Visual Studio,
 Xcode and SCons and/or make build files from a platform-independent input
 format.  Make the input format as reasonably general as possible without
 spending extra time trying to "get everything right," except where not doing so
 would likely lead Chromium to an eventual dead end.  When in doubt, do what
 Chromium needs and don't worry about generalizing the solution.
@@ skipping 371 matching lines @@
 
   * `Projects`:
     * `WebsiteProperties`:
     * `ProjectDependencies`:
   * `Global`:
     * `SolutionConfigurationPlatforms`:
     * `ProjectConfigurationPlatforms`:
     * `SolutionProperties`:
     * `NestedProjects`:
 
-## Code Location
-
-Here!  http://gyp.googlecode.com/
-
-## Group Members
-
-|:-----------------|:---------------------------------|
-| Darin Fisher     | Overall approval of final design |
-| Elliot Glaysher  | Approval of Linux build functionality. |
-| Alex Harper      |  |
-| Steven Knight    | Language specification.<br />Code for generating Scons files from `.gyp` files. |
-| Mark Mentovai    | Input language design and implementation.<br />Code for generating Xcode files from `.gyp` files.<br />Approval of Mac (Xcode) build functionality. |
-| Bradley Nelson   | Code for generating Visual Studio files from `.gyp` files. |
-| Randall Spangler |  |
-| Nicolas Sylvain  | Approval of Windows build functionality. |
-
 ## Caveats
 
-TODO(sgk):  Notes/Question from very first prototype draft of the language.
+Notes/Question from very first prototype draft of the language.
 Make sure these issues are addressed somewhere before deleting.
 
   * Libraries are easy, application abstraction is harder
     * Applications involves resource compilation
     * Applications involve many inputs
     * Applications include transitive closure of dependencies
   * Specific use cases like cc\_library
     * Mac compiles more than just .c/.cpp files (specifically, .m and .mm
       files)
     * Compiler options vary by:
       * File type
       * Target type
       * Individual file
     * Files may have custom settings per file per platform, but we probably
       don't care or need to support this in gyp.
   * Will all linked non-Chromium projects always use the same versions of every
     subsystem?
   * Variants are difficult.  We've identified the following variants (some
     specific to Chromium, some typical of other projects in the same ballpark):
     * Target platform
     * V8 vs. JSC
     * Debug vs. Release
     * Toolchain (VS version, gcc, version)
     * Host platform
     * L10N
     * Vendor
     * Purify / Valgrind
   * Will everyone upgrade VS at once?
   * What does a dylib dependency mean?
-
-## Testing Plan
-
-_What are the sub-units of your system that will be independently testable?
-Tests must be approved by the code reviewer, and must follow the guidelines in
-the unittesting document as far as possible. See What Is A Design Document for
-criteria for whole system tests on servers.  If there are changes envisaged in
-your future work, would your tests verify the base functionality? If some of
-your tests cannot be easily automated (e.g. UI tests), how will you document
-the needed special procedures?_
-
-## Documentation Plan
-
-Documentation via this wiki: http://code.google.com/p/gyp
-
-## Work Estimates
-
-_Estimates of how long each phase will take (please be detailed; subtask
-granularity should be roughly one week)_
-
-## Launch Plans
-
-_What are the launch plans for your project? This includes, but is not limited
-to:
-    * What visible changes your project will cause on the site.
-    * What will be the impact on production and/or search partners.
-    * What new servers will be introduced.
-    * Rough timeline for releasing your project._