1. 1 Media Production Support v1 5 May 2010 Blake Crosby June 2, 2010 Standards Documents

2. 2 Media Production Support v1 5 May 2010 Purpose  Common questions.  MPS would get the same questions over and over again from internal employees and external vendors.  More than one way to skin a cat.  There was no standard way of doing things.  Reduce frustration.  Make Your Work Easier  No need to submit tickets as answers can be found in the standards docs.  Develop a package for external vendors.  The standard documents are to be used to ensure that the vendors are familiar with our environment.  Educate employees.  Anyone is welcome to read and understand them.

3. 3 Media Production Support v1 5 May 2010 What They Are/Are Not  The Standards Documents Are:  Industry best practices  Developed in conjunction with DP&BD Apps, Partnering, and QA and are not arbitrary  Ratified policies by CBC Account Managers and Partners  Based on educated decisions  A way to make your work easier  A way to improve site stability  Updated as needed (and re-ratified).  They are not:  Written in stone. Corrections or changes are welcome  The law. Provisions are in place for derogations if required  Meant to make your work more difficult

4. 4 Media Production Support v1 5 May 2010 What MPS Expects of You  Understand Them  Developers read and understand them when they first start (new hires). This includes developers hired by individual content areas.  That account managers/directors understand the general contents and are able to provide guidance to their clients.  Ask Questions  If you don’t understand them, that you ask MPS for clarification.  Enforcement  MPS will conduct periodic audits for compliance and we expect everyone to come to the table to commit to fixing non-compliant software or processes.  Report Errors / Changes  If there are errors or changes that need to be made, that you will report them to MPS.

5. 5 Media Production Support v1 5 May 2010 Overview  Filesystem Organization Schedule  Outlines the locations of files for dev, qa, production. Where libraries, logs, media, PHP & Java applications are to be installed.  Outlines virtual hosting naming conventions (eg: www.qa.nm.cbc.ca)  Content Delivery Infrastructure Platform  Outlines the versions and type of software that runs CBC.ca (java, tomcat, apache, database)  Outlines libraries and extensions available to PHP, Apache, and Tomcat (gd, mod_rewrite)  Outlines usage of scheduled jobs  Application Development Standards  Covers how to package your applications for deployment (PHP, Java, and Feed/Batch)  Outlines what needs to be documented  Logging and log management  Change Management for Applications  Roles and responsibilities of Devs, QA, and MPS for change management  What needs to accompany each release (release notes, installer)  Change management workflow and Release Windows

6. 6 Media Production Support v1 5 May 2010 Overview  Database Standards  Outlines principles of design.  Naming conventions for tables, databases, functions, indexes, etc..  Database creation workflow  HTTP Content Delivery Standards  Outlines when redirects or rewrite rules should be used  Cache times and policies  Supported and Unsupported features (ESIs, and Geofencing)  Source Code Repository Standards  Location of subversion and how to access it  Organization structure of modules, and code  Access control list (who has access to what)  Movable Type Standards  Usage of MT for Blogs and as a “CMS”.  Access control lists (who has access to what)  Policies governing the usage of templates and media.

7. 7 Media Production Support v1 5 May 2010 Overview  Media Delivery Standards  Outlines how delivery of media (on-demand, live) to end users.  Naming conventions for streaming entry points  Protocols used for streaming (http, rtmp)

8. 8 Media Production Support v1 5 May 2010 Where can I get them?  Live Link  http://nt03otll/livelinke/livelink.exe/open/12171228

9. 9 Media Production Support v1 5 May 2010 Questions?  Questions?