docs: add 2019-05-09 Docs and Tools WG meeting notes (#88)

* docs: add 2019-05-09 Docs and Tools WG meeting notes

* fixup! docs: add 2019-05-09 Docs and Tools WG meeting notes

wg-docs-tools/meeting-notes/2019-05-09.md

@@ -0,0 +1,36 @@
+# Docs & Tools WG meeting 2019-05-09
+
+## Attendees
+ @Hashimoto
+ @ckerr
+ @killian
+
+## Agenda
+
+1. Unified Documentation 
+    * Reiteration of goals from ckerr: have a single set of sample code that can be shared across website, Fiddle, and api-demos; make electronjs.org/docs more organized & navigatable, increase the number of code samples so that new users will know how to do anything in Electron
+    * Launching code examples from docs into Fiddle (@ckerr)
+    * What changes would we need to make to the docs in `electron/electron`? (@ckerr)
+
+1. Making 'Breaking Changes' more discoverable
+    * Kilian points out this is useful to link to in release notes
+    * If we use the same terminology and link to this in every release notes post, developers will know to use that.
+
+## Action Items
+
+ * Open tracking issue for electronjs.org/docs page brainstorming & improvements (@ckerr)
+ * Add link to 'Breaking Changes' in release notes script? Open issue & get feedback from Releases WG (@ckerr)
+
+## Future Agenda
+
+1. Unified Documentation
+    * Embed Fiddle gists as code samples? (@malept)
+
+1. How the [Squirrel.Windows deprecation](https://github.com/electron/electron/issues/17722) affects us (@malept)
+    * [Reboot proposal from @shiftkey](https://github.com/Squirrel/Squirrel.Windows/issues/1470)
+    * Someone from governance should be a part of talks if they aren't already
+
+1. `electron-prebuilt-compile` follow-up (@malept, for @felix)
+
+1. `@electron/download` update (@malept, @MarshallOfSound)
+    * Needs to be renamed something else due to NPM naming restrictions