Creating a list of possible additions (copied from email discussion):
- Overview of the Organization - Talk about how we interact with the rest of the organization and how we fit in. We have the staff pages which describe the roles - but its difficult yo get a picture of the organization in my head.
- Organization Technical Architecture Overview - Relates to above. How are the systems organized and who is responsible for them.
- Overview of the sites - mediawiki, labs, wikimedia, office, etc… Much like the organization overview, I can read the sites purpose on line, but its not clear on how we use them day-to-day. What goes where? How do they relate to each other, etc…
- Deployment - How do we get code to the app store? How do we ship betas. Provisioning profiles, iTunes Connect / Dev Portal Access. etc…
- Jenkins / Builds - Related to the previous topic. Discus the build system. How do we access and modify jenkins. Any server scripts we need to know about? Whats the versioning scheme, etc…
- Coding Guidelines / Architecture - Do we have any docs on these? If not, we can just discus at the next code meeting.
- Onboard Code Review - I've done this a couple times and wanted to know what you thought. As Brian and I tackle our first bugs, we could write up a review of the code base with comments and questions on etherpad - and then discus them with the team. This lets us give you a fresh "outsider" perspective before we get too ingrained in the team.