Websites/Affiliates: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 27: Line 27:
* [[Websites/Affiliates/Newsletter|Affiliates Newsletter]]
* [[Websites/Affiliates/Newsletter|Affiliates Newsletter]]
* [[Websites/Affiliates/Future Goals|Future Goals / Wish List]] -- features identified during initial build-out as desirable but not in scope.
* [[Websites/Affiliates/Future Goals|Future Goals / Wish List]] -- features identified during initial build-out as desirable but not in scope.
=== Bugs ===
* [https://bugzilla.mozilla.org/show_bug.cgi?id=945867 2014 redesign tracker]


== Resources ==
== Resources ==

Revision as of 23:56, 3 December 2013

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

Overview

Elevator Pitch

The affiliate program website is 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.
  • Statistics (Updated regularly)

Maintenance/enhancement projects

Planning

Specifications/Requests

Bugs

Resources

  • Code: Python / Playdoh(Django)
  • Product Owner: Chelsea Novak
  • TPM: Justin Crawford
  • Dev Team: Michael Kelly, Josh Mize
  • 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 - Justin Crawford
  • Developers - Mike Kelly, Josh Mize
  • L10N - Matjaž Horvat
  • Designer - Lee Tom
  • UX: TBD
  • IT - TBD
  • QA - Rebecca Billings and Matt Brandt
  • Security - TBD

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