WIP: Migrate Wiki content over to src/docs

docs/design_docs_to_write.md

Index: docs/design_docs_to_write.md
diff --git a/docs/design_docs_to_write.md b/docs/design_docs_to_write.md
new file mode 100644
index 0000000000000000000000000000000000000000..95bf118638925e6e10ab2d9890dff2c50045d484
--- /dev/null
+++ b/docs/design_docs_to_write.md
@@ -0,0 +1,29 @@
+# Introduction

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

Delete?

+
+This page contains a list of all the design documents that we need to write in order to better document how our infrastructure and features are implemented. Feel free to add something to the list. Doing so does **not** mean that you are signing up to write it, we'll find someone!
+
+## Cross-Platform
+
+  * how the password manager works at a high level (when new entries are stored, how scoring works, how imported passwords without stored action URLs are handled, etc.) (stuartmorgan) (note see https://wiki/Main/ChromePasswordManagerDesignDoc)
+  * try servers - how they work, limitations, different supported methods to upload patches, etc.
+  * how the update mechanism works - how the server communicates with the chrome, how to use Courgette, etc.
+  * webintents
+
+## Mac
+
+  * tab dragging in and between windows (pink)
+  * tab layout (pink)
+  * BWC ownership model, NSViewController/NSWindowController ownership, how to write CocoaTests (pink, dmaclach)
+  * animations (infobar, download shelf, bookmarkbar)
+  * omnibox (class hierarchy, what happens when you type into the omnibox, etc)
+  * keypress/keyboard/IME/main menu shortcuts input flow (owner: thakis, work-in-progress at http://sites.google.com/a/chromium.org/dev/developers/os-x-keyboard-handling)
+  * how to write l10n-savvy nibs
+    * http://dev.chromium.org/developers/design-documents/ui-localization/mac-notes is decent imho (thakis)
+    * however, it has many ???'s for complex examples. it's a great starting point but needs finishing (pinkerton)
+  * graphics rendering and event processing for plug-ins, particularly how Mac NPAPI differs from Windows/Linux (awalker)
+  * Make sure SpellingPanelPlanningDoc is up to date
+  * on-disk app structure and maybe some autoupdate tidbits (mark)
+
+## Linux
+
+  * how zygotes work, why they were chosen (distribution partners), and why it isn't a recommended approach for others to take (ie, mozilla).  Probably should just flesh out the LinuxZygote doc