WIP: Migrate Wiki content over to src/docs

Per https://groups.google.com/a/chromium.org/forum/#!topic/chromium-dev/irLAQ8f8uGk

Initial migration of wiki content over to src/docs

There will be a follow-up CL to ensure docs are following chromium’s style guide, links are fixed, etc. The file auditing was becoming too much for a single change and per Nico’s suggestion, it seems to be better to do

+ Bulk import with initial prune.
+ Follow-up CLs to clean up the documentation.

So that each CL has its own purpose.

BUG=none

Committed: https://crrev.com/3322f7611ba1444e553b2cce4de3a1a32ad46e72
Cr-Commit-Position: refs/heads/master@{#345186}

[Bons, 2015-08-20 20:16:47]

andybons@chromium.org changed reviewers:
+ jparent@chromium.org, nodir@chromium.org

[Bons, 2015-08-20 20:16:51]

initial dump of docs with a comb-through of what should be deleted. any help on
marking docs as "we don't need this anymore" would be very helpful.

https://codereview.chromium.org/1309473002/diff/1/docs/breakpad.md
File docs/breakpad.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/breakpad.md#newcode1
docs/breakpad.md:1: See LinuxCrashDumping.
delete file

https://codereview.chromium.org/1309473002/diff/1/docs/bug_horizons.md
File docs/bug_horizons.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/bug_horizons.md#newcode1
docs/bug_horizons.md:1: The bugs that need to be fixed for the next release can
be found for a given component by looking at the bug "horizon" URL:
none of these links work. propose deletion.

https://codereview.chromium.org/1309473002/diff/1/docs/chromium_software_cons...
File docs/chromium_software_construction_system.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/chromium_software_cons...
docs/chromium_software_construction_system.md:7: ## Obsolete
propose to delete based on this

https://codereview.chromium.org/1309473002/diff/1/docs/dealing_with_greasemon...
File docs/dealing_with_greasemonkey.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/dealing_with_greasemon...
docs/dealing_with_greasemonkey.md:3: Lots of users still complain that Chrome
does not support Greasemonkey user scripts. Even though we have had the
infrastructure in place to handle user scripts for some time now, it has never
been clear how the feature would relate to full extensions, and so it has
remained incomplete.
propose to delete due to the age of the doc

https://codereview.chromium.org/1309473002/diff/1/docs/developer_wiki.md
File docs/developer_wiki.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/developer_wiki.md#newc...
docs/developer_wiki.md:1: # Chromium Developer Wiki
propose deletion since this doesn't cover every document.

https://codereview.chromium.org/1309473002/diff/1/docs/embedded_browser_frame...
File docs/embedded_browser_framework.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/embedded_browser_frame...
docs/embedded_browser_framework.md:1: **This document is obsolete.  Please visit
the chromium embedded framework project page at
http://code.google.com/p/chromiumembedded/**
propose deletion based on this comment

https://codereview.chromium.org/1309473002/diff/1/docs/glossary.md
File docs/glossary.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/glossary.md#newcode1
docs/glossary.md:1: https://sites.google.com/a/chromium.org/dev/glossary
delete

https://codereview.chromium.org/1309473002/diff/1/docs/google_summer_of_code2...
File docs/google_summer_of_code2010.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/google_summer_of_code2...
docs/google_summer_of_code2010.md:3: Thanks for your interest in the GSoC 2010
for Chromium. Before applying, make sure you have checked out, built chromium
and run the unit\_tests. Visit http://dev.chromium.org/ for the guidelines. Once
you've done that (and not before), feel free to contact your potential mentor on
the chromium irc channel.
propose deletion due to this doc being 5 years old

https://codereview.chromium.org/1309473002/diff/1/docs/info_bar_extension_api.md
File docs/info_bar_extension_api.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/info_bar_extension_api...
docs/info_bar_extension_api.md:3: Lots of extensions want to show infobars for
various reasons. Though the infobars usually follow the pattern of a string of
text and a few buttons, they sometimes also want to show richer controls.
propose to delete

https://codereview.chromium.org/1309473002/diff/1/docs/inter_extension_commun...
File docs/inter_extension_communication.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/inter_extension_commun...
docs/inter_extension_communication.md:7: Proposed API for communication between
different extensions.  There are three parts, the actual APIs exposed to
extensions, a change to the manifest to declare communication permissions, and a
change to the event firing behavior
delete

https://codereview.chromium.org/1309473002/diff/1/docs/jon.md
File docs/jon.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/jon.md#newcode1
docs/jon.md:1: #summary Jon@chromium.org's test page
delete

https://codereview.chromium.org/1309473002/diff/1/docs/kayako.md
File docs/kayako.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/kayako.md#newcode10
docs/kayako.md:10: Add your content here.  Format your content with:
delete

https://codereview.chromium.org/1309473002/diff/1/docs/kde_support.md
File docs/kde_support.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/kde_support.md#newcode13
docs/kde_support.md:13: XXX fill me in with kwallet integration notes
delete. file is incomplete.

https://codereview.chromium.org/1309473002/diff/1/docs/linux_build32_on64.md
File docs/linux_build32_on64.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/linux_build32_on64.md#...
docs/linux_build32_on64.md:3: _OBSOLETE: Building 32-bit Chromium on 64-bit
Linux is no longer officially supported. The "32-bit compatibility libs"
instructions probably won't work. The chroot instructions are your best bet, but
it is not actively tested or maintained._
delete due to this being obsolete

https://codereview.chromium.org/1309473002/diff/1/docs/linux_build64_bit.md
File docs/linux_build64_bit.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/linux_build64_bit.md#n...
docs/linux_build64_bit.md:1: Obsolete; folded into LinuxBuildInstructions.
delete

https://codereview.chromium.org/1309473002/diff/1/docs/linux_chromium64.md
File docs/linux_chromium64.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/linux_chromium64.md#ne...
docs/linux_chromium64.md:1: See LinuxBuild64Bit.
delete

https://codereview.chromium.org/1309473002/diff/1/docs/linux_make_build.md
File docs/linux_make_build.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/linux_make_build.md#ne...
docs/linux_make_build.md:1: The make build is no longer used. Look at
[ninja](NinjaBuild.md) instead.
remove

https://codereview.chromium.org/1309473002/diff/1/docs/migrating_from_subvers...
File docs/migrating_from_subversion_to_git.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/migrating_from_subvers...
docs/migrating_from_subversion_to_git.md:3: If you'd like to use git but you
have only used subversion for chromium until now, then you are faced with the
prospect of cloning the entire repo again to start using git or downloading a
big rather old bootstrap tarball and updating from there. This sucks. However
since git is all about **content** and since you already have the content on
your drive it is possible to cheat. This set of instructions will guide you
through manually creating a new git repo that is the equivalent of your current
svn repo without downloading stuff from the net.
propose obsoletion since git is the standard now

https://codereview.chromium.org/1309473002/diff/1/docs/page_action_ap_iv2.md
File docs/page_action_ap_iv2.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/page_action_ap_iv2.md#...
docs/page_action_ap_iv2.md:3: We currently have a page actions API, but it is
very weird because we were learning what we liked as we were building it. We
also now have a BrowserActions API that we like a lot more, but it stinks that
it is very different from the page actions API.
delete due to staleness?

https://codereview.chromium.org/1309473002/diff/1/docs/running_chrome_ui_test...
File docs/running_chrome_ui_tests.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/running_chrome_ui_test...
docs/running_chrome_ui_tests.md:1: _**NOTE: These directions seem to be
incomplete or out of date. The test binaries are all in out/Debug (for Debug
builds using Ninja). See http://crbug.com/95848**_
delete due to out of date content?

https://codereview.chromium.org/1309473002/diff/1/docs/startup.md
File docs/startup.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/startup.md#newcode1
docs/startup.md:1: (Just some notes as I go)
delete

https://codereview.chromium.org/1309473002/diff/1/docs/user_scripts.md
File docs/user_scripts.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/user_scripts.md#newcode1
docs/user_scripts.md:1: # User Scripts in Chromium and Google Chrome
remove

https://codereview.chromium.org/1309473002/diff/1/docs/using_git_submodules.md
File docs/using_git_submodules.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/using_git_submodules.m...
docs/using_git_submodules.md:1: # AS OF 2014-05-08 SUBMODULES HAVE BEEN REMOVED
AND ARE NO LONGER OPERATIVE
remove

https://codereview.chromium.org/1309473002/diff/1/docs/using_new_git.md
File docs/using_new_git.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/using_new_git.md#newcode1
docs/using_new_git.md:1: Moved to
https://sites.google.com/a/chromium.org/dev/developers/how-tos/get-the-code
remove

https://codereview.chromium.org/1309473002/diff/1/docs/using_old_git_deprecat...
File docs/using_old_git_deprecated.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/using_old_git_deprecat...
docs/using_old_git_deprecated.md:2: # DO NOT USE THIS PAGE
remove

https://codereview.chromium.org/1309473002/diff/1/docs/views_extraction_statu...
File docs/views_extraction_status.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/views_extraction_statu...
docs/views_extraction_status.md:7: **Outstanding deps:**<br>
remove since this is a work in progress doc

https://codereview.chromium.org/1309473002/diff/1/docs/windows_visual_studio_...
File docs/windows_visual_studio_macros.md (right):

https://codereview.chromium.org/1309473002/diff/1/docs/windows_visual_studio_...
docs/windows_visual_studio_macros.md:5: The following macros can aid your
workflow under the full (non-Express, i.e. paid) versions of Visual Studio 2010
and earlier. Unfortunately, Visual Studio 2012 and later <a
href='http://social.msdn.microsoft.com/Forums/vstudio/en-US/d8410838-085b-4647-8c42-e31b669c9f11/macros-in-visual-studio-11-developer-preview?forum=vsx'>do
not support macros</a>. You should try <a
href='http://chromium.github.io/vs-chromium/'>the <b>vs-chromium</b> Visual
Studio Extension which provides similar functionality</a>.
delete since all builds are with ninja, now.

[Robert Sesek, 2015-08-24 18:07:42]

rsesek@chromium.org changed reviewers:
+ rsesek@chromium.org

[Robert Sesek, 2015-08-24 18:07:43]

https://codereview.chromium.org/1309473002/diff/40001/docs/c_cache_mac.md
File docs/c_cache_mac.md (right):

https://codereview.chromium.org/1309473002/diff/40001/docs/c_cache_mac.md#new...
docs/c_cache_mac.md:1: # Introduction
Most of the linux docs have a linux_ prefix, whereas some Mac docs have a _mac
suffix. Probably be consistent?

https://codereview.chromium.org/1309473002/diff/40001/docs/design_docs_to_wri...
File docs/design_docs_to_write.md (right):

https://codereview.chromium.org/1309473002/diff/40001/docs/design_docs_to_wri...
docs/design_docs_to_write.md:1: # Introduction
Delete?

https://codereview.chromium.org/1309473002/diff/40001/docs/stability_fixit_we...
File docs/stability_fixit_week.md (right):

https://codereview.chromium.org/1309473002/diff/40001/docs/stability_fixit_we...
docs/stability_fixit_week.md:1: # Stability Fixit Week
Delete?

https://codereview.chromium.org/1309473002/diff/40001/docs/stabilize_trunk.md
File docs/stabilize_trunk.md (right):

https://codereview.chromium.org/1309473002/diff/40001/docs/stabilize_trunk.md...
docs/stabilize_trunk.md:1: # What should I work on?
Seems obsolete.

https://codereview.chromium.org/1309473002/diff/40001/docs/useful_ur_ls.md
File docs/useful_ur_ls.md (right):

https://codereview.chromium.org/1309473002/diff/40001/docs/useful_ur_ls.md#ne...
docs/useful_ur_ls.md:1: # Introduction
Nasty filename. useful_urls.md ?

https://codereview.chromium.org/1309473002/diff/40001/docs/using_web_kit_git.md
File docs/using_web_kit_git.md (right):

https://codereview.chromium.org/1309473002/diff/40001/docs/using_web_kit_git....
docs/using_web_kit_git.md:1: ## If you know how to use Git
Delete

https://codereview.chromium.org/1309473002/diff/40001/docs/xcode4_tips.md
File docs/xcode4_tips.md (right):

https://codereview.chromium.org/1309473002/diff/40001/docs/xcode4_tips.md#new...
docs/xcode4_tips.md:1: # Introduction
Delete?

[Bons, 2015-08-24 21:11:08]

andybons@chromium.org changed reviewers:
+ ben@chromium.org, brettw@chromium.org
- rsesek@chromium.org

[Bons, 2015-08-24 21:11:59]

Adding Ben and Brett for review since it’s adding a top-level dir.

[Ben Goodger (Google), 2015-08-24 21:20:28]

lgtm for toplevel

[Bons, 2015-08-24 21:24:43]

The CQ bit was checked by andybons@chromium.org

[Bons, 2015-08-24 21:24:43]

The patchset sent to the CQ was uploaded after l-g-t-m from ben@chromium.org
Link to the patchset: https://codereview.chromium.org/1309473002/#ps120001
(title: " ")

[commit-bot: I haz the power, 2015-08-24 21:25:11]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1309473002/120001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1309473002/120001

[commit-bot: I haz the power, 2015-08-24 21:37:18]

Committed patchset #7 (id:120001)

[commit-bot: I haz the power, 2015-08-24 21:39:49]

Patchset 7 (id:??) landed as
https://crrev.com/3322f7611ba1444e553b2cce4de3a1a32ad46e72
Cr-Commit-Position: refs/heads/master@{#345186}

[tomhudson, 2015-08-28 15:05:08]

How do you want follow-ups handled? Comments here, Chrome bugs, emails?

It looks like various using_git documents were deleted, but there's still a
"Using Git for version control and code reviews." link on the wiki which is now
broken. Digging through history
(https://code.google.com/p/chromium/wiki/UsingOldGitDeprecated) perhaps the
Using Git should now be pointed to Get the Code, but that doesn't quite cover
the same range of issues implied by the original link.