Websites/Affiliates: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 67: Line 67:
= Meetings =
= Meetings =


* [[Websites/Affiliates/Meetings/2012|2012]]
* [[Websites/Affiliates/Meetings/2011|2011]]
* [[Websites/Affiliates/Meetings/2011|2011]]
* [[Websites/Affiliates/Meetings/2012-01-05|2012-01-05 Project Update]]
* [[Websites/Affiliates/Meetings/2012-01-12|2012-01-12 Project Update]]
* [[Websites/Affiliates/Meetings/2012-01-19|2012-01-19 Project Update]]
* [[Websites/Affiliates/Meetings/2012-02-03|2012-02-03 Project Update]]
* [[Websites/Affiliates/Meetings/2012-02-23|2012-02-23 Project Update]]

Revision as of 18:31, 23 February 2012

This page contains all of the important details for Affiliates website.

Overview

Elevator Pitch

The affiliate program website will become the main repository for banners and links that help spread the use of Mozilla's Firefox browser.

Goals and Measurements

  • Allowing the website to include localization for its content.
  • Easing the process of editing, and deleting the website's content, as well as adding new content.
  • Implementing means to communicate to affiliates, the news and updates of the available banners and links.
  • Future Goals / Wish List -- features out of scope for the current project.
  • Statistics (Updated regularly)

Planning

Resources

  • Code: Python / Playdoh(Django)
  • Product Owner: Chelsea Novak
  • TPM: Chris More
  • Dev Team: Flux; Michael Kelly
  • IRC Channel: #affiliates on irc.mozilla.org

Information

Team

The primary and secondary contacts for each role of this project:

  • Product owner - Chelsea Novak
  • TPM - Chris More
  • Developers - Mike Kelly
  • L10N - Milos Dinic and Stas Malolepszy
  • Designer - Ty Flanagan
  • UX: Crystal Beasley
  • IT - Corey Shields
  • QA - Rajeev Bharshetty, Matt Brandt
  • Security - Yvan Boily and Michael Coates

Updates

Release Process

Development happens on the develop branch, which is synced to affiliates-dev every 15 minutes.

Releases typically happen once a week. develop is merged to master on Monday, and pushed to stage. The code is pushed to production Wednesday morning (usually 11AM PST) unless an issue is found. Depending on the issue, a release may be delayed until the following week.

Meetings