Mozilla needs your help learning more about your experience as a contributor! Please take the volunteer survey to help set guidance for future projects (No Thanks).

This is a test installation, if you're filing a real bug, please go here. Notification email sending is disabled here. Current database is a snapshot of production from September 13, 2011.


Please use this form for submitting a Mozilla Project Review If you have a bug to file, go here.

(* = Required Field)

Initial Questions
Project/Feature Name:
Tracking Bug ID:
Master tracking bug number (if it exists)?
Points of Contact:
Who are the points of contact for this review?
Description:
Please provide a short description of the feature / application / project / business relationship (e.g. problem solved, use cases, etc.)
Additional Information:
Please provide links to additional information (e.g. feature page, wiki) if available and not yet included in feature description.)
Urgency:
What is the urgency of this project?
Key Initiative:
Which key initiative does this support?
 
Release Date:
What is your key release / launch date (if applicable)?
Previous Month (December 2012) January 2013 Next Month (February 2013)
Su Mo Tu We Th Fr Sa
30 31 1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31 1 2
3 4 5 6 7 8 9
Project Status:
What is the current state of your project?
Mozilla Data:
Does this product/service/project access, interact with, or store Mozilla (customer, contributor, user, employee) data? Example of such data includes email addresses, first and last name, addresses, phone numbers, credit card data.)
New or Change:
Is this a NEW product, service, project, feature, or functionality, a change to an EXISTING one, or neither?
Mozilla Project:
What product/service/project does this pertain to?
Separate Party:
Does this project involve a relationship with another party (such as a third party vendor, hosted service provider, consultant or strategic partner)? This includes MSAs, Consulting Agreements, NDAs, click to accept, API agreements, open source licenses, renewals, additional services or goods, and any other agreements.
Type of Relationship:
What type of relationship?
Data Access:
Will the other party have access to Mozilla (customer, contributor, user, employee) data? (If this is for an NDA, choose no)
Privacy Policy:
What is the url for their privacy policy?
Vendor Cost:
What is the anticipated cost of the vendor relationship? (Entire Contract Cost, not monthly cost)
PO Needed?:
Security Review
Affects Products:
Does this feature or code change affect Firefox, Thunderbird or any product or service the Mozilla ships to end users?
Review Due Date:
When would you like the review to be completed? (more info)
Previous Month (December 2012) January 2013 Next Month (February 2013)
Su Mo Tu We Th Fr Sa
30 31 1 2 3 4 5
6 7 8 9 10 11 12
13 14 15 16 17 18 19
20 21 22 23 24 25 26
27 28 29 30 31 1 2
3 4 5 6 7 8 9
Review Invitees:
Whom should be invited to the review?
Extra Information:
If you feel something is missing here or you would like to provide other kind of feedback, feel free to do so here?
Privacy (Policy/Project)
Privacy Policy:
Do you currently have a privacy policy for your project / site / product?
User Data:
Does your product/service/project collect, use or maintain any user data?
Data Safety Bug ID:
Please provide link to Data Safety bug
Privacy (Policy/Vendor)
Privacy Policy:
Will the vendor have access to Mozilla (customer, contributor, user, employee) data?
Privacy Questionnaire:
Has vendor completed Mozilla Vendor Privacy Questionnaire?
Finance
Vendor:
Is this line item in budget?:
Not In Budget Why: Please include additional description for this out of budget line item
What is the purchase for?:
Why is the purchase needed?:
What is the risk
if not purchased?:
What is the alternative?:
When do the items need
to be ordered by?:
Total Cost:
Data Safety
User Data:
Does your project collect data from users?
How many involved?:
How many users are currently involved?
How many antcipated?:
How many users do you anticipate to be involved?
Type of Data:
Please provide examples of the types of user data you collect.
Data Reason:
Why do you need to collect user data?
Community Benefit:
What community benefits are derived from the collection of user data for your project?
Data Collection:
How is the data being collected? (e.g., forms on web site, provided directly by user, observed data collection, etc.) (Consider that you may be collecting data unintentionally such as automatic logging by web servers)
Data Retention:
Will your project / team members need to retain user data?
Data Retention Length:
If the data is being retained, for how long?
Separate Party:
Will any user data be shared or accessed by third party partners, customers or providers?
Separate Party Data Type:
What is the data being shared or accessed?
Separate Party
Data Communication:
How would the data be communicated / transferred to the third parties?
Who are the separate parties?:
Who are the third party vendors and in what countries are they based?
Community Visibility and Input:
Has your proposal been shared publicly, including requirements for Mozilla to collect and host user data?
Communication Channels:
What communication channels are you using and what kind of input have you received thus far?
Public Communication Plan:
Data Safety discussion needed. Provide your plan for publicly sharing your proposal.

Thanks for contacting us. You will be notified by email of any progress made in resolving your request.