Intro To Engagement Engineering
May 2015
(use arrow keys to navigate)
Our Team's Key Objectives
- Support Brand & the PMM team with technical expertise.
- Provide technical services for campaigns, websites and platforms.
- Develop solutions that showcase the best of open web technologies.
- Foster community based participation in our work.
- Uphold the values outlined in the Manifesto.
The Team
Craig Cook
Front End Web Developer
San Francisco: UTC -7
IRC: craigcook
Alex Gibson
Front End Web Developer
UK: UTC +1
IRC: agibson
Giorgos Logiotatidis
Web Developer
Greece: UTC +1
IRC: giorgos
Paul McLanahan
Senior Web Developer
USA Atlanta: UTC -4
IRC: pmac
Josh Mize
Senior Web Developer
USA Tulsa: UTC -5
IRC: jgmize
Schalk Neethling
Front End Web Developer
South Africa: UTC +2
IRC: espressive
Benjamin Sternthal
Web Development Manager
USA Portland: UTC -7
IRC: bensternthal
Long Term Strategic Contractors
Equal Parts Creative
Silver Orange
How We Measure Success
- We are a service team. Most of our goals are inherited from other team's goals.
- Example: PMM wants to increase Android downloads 5.6% -- We implement a page in support of that goal.
- Internally we focus on:
- Getting projects built and out the door.
- Providing innovative technical solutions and serving as technical advisors.
- Performance of our code and systems.
- Enabling participation from the community on our projects.
- Evolving our process.
What We Do
- Websites (mozilla.org, mobilepartners.mozilla.org).
- Services (basket, snippets).
- Support / Maintenance / Feature Development for the above.
affiliates.mozilla.org
basket.mozilla.com
careers.mozilla.org
firefoxflicks.mozilla.org
masterfirefoxos.mozilla.org
mobilepartners.mozilla.org
mozilla.org
mozillalabs.com
mozillians.org
reps.mozilla.org
shapeoftheweb.com
snippets.mozilla.com
webwewant.mozilla.org
How We Do It – Key Processes
- Mostly Kanban With Waterfall-ish Mixed In For Fixed Deadline / Launch Projects
- Perhaps you should read my blog post.
- Creative Process (We Work With These Folks A Lot):
- Currently: PSD -> Revision -> PSD -> Code -> Done
- Goal to move towards prototype based iterations.
Key Tools
Clearly.io - whose on what?
Bugzilla - what are we doing?
Kanbanery - when are we doing it?
Github - code, all public all the time (mostly)
Read The Docs - documentation
wiki.mozilla.org - documentation
New Relic - health of applications & performance monitoring
Travis & Jenkins - continuous integration
Google Analytics - traffic
IRC - communication, bots!
Our Stack
- Infra – Currently WebOps, Mozilla Hosted
- Infra – Moving Towards Docker, Deis, Heroku and AWS
- Perhaps you should read our roadmap.
-
Code:
Front End – The Usual JS, HTML, CSS
Back End – Python and Django
Node – automation, minification, testing, glue
How We Deploy - Example Bedrock
How We Deploy - Future
- 12 Factoring Our Apps http://12factor.net/
- Continous Delivery – Once merged to master magic happens.
- Already working on masterfirefoxos!
Teams We Rely On
WebOps
UX
Program & Project Managers
L10N
WebQA
Creative
Growth Team
The Internal Mozilla WebDev Community
Contributors
Q1 Highlights
| Product | Initiative |
|---|---|
| Firefox |
Spring Campaign
Family Page & Navigation Hello / What's New / First Run FF Android What's New |
| Firefox OS |
Masterfirefox - Launch and proof of concept for Docker and Deis.
MWC Support & Firefox OS Page MobilePartners - Ongoing Support |
| Mozilla |
Smart On
Shape Of The Web Snippet Sec Audit / New Features / Ongoing Support |
Q1 Highlights (Continued)
| Product | Initiative |
|---|---|
| Internal |
Deis / Docker Proof Of Concept Site Launched
Discussions Across Moz WebDev On AWS Migration/Hosting Development of first technical roadmap for team. Bedrock (mozilla.org) downtime sparked discussions about WebOps resources and roles. |
Q1 Takeaways
- Spring campaign plan was not in sync with the reality of FF product development.
- L10N - we are stressing that community.
- WebDev across Org in flux - Teams developing multiple solutions.
- WebOps challenged, high turnover, resource constrained.
- Shape of The Web - much stricter guidance and oversight needed when working with 3rd parties.
- Engagement engineering benefits from prioritizing engineering goals alongside marketing goals.
Q2 Overview
| Product | Initiative |
|---|---|
| Firefox |
Spring Campaign Launch and Followup
Everything From Jenn Bertsch's Slides (iOS, Content Redesign) Support Growth Team Tactics & Implementation |
| Firefox OS | None at this time. |
| Mozilla |
Shape Of The Web Support / Long Term Plan
Support Smart On Series Development Pay Down Technical Debt - Mozilla.org. |
| Internal |
Finalize Infra plan and begin rollout with IT and Cloud Services.
Provide expertise for CRM and Snippet projects. Prototyping process with creative outlined. Plan for PHX1 Exit (this could be big). Roll Out Front End Testing Framework. Firefox Affiliates Shutdown Plan & Tasks |