Update 20190513 alldevs notes (#462)

docs/videos/meeting_notes/all_aragon_devs/alldevs20190513.md

@@ -1,12 +1,12 @@
 # All Aragon Devs #22
 
 Call #22: May 13, 2019 8am PST / 11am EST / 3pm UTC / 5pm CEST
-- [Audio/video of the meeting]()
+- [Audio/video of the meeting](https://www.youtube.com/watch?v=q4ytqn8p5do)
 - See [notes](#notes)
 
 ## Agenda
 
-- Appoint note takers 
+- Appoint note takers
 - Introduce team members who haven’t already met each other (~0-5min)
 - Aragon One updates from last call and current priorities (~5min)
 - Aragon Autark updates from last call and current priorities (~5min)
@@ -22,22 +22,24 @@ Call #22: May 13, 2019 8am PST / 11am EST / 3pm UTC / 5pm CEST
     - Visual refresh
     - App caching
     - aragonOS news
-- Potential caching solutions (A1 / AB)
+- **(Moved to next call)** Potential caching solutions (A1 / AB)
     - The Graph
     - Centralized cache server
-- Forwarding API
-- IPFS follow-up
-- Aragon Mini Lib [can skip]
+- **(Moved to next call)** Forwarding API
+- **(Moved to next call)** IPFS follow-up
+- **(Moved to next call)** Aragon Mini lib
 
 ## Notes
 
 ### Introductions
 
+- Welcome Cory from Aragon Black!
+
 ### Updates
 
 #### Aragon One
 - A1 preparing 0.7.2 for the client
-- Trying to finish up payroll app, staging should be out soon! 
+- Trying to finish up payroll app, staging should be out soon!
 - Contract still has to get audited
 - Worked on 0.8 scope, the next release. We want to keep it stable and backward compatible, but it will introduce some visual changes. Middle / end July.
 - A1 started splitting court implementation in different contracts
@@ -46,9 +48,9 @@ Call #22: May 13, 2019 8am PST / 11am EST / 3pm UTC / 5pm CEST
 
 #### Autark
 
-- determined contract changes needed to implement through external audit
+- Determined contract changes needed to implement through external audit
 - Home app: all the design screens are done, working on the initial implementation.
-- Confirmed first external higher, should be on next All Devs!
+- Confirmed first external hire, should be on next All Devs!
 
 
 #### Open Work Labs
@@ -58,7 +60,7 @@ Call #22: May 13, 2019 8am PST / 11am EST / 3pm UTC / 5pm CEST
 
 
 #### Aragon Mesh
- 
+
 - Been fixing some bugs during the past 2 weeks and writing tests for the CLI
 - Tutorial to use the CLI with Frame.
 - Enhancement to the `aragon start` command (it now accepts a dao address argument).
@@ -70,7 +72,7 @@ Call #22: May 13, 2019 8am PST / 11am EST / 3pm UTC / 5pm CEST
 - Some work on Apiary
 - Apiary contracts are almost ready
 - Spent the last week double checking all the tests.
--  The bonding curve still require some checks but should be ready 2 weeks from now to be shipped for audit
+- The bonding curve still require some checks but should be ready 2 weeks from now to be shipped for audit
 - UI/UX is almost there, still some polish to be done (responsiveness, data fetching), will be totally ready in two weeks. From there, there will be some work on the background scripts.
 - Started working on documentation around Apiary, both for developers and end users.
 - Worked on making it possible to commit from the browser.
@@ -89,20 +91,20 @@ Call #22: May 13, 2019 8am PST / 11am EST / 3pm UTC / 5pm CEST
 
 ### Announcements
 
-
 ### Discussions
 
-#### Release dev tools
+#### Releasing dev tools and communicating their releases
 
 - Suggestion to have two release channels, “stable” and “next”, so that we can release more often.
 - We could have a Twitter account for the Aragon dev tools.
 - We could use multiple channels: Rocket.chat, micro blog post, forum, Twitter, GitHub releases.
+  - For now: use Twitter and Rocket.chat, for people who would like to follow the updates on Github, they can use the "watch releases" functionality
 
 #### Aragon Design system
 
 - Started as a visual refresh, evolved into a new design system for Aragon.
 - Presentation by Paty: introduction to design systems and w hy it is needed for Aragon.
-- collection of rules constraints and principles for design in Aragon
+- Collection of rules constraints and principles for design in Aragon
 - We could define a governance model for this design system (quality criteria, roles, production stages).
 - Aragon One started creating guidelines about how to create design and components specifications.
 - Overview of the recent design work by the Aragon One design team.
@@ -116,25 +118,22 @@ Call #22: May 13, 2019 8am PST / 11am EST / 3pm UTC / 5pm CEST
 - Next step is to align with all teams and front end leads to discuss implementation with aragonUI and API
 - Design part is finalized in the coming weeks
 
-
-
-
 ## Attendance:
 
 Aragon Black: Olivier, Xavier, Cory, Deam
 
-A1:Brett, Jorge, Bingen, Luis, Paty, Pierre, Maria, Facu, Daniel, Gorka, Luke
+A1: Brett, Jorge, Bingen, Luis, Paty, Pierre, Maria, Facu, Daniel, Gorka, Luke
 
-Autark: Arthur, Yalda, Radek, 
+Autark: Arthur, Yalda, Radek,
 
 Open Work Labs: Jonathan
- 
+
 Aragon Mesh: Gabi, Daniel
- 
+
 AA: Louis
 
 Community:
 
 
 ## License
-This template is modified from the Ethereum All Core Devs call notes [template](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%20Template.md) and inherits the same [CC-BY-SA 3.0 License](https://github.com/ethereum/pm/blob/master/LICENSE).
+This template is modified from the Ethereum All Core Devs call notes [template](https://github.com/ethereum/pm/blob/master/All%20Core%20Devs%20Meetings/Meeting%20Template.md) and inherits the same [CC-BY-SA 3.0 License](https://github.com/ethereum/pm/blob/master/LICENSE).

mkdocs.yml

@@ -98,6 +98,8 @@ pages:
         - Notes template: 'videos/template.md'
         - Running the call: 'videos/running_all_devs.md'
         - Meeting Notes:
+          - May 2019:
+            - 13.05.2019: 'videos/meeting_notes/all_aragon_devs/alldevs20190513.md'
           - April 2019:
             - 29.04.2019: 'videos/meeting_notes/all_aragon_devs/alldevs20190429.md'
             - 15.04.2019: 'videos/meeting_notes/all_aragon_devs/alldevs20190415.md'