Add dev goals section, add more core devs and minor updates

Author: jwilander

source/developer/core-developer-handbook.md

@@ -13,22 +13,25 @@ Below is the list of core developers working on Mattermost:
 - Harrison Healey - @harrison on [pre-release.mattermost.com](https://pre-release.mattermost.com/) and [@hmhealey](https://github.com/hmhealey) on GitHub
 - Elias Nahum - @elias on [pre-release.mattermost.com](https://pre-release.mattermost.com/) and [@enahum](https://github.com/enahum) on GitHub
 - George Goldberg - @george on [pre-release.mattermost.com](https://pre-release.mattermost.com/) and [@grundleborg](https://github.com/grundleborg) on GitHub
+- Saturnino Abril - @saturnino on [pre-release.mattermost.com](https://pre-release.mattermost.com/) and [@saturninoabril](https://github.com/saturninoabril) on GitHub
+- Chris Duarte - @uberchris on [pre-release.mattermost.com](https://pre-release.mattermost.com/) and [@csduarte](https://github.com/csduarte) on GitHub
 
 Below is the list of core developers working on individual Mattermost repositories:
 - Pan Luo - [mattermost-docker](https://github.com/mattermost/mattermost-docker) - @compass on [pre-release.mattermost.com](https://pre-release.mattermost.com/) and [@xcompass](https://github.com/xcompass) on GitHub
 - Yuya Ochiai - [desktop](https://github.com/mattermost/desktop) - @yuya-oc on [pre-release.mattermost.com](https://pre-release.mattermost.com/) and [@yuya-oc](https://github.com/yuya-oc) on GitHub
 
-### Reviewing & Merging Pull Requests ###
+### Technical Development Goals ###
 
-Core developers are expected to code review pull requests submitted to the Mattermost repositories. Below are some guidelines for reviewing code:
+We discuss these goals every other week during the [weekly developer meeting](https://docs.mattermost.com/process/training.html#developer-meeting).
 
-- Responsibility for the submitted code relies on the submitter, it is their responsibility to test and implement any changes at high quality. As a result, code reviewers are not required to do a full audit of code changes but should read through the code to:
-  - Make sure the implementation matches the description of the ticket being completed
-  - Ask questions about anything that is not clear
-  - To request changes when the code looks incorrect or doesn't match the correct design patterns
-- Stable respositories that have had a 1.0.0 release require two approved reviews before the changes can be merged
-- Unstable repositories that are still in development may be merged with a single approved review
-- Trivial changes, such as PM-approved text changes or typo fixes, maybe merged with only a single approved review for both stable and unstable repositories
+#### Short Term ####
+- Performance for 20,000 daily active users
+- React Native mobile apps
+
+#### Long Term ####
+- Performance for 200,000 daily active users, 200 million messages per month
+- Orchestration/SAAS
+- Developer Toolkit (APIs, plugins, integrations, samples, documentation)
 
 ### Technical Direction Resolutions ###
 
@@ -41,6 +44,18 @@ Technical direction resolutions are any decisions made by the team affecting the
 5. Removing localization of the server logs. We haven't found it beneficial to localize these messages, and in some cases it has made it more difficult for us to help troubleshoot issues for non-English users. This will also reduce some of the work required when translating Mattermost. ([https://pre-release.mattermost.com/core/pl/13xdrfnw5bb5mnagth5kt48kyr](https://pre-release.mattermost.com/core/pl/13xdrfnw5bb5mnagth5kt48kyr))
 6. All new webapp components should be built against Redux and [follow the new guide](https://docs.mattermost.com/developer/webapp-component.html)
 
+### Reviewing & Merging Pull Requests ###
+
+Core developers are expected to code review pull requests submitted to the Mattermost repositories. Below are some guidelines for reviewing code:
+
+- Responsibility for the submitted code relies on the submitter, it is their responsibility to test and implement any changes at high quality. As a result, code reviewers are not required to do a full audit of code changes but should read through the code to:
+  - Make sure the implementation matches the description of the ticket being completed
+  - Ask questions about anything that is not clear
+  - To request changes when the code looks incorrect or doesn't match the correct design patterns
+- Stable respositories that have had a 1.0.0 release require two approved reviews before the changes can be merged
+- Unstable repositories that are still in development may be merged with a single approved review
+- Trivial changes, such as PM-approved text changes or typo fixes, maybe merged with only a single approved review for both stable and unstable repositories
+
 ### Useful Guides and Documentation ###
 - [Adding a webapp component](https://docs.mattermost.com/developer/webapp-component.html)
 - [Adding actions and selectors to Redux](https://docs.mattermost.com/developer/redux.html)