MozillaWiki - User contributions [en]

ParticipationSystems

2016-06-03T19:47:44Z

DavidA: /* Access for non-staff mozillians to documents and collaborative tools, Mozilla identity */

{{draft}}
== Vision ==

This program’s purpose is to align the software and IT systems that we use to match our aspiration for being a great participatory organization, welcoming to staff, volunteers and allied communities alike. We want work at Mozilla to, in general, not care whether you’re an employee or not. Our software tools need to move to match that vision, and encourage (responsible) openness.

== Current Challenges ==

We have a legacy to clean up: the systems we use at Mozilla are too messy and complicated -- this makes us less engaging and less able to strategically work across employee-volunteer-community boundaries.

Our leadership is unified in wanting Mozilla to be truly open to volunteer participation, but the organization and its “operating system” needs some tweaks. We have walls that need to be taken down, and some new systems that need to get built.

== Identified pain points ==

# The most frequent information and collaboration systems need to be accessible at least to NDA’ed volunteers (specifically, google documents/slides/etc and content that is in Mana)
# We don’t have an identity system for volunteers, while we know that identity can unlock access and collaboration. This is complex given the broader need for an identity strategy for staff that is happening in parallel.
# We have a set of useful components such as Mozillians, LDAP, etc, but they’re not yet integrated.
# Volunteers who want to manage their contributions and touch-points with Mozilla have to interact with many different of systems and processes that are inconsistent and don't relate or speak to one another. This also makes it hard for them to find/understand opportunities for participation that exist.
# We have no understanding of volunteer involvement in different areas (advocacy, coding, SuMo, innovation), and limited/fragmented tools and limited systems that allow us to manage our relationship with volunteers and help them be effective.

== How do we plan to provide change ==

# Generate Momentum/Create Demand
#* Close collaboration with groups that want to work together, on “low hanging” or urgent projects.
#* When: In progress w/ IT, MoFo, Participation, CD, identifying other key parties.
# Scale to “new” areas
#* Build on infrastructure to facilitate new pan-Mozilla projects #* that leverage participation.
#* When: by EOY, ongoing
# Replace legacy systems
#* Identifying legacy systems for participation and migrating them.
#* When: TBD

== Program goals ==
# Evolve collaboration systems
# Design and implement contributor management systems
# Evolve contributor compute infrastructure
# Enable Mozilla identity (non-LDAP)

== Who is the team ==
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
|rowspan="3" style="height:100px; text-align:center;" |George Roter
Sean Rich
|rowspan="3" style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |'''Product/Program Management'''
Hermina Condei

Lyre Calliope

Arielle Kilroy
|rowspan="3" style="height:100px; text-align:center;" |Simon Wex
REPS Council
|rowspan="3" style="height:100px; text-align:center;" |Katharina Borchert - CIO
Sylvie Veilleux - VP IT

Mark Surman - MoFo ED

Mitchell Baker - Executive Chair

|-
| style="height:100px; text-align:center;" |'''Engineering - Participation'''
Pierros Papadeas

John Giannelos (Nemo)

Tasos Katsoulas

Nikos Roussos
|-
| style="height:100px; text-align:center;" |'''Engineering IT'''
Corey Shields
Team to TBC
|}

Communication channels
* IRC channel: [irc://irc.mozilla.org/%23participationsystems #participationsystems] ([http://chat.mibbit.com/?channel=%23participationsystems&server=irc.mozilla.org Mibbit])
* Forum: [https://discourse.mozilla-community.org/c/participationsystems Participation Systems Discourse Category]

* Team Vidyo room: (to be created)

== Projects ==

=== Contributor compute infrastructure plan ===
Subproject: Community website migration

'''Project Wiki page'''

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Pierros Papadeas
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Tanner Filip
John Giannelos (Nemo)

Yousef Alam
| style="height:100px; text-align:center;" |Corey Shields
| style="height:100px; text-align:center;" |David Ascher
|}

=== Participation Metrics - org-level dashboards and data ===
[[ParticipationSystems/Particiption_Metrics|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
[https://mozillians.org/en-US/u/couci/ Konstantina Papadea]

[https://mozillians.org/en-US/u/pierros/ Pierros Papadeas]
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/lucyeoh/ Lucy Harris]
[https://mozillians.org/en-US/u/nukeador/ Ruben Martin]
| style="height:100px; text-align:center;" |Adam Lofting
John Jensen

Rosana Ardila

David Ascher

REPS Council
| style="height:100px; text-align:center;" |Mitchell Baker
Mark Surman

Katharina Borchert
|}

=== Access for non-staff mozillians to documents and collaborative tools, Mozilla identity ===
[[ParticipationSystems/Volunteer Identity and Document Access|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |David Ascher
Pierros Papadeas

IT TBD
| style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |Hermina Condei
Josh Howard (IT)
| style="height:100px; text-align:center;" |Ryan Kelly (FxA)
Jeff Bryner (IT)

Josh Howard (IT)
| style="height:100px; text-align:center;" |George Roter

|}

=== Volunteer Management Systems ===
'''Project Wiki page'''

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |REPS Council
MoFO
| style="height:100px; text-align:center;" |David Ascher
|}

=== Reps Portal ===
[[ParticipationSystems/RepsPortal|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Nemo
Tasos

Youseff

Simon Wex

Sean Rich

More TBD
| style="height:100px; text-align:center;" |Pierros
George

Rosana

Ruben

Konstantina

Guillermo

Hannah Kane

Lucy Harris
| style="height:100px; text-align:center;" |David Ascher

|}

=== Discourse Evolution ===
[[ParticipationSystems/discourse_evolution|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Lyre Calliope
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |Community Ops
REPS Council
| style="height:100px; text-align:center;" |David Ascher
|}

ParticipationSystems/Volunteer Identity and Document Access

2016-06-03T19:47:39Z

DavidA:

= 🌍 Project Information =
== 📎 Summary ==

We want to make it possible for anyone regardless of employment status to be able to contribute to the work of Mozilla. Sometimes that is
accomplished by doing work in the public sphere, but sometimes that can also mean welcoming trusted volunteers into collaboration and
communication spaces where we discuss or prototype things before they're ready for the harsh light of day.

In order to do this, we need to both understand the collaboration and communication tools that we think Mozillians should use, and then
build an architecture and approach to this work that is welcoming of non-staff Mozillians.

This is a complicated topic that touches on very thorny issues, from security and identity infrastructure to tooling choices and
process and cultural norms.

A this point, there are two different timelines of work being done:

# understanding our long term vision and roadmap, especially to inform the roadmap of Mozilla's Identity and Access Management approach
# understanding the near term opportunities to alleviate day-to-day pain.

A few things have become clear:

# It is problematic from an architectural and implementation point of view that we don't have a consistent way of logging into websites (ours and others) which integrates with our systems to understand permissions.
# It is problematic that our volunteer management databases (mozillians.org, reps portal) are so disconnected from our staff management databases (workday) and LDAP infrastructure
# We have a lot of disconnected pieces of technology and data that need closer coupling

Furthermore, it has become clear that short term fixes for day-to-day pain has the likelihood of causing long term challenges.

The current status is that the team is fleshing out some scenarios which can let us understand what rational options are with respect to near term and longer term plans. There is emerging consensus that one of the near term wins would be to bring the Mozillians database in closer coordination w/ the LDAP system for example.

This project is part of the larger [[ParticipationSystems|Participation Systems]] initiative.

= 👥 Get Involved =

This is a joint effort between MoFo, the Participation team and the IT team. Please get in touch with [https://mozillians.org/en-US/u/davidascher/ David Ascher] if you're interested or have suggestions.

Additionally, you can connect with us through Participation Systems communications channels:
* IRC channel: [irc://irc.mozilla.org/%23participationsystems #participationsystems] ([http://chat.mibbit.com/?channel=%23participationsystems&server=irc.mozilla.org Mibbit])
* Forum: [https://discourse.mozilla-community.org/c/participationsystems Participation Systems Discourse Category]

= 📝 Project Management =

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |David Ascher
Pierros Papadeas

IT TBD
| style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |Hermina Condei
Josh Howard (IT)
| style="height:100px; text-align:center;" |Ryan Kelly (FxA)
Jeff Bryner (IT)

Josh Howard (IT)
| style="height:100px; text-align:center;" |George Roter

|}

ParticipationSystems/Volunteer Identity and Document Access

2016-06-03T19:47:20Z

DavidA: Created page with "= 🌍 Project Information = == 📎 Summary == We want to make it possible for anyone regardless of employment status to be able to contribute to the work of Mozilla. Some..."

= 🌍 Project Information =
== 📎 Summary ==

We want to make it possible for anyone regardless of employment status to be able to contribute to the work of Mozilla. Sometimes that is
accomplished by doing work in the public sphere, but sometimes that can also mean welcoming trusted volunteers into collaboration and
communication spaces where we discuss or prototype things before they're ready for the harsh light of day.

In order to do this, we need to both understand the collaboration and communication tools that we think Mozillians should use, and then
build an architecture and approach to this work that is welcoming of non-staff Mozillians.

This is a complicated topic that touches on very thorny issues, from security and identity infrastructure to tooling choices and
process and cultural norms.

A this point, there are two different timelines of work being done:

# understanding our long term vision and roadmap, especially to inform the roadmap of Mozilla's Identity and Access Management approach
# understanding the near term opportunities to alleviate day-to-day pain.

A few things have become clear:

# It is problematic from an architectural and implementation point of view that we don't have a consistent way of logging into websites (ours and others) which integrates with our systems to understand permissions.
# It is problematic that our volunteer management databases (mozillians.org, reps portal) are so disconnected from our staff management databases (workday) and LDAP infrastructure
# We have a lot of disconnected pieces of technology and data that need closer coupling

Furthermore, it has become clear that short term fixes for day-to-day pain has the likelihood of causing long term challenges.

The current status is that the team is fleshing out some scenarios which can let us understand what rational options are with respect to near term and longer term plans. There is emerging consensus that one of the near term wins would be to bring the Mozillians database in closer coordination w/ the LDAP system for example.

This project is part of the larger [[ParticipationSystems|Participation Systems]] initiative.

= 👥 Get Involved =

This is a joint effort between MoFo, the Participation team and the IT team. Please get in touch with [https://mozillians.org/en-US/u/davidascher/ David Ascher] if you're interested or have suggestions.

Additionally, you can connect with us through Participation Systems communications channels:
* IRC channel: [irc://irc.mozilla.org/%23participationsystems #participationsystems] ([http://chat.mibbit.com/?channel=%23participationsystems&server=irc.mozilla.org Mibbit])
* Forum: [https://discourse.mozilla-community.org/c/participationsystems Participation Systems Discourse Category]

= 📝 Project Management =

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |David Ascher
Pierros Papadeas

IT TBD
| style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |Hermina Condei
Josh Howard (IT)
| style="height:100px; text-align:center;" |Ryan Keylly (FxA)
Jeff Bryner (IT)

Josh Howard (IT)
| style="height:100px; text-align:center;" |George Roter

|}

ParticipationSystems

2016-06-03T19:33:28Z

DavidA: /* Access for non-staff mozillians to documents and collaborative tools, Mozilla identity */

{{draft}}
== Vision ==

This program’s purpose is to align the software and IT systems that we use to match our aspiration for being a great participatory organization, welcoming to staff, volunteers and allied communities alike. We want work at Mozilla to, in general, not care whether you’re an employee or not. Our software tools need to move to match that vision, and encourage (responsible) openness.

== Current Challenges ==

We have a legacy to clean up: the systems we use at Mozilla are too messy and complicated -- this makes us less engaging and less able to strategically work across employee-volunteer-community boundaries.

Our leadership is unified in wanting Mozilla to be truly open to volunteer participation, but the organization and its “operating system” needs some tweaks. We have walls that need to be taken down, and some new systems that need to get built.

== Identified pain points ==

# The most frequent information and collaboration systems need to be accessible at least to NDA’ed volunteers (specifically, google documents/slides/etc and content that is in Mana)
# We don’t have an identity system for volunteers, while we know that identity can unlock access and collaboration. This is complex given the broader need for an identity strategy for staff that is happening in parallel.
# We have a set of useful components such as Mozillians, LDAP, etc, but they’re not yet integrated.
# Volunteers who want to manage their contributions and touch-points with Mozilla have to interact with many different of systems and processes that are inconsistent and don't relate or speak to one another. This also makes it hard for them to find/understand opportunities for participation that exist.
# We have no understanding of volunteer involvement in different areas (advocacy, coding, SuMo, innovation), and limited/fragmented tools and limited systems that allow us to manage our relationship with volunteers and help them be effective.

== How do we plan to provide change ==

# Generate Momentum/Create Demand
#* Close collaboration with groups that want to work together, on “low hanging” or urgent projects.
#* When: In progress w/ IT, MoFo, Participation, CD, identifying other key parties.
# Scale to “new” areas
#* Build on infrastructure to facilitate new pan-Mozilla projects #* that leverage participation.
#* When: by EOY, ongoing
# Replace legacy systems
#* Identifying legacy systems for participation and migrating them.
#* When: TBD

== Program goals ==
# Evolve collaboration systems
# Design and implement contributor management systems
# Evolve contributor compute infrastructure
# Enable Mozilla identity (non-LDAP)

== Who is the team ==
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
|rowspan="3" style="height:100px; text-align:center;" |George Roter
Sean Rich
|rowspan="3" style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |'''Product/Program Management'''
Hermina Condei

Lyre Calliope

Arielle Kilroy
|rowspan="3" style="height:100px; text-align:center;" |Simon Wex
REPS Council
|rowspan="3" style="height:100px; text-align:center;" |Katharina Borchert - CIO
Sylvie Veilleux - VP IT

Mark Surman - MoFo ED

Mitchell Baker - Executive Chair

|-
| style="height:100px; text-align:center;" |'''Engineering - Participation'''
Pierros Papadeas

John Giannelos (Nemo)

Tasos Katsoulas

Nikos Roussos
|-
| style="height:100px; text-align:center;" |'''Engineering IT'''
Corey Shields
Team to TBC
|}

Communication channels
* IRC channel: [irc://irc.mozilla.org/%23participationsystems #participationsystems] ([http://chat.mibbit.com/?channel=%23participationsystems&server=irc.mozilla.org Mibbit])
* Forum: [https://discourse.mozilla-community.org/c/participationsystems Participation Systems Discourse Category]

* Team Vidyo room: (to be created)

== Projects ==

=== Contributor compute infrastructure plan ===
Subproject: Community website migration

'''Project Wiki page'''

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Pierros Papadeas
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Tanner Filip
John Giannelos (Nemo)

Yousef Alam
| style="height:100px; text-align:center;" |Corey Shields
| style="height:100px; text-align:center;" |David Ascher
|}

=== Participation Metrics - org-level dashboards and data ===
[[ParticipationSystems/Particiption_Metrics|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
[https://mozillians.org/en-US/u/couci/ Konstantina Papadea]

[https://mozillians.org/en-US/u/pierros/ Pierros Papadeas]
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/lucyeoh/ Lucy Harris]
[https://mozillians.org/en-US/u/nukeador/ Ruben Martin]
| style="height:100px; text-align:center;" |Adam Lofting
John Jensen

Rosana Ardila

David Ascher

REPS Council
| style="height:100px; text-align:center;" |Mitchell Baker
Mark Surman

Katharina Borchert
|}

=== Access for non-staff mozillians to documents and collaborative tools, Mozilla identity ===
[[ParticipationSystems/Volunteer Identity and Document Access|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |David Ascher
Pierros Papadeas

IT TBD
| style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |Hermina Condei
Josh Howard (IT)
| style="height:100px; text-align:center;" |Ryan Keylly (FxA)
Jeff Bryner (IT)

Josh Howard (IT)
| style="height:100px; text-align:center;" |George Roter

|}

=== Volunteer Management Systems ===
'''Project Wiki page'''

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |REPS Council
MoFO
| style="height:100px; text-align:center;" |David Ascher
|}

=== Reps Portal ===
[[ParticipationSystems/RepsPortal|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Nemo
Tasos

Youseff

Simon Wex

Sean Rich

More TBD
| style="height:100px; text-align:center;" |Pierros
George

Rosana

Ruben

Konstantina

Guillermo

Hannah Kane

Lucy Harris
| style="height:100px; text-align:center;" |David Ascher

|}

=== Discourse Evolution ===
[[ParticipationSystems/discourse_evolution|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Lyre Calliope
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |Community Ops
REPS Council
| style="height:100px; text-align:center;" |David Ascher
|}

ParticipationSystems

2016-06-03T19:32:33Z

DavidA: /* Access for non-staff mozillians to documents and collaborative tools, Mozilla identity */

{{draft}}
== Vision ==

This program’s purpose is to align the software and IT systems that we use to match our aspiration for being a great participatory organization, welcoming to staff, volunteers and allied communities alike. We want work at Mozilla to, in general, not care whether you’re an employee or not. Our software tools need to move to match that vision, and encourage (responsible) openness.

== Current Challenges ==

We have a legacy to clean up: the systems we use at Mozilla are too messy and complicated -- this makes us less engaging and less able to strategically work across employee-volunteer-community boundaries.

Our leadership is unified in wanting Mozilla to be truly open to volunteer participation, but the organization and its “operating system” needs some tweaks. We have walls that need to be taken down, and some new systems that need to get built.

== Identified pain points ==

# The most frequent information and collaboration systems need to be accessible at least to NDA’ed volunteers (specifically, google documents/slides/etc and content that is in Mana)
# We don’t have an identity system for volunteers, while we know that identity can unlock access and collaboration. This is complex given the broader need for an identity strategy for staff that is happening in parallel.
# We have a set of useful components such as Mozillians, LDAP, etc, but they’re not yet integrated.
# Volunteers who want to manage their contributions and touch-points with Mozilla have to interact with many different of systems and processes that are inconsistent and don't relate or speak to one another. This also makes it hard for them to find/understand opportunities for participation that exist.
# We have no understanding of volunteer involvement in different areas (advocacy, coding, SuMo, innovation), and limited/fragmented tools and limited systems that allow us to manage our relationship with volunteers and help them be effective.

== How do we plan to provide change ==

# Generate Momentum/Create Demand
#* Close collaboration with groups that want to work together, on “low hanging” or urgent projects.
#* When: In progress w/ IT, MoFo, Participation, CD, identifying other key parties.
# Scale to “new” areas
#* Build on infrastructure to facilitate new pan-Mozilla projects #* that leverage participation.
#* When: by EOY, ongoing
# Replace legacy systems
#* Identifying legacy systems for participation and migrating them.
#* When: TBD

== Program goals ==
# Evolve collaboration systems
# Design and implement contributor management systems
# Evolve contributor compute infrastructure
# Enable Mozilla identity (non-LDAP)

== Who is the team ==
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
|rowspan="3" style="height:100px; text-align:center;" |George Roter
Sean Rich
|rowspan="3" style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |'''Product/Program Management'''
Hermina Condei

Lyre Calliope

Arielle Kilroy
|rowspan="3" style="height:100px; text-align:center;" |Simon Wex
REPS Council
|rowspan="3" style="height:100px; text-align:center;" |Katharina Borchert - CIO
Sylvie Veilleux - VP IT

Mark Surman - MoFo ED

Mitchell Baker - Executive Chair

|-
| style="height:100px; text-align:center;" |'''Engineering - Participation'''
Pierros Papadeas

John Giannelos (Nemo)

Tasos Katsoulas

Nikos Roussos
|-
| style="height:100px; text-align:center;" |'''Engineering IT'''
Corey Shields
Team to TBC
|}

Communication channels
* IRC channel: [irc://irc.mozilla.org/%23participationsystems #participationsystems] ([http://chat.mibbit.com/?channel=%23participationsystems&server=irc.mozilla.org Mibbit])
* Forum: [https://discourse.mozilla-community.org/c/participationsystems Participation Systems Discourse Category]

* Team Vidyo room: (to be created)

== Projects ==

=== Contributor compute infrastructure plan ===
Subproject: Community website migration

'''Project Wiki page'''

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Pierros Papadeas
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Tanner Filip
John Giannelos (Nemo)

Yousef Alam
| style="height:100px; text-align:center;" |Corey Shields
| style="height:100px; text-align:center;" |David Ascher
|}

=== Participation Metrics - org-level dashboards and data ===
[[ParticipationSystems/Particiption_Metrics|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
[https://mozillians.org/en-US/u/couci/ Konstantina Papadea]

[https://mozillians.org/en-US/u/pierros/ Pierros Papadeas]
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/geroter/ George Roter]
| style="height:100px; text-align:center;" |[https://mozillians.org/en-US/u/lucyeoh/ Lucy Harris]
[https://mozillians.org/en-US/u/nukeador/ Ruben Martin]
| style="height:100px; text-align:center;" |Adam Lofting
John Jensen

Rosana Ardila

David Ascher

REPS Council
| style="height:100px; text-align:center;" |Mitchell Baker
Mark Surman

Katharina Borchert
|}

=== Access for non-staff mozillians to documents and collaborative tools, Mozilla identity ===
[[ParticipationSystems/VolunteerIdentity|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |David Ascher
Pierros Papadeas

IT TBD
| style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |Hermina Condei
Josh Howard (IT)
| style="height:100px; text-align:center;" |Ryan Keylly (FxA)
Jeff Bryner (IT)

Josh Howard (IT)
| style="height:100px; text-align:center;" |George Roter

|}

=== Volunteer Management Systems ===
'''Project Wiki page'''

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |REPS Council
MoFO
| style="height:100px; text-align:center;" |David Ascher
|}

=== Reps Portal ===
[[ParticipationSystems/RepsPortal|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Nemo
Tasos

Youseff

Simon Wex

Sean Rich

More TBD
| style="height:100px; text-align:center;" |Pierros
George

Rosana

Ruben

Konstantina

Guillermo

Hannah Kane

Lucy Harris
| style="height:100px; text-align:center;" |David Ascher

|}

=== Discourse Evolution ===
[[ParticipationSystems/discourse_evolution|'''Project Wiki page''']]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Lyre Calliope
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |Community Ops
REPS Council
| style="height:100px; text-align:center;" |David Ascher
|}

ParticipationSystems

2016-05-26T20:04:31Z

DavidA: Copy edit after discussion w/ george

{{draft}}
== Vision ==

This program’s purpose is to align the software and IT systems that we use to match our aspiration for being a great participatory organization, welcoming to staff, volunteers and allied communities alike. We want work at Mozilla to, in general, not care whether you’re an employee or not. Our software tools need to move to match that vision, and encourage (responsible) openness.

== Current Challenges ==

We have a legacy to clean up: the systems we use at Mozilla are too messy and complicated -- this makes us less engaging and less able to strategically work across employee-volunteer-community boundaries.

Our leadership is unified in wanting Mozilla to be truly open to volunteer participation, but the organization and its “operating system” needs some tweaks. We have walls that need to be taken down, and some new systems that need to get built.

== Identified pain points ==

# The most frequent information and collaboration systems need to be accessible at least to NDA’ed volunteers (specifically, google documents/slides/etc and content that is in Mana)
# We don’t have an identity system for volunteers, while we know that identity can unlock access and collaboration. This is complex given the broader need for an identity strategy for staff that is happening in parallel.
# We have a set of useful components such as Mozillians, LDAP, etc, but they’re not yet integrated.
# Volunteers who want to manage their contributions and touch-points with Mozilla have to interact with many different of systems and processes that are inconsistent and don't relate or speak to one another. This also makes it hard for them to find/understand opportunities for participation that exist.
# We have no understanding of volunteer involvement in different areas (advocacy, coding, SuMo, innovation), and limited/fragmented tools and limited systems that allow us to manage our relationship with volunteers and help them be effective.

== How do we plan to provide change ==

# Generate Momentum/Create Demand
#* Close collaboration with groups that want to work together, on “low hanging” or urgent projects.
#* When: In progress w/ IT, MoFo, Participation, CD, identifying other key parties.
# Scale to “new” areas
#* Build on infrastructure to facilitate new pan-Mozilla projects #* that leverage participation.
#* When: by EOY, ongoing
# Replace legacy systems
#* Identifying legacy systems for participation and migrating them.
#* When: TBD

== Program goals ==
# Evolve collaboration systems
# Design and implement contributor management systems
# Evolve contributor compute infrastructure
# Enable Mozilla identity (non-LDAP)

== Who is the team ==
{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
|rowspan="3" style="height:100px; text-align:center;" |George Roter
Sean Rich
|rowspan="3" style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |'''Product/Program Management'''
Hermina Condei

Lyre Calliope

Arielle Kilroy
|rowspan="3" style="height:100px; text-align:center;" |Simon Wex
REPS Council
|rowspan="3" style="height:100px; text-align:center;" |Katharina Borchert - CIO
Sylvie Veilleux - VP IT

Mark Surman - MoFo ED

Mitchell Baker - Executive Chair

|-
| style="height:100px; text-align:center;" |'''Engineering - Participation'''
Pierros Papadeas

John Giannelos (Nemo)

Tasos Katsoulas

Nikos Roussos
|-
| style="height:100px; text-align:center;" |'''Engineering IT'''
Corey Shields
Team to TBC
|}

Communication channels
Irc channel: #parsol
Team mailing list: to be created
Team vidyo room: to be created

Program docs
Participation Systems – v4

== Projects ==

=== Contributor compute infrastructure plan ===
Subproject: Community website migration

Project Wiki page

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Pierros Papadeas
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Tanner Filip
John Giannelos (Nemo)

Yousef Alam
| style="height:100px; text-align:center;" |Corey Shields
| style="height:100px; text-align:center;" |David Ascher
|}

=== Participation Metrics - org-level dashboards and data ===
Project Wiki page

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Bitergia -development
Lucy Harris

Ruben Martin

Konstantina Papadea
| style="height:100px; text-align:center;" |Adam Lofting

John Jensen

Dominik Strohmeier

Rosana Ardila
| style="height:100px; text-align:center;" |David Ascher
|}

=== Access for non-staff mozillians to documents and collaborative tools, Mozilla identity ===
Project Wiki page

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |David Ascher
Pierros Papadeas

IT TBD
| style="height:100px; text-align:center;" |David Ascher
| style="height:100px; text-align:center;" |Hermina Condei
Josh Howard (IT)
| style="height:100px; text-align:center;" |Ryan Keylly (FxA)
Jeff Bryner (IT)

Josh Howard (IT)
| style="height:100px; text-align:center;" |George Roter

|}

=== Volunteer Management Systems ===

Project Wiki Page

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Arielle Kilroy
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |REPS Council
MoFO
| style="height:100px; text-align:center;" |David Ascher
|}

=== Discourse Evolution ===
[[ParticipationSystems/discourse_evolution|Project Wiki]]

{| class="wikitable" style="width:90%;"
! scope="col"|Responsible
! scope="col"|Accountable
! scope="col"|Support
! scope="col"|Consulted
! scope="col"|Informed
|-
| style="height:100px; text-align:center;" |Lyre Calliope
| style="height:100px; text-align:center;" |George Roter
| style="height:100px; text-align:center;" |Hermina Condei
| style="height:100px; text-align:center;" |Community Ops
REPS Council
| style="height:100px; text-align:center;" |David Ascher
|}

WeeklyUpdates/2016-02-29

2016-02-29T19:06:19Z

DavidA: removing webmaker

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* http://air.mozilla.org/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==
*Congrats to [https://blog.mozilla.org/addons/2016/02/25/friend-of-add-ons-johann-hofmann/ Johann Hofmann], our newest Friend of Add-ons! Johann is the author of [https://addons.mozilla.org/firefox/addon/emoji-cheatsheet/ Emoji Cheatsheet], and has been active in contributing to WebExtensions. Thanks Johann!

* Thanks to Gabriel Micko, Mozilla Tech Speaker from the Moz Hungary community, who traveled to Minsk, Belarus a couple weekends ago, to represent Mozilla at the Rolling Scopes dev conference when one of our staffers had to cancel - gave a talk about WebRTC, demo'ed WebVR and wowed the attendees!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* [https://quality.mozilla.org/event/bug-triage-day-100/ Weekly Bug Triage Day]

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
* [[Webdev/Meetings/2016/March_1|Webdev Extravaganza]]: 10:00 AM Pacific in the Webdev Vidyo (Open to the public)
** Stream on Air Mozilla: https://air.mozilla.org/webdev-extravaganza-february-2016/
** Monthly get-together for anyone in Mozilla interested in web development. Updates on shipped projects, libraries we're working on, and more!
*10am Pacific - Add-on Bi-weekly Community Meeting: https://wiki.mozilla.org/Add-ons/Community/Meetings

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [https://quality.mozilla.org/event/bug-verification-day-106/ Weekly Bug Verification Day]

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox and Cloud Services ===
''Speaker Location:''

=== Connected Devices ===
John Bernard (London office)

Panasonic announce Firefox OS on 2016 4K Pro Ultra HD Smart TV range. Blog post out TODAY. http://news.panasonic.co.uk/pressreleases/panasonic-unveils-next-generation-of-tv-technology-with-2016-line-up-of-4k-pro-ultra-hd-tvs-1327623

Mobile World Congress (MWC) Update.

=== CTO Update ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Brett Gaylor
| Director, Open Web Fellows Program
| Update on Mozilla Foundation's encryption campaign
| Remote
| Yes
| https://goo.gl/SXHxPe
| [http://mzl.la/encrypt mzl.la/encrypt]
|-
| Bill Walker
| Senior Manager, Web App Developer Initiative (WADI)
| Update on recent web app workshop in MTV
| MTV
| No
| https://pbs.twimg.com/media/CcFE59uVAAAtC-F.jpg:large
| http://wiki.mozilla.org/Apps and https://github.com/owencm/ModernWebSummitWorkshop
|-
| Larissa Shapiro
| Senior Program Manager, Diversity and Inclusion
| Outreachy Applications now open!
| MTV
| No
| http://wiki.mozilla.org/Outreachy
|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME New Volunteer]
! [https://mozillians.org/u/USERNAME Introduced by]
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be contributing from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Justin Terry''
| ''Mary Colvig''
| ''Audio''
| ''New York''
| ''Paid Media''
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Engineering Productivity (Automation & Tools) ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Template:WeeklyUpdates

2016-02-29T19:05:36Z

DavidA: remove webmaker from template

<noinclude><div style="background: #EFE; margin: 1em; border: 1px solid #EEE; padding: 1em; font-size: 110%;">
To use this template, create a new [[WeeklyUpdates]] page (e.g. [[WeeklyUpdates/2011-07-25]]), insert the following text into the page:

<code>{{<nowiki>subst:</nowiki>WeeklyUpdates}}</code>

Save the page, then edit the text that the template has inserted into the page.
</div></noinclude>
{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* http://air.mozilla.org/ to watch and listen
* join irc.mozilla.org #airmozilla for backchannel discussion
* Presenters only: Vidyo room "Brownbags". Do '''not''' use this room if you're not planning to speak.
{{conf|8600}}
** If you plan on presenting, please join the Vidyo BrownBags 20 minutes prior to the start of the meeting and announce to the A/V Technicians that you will be speaking so that they can confirm your Audio and Video.

<noinclude>== Video for today's meeting ==

<video controls="controls"><source src="http://videos.mozilla.org/serv/air_mozilla/monday_meetings/status-{{#time:Y-m-d|{{SUBPAGENAME}}}}.ogg" type="video/ogg; codecs="theora, vorbis"" /></video>

</noinclude>__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox and Cloud Services ===
''Speaker Location:''

=== Connected Devices ===
''Speaker Location:''

=== CTO Update ===
''Speaker Location:''

=== Mozilla Communities ===
''Speaker Location:''

== Speakers ==

The limit is '''3 minutes per topic'''. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week. The meeting is streamed in a 4:3 format in order to allow for split screen. If your slides are 16:9 "widescreen" format, please indicate in the "Sharing" column below.

{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME Presenter]
! Title
! Topic
! Location
! Sharing
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, 4:3 or 16:9)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table wikitable"
|-
! [https://mozillians.org/u/USERNAME New Volunteer]
! [https://mozillians.org/u/USERNAME Introduced by]
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be contributing from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table wikitable"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table wikitable"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Cloud Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== Web QA ====

==== QA Community ====

=== Engineering Productivity (Automation & Tools) ===

=== Security ===

=== Engagement ===

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/1X5kUBkEAicEe2unDaaLGTYzAJbphWFoaJYBTasHrcHQ/edit#gid=1764494528 Engagement's Active Project Dashboard]

==== PR ====

==== Events ====

==== Social Support ====

[[Category:Weekly Updates]]
[[Category:Meeting Notes]]

Learning/impact howto

2015-08-26T19:47:36Z

DavidA: /* Baseline Impact Statements */

= How To=
 
<big>'''Impact statement''': describes the overall change we want to see in the world.
* Who is impacted?
* What is the change for them, and the world?
* One statement for 'leadership' and one for 'advocacy'.
* See baseline statements below.

'''Impact milestones''': describe specific measurable changes that are a step towards the impact statement.

* A win we can map a path to in 6-24 months
* Rolls up into one of the two main impact statements
* Each working group will have several (or many) milestones
* '''These milestones will drive options for where and when we invest resources'''

* Aim for: Memorable, measurable, motivational, manageable (4Ms)
* Aim for: 8 words or less
* Also see [https://en.wikipedia.org/wiki/SMART_criteria SMART] goals for a useful framework
</big>

=Baseline Impact Statements =

* Leadership: More people teach and advocate for the web.
* Advocacy: ''Many'' more people understand and care about the internet.
* We can and should evolve the wording, but the core goals are fixed at this point.

* Ideally, these feed each other:
** 0. We provide leadership development and advocacy platform
** 1. Result: more people teach and advocate for the web
** 2. Which ultimately results in: many more people understand and care about the internet.

=Example Impact Milestones =

* By 2016, 100k people have completed our basic online privacy training (SmartOn)
* By 2016, x% of fellowship partner organizations offer regular web literacy training for staff
* By 2017, y% of fellowship alumni continue to 'teach it forward' (in a way we can track)
* By 2017, we've seen an z% increase in public concern about key internet policy issues
* By 2018, we see a,b,c indicators that web literacy is being integrated into formal education
* Etc...

* Good impact milestones are about something that happens external to Mozilla
* Bad impact milestones just focus on our own growth, popularity or quality

MozWeek/2015 Whistler

2015-06-17T17:40:57Z

DavidA: /* Vancouver before and after */

'''What is it?''' -- multiple work weeks, happening in the same city, at the same time + some opportunity to get together as one big group as well as with other teams as it makes sense. Then, on the last day, we have a fun social event for all, Mozilla-style!

=='''Dates, Location and Weather'''==
Monday, June 22 - Friday, June 26, 2015 (travel days are Monday & Saturday*) in Whistler, British Columbia, CANADA (various venues, all within [https://www.google.com/maps/d/edit?mid=zGDglM1VcNwI.kO8bbJ9I88W0 Whistler Village]. Feel free to use/edit this [http://umap.openstreetmap.fr/en/map/mozilla-whistler-map_39985 OpenStreetMap version])

[http://www.whistler.com/pdf/maps/whistler-village-map-small.pdf Downloadable and printable map]

''*For those countries where rest time is required on weekends (vs. work travel), Mozilla will cover a return on the next available work day, if you choose.''

===Weather===
Averages temperatures range from lows of 48 Fahrenheit (9 Celsius) to 70 Fahrenheit (21 Celsius). It can/will rain and will be cool (could even snow of Friday night since the party’s at ~6,000 feet/1,850 metres). Bring layers but a ski jacket isn’t necessary.

=='''Registration'''==
This is an invite only event and registration is complete. You should have received a confirmation email. If you are unsure if you are registered, email mozilla@shworldwide.com.

=='''Booking Travel'''==
All paid staff and Elancers (MoCo only [1], exceptions below [2]) may begin booking their air travel to Vancouver (YVR) through a special [https://www.egencia.com/pub/agent.dll?qscr=mtgd&mgid=66121&gpid=4942E5086162 “meeting” section of Egencia]. The meeting section ensures we can meaningfully balance 1,000 of us to booking our own flights with a need to be mindful of budget. As such, we ask that you only book Whistler travel within this framework (instructions [https://docs.google.com/a/mozilla.com/presentation/d/1vchB3eDbLPPfW1SKUksIE575qwyGw3LrSj0M0zscaug/present#slide=id.p here]). Please complete all bookings by ''17 April 2015''.

*[1] Mozilla Foundation employees - Angela Plohman is your coordinator.
*[2] Employees from our Japan office will use a local agency and Yuka Takagi is your coordinator.

We have secured hotel rooms for everyone (please do not book hotel) - see below for Hotel & Meeting Space information.

===Air Travel Guidelines (and tips)===
Our standard travel guidelines apply (pre-populated in Egencia and [https://mana.mozilla.org/wiki/display/WPR/Travel+and+Egencia here] for reference) when booking for Whistler. Anything booked outside of them will require approval.

Everyone should plan to arrive in Vancouver, BC (YVR) on Monday, June 22. Exceptions are possible for those traveling on long distance flights that require an earlier arrival. Everyone should plan to depart from Vancouver, BC (YVR) on Saturday, June 27. '''NOTE: You will need to leave Whistler at least five hours prior to your flight. Please consider this when booking your departure.'''

If you are traveling from afar, we recommend avoiding a layover in the United States and aiming for one in Canada. This minimizes the number of visas you will need.

===Early Arrivals/Late Departures===
Provided there is no incremental cost (>$100USD) to your airfare for an earlier arrival or later departure, you are totally welcome to have at it. While we have negotiated rates with some Whistler hotels for the three days prior to and the three days following our work week, they are subject to availability (NOTE: There is a big deal event going on just prior to our work week in [https://toughmudder.com/events/2015-whistler Whistler], so it’s going to be tough to get a room no matter what. In Vancouver, matches of the [http://www.fifa.com/womensworldcup/ Women's Football (Soccer) World Cup] take place before, during and after the workweek.)

===Canadian Visas===
Check here to see if you need a visa: http://www.cic.gc.ca/english/visit/visas.asp
You can request a visa invitation letter during [https://www.signup4.net/Public/ap.aspx?EID=WHIS12E registration]. You will need to provide your passport details for the letter.

Some people are not allowed to come to Canada (known as “inadmissible” under Canada’s [http://www.cic.gc.ca/english/information/inadmissibility/conviction.asp immigration law]), check here to see if you might be "inadmissible" (you'll be turned away at the border if you are, so best to know ahead of time): http://www.cic.gc.ca/english/information/inadmissibility/index.asp and http://www.ezbordercrossing.com/the-inspection-experience/prior-criminal-offenses/crossing-canadian-border-with-a-dui/#.VThVDRfnfVp

===Not paid staff===
If you are a vendor (paid by a company other than Mozilla or Elance), contractor, or seasonal staff, your manager must confirm your participation before you will be able to book travel. We have reached out to managers for this confirmation and will let you know when you may book your travel.

'''Interns''' -- Participation will be coordinated by Misty Orr and Kyle Poffenroth.
'''Volunteers''' -- Participation will be coordinated by Brian King and George Roter. They have reached out already to each team, but if you’re unsure if your team was included, please get in touch with them. [[Coincidental work weeks/2015 Whistler/Volunteer Invites Criteria|Volunteer Invites Criteria]]
'''Partners''' -- Invitations will be considered on a case by case basis. Please send those requests to mdouglass@mozilla.com for review.

===New Hires===
We have a process to identify new hires each week and will invite them to book travel (and register) on a steady basis. No action necessary from managers other than to let them know about the event.

==''' Arriving at Vancouver International Airport '''==
;Documentation for Canadian Customs
We have informed Canadian Customs about the Whistler Work Week. It is recommended that you carry [https://drive.google.com/file/d/0BxpoaXUTHH24YnZIVTV2RTFWSzg/view?usp=sharing this letter] from Canada Border Services Agency with you while traveling and present it to any Border Customs Agent.

[[File:Canada-declaration-card.png|frame|left]]
;If you're flying from outside of Canada
:You'll be handed a [http://cbsa.gc.ca/publications/forms-formulaires/e311-eng.pdf Declaration Card](PDF) on your flight. Fill out this card out before you land:
* the purpose of your travel is "Business",
* declare any gifts, alcohol, or tobacco that you are bringing into the country,
* you do ''not'' need to declare personal baggage such as your computer, camera, and clothing as long as you're taking it with you when you leave.
:When you arrive at the airport, follow the signs for "Canada Arrivals" to Canada Customs and Immigration. Hand your Declaration Card and Passport to the officer, and explain that you are visiting for a conference in Whistler, BC. If they ask for evidence of your invitation to the conference, produce the Pocket Letter that Mozilla sent you. The officer will mark and return your card and direct you to the baggage claim. Collect your bags and exit the Customs Hall, turning in your marked Declaration Card to the officer at the doors.

;If you're flying from within Canada
:If you're coming from within Canada, simply proceed to the baggage claim from your gate once you arrive.

=='''Ground Transportation to/from YVR'''==
Ground transfers via bus from Vancouver Int’l Airport to Whistler will be provided on Monday, June 22nd and from Whistler to Vancouver Int’l Airport on Saturday, June 27th.

===Arrivals===
Airport shuttles on Monday, June 22 are scheduled based upon your flights. That means if you arrive on June 22, we have a seat for you. If you arrive prior to June 22 and have not made other arrangements or gotten specific instructions, please plan to be at the airport between 10 am and 5 pm to board a shuttle.

'''YVR Domestic Arrivals:'''
After departing the plane, please proceed to the luggage carousel area. There you will find meet and greet staff with Mozilla signage. Follow their direction and they will show you to the bus for your transfer to Whistler. Be prepared to tell the driver your hotel location so they can ensure you and your luggage make it to the appropriate location in Whistler.

'''YVR International Arrivals:'''
After departing the plane, gathering your luggage and clearing customs please proceed through the double set of glass doors. Once through you will find your meet and greet person, with a Mozilla sign. Follow their direction and they will show you to the bus for your transfer to Whistler. Be prepared to tell the driver your hotel location so they can ensure you and your luggage make it to the appropriate location in Whistler.

===Already in Vancouver?===
If you arrive prior to June 22 and have not made other arrangements or gotten specific instructions, please plan to be at the airport between 10 am and 5 pm to board a shuttle. Go to the baggage claim area and look for Mozilla signs.

Vancouver office, MDN Orientation and those arriving by trains and boats, we will have 2 shuttles from the office (one at 11 am and one at 1 pm), please add your name [https://docs.google.com/a/mozilla.com/spreadsheets/d/1sqFDdqddVyKSESFO5R63cJ4A44IcXlTVfGHMYCV2pxI/edit?usp=sharing here] so we can track you. Sign-ups for this list close on Friday, June 5.

For those of you staying at the ''Sheraton Vancouver Airport Hotel'', we will have shuttles departing at 11 am from the main entrance on Monday, June 22. If you would like to depart earlier or later, you will need to make your way to the airport terminal and the transportation team will get you on a coach with space, between 10 am and 5 pm.

===Departing Early?===
If you are departing Whistler prior to the 27th, you will need to book your transportation on your own [http://www.whistler.com/delegates/mozilla/ here]. On the main page, choose one of the two services and only enter a departure date. For the Shuttle, on the second page, there will be a drop down where you can choose "Whistler Village to YVR Airport" and reconfirm your date. For the van, there are options for Whistler to YVR. Then, for both "add it to your cart" and "then proceed to checkout" and that is where it will ask for your personal information and get you booked.
Please do not use this if you are departing on 6/27.

===Departures on 6/27===
Shuttles will pick up from each hotel. There will be a staff person in each hotel lobby to help you. We will post a list with your assigned departure time. Please be ready in the lobby of your hotel at this time.

=='''Hotel Assignments/Reservations & Meeting Space'''==
We have all hotels rooms covered and we’ll try to get teams in hotels together where possible. The hotels are all close together , so even if it the numbers aren’t perfect, it should all work pretty well. You have all received a confirmation email with your hotel assignment and dates - if not, email mozilla@shworldwide.com and request one. If you asked to extend at your own cost, the email will include that information as well.

Everyone will have individual rooms (unless you want to share). Interns will be sharing rooms.

There is complimentary wifi in the hotel rooms and lobby spaces so everyone can work in the evenings or prepare stuff for the next day.

===Parking in Whistler===
Parking - For those who are renting a car or driving up from Vancouver. There are less expensive options than parking at your hotel. With everything being within walking distance, there a lot of options [https://www.whistler.ca/services/transportation/parking/day-lots here]. Parking lots 4 and 5 are free parking, but a car would need to be moved every 72 hours. And for $30 you can get a month pass and park in lots 1, 2, and 3 as well.

===Smoking in Whistler===
Smoking in all of Canada has been banned in all indoor spaces since 2010 - this includes bars, restaurants & casinos. All of our hotels and venues are non-smoking. [https://docs.google.com/spreadsheets/d/1EUxX9AodZpcUN5rvn645lRW_UEg_qYGOsDGyYTVFIMY/edit?usp=sharing Here] are specifics by all of our event venues. Most venues have fines for smoking starting at $250 CAD and up.

=='''Families and loved ones at work weeks'''==
As a general principle, when organizing our work weeks, we look to design an experience that accommodates a variety of individual situations and requirements while also ensuring we have a productive and focused event.

Because of our size and varied space requirements (we require 3x the breakout space of most corporate meetings), it's cheaper to book our work weeks in holiday locations -- or cities like Portland -- during off-seasons. This approach means we can get the best rates and these cities typically already have great transportation infrastructure, resources for meals and social event, proximity to a major airport, have ample hotels, etc.

As part of planning, we work with hotels to ensure our employees, at their own expense, are able to extend their stay before or after our event, at our negotiated group rates. This makes it easier for anyone wanting to organize a getaway at the work week destination with their family and/or other Mozillians

'''Specifics'''

:In most cases, group discount rates apply for least three nights before and three night after our events. Reservations for those rooms are based on availability, should be requested as part of registration, and are at your expense. For those who plan getaways, our preference is for those to happen towards the end of the week. That way, when space permits, they can attend our Friday night event (typically only for adults).

:Before you decide to invite your partner or family (thinking kids or parents, not cousins or uncles) to join you for the full week, make sure they know what is expect of you. That for the majority of the time, your attention, focus and presence will need to be on your team and on Mozilla. Meals and any full-company social events, other than the Friday party (which we will open as broadly as our space permits in most cases), will be at your expense too.

===Mother’s Room Requests===
If you need one during the week, please go [https://docs.google.com/a/mozilla.com/document/d/17LyXjNb1qRAHrhI25wraTZPClhtYC4ciYpocIasgpf4/edit here] and add your needs.

=='''Food & Drink'''==
All meals (breakfast, lunch and dinner) will be provided and paid for centrally. It is all local, fresh and delicious. Any other food or drink expenses (including room service and in-room minibar charges) will be the responsibility of the attendee.

*Allergies: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options (and gfv options). If you have severe allergies that we need to know about; you can indicate in registration, or email mozilla@shworldwide.com

*Menus: Here are [https://docs.google.com/document/d/17xS8z7ifLUwGQe0xhsKNhF8p3u0yRCI-ldrRPNEPlZA/edit menus]! This doesn't include snacks, which there will be plenty of.

===Welcome Reception on Monday===
From 7 pm to 9 pm, we'll be showing off a bit of Whistler cuisine with plenty of food and drink + some local entertainment. The Information Desk will be open for any questions. Stay as long as you like (or go explore).

===Breakfast Daily===
Breakfast (including espresso) will be at the Whistler Conference Centre daily, Tuesday through Saturday. Check sched for exact timing each day.

===Lunch Daily===
Lunch on Tuesday and Thursday will be boxed lunches that you can grab as you leave the All Hands and take where you want. Eat with the bears, eat with your colleagues - totally up to you.

Lunch on Wednesday & Friday varies a bit based upon where your meetings take place:
*Lunch at Whistler Conference Centre will be those meeting at WCC, Delta, Aava, Pan Pacific Mountainside, Pan Pacific Village Centre and Crystal Lodge.
*Lunch at Hilton for those meeting at Hilton
*Lunch at Westin for those meeting at Westin
*Lunch at Fairmont for those meeting at Fairmont
*Lunch at Four Seasons for those meeting at Four Seasons

===Dinner on Tuesday & Thursday===
These will be at various restaurants in Whistler Village - at your choice and for you to go when you like. You will be provided meal voucher tickets on arrival in Whistler that will be valid for Tuesday and Thursday evenings. This [https://docs.google.com/spreadsheets/d/14mbIeIEIRLB2PMmR4maehKJwVQUKNUv_C9OXXST94l8/edit?usp=sharing list] shows the restaurants that are participating, with details about hours, menus, etc. Restaurants not on this list are not participating (and may not be expensed). Amounts above the voucher value ($40) may not be expensed.

===Dinner on Wednesday===
We have a group dinner for everyone at the Squamish Lil'wat Cultural Center from 6 pm - 10 pm, with dessert and local music at the Fairmont after. Add it to your schedule [http://sched.co/31m3 here]

===Friday Night Party===
So excited! Will be lovely. We'll feed, water & entertain you.

We’re going for a lumberjack chic vibe, being in the mountains. What that means exactly, is up to you. The party is at 6,000 feet, so it could be chilly, even snow. Keep that in mind when considering your wardrobe.

Gondola rides will start at 6:30 pm.

===Ramadan===
If you observe Ramadan and need accommodations for meals outside of daylight hours, please add your name [https://docs.google.com/document/d/19NEleRDm8qlBhdTx5NPSAgcvpEge-oBadiMO11Vsv5Q/edit?usp=sharing here]. Please note that the sun will rise at 5:00 am and set at 9:25 pm while we are in Whistler.

=='''Out of Pocket Expenses'''==
The intention of our work weeks are to centrally organize a structure within which teams can come together to work on deliverables and plans, to socialize, to meet and share with other teams, and generally come together as one Mozilla family, two times each year. The central organization includes meals (three/day + snacks), transportation, accommodations, and some number of social events.

Because of that, we’d expect a very limited number, if any, of work week-related expenses for food or social events (this includes team events, room service, mini-bar charges, and food/drink costs above the vouched amounts). Any social events that are not part of our central plan will generally be self-organized and funded by participants. This is a modified policy from Portland. For specifics on meals, please go to the Food & Drink section (above). If you have questions about any of this, please reach out to bmark@mozilla.com

===Volunteer Reimbursement via Reps===

Volunteers attending this event may submit for visa and U.S. travel/health insurance- related costs (and other incidentals) via Mozilla Reps:

Mozilla Reps attending this event may submit for reimbursement through the standard process.
Mozillians who are not Mozilla Reps should contact a local Rep and the Rep will help them get reimbursed. The process is as follows:
:Step 1: contact a Rep [https://reps.mozilla.org/people/ in your country]*
:Step 2: once the Rep has accepted to process your reimbursement, give them an estimate of what your costs will be. If you need the funds beforehand, be sure to say that
:Step 3: after the event, send him/her all your scanned receipts and bank details/paypal account
:Step 4: inform the Rep once you have successfully received the funds

=='''Schedule, Sched and Tracks'''==
Here is a [https://docs.google.com/a/mozilla.com/spreadsheets/d/1VBfbtDuzC7yc2MHYCk_yQB4HHgDBp70FnrB2k8WS6OY/edit#gid=0 high-level schedule] for Whistler (some things may shift but the event start and end times are firm).

===Scheduling Tool===
For Whistler, we’re using [https://juneworkweekwhistler2015.sched.org/ Sched] as our online scheduling tool. This replaces the giant spreadsheet we had last year and is where you go when you need to know where to be and when. This is a public website. Thus, anything we put into our session summaries or anything you sign up for is public. ''Think of this as twitter - if you wouldn't tweet it, it probably shouldn't be right IN sched. It could be in a link (with @Mozilla only access).'' Because of that, we shouldn’t use sched for Legal or proprietary information and anything about partners, vendors and the relationships with each

https://juneworkweekwhistler2015.sched.org/

====Overview====
With the tool, you can create a customized calendar view so you see only those sessions you need to attend. There is a mobile web app that allows you to view your personal schedule, browse what's happening right now or search for what you want. The mobile web app stores the schedule data locally on your phone for offline access too. (handy!) Head to the [https://juneworkweekwhistler2015.sched.org/ website] on your phone and you can bookmark (or add to your home screen) the site, making the data available offline.

====Creating a profile====
You can create a profile with as little information as a name (alias is okay) and an email. We do recommend that you choose a new password, and not one used on other sites. This profile enables you to create your own custom schedule. As you go through the agenda, you can check items to add to your schedule (click the circle to the left of the session title).

Adding a session will identify you as attending a session or event and others can see if you are going. You can make yourself a private profile by going to settings, and clicking the “Hide my profile & schedule from others at this event.”

Once you have a profile and have added sessions, you can do many things, including subscribing to the iCal feed in your calendar program or mobile phone. You will have instant, offline access to your schedule or the entire schedule of events. It even automatically pulls in updates of schedule changes. There are specific instructions available on their [https://juneworkweekwhistler2015.sched.org/signup#.VXfMpufneqQ website], as well as a [https://juneworkweekwhistler2015.sched.org/help#.VXfMSufneqQ video tour].

Here is a link to Sched’s [https://sched.org/about/legal/privacy-policy privacy policy]

====If you do not want to create a profile====
For those who don't want to sign up for a sched account, Sched provides an ics feed.

In Google Calendar:
Click on the down arrow next to Other Calendars
Select "Add by URL"
Enter this url: http://juneworkweekwhistler2015.sched.org/all.ics
The calendar will appear under Other Calendars.
Once the calendar is imported, it will be updated once a day. There's no way to change the frequency of updates. A note: you will see all schedules in this view (not a personal calendar).

===Tracks Open to All===

=====Mozilla-Wide 'Science Fair' (& Drink)=====
On Tuesday from 5pm - 7pm Mozillians will be showing off their projects at our first-ever Work Week “Science Fair.” This will be an informal gathering where you can demo your latest stuff. Did we mention this is over drinks?
* '''When & Where.''' Tuesday June 23, 5pm - 7pm at Whistler Conference Centre Grand Foyer (go to the main lobby right outside the Sea to Sky Ballroom where we have our all-hands sessions)
* '''What will I see?''' Check out who is showing off what [[Coincidental_work_weeks/2015_Whistler/ScienceFairDemos|here]].
* '''Questions?''' Ask Diane Tate <diane@mozilla.com>

=====Data, User, and Market Insights Track=====
On Thursday afternoon, at the Four Seasons Piccolo room, Mozillians from throughout the Project will make short presentations about what they are working on in the area of better understanding our users. The initial calendar is available [https://www.google.com/calendar/embed?src=mozilla.com_7kf06v6c1pbcsb6j31pesa1jn0%40group.calendar.google.com&ctz=America/Vancouver here]. Watch this space or the sched.org (http://sched.co/3Wyo) for further details.

=='''FAQ'''==
Anything not covered here, please add to this [https://docs.google.com/a/mozilla.com/document/d/1lBMU0wnmSL3AOm2zMf9ssK0xP3udX3kbPnSS8P6LbBU/edit?usp=sharing document] and we'll answer

=='''Extra Curriculars'''==
If you have one to propose, add it here with a sign up link. Note that these things are self-organized and self-funded.

[https://docs.google.com/spreadsheets/d/18LFB3s_fPiVu_wuht25uPl3bB2-jzWoWCJ4GkMRg5DE/edit#gid=0 Families of Whistlandia] If your kids are coming, sign up here to share events and fun (its locked down to mozilla.com addresses for security, but just ask to join and tell me who you are if you want in from another email)

[[Coincidental work weeks/2015 Whistler/jam band|Moz Jam Band: Getting Mozillians together to make music + perform a set at the end of the week (Show your interest here)]]

[[Workweek Gaming]] - was popular after-hours activity at Portland
* [https://etherpad.mozilla.org/WhistlerMTG Magic: The Gathering]
* [https://etherpad.mozilla.org/WhistlerRPG One-shot RPG]

[http://bike.whistlerblackcomb.com/tickets-passes/tickets/index.aspx Whistler Bike Park 3-lap sampler] - for the cycling inclined

[http://www.whistlerblackcomb.com/events-and-activities/summer-activities/index.aspx Full List of Whistler/Blackcomb Activities] - Peak2Peak, Ziptrek, Rafting, Alpine Tours, many more

[[Coincidental work weeks/2015 Whistler/Russet Lake and Overlord_Mountain|Overnight hike]] - Hike and camp at Russet Lake and summit Overlord Mountain. Fri-Sat or Sat-Sun weekend after work week.

[https://etherpad.mozilla.org/whistler-day-hike Day hike] - Non-overnight hiking trip, either on Monday or on Saturday. If interested, please indicate your preference on the etherpad!

[http://cayooshexpeditions.ca Paraglide Pemberton valley] - 1/2 day, 20min drive from Whistler

[http://www.whistlerskydiving.ca Skydive Pemberton valley] - 1/2 day, 20min drive from Whistler

[https://etherpad.mozilla.org/WhistlerZumba Zumba with Rowe!] - Please sign up for Wednesday at 7:45 am or Thursday at 4:30 pm. Maximum 20 spots each class.

[https://etherpad.mozilla.org/WhistlerSquash Squash] - There are two courts at "Meadow Park Sports Center" nearby Whistler village (10-min bus transportation). Please sign up.

[https://etherpad.mozilla.org/dpO9GwGTZG Rock climbing] - Let's go rock climbing together! In the Whistler Core Climbing and Fitness Centre!

[https://docs.google.com/spreadsheets/d/11Iyh_bkeyS-TRtEwZZlFMjm0HB78fhlTK7tsrnda95I/edit#gid=0 Running groups] - Find Mozillians to run with in scenic Whistler! Sign up to lead a running group, or join one!

[https://www.facebook.com/WhistlersCrystalLounge The Crystal Lounge] has karaoke night Tuesday night starting at 9pm. No sign up needed, but contact [mailto:ted@mielczarek.org Ted Mielczarek] if you're interested in going (a rough head count would be nice).

[https://etherpad.mozilla.org/WhistlerDiscGolf Disc Golf] Any Disc Golfers out there? Take a flex dinning evening to rattle some chains.

[https://etherpad.mozilla.org/whistler-introverts Mozilla Introverts List] - A list of things to help folks recover from days filled with people.

===Vancouver before and after===

If you are in Vancouver before or after the Work Week, the Vancouver office are running some events. These are all self funded and organized. If you would like to come, '''please add yourself to the google doc''' [https://docs.google.com/a/mozilla.com/spreadsheets/d/120PW5uWcMPpkTkWFS5Xom3OyCeY19iregm3kCjaDVi4/edit#gid=0 here]. Currently we've got the following:

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/120PW5uWcMPpkTkWFS5Xom3OyCeY19iregm3kCjaDVi4/edit#gid=1525760068 Brewery crawl] Sunday 21st

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/120PW5uWcMPpkTkWFS5Xom3OyCeY19iregm3kCjaDVi4/edit#gid=947422238 Visit Capilano Salmon Hatchery] Sunday 21st

* [https://etherpad.mozilla.org/spanishbanks Dinner on the beach] Sunday 21st

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/120PW5uWcMPpkTkWFS5Xom3OyCeY19iregm3kCjaDVi4/edit#gid=2021066743 Hiking to Bowen Lookout] Saturday 27th

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/120PW5uWcMPpkTkWFS5Xom3OyCeY19iregm3kCjaDVi4/edit#gid=1292363151 Kayaking in Deep Cove] Sunday 21st

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/120PW5uWcMPpkTkWFS5Xom3OyCeY19iregm3kCjaDVi4/edit#gid=115488785 Mountain Biking at Squamish or the North Shore] (ride moved to mid-week in Whistler)

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/120PW5uWcMPpkTkWFS5Xom3OyCeY19iregm3kCjaDVi4/edit#gid=383289966 Photowalk around Vancouver] (date undecided)

* [https://docs.google.com/a/mozilla.com/spreadsheets/d/120PW5uWcMPpkTkWFS5Xom3OyCeY19iregm3kCjaDVi4/edit#gid=1363419972 Canada Day party] July 1st. When else?

===Whistler Activities - Discount Link===

We’ve also negotiated some discounted rates on some fun things to do in and around Whistler and that list is [http://www.whistler.com/delegates/mozilla-activities/ here]

Learning/2015

2014-11-28T18:46:02Z

DavidA:

__NOTOC__
<big>'''PORTLAND'''</big>
* '''MoFo Portland schedule''': http://mzl.la/portland_schedule_view [https://etherpad.mozilla.org/MoFoPortland (etherpad version)]
* '''Home base''': http://mzl.la/portland_art_museum
* '''Logistics''': https://wiki.mozilla.org/Portland_coincidental_work_week
Need to change the schedule?
# Change the spreadsheet directly
# Create an etherpad for the session in mofoportland.etherpad.mozilla.org/''your-session-** name-here''
# Add a link to that etherpad in the spreadsheet cell (command-k is your friend)
# Add a note to the [https://etherpad.mozilla.org/MoFoPortland etherpad version]

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ws1zupez.png 

<big> '''THE PLAN: Mozilla Learning in 2015''' 
http://mzl.la/mozilla_learning_2015</big>
* ^ '''Start here'''. The high-level plan.
[[File:Mozilla Learning.002.png|600px]] 
==[[Webmaker/2015/Product|1) Webmaker]] ==
<big>PRODUCT</big>
* https://wiki.mozilla.org/Webmaker/2015/Product
'''Focused on learners and makers.''' Grow our base of engaged users. Lower barriers to participation. Emphasize mobile. Build community features that lead to more sustained involvement. Add online mentoring into the product. Experiment w. integrating Webmaker into Firefox and Firefox OS (aka "[https://wiki.mozilla.org/Webmaker/2015/MakerFox MakerFox].")
 
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/2w_m04q6.png

==[[Webmaker/2015/Mentors|2) Mentor Networks]]==
<big>PROGRAM</big>
* '''Hives''' https://wiki.mozilla.org/Webmaker/2015/Mentors
* '''Clubs''' https://wiki.mozilla.org/Webmaker/2015/Mentors/Clubs
'''Focused on teachers and mentors.''' The ground game. Local organizing. Grow events, clubs and hives. Move and use the parts of the product that work -- uncouple the parts that don't. "teach.webmaker.org" as a global hub. Continue building curriculum and credentialing. Teaching digital skills, web literacy, open ethos -- whether our tools or others. Work with Engagement Team on "sales" into partnerships with access to lots of mentors and teachers. Keep events platform and badges platform. Give local clubs and hives their own web presence.
* '''Online plan''' https://teach.etherpad.mozilla.org/requirements
* '''Curriculum plan''' https://wiki.mozilla.org/Webmaker/Curriculum
* '''Badges plan''' https://etherpad.mozilla.org/badges2015plan

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/bg3qwxfv.png

==[[Webmaker/2015/Leaders|3) Leaders & Fellows]]==
<big>LEADERSHIP DEVELOPMENT</big>
* https://wiki.mozilla.org/Webmaker/2015/Leaders
'''Focused on leaders and fellows.''' Develop leaders to protect the open web. Build a long-term strategic plan for a Mozilla leadership development program. Roll in great work from Fellowship programs -- Open News, Science Lab, Policy. Not all of it needs to fit here -- but find points of connection and wider theme / story. Lay the groundwork for Mozilla's global, community-based learning and leadership arm.

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/jwf977xl.png

=Supporting Documents=
* '''2015 Mozilla-wide plan''' -- How this fits into the bigger Mozilla picture http://mzl.la/mozilla_2015
* '''2015 Risks, Tensions and Questions''' https://etherpad.mozilla.org/learning2015
* '''2015 Marketing Plan''' https://foundation.etherpad.mozilla.org/webmakermarketing2015
* '''2015 Partner & Funder Analysis''' https://foundation.etherpad.mozilla.org/2015-pipeline-analysis
* '''2015 Key Partners and Campaign''' https://wiki.mozilla.org/Webmaker/2015/Partners

Learning/2015

2014-11-28T18:38:13Z

DavidA:

__NOTOC__
<big>'''PORTLAND'''</big>
* '''MoFo Portland schedule''': http://mzl.la/portland_schedule_view [https://etherpad.mozilla.org/MoFoPortland (etherpad version)]
** Need to change the schedule?
*** '''first''' Change the spreadsheet directly
*** '''then''' Add a note to the [https://etherpad.mozilla.org/MoFoPortland etherpad version]
* '''Home base''': http://mzl.la/portland_art_museum
* '''Logistics''': https://wiki.mozilla.org/Portland_coincidental_work_week
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ws1zupez.png 
<big> '''THE PLAN: Mozilla Learning in 2015''' 
http://mzl.la/mozilla_learning_2015</big>
* ^ '''Start here'''. The high-level plan.
[[File:Mozilla Learning.002.png|600px]] 
==[[Webmaker/2015/Product|1) Webmaker]] ==
<big>PRODUCT</big>
* https://wiki.mozilla.org/Webmaker/2015/Product
'''Focused on learners and makers.''' Grow our base of engaged users. Lower barriers to participation. Emphasize mobile. Build community features that lead to more sustained involvement. Add online mentoring into the product. Experiment w. integrating Webmaker into Firefox and Firefox OS (aka "[https://wiki.mozilla.org/Webmaker/2015/MakerFox MakerFox].")
 
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/2w_m04q6.png

==[[Webmaker/2015/Mentors|2) Mentor Networks]]==
<big>PROGRAM</big>
* '''Hives''' https://wiki.mozilla.org/Webmaker/2015/Mentors
* '''Clubs''' https://wiki.mozilla.org/Webmaker/2015/Mentors/Clubs
'''Focused on teachers and mentors.''' The ground game. Local organizing. Grow events, clubs and hives. Move and use the parts of the product that work -- uncouple the parts that don't. "teach.webmaker.org" as a global hub. Continue building curriculum and credentialing. Teaching digital skills, web literacy, open ethos -- whether our tools or others. Work with Engagement Team on "sales" into partnerships with access to lots of mentors and teachers. Keep events platform and badges platform. Give local clubs and hives their own web presence.
* '''Online plan''' https://teach.etherpad.mozilla.org/requirements
* '''Curriculum plan''' https://wiki.mozilla.org/Webmaker/Curriculum
* '''Badges plan''' https://etherpad.mozilla.org/badges2015plan

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/bg3qwxfv.png

==[[Webmaker/2015/Leaders|3) Leaders & Fellows]]==
<big>LEADERSHIP DEVELOPMENT</big>
* https://wiki.mozilla.org/Webmaker/2015/Leaders
'''Focused on leaders and fellows.''' Develop leaders to protect the open web. Build a long-term strategic plan for a Mozilla leadership development program. Roll in great work from Fellowship programs -- Open News, Science Lab, Policy. Not all of it needs to fit here -- but find points of connection and wider theme / story. Lay the groundwork for Mozilla's global, community-based learning and leadership arm.

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/jwf977xl.png

=Supporting Documents=
* '''2015 Mozilla-wide plan''' -- How this fits into the bigger Mozilla picture http://mzl.la/mozilla_2015
* '''2015 Risks, Tensions and Questions''' https://etherpad.mozilla.org/learning2015
* '''2015 Marketing Plan''' https://foundation.etherpad.mozilla.org/webmakermarketing2015
* '''2015 Partner & Funder Analysis''' https://foundation.etherpad.mozilla.org/2015-pipeline-analysis
* '''2015 Key Partners and Campaign''' https://wiki.mozilla.org/Webmaker/2015/Partners

Learning/2015

2014-11-28T18:37:43Z

DavidA: tweaks

__NOTOC__
<big>'''PORTLAND'''</big>
* '''MoFo Portland schedule''': http://mzl.la/portland_schedule_view [https://etherpad.mozilla.org/MoFoPortland (etherpad version)]
** Need to change the schedule?
*** **first** Change the spreadsheet directly
*** **then** Add a note to the [https://etherpad.mozilla.org/MoFoPortland etherpad version]
* '''Home base''': http://mzl.la/portland_art_museum
* '''Logistics''': https://wiki.mozilla.org/Portland_coincidental_work_week
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ws1zupez.png 
<big> '''THE PLAN: Mozilla Learning in 2015''' 
http://mzl.la/mozilla_learning_2015</big>
* ^ '''Start here'''. The high-level plan.
[[File:Mozilla Learning.002.png|600px]] 
==[[Webmaker/2015/Product|1) Webmaker]] ==
<big>PRODUCT</big>
* https://wiki.mozilla.org/Webmaker/2015/Product
'''Focused on learners and makers.''' Grow our base of engaged users. Lower barriers to participation. Emphasize mobile. Build community features that lead to more sustained involvement. Add online mentoring into the product. Experiment w. integrating Webmaker into Firefox and Firefox OS (aka "[https://wiki.mozilla.org/Webmaker/2015/MakerFox MakerFox].")
 
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/2w_m04q6.png

==[[Webmaker/2015/Mentors|2) Mentor Networks]]==
<big>PROGRAM</big>
* '''Hives''' https://wiki.mozilla.org/Webmaker/2015/Mentors
* '''Clubs''' https://wiki.mozilla.org/Webmaker/2015/Mentors/Clubs
'''Focused on teachers and mentors.''' The ground game. Local organizing. Grow events, clubs and hives. Move and use the parts of the product that work -- uncouple the parts that don't. "teach.webmaker.org" as a global hub. Continue building curriculum and credentialing. Teaching digital skills, web literacy, open ethos -- whether our tools or others. Work with Engagement Team on "sales" into partnerships with access to lots of mentors and teachers. Keep events platform and badges platform. Give local clubs and hives their own web presence.
* '''Online plan''' https://teach.etherpad.mozilla.org/requirements
* '''Curriculum plan''' https://wiki.mozilla.org/Webmaker/Curriculum
* '''Badges plan''' https://etherpad.mozilla.org/badges2015plan

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/bg3qwxfv.png

==[[Webmaker/2015/Leaders|3) Leaders & Fellows]]==
<big>LEADERSHIP DEVELOPMENT</big>
* https://wiki.mozilla.org/Webmaker/2015/Leaders
'''Focused on leaders and fellows.''' Develop leaders to protect the open web. Build a long-term strategic plan for a Mozilla leadership development program. Roll in great work from Fellowship programs -- Open News, Science Lab, Policy. Not all of it needs to fit here -- but find points of connection and wider theme / story. Lay the groundwork for Mozilla's global, community-based learning and leadership arm.

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/jwf977xl.png

=Supporting Documents=
* '''2015 Mozilla-wide plan''' -- How this fits into the bigger Mozilla picture http://mzl.la/mozilla_2015
* '''2015 Risks, Tensions and Questions''' https://etherpad.mozilla.org/learning2015
* '''2015 Marketing Plan''' https://foundation.etherpad.mozilla.org/webmakermarketing2015
* '''2015 Partner & Funder Analysis''' https://foundation.etherpad.mozilla.org/2015-pipeline-analysis
* '''2015 Key Partners and Campaign''' https://wiki.mozilla.org/Webmaker/2015/Partners

Learning/2015

2014-11-28T18:36:58Z

DavidA:

__NOTOC__
<big>'''PORTLAND'''</big>
* '''MoFo Portland schedule''': http://mzl.la/portland_schedule_view [https://etherpad.mozilla.org/MoFoPortland (etherpad version)]
** Need to change the schedule?
*** Change the spreadsheet directly
*** Add a note to the [https://etherpad.mozilla.org/MoFoPortland etherpad version]
* '''Home base''': http://mzl.la/portland_art_museum
* '''Logistics''': https://wiki.mozilla.org/Portland_coincidental_work_week
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ws1zupez.png 
<big> '''THE PLAN: Mozilla Learning in 2015''' 
http://mzl.la/mozilla_learning_2015</big>
* ^ '''Start here'''. The high-level plan.
[[File:Mozilla Learning.002.png|600px]] 
==[[Webmaker/2015/Product|1) Webmaker]] ==
<big>PRODUCT</big>
* https://wiki.mozilla.org/Webmaker/2015/Product
'''Focused on learners and makers.''' Grow our base of engaged users. Lower barriers to participation. Emphasize mobile. Build community features that lead to more sustained involvement. Add online mentoring into the product. Experiment w. integrating Webmaker into Firefox and Firefox OS (aka "[https://wiki.mozilla.org/Webmaker/2015/MakerFox MakerFox].")
 
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/2w_m04q6.png

==[[Webmaker/2015/Mentors|2) Mentor Networks]]==
<big>PROGRAM</big>
* '''Hives''' https://wiki.mozilla.org/Webmaker/2015/Mentors
* '''Clubs''' https://wiki.mozilla.org/Webmaker/2015/Mentors/Clubs
'''Focused on teachers and mentors.''' The ground game. Local organizing. Grow events, clubs and hives. Move and use the parts of the product that work -- uncouple the parts that don't. "teach.webmaker.org" as a global hub. Continue building curriculum and credentialing. Teaching digital skills, web literacy, open ethos -- whether our tools or others. Work with Engagement Team on "sales" into partnerships with access to lots of mentors and teachers. Keep events platform and badges platform. Give local clubs and hives their own web presence.
* '''Online plan''' https://teach.etherpad.mozilla.org/requirements
* '''Curriculum plan''' https://wiki.mozilla.org/Webmaker/Curriculum
* '''Badges plan''' https://etherpad.mozilla.org/badges2015plan

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/bg3qwxfv.png

==[[Webmaker/2015/Leaders|3) Leaders & Fellows]]==
<big>LEADERSHIP DEVELOPMENT</big>
* https://wiki.mozilla.org/Webmaker/2015/Leaders
'''Focused on leaders and fellows.''' Develop leaders to protect the open web. Build a long-term strategic plan for a Mozilla leadership development program. Roll in great work from Fellowship programs -- Open News, Science Lab, Policy. Not all of it needs to fit here -- but find points of connection and wider theme / story. Lay the groundwork for Mozilla's global, community-based learning and leadership arm.

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/jwf977xl.png

=Supporting Documents=
* '''2015 Mozilla-wide plan''' -- How this fits into the bigger Mozilla picture http://mzl.la/mozilla_2015
* '''2015 Risks, Tensions and Questions''' https://etherpad.mozilla.org/learning2015
* '''2015 Marketing Plan''' https://foundation.etherpad.mozilla.org/webmakermarketing2015
* '''2015 Partner & Funder Analysis''' https://foundation.etherpad.mozilla.org/2015-pipeline-analysis
* '''2015 Key Partners and Campaign''' https://wiki.mozilla.org/Webmaker/2015/Partners

Learning/2015

2014-11-28T18:35:51Z

DavidA: change heading

__NOTOC__
<big>'''PORTLAND'''</big>
* '''MoFo Portland schedule''': http://mzl.la/portland_schedule_view [https://etherpad.mozilla.org/MoFoPortland (etherpad version)]
* '''Home base''': http://mzl.la/portland_art_museum
* '''Logistics''': https://wiki.mozilla.org/Portland_coincidental_work_week
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/ws1zupez.png 
<big> '''THE PLAN: Mozilla Learning in 2015''' 
http://mzl.la/mozilla_learning_2015</big>
* ^ '''Start here'''. The high-level plan.
[[File:Mozilla Learning.002.png|600px]] 
==[[Webmaker/2015/Product|1) Webmaker]] ==
<big>PRODUCT</big>
* https://wiki.mozilla.org/Webmaker/2015/Product
'''Focused on learners and makers.''' Grow our base of engaged users. Lower barriers to participation. Emphasize mobile. Build community features that lead to more sustained involvement. Add online mentoring into the product. Experiment w. integrating Webmaker into Firefox and Firefox OS (aka "[https://wiki.mozilla.org/Webmaker/2015/MakerFox MakerFox].")
 
https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/2w_m04q6.png

==[[Webmaker/2015/Mentors|2) Mentor Networks]]==
<big>PROGRAM</big>
* '''Hives''' https://wiki.mozilla.org/Webmaker/2015/Mentors
* '''Clubs''' https://wiki.mozilla.org/Webmaker/2015/Mentors/Clubs
'''Focused on teachers and mentors.''' The ground game. Local organizing. Grow events, clubs and hives. Move and use the parts of the product that work -- uncouple the parts that don't. "teach.webmaker.org" as a global hub. Continue building curriculum and credentialing. Teaching digital skills, web literacy, open ethos -- whether our tools or others. Work with Engagement Team on "sales" into partnerships with access to lots of mentors and teachers. Keep events platform and badges platform. Give local clubs and hives their own web presence.
* '''Online plan''' https://teach.etherpad.mozilla.org/requirements
* '''Curriculum plan''' https://wiki.mozilla.org/Webmaker/Curriculum
* '''Badges plan''' https://etherpad.mozilla.org/badges2015plan

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/bg3qwxfv.png

==[[Webmaker/2015/Leaders|3) Leaders & Fellows]]==
<big>LEADERSHIP DEVELOPMENT</big>
* https://wiki.mozilla.org/Webmaker/2015/Leaders
'''Focused on leaders and fellows.''' Develop leaders to protect the open web. Build a long-term strategic plan for a Mozilla leadership development program. Roll in great work from Fellowship programs -- Open News, Science Lab, Policy. Not all of it needs to fit here -- but find points of connection and wider theme / story. Lay the groundwork for Mozilla's global, community-based learning and leadership arm.

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/jwf977xl.png

=Supporting Documents=
* '''2015 Mozilla-wide plan''' -- How this fits into the bigger Mozilla picture http://mzl.la/mozilla_2015
* '''2015 Risks, Tensions and Questions''' https://etherpad.mozilla.org/learning2015
* '''2015 Marketing Plan''' https://foundation.etherpad.mozilla.org/webmakermarketing2015
* '''2015 Partner & Funder Analysis''' https://foundation.etherpad.mozilla.org/2015-pipeline-analysis
* '''2015 Key Partners and Campaign''' https://wiki.mozilla.org/Webmaker/2015/Partners

Foundation/EOY

2014-11-21T20:58:23Z

DavidA: try to show priority column

__NOTOC__
=Emergency Plan=
Add your PTO and sign up to be on call here: http://mzl.la/911

=Current status=
As of November 20:
* Our first '''“select amount” snippet''' is now in circulation to about 10% of US-EN general Firefox snippet traffic: https://snippets.mozilla.com/show/4758/. It went live around 9:35pm PST. Users who click hit our new, highest-performing 1-page form. Putting donate buttons right on the snippet is a significant departure from previous fundraising snippet designs. This one is most definitely breaking new ground. We’ll let this one stay up for at least 3-4 days, to get a nice sample size. 

* We are now accepting '''Bitcoin donations'''. https://blog.mozilla.org/blog/2014/11/20/mozilla-now-accepts-bitcoin/
 

* Our new '''Directory Tile''' for EOY is now live. (Nice job Sabrina!) This is the first time we’re using that channel for fundraising. The Tiles team asked us to share the data with them…. and of course we will! The total will show up on fundraising.mozilla.org once it’s launched soon. Here’s what it looks like: https://bug1076000.bugzilla.mozilla.org/attachment.cgi?id=8522356 

* Our top dev priority is finishing '''fundraising.mozilla.org''' 

* Our secondary dev priority is finishing the '''sequential donate form''' 

=Daily Stand-ups=
* 10:30am PT daily in Andrea Wood's Vidyo Room

=Do These First=
[EOYFR2014] [p1]
<bugzilla>
{
"whiteboard": "[EOYFR2014] [p1]",
"include_fields": "id, summary, whiteboard, assigned_to, status, priority",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=Do These Second=
[EOYFR2014] [p2]
<bugzilla>
{
"whiteboard": "[EOYFR2014] [p2]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=Deliverable: Donation Form and Flow=
* '''[EOYFR2014] [donation flow]'''
* see the work flows [https://redpen.io/p/oybcabfb1688e2e80e here] and [https://redpen.io/bv431b4fdc69222cf2#showing-comment-612913 here]
* '''Donation form testing plan''' -- see the [https://docs.google.com/a/mozillafoundation.org/drawings/d/1QPcx_nrDZgcAPH4Hdyl6uNet5LIQN2v2RrcYnZvz6qU/edit variation tree]
<bugzilla>
{
"whiteboard": "[EOYFR2014] [donation flow]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=Deliverable: fundraising.mozilla.org (including localization)'''=
* '''[EOYFR2014] [f.m.o]'''
* see the [https://redpen.io/fw5f9cf2476ea0a2c6 wireframe]
<bugzilla>
{
"whiteboard": "[EOYFR2014] [f.m.o]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=Deliverable: Snippet'''=
* '''[EOYFR2014] [snippet]'''
* Summary of 2014 snippet designs: https://docs.google.com/a/mozillafoundation.org/document/d/1NlJ7KXdf4guv8aaGWoyFOlJ40LnvFPc1Flfv6S2Kj9o/edit
* Background on the snippet: https://fundraising.mozilla.org/geeking-out-on-the-snippet/
* see initial sketches [https://docs.google.com/a/mozillafoundation.org/file/d/0B_VT8vv8uni5aHE1RGY3MkEyMkE/edit here] and [http://images.adamlofting.com/#2/14115688785170 here]
<bugzilla>
{
"whiteboard": "[EOYFR2014] [snippet]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=Deliverable: Visual Assets'''=
* '''[EOYFR2014] [assets]'''
<bugzilla>
{
"whiteboard": "[EOYFR2014] [assets]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=Deliverable: Community Marketing'''=
* '''[EOYFR2014] [community]'''
* see [https://etherpad.mozilla.org/engagementworkweekfall2014-EOYcommunity notes]
<bugzilla>
{
"whiteboard": "[EOYFR2014] [community]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=Deliverable: Comms=
* '''[EOYFR2014] [comms]'''
<bugzilla>
{
"whiteboard": "[EOYFR2014] [comms]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

=Deliverable: Localization=
* [EOYFR2014] [l10n]
* Notes: https://foundation.etherpad.mozilla.org/EOYFR-2014-translate
<bugzilla>
{
"whiteboard": "[EOYFR2014] [l10n]",
"include_fields": "id, summary, whiteboard, assigned_to, status",
"resolution": "---",
"maxrows":"50",
"order": "bug_id"
}
</bugzilla>

==Goal==
In 2014 we need to raise $17 million to fund the work of the Mozilla Foundation, with $2.25 million coming from small dollar fundraising.

==Docs==
* '''Slides''' http://mzl.la/2014_fundraising_slides
* '''Project Brief''': http://mzl.la/10SvTj6
* '''To Do List''': http://mzl.la/1Eg6cqG
* '''Initial testing results''': http://mzl.la/1tXMb56
* '''Snippet Types:''' http://mzl.la/snippet_types

==Key Outcomes==
This campaign is projected to bring in at least 75% of the total small dollar revenue goal in 2014. Additionally, we expect to increase the proportion of donations from outside the United States, increase snippet revenue to at least $1 million, increase the total number of donors while maintaining an average donation of $11.63, and improve the donor experience.

==Target audience==
** Previous donors from all channels;
** New donors who see our channel promotion (e.g. the snippet);
** New donors who see that a friend or family donated (via share on Twitter, for instance);
** Mozilla community members, their friends & family;
** Targeting the following locales:
*** EN (USA, Canada, UK, Australia and also Sweden, Denmark, and other locales where EN is widely spoken)
*** France (FR)
*** Germany (DE)
*** Brazil (PT-BR)
*** NEW Indonesia (ID)
*** NEW Latin America (Spanish)

==Success metrics==
** Raise $1.75 million November 1 - December 31;
** Donor retention (2013 donors who donate again in 2014);
** New donor acquisition (75% more donors than the 2013 campaign).

==Roles==
** R: Andrea Wood
** A: Geoffrey MacDougall
** S: Kelli Klein, Studio Mofo, Jean Collings, Michaela Smiley

Webmaker/2015/MakerFox

2014-11-12T16:22:58Z

DavidA: v1

=Vision=
<big>'''Experiment with integrating Webmaker into Firefox/Fennec/FirefoxOS directly'''</big>

MakerFox is a deliberately silly name to provide an umbrella for surgical, deliberate explorations of how 1+1 might equal 3, by combining the generic consumer-grade brand that is the Firefox product line (& Mozilla properties that go along) with the Web literacy and maker-centric product that is Webmaker.

In 2015, the focus is to make small, motivated experiments to explore whether there might be near-term wins that could result from a more intentional cross-product approach.

Examples include using MDN or SUMO to recruit Webmaker mentors; make a new feature inside of Firefox (either a mainstream edition or via a new add-on) to surface Webmaker features; a marketing campaign that showcases Firefox as the browser that shows you what's going on, as contrasted with the opaque competition.

Other examples that the team might consider

* Changes to Fennec that would make it obviously a better "maker" browser on Android (e.g. by integrating Makedrive with Activities, by making the personal gallery one of the panes in the home view)

* Explorations of whether Making & Web literacy could be ingredients of a market-specific differentation strategy for FirefoxOS (e.g. supporting a youth-centric approach to operating system GTM).

* Running AdWords campaigns targeted at Chrome/Safari users to see if we can establish interest in a making-oriented browser for those audiences before even building anything. Using whoever clicks to help us understand their pain points.

* Making a Firefox or Fennec add-on that connects users' Firefox account w/ their Makedrive assets.

* Making a Firefox add-on that surfaces information that people curious about how the web is made might appreciate (more info on URLs, more info on images, … cf some of mwilse's work)

* Explore what user benefits might come from connecting Firefox Accounts and Webmaker accounts (e.g. "call a mentor on Loop")

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/df70t5s6.png 

=Before & After=
* ''Before'': Firefox and Webmaker are related brands, but Firefox makes almost no mention of Webmaker and vice versa. Web literacy is appealing as part of the Mozilla brand story, but currently not reflected in either the Firefox product line or in the marketing+brand plans.

* ''After'' By EOY 2015, we will have identified 2-3 promising avenues for cross-product integration in the Firefox+FirefoxOS product line, and have one in production. Firefox products will hopefully derive greater differentiation and stickier relationships with users, and Webmaker will hopefully derive scaling support from these integrations.

=KPIs=

These are tentative, but from an exploratory POV, the KPIs could be:
* click rate for adwors which mention presumed value prop relative to those that don't
* net promoter score for add-on user

Long term KPIs:
* % of time using "enhanced" firefox relative to other browser is greater (# of hours per day) than before

=Milestones=
* Q4 2014: gathering of friendlies in portland; figuring out who within MoFo+MoCo is on the tiger team, and securing time budgets.
* Q1 2015: ideation & prototyping: identify up to 20 possible ideas
* Q2 2015: with the help of advisory committee, winnow that down to top 3 to start first, and test-market them
* Q3 2015: test-market 3 ideas & pick top one
* Q4 2015: switch to implementation of best idea

=''Links''=
* ''should add links to some of the previous decks & matthew's mocks''

Webmaker/2015/MakerFox

2014-11-12T16:22:27Z

DavidA: v1

Webmaker/2015/MakerFox

2014-11-12T16:19:55Z

DavidA: /* Vision */

=Vision=
<big>'''Experiment with integrating Webmaker into Firefox/Fennec/FirefoxOS directly'''</big>

MakerFox is a deliberately silly name to provide an umbrella for surgical, deliberate explorations of how 1+1 might equal 3, by combining the generic consumer-grade brand that is the Firefox product line (& Mozilla properties that go along) with the Web literacy and maker-centric product that is Webmaker.

In 2015, the focus is to make small, motivated experiments to explore whether there might be near-term wins that could result from a more intentional cross-product approach.

Examples include using MDN or SUMO to recruit Webmaker mentors; make a new feature inside of Firefox (either a mainstream edition or via a new add-on) to surface Webmaker features; a marketing campaign that showcases Firefox as the browser that shows you what's going on, as contrasted with the opaque competition.

Other examples that the team might consider

* Changes to Fennec that would make it obviously a better "maker" browser on Android (e.g. by integrating Makedrive with Activities, by making the personal gallery one of the panes in the home view)

* Explorations of whether Making & Web literacy could be ingredients of a market-specific differentation strategy for FirefoxOS (e.g. supporting a youth-centric approach to operating system GTM).

* Running AdWords campaigns targeted at Chrome/Safari users to see if we can establish interest in a making-oriented browser for those audiences before even building anything. Using whoever clicks to help us understand their pain points.

* Making a Firefox or Fennec add-on that connects users' Firefox account w/ their Makedrive assets.

* Making a Firefox add-on that surfaces information that people curious about how the web is made might appreciate (more info on URLs, more info on images, … cf some of mwilse's work)

* Explore what user benefits might come from connecting Firefox Accounts and Webmaker accounts (e.g. "call a mentor on Loop")

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/df70t5s6.png 

=Before & After=
* ''Before'': Firefox and Webmaker are related brands, but Firefox makes almost no mention of Webmaker and vice versa. Web literacy is appealing as part of the Mozilla brand story, but currently not reflected in either the Firefox product line or in the marketing+brand plans.

* ''After'' By EOY 2015, we will have identified 2-3 promising avenues for cross-product integration in the Firefox+FirefoxOS product line, and have one in production. Firefox products will hopefully derive greater differentiation and stickier relationships with users, and Webmaker will hopefully derive scaling support from these integrations.

=KPIs=
* ''to come''

=Milestones=
* Q4 2014: gathering of friendlies in portland; figuring out who within MoFo+MoCo is on the tiger team, and securing time budgets.
* Q1 2015: ideation & prototyping: identify up to 20 possible ideas
* Q2 2015: with the help of advisory committee, winnow that down to top 3 to start first, and test-market them
* Q3 2015: test-market 3 ideas & pick top one
* Q4 2015: switch to implementation of best idea

=''Links''=
* ''helpful added context or documents''

Webmaker/2015/MakerFox

2014-11-12T16:07:46Z

DavidA: adding some examples

=Vision=
<big>'''Experiment with integrating Webmaker into Firefox/Fennec/FirefoxOS directly'''</big>

MakerFox is a deliberately silly name to provide an umbrella for surgical, deliberate explorations of how 1+1 might equal 3, by combining the generic consumer-grade brand that is the Firefox product line (& Mozilla properties that go along) with the Web literacy and maker-centric product that is Webmaker.

In 2015, the focus is to make small, motivated experiments to explore whether there might be near-term wins that could result from a more intentional cross-product approach.

Examples include using MDN or SUMO to recruit Webmaker mentors; make a new feature inside of Firefox (either a mainstream edition or via a new add-on) to surface Webmaker features; a marketing campaign that showcases Firefox as the browser that shows you what's going on, as contrasted with the opaque competition.

Other examples that the team might consider

* Changes to Fennec that would make it obviously a better "maker" browser on Android (e.g. by integrating Makedrive with Activities, by making the personal gallery one of the panes in the home view)

* Explorations of whether Making & Web literacy could be ingredients of a market-specific differentation strategy for FirefoxOS (e.g. supporting a youth-centric approach to operating system GTM).

* Running AdWords campaigns targeted at Chrome/Safari users to see if we can establish interest in a making-oriented browser for those audiences before even building anything. Using whoever clicks to help us understand their pain points.

* Making a Firefox or Fennec add-on that connects users' Firefox account w/ their Makedrive assets.

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/df70t5s6.png 

=Before & After=
* ''Before'': Firefox and Webmaker are related brands, but Firefox makes almost no mention of Webmaker and vice versa. Web literacy is appealing as part of the Mozilla brand story, but currently not reflected in either the Firefox product line or in the marketing+brand plans.

* ''After'' By EOY 2015, we will have identified 2-3 promising avenues for cross-product integration in the Firefox+FirefoxOS product line, and have one in production. Firefox products will hopefully derive greater differentiation and stickier relationships with users, and Webmaker will hopefully derive scaling support from these integrations.

=KPIs=
* ''to come''

=Milestones=
* Q4 2014: gathering of friendlies in portland; figuring out who within MoFo+MoCo is on the tiger team, and securing time budgets.
* Q1 2015: ideation & prototyping: identify up to 20 possible ideas
* Q2 2015: with the help of advisory committee, winnow that down to top 3 to start first, and test-market them
* Q3 2015: test-market 3 ideas & pick top one
* Q4 2015: switch to implementation of best idea

=''Links''=
* ''helpful added context or documents''

Webmaker/2015/MakerFox

2014-11-12T15:51:45Z

DavidA: v1

=Vision=
<big>'''Experiment with integrating Webmaker into Firefox directly'''</big>

MakerFox is a deliberately silly name to provide an umbrella for surgical, deliberate explorations of how 1+1 might equal 3, by combining the generic consumer-grade brand that is the Firefox product line (& Mozilla properties that go along) with the Web literacy and maker-centric product that is Webmaker.

In 2015, the focus is to make small, motivated experiments to explore whether there might be near-term wins that could result from a more intentional cross-product approach.

Examples include using MDN or SUMO to recruit Webmaker mentors; make a new feature inside of Firefox (either a mainstream edition or via a new add-on) to surface Webmaker features; a marketing campaign that showcases Firefox as the browser that shows you what's going on, as contrasted with the opaque competition.

Other examples that the team might consider

* Changes to Fennec that would make it obviously a better "maker" browser on Android (e.g. by integrating Makedrive with Activities, by making the personal gallery one of the panes in the home view)

* Explorations of whether Making & Web literacy could be ingredients of a market-specific differentation strategy for FirefoxOS (e.g. supporting a youth-centric approach to operating system GTM).

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/df70t5s6.png 

=Before & After=
* ''Before'': Firefox and Webmaker are related brands, but Firefox makes almost no mention of Webmaker and vice versa. Web literacy is appealing as part of the Mozilla brand story, but currently not reflected in either the Firefox product line or in the marketing+brand plans.

* ''After'' By EOY 2015, we will have identified 2-3 promising avenues for cross-product integration in the Firefox+FirefoxOS product line, and have one in production. Firefox products will hopefully derive greater differentiation and stickier relationships with users, and Webmaker will hopefully derive scaling support from these integrations.

=KPIs=
* ''to come''

=Milestones=
* Q4 2014: gathering of friendlies in portland; figuring out who within MoFo+MoCo is on the tiger team, and securing time budgets.
* Q1 2015: ideation & prototyping: identify up to 20 possible ideas
* Q2 2015: with the help of advisory committee, winnow that down to top 3 to start first, and test-market them
* Q3 2015: test-market 3 ideas & pick top one
* Q4 2015: switch to implementation of best idea

=''Links''=
* ''helpful added context or documents''

Webmaker/2015/MakerFox

2014-11-12T15:45:53Z

DavidA: v1

=Vision=
<big>'''Experiment with integrating Webmaker into Firefox directly'''</big>

MakerFox is a deliberately silly name to provide an umbrella for surgical, deliberate explorations of how 1+1 might equal 3, by combining the generic consumer-grade brand that is the Firefox product line (& Mozilla properties that go along) with the Web literacy and maker-centric product that is Webmaker.

In 2015, the focus is to make small, motivated experiments to explore whether there might be near-term wins that could result from a more intentional cross-product approach.

Examples include using MDN or SUMO to recruit Webmaker mentors; make a new feature inside of Firefox (either a mainstream edition or via a new add-on) to surface Webmaker features; a marketing campaign that showcases Firefox as the browser that shows you what's going on, as contrasted with the opaque competition.

Other examples that the team might consider

* Changes to Fennec that would make it obviously a better "maker" browser on Android (e.g. by integrating Makedrive with Activities, by making the personal gallery one of the panes in the home view)

* Explorations of whether Making & Web literacy could be ingredients of a market-specific differentation strategy for FirefoxOS (e.g. supporting a youth-centric approach to operating system GTM).

https://dl.dropboxusercontent.com/spa/6c38yp3crbxni5b/df70t5s6.png 

=Before & After=
* ''Before'': Firefox and Webmaker are related brands, but Firefox makes almost no mention of Webmaker and vice versa. Web literacy is appealing as part of the Mozilla brand story, but currently not reflected in either the Firefox product line or in the marketing+brand plans.

* ''After'' By EOY 2015, we will have identified 2-3 promising avenues for cross-product integration in the Firefox+FirefoxOS product line, and have one in production. Firefox products will hopefully derive greater differentiation and stickier relationships with users, and Webmaker will hopefully derive scaling support from these integrations.

=KPIs=
* ''to come''

=Milestones=
* ''to come''

=''Links''=
* ''helpful added context or documents''

Webmaker/2015/MakerFox

2014-11-12T15:40:29Z

DavidA: v1

Vancouver

2014-06-26T20:57:10Z

DavidA: /* Other */

Recommendations for people visiting the Mozilla office in Vancouver.

== Airport Transportation ==

The best way is to take the 'Canada Line' train [http://goo.gl/maps/1REK from the airport].

== Hotels ==

We've had the best luck with the St. Regis Hotel which is near the office and the Canada line station, and bookable via egencia:

* Hotel Website: [http://www.stregishotel.com/ http://www.stregishotel.com/]
* [http://goo.gl/maps/ngIX Directions from the Airport]
* [http://goo.gl/maps/CMSE Walking directions from the hotel to office]

== Food ==

=== Vegetarian-friendly Options ===

* Nicli Antica Pizza
* Verace Pizza
* Incendio Pizza
* Deacon's Corner (diner)
* Sitar (indian)
* Acme (diner)
* Nuba (lebanese)
* La taqueria (tacos, duh)
* Golden Garden (vietnamese)
* Salad Loop (one under harbour centre, one in central library)
* MoMo Sushi
* Finch's (sandwiches, slow but very good)
* Gorilla Food (raw vegan)
* International Village food court (by stadium)
* Harbour centre food court

=== Non-Vegetarian Options ===

* [http://guu-izakaya.com/gastown Guu Izakaya] (A Vancouver Gastown tradition)
* Chambar (belgian, dinner)
* Cafe Medina (brunch, lunch, waffles, pseudo-european-fusion)
* Meat & Bread (lunch; excellent "sandwiches")
* Acme Cafe (lunch; diner)
* Guu Izakaya in Gastown (water st. location)
* Pour House (excellent burger among others, not cheap)
* Revel Room (decent burger)
* Irish Heather
* Salt (cold cuts, cheeses, wine)
* Jules Bistro
* L'abbatoir (cutting edge, v. good, not cheap)

=== Not close to the office ===

* Sushi: Hitae Sushi on 4th in Kits for traditional; The Eatery for a weird hip scene. There are lots of other good choices.
* Italian: La Buca; La Quercia; Campagnolo; Quattro
* Pizza: Verace; Bibo
* Indian: Vij's (fancy fusion); Rangoli (related, less fancy)
* Thai: Krua Thai in North Vancouver
* Japanese: the other Guu restaurants; Gyoza King; Kintaro Ramen on Denman; Motomachi Shokudo Ramen
* French: Regalade; Au petit Chavignol; Aux faux bourgeois; Salade de fruits
Chinese: I'm not competent in that domain, but there are apparently world-class options here. Ask Roland Tanglao.
* Refuel's sous-vide fried chicken is quite tasty. Meat & Bread for a yummy sandwich; Harvest Deli on Broadway for classic sandwiches; Salt is a charcuterie/cheese/wine destination; Judas Goat is a fancy $$ tapas run by the same folks;
* Templeton (check out the Portobello "burger", and the $5-shake); Deacon's corner for a corned beef hash;

Lots of street food vendors!

== Drinks ==

===Drinks that make you feel funny===
* Alibi Room - lots of local beers on tap & decent food
* L'abbatoir - fancy cocktails
* The Diamond - Fancy cocktails and fun Asian fusion food but closed on Mondays!
* Six Acres - lots of bottled beers and pub grub and staggering distance from Irish Heather
* Irish Heather - Guiness! and decent pub grub!
* [http://www.yelp.ca/biz/guilt-and-co-vancouver Guilt & Co] Luxurious cocktails, hotties and board games!

===Coffee drinks===
(FYI: Vancouverites are *serious* about coffee places.)
* [http://www.yelp.ca/biz/revolver-vancouver Revolver] (the boss)
* [http://www.yelp.ca/biz/acme-caf%C3%A9-vancouver-4 Acme] (for when you want to impress)
* [http://www.yelp.ca/biz/east-van-roasters-vancouver East Van Roasters] (tiny, cute, chocolate involved)
* [http://www.yelp.ca/biz/nelson-the-seagull-vancouver Nelson the Seagull] (next to East Van Roasters, better for longer stays, fresh-made bread too)
* Timbertrain [wooden, Gastowny, "hip"]

== Other ==

* Chiropractor
* Massage Therapist
** i've used Sitka Therapeutic in basement of Georgia Hotel -- da
** Pacific Coast Massage Therapy
** Vancouver College of Massage Therapy student clinic (http://vcmt.ca/our-clinic/)
* Gym
** YWCA http://www.ywcahealthandfitness.com/content/FACILITIES/64/1/0
** Steve Nash http://www.snclubs.com/locations/fitness-world/
* Haircuts
** For ladies, [http://www.yelp.ca/biz/lisas-chop-shop-vancouver Lisa's Chop Shop] is down the road, cheaper than most, and great, especially if you have dyed hair and like rockabily music. Ask for Jen, who is lovely.
** For mostly men but they do women too: JD's barbershop is close. Unpredictable results if you don't have a specific person.
* Yoga Studio
** One Yoga For The People http://oneyogaforthepeople.ca/
** Blue Egg http://blueeggstudios.com/
* Physio Therapist
* Dentist
** Harbour Centre Dental http://www.harbourcentredental.com/
** Andrew Shannon http://www.dr-shannon.com (Bentall Centre)
** i'm satisfied w/ http://dentalclinicrobson.com/
* Walk in Clinic
* Dance Studio
** Blue Egg http://blueeggstudios.com/
* Spa
* Sensory isolation tanks: http://www.floathouse.ca/
* Sauna
** Hastings Steam http://www.hastingssteamandsauna.com/
* Acupuncturist
* Nutritionist
* Walking trails
** Crab Park
** Sea Wall north side (Burrard Inlet, Stanley Park)
** Sea Wall south side (False Creek)

Vancouver

2014-06-26T18:31:31Z

DavidA: /* Other */

Vancouver

2014-06-26T18:29:59Z

DavidA:

Mobile Opportunity

2014-05-27T23:13:39Z

DavidA: /* Tasks */

== Summary ==

This is a cross-Mozilla research project investigating how to put the power of the web in more hands, in more places— particularly emerging digital economies.

__TOC__
= Roles =

* Responsible: Product Manager (TBD), Design Lead (TBD), Development Contractor (TBD)
* Accountable: David Ascher

= Project Budget =
* TBD

= Project Calendar =

See calendar of [https://wiki.mozilla.org/Mobile_Opportunity/Calendar planned activities]

== Tasks ==
<onlyinclude>
<bugzilla>
{
"whiteboard": "[mobile-opportunity]",
"status":["NEW","REOPENED","ASSIGNED"],
"include_fields": "id, summary, assigned_to, status, last_change_time",
"maxrows":"100",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>

= What, How, and Why =

== What We’re Going To Do Now ==
* Create prototypes for on-device app authoring (proposed owner: Bryan Clark)
* Test these prototypes in the field in key Firefox OS markets (proposed owner: new program manager hire)
* Produce competitive insights based on consumer segmentation in key markets (confirmed owner: Ria Joy)
* Secure 3 major philanthropic partnerships to fund and amplify project (i.e., GSMA, Gates, Mastercard, Omidyar, USAid). (confirmed owner: Ben Moskowitz)

== What We’re Going To Do Six Months From Now ==
* Lead a formal PRD for on-device apps authoring as part of Firefox OS (proposed owner: Maureen Hanratty/Tony Santos?)
* Weave into brand / marketing story and celebrate at MWC 2015 (confirmed owner: Pete Scanlon/Mary Ellen Muckerman)
* Commission, review and greenlight business plans, as appropriate (proposed owner: Rick Fant)

== How It Will Work ==

Create a “core project team” comprised of cross-section of FTEs on a 6 month special assignment.

The roles in this team are still TBD, but likely consist of at least:

* Product manager: requirements gathering, stakeholder validation, etc (maybe Bryan Clark?)
* Project coordinator: ensuring strong communication within the team, to other Mozilla stakeholders, and to local teams
* Interaction & prototype design: everything from paper prototypes to wireframes that can be assessed in field tests and other user testing scenarios
* Developers, with a particular focus on rapid prototyping / iteration, good UX instinct

This team will work closely with Ben Moskowitz and David Ascher, and periodically report into the Steering Committee. No HR changes to take place for existing staff (they would be seconded to the project for a fixed duration).

== Why It Matters ==

On-device app authoring could dramatically grow the supply of local apps in emerging markets, which could differentiate Firefox OS and the web platform and drive both consumer and operator demand. Though risky, a breakthrough user-facing innovation like this could re-energize partner, contributor, and user interest in Mozilla and its products. Our window of opportunity to realize these kinds of breakthrough innovations is small.

= Resources =

==Advisors==

* Ben Moskowitz: program strategist, director of philanthropic partnerships
* Ria Joy: advise on partner research agenda, product strategy
* Harald Kirschner: advise on Marketplace / carrier API integration
* Michael Henretty: advise on Gaia optimization
* Rina Jensen: advise content trends
* Rory Petty: advise on program design
* Michelle Thorne: Webmaker and Reps community
* Emily Goligoski: user research lead

==Key community members==
* Andre Garzia: technologist/community liaison coordinating Brazil pilots
* Ricardio Panaggio: technologist/community liaison coordinating Brazil pilots
* Aschickur Raman: technologist/community liaison coordinating Bangladesh pilots
* Mahay Alam Khan: technologist/community liaison coordinating Bangladesh pilots
* TBD: technologist/community liaison coordinating India pilots
* TBD: technologist/community liaison coordinating India pilots
* TBD: technologist/community liaison coordinating African pilots
* TBD: technologist/community liaison coordinating African pilots

==Executive support==

*Chris Beard
*Mark Surman
*Pete Scanlon
*Rick Fant

= Documentation and research =

* [https://www.dropbox.com/sh/i810i10a2v5eev7/AABky5kJ3iBb3SJ9D1fPfF0oa Introductory Slide Deck]
* [https://wiki.mozilla.org/AppMaker Appmaker]
* [https://www.dropbox.com/s/xzu0b1svjb8lokz/Mozilla_ConceptRefine.pdf Firefox OS Concept Refinement]
* [https://www.dropbox.com/s/z7hu056b9zgbooh/Mozilla_concept_documentation.pdf Firefox OS Demo Documentation: Mozillapps and Just For You]

Mobile Opportunity

2014-05-27T23:12:50Z

DavidA: /* How It Will Work */

== Summary ==

This is a cross-Mozilla research project investigating how to put the power of the web in more hands, in more places— particularly emerging digital economies.

__TOC__
= Roles =

* Responsible: Product Manager (TBD), Design Lead (TBD), Development Contractor (TBD)
* Accountable: David Ascher

= Project Budget =
* TBD

= Project Calendar =

See calendar of [https://wiki.mozilla.org/Mobile_Opportunity/Calendar planned activities]

== Tasks ==
<onlyinclude>
<bugzilla>
{
"whiteboard": "[mobile-opportunity]",
"status":["NEW","REOPENED","ASSIGNED"],
"include_fields": "id, summary, whiteboard, assigned_to, status, last_change_time",
"maxrows":"100",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>

= What, How, and Why =

== What We’re Going To Do Now ==
* Create prototypes for on-device app authoring (proposed owner: Bryan Clark)
* Test these prototypes in the field in key Firefox OS markets (proposed owner: new program manager hire)
* Produce competitive insights based on consumer segmentation in key markets (confirmed owner: Ria Joy)
* Secure 3 major philanthropic partnerships to fund and amplify project (i.e., GSMA, Gates, Mastercard, Omidyar, USAid). (confirmed owner: Ben Moskowitz)

== What We’re Going To Do Six Months From Now ==
* Lead a formal PRD for on-device apps authoring as part of Firefox OS (proposed owner: Maureen Hanratty/Tony Santos?)
* Weave into brand / marketing story and celebrate at MWC 2015 (confirmed owner: Pete Scanlon/Mary Ellen Muckerman)
* Commission, review and greenlight business plans, as appropriate (proposed owner: Rick Fant)

== How It Will Work ==

Create a “core project team” comprised of cross-section of FTEs on a 6 month special assignment.

The roles in this team are still TBD, but likely consist of at least:

* Product manager: requirements gathering, stakeholder validation, etc (maybe Bryan Clark?)
* Project coordinator: ensuring strong communication within the team, to other Mozilla stakeholders, and to local teams
* Interaction & prototype design: everything from paper prototypes to wireframes that can be assessed in field tests and other user testing scenarios
* Developers, with a particular focus on rapid prototyping / iteration, good UX instinct

This team will work closely with Ben Moskowitz and David Ascher, and periodically report into the Steering Committee. No HR changes to take place for existing staff (they would be seconded to the project for a fixed duration).

== Why It Matters ==

On-device app authoring could dramatically grow the supply of local apps in emerging markets, which could differentiate Firefox OS and the web platform and drive both consumer and operator demand. Though risky, a breakthrough user-facing innovation like this could re-energize partner, contributor, and user interest in Mozilla and its products. Our window of opportunity to realize these kinds of breakthrough innovations is small.

= Resources =

==Advisors==

* Ben Moskowitz: program strategist, director of philanthropic partnerships
* Ria Joy: advise on partner research agenda, product strategy
* Harald Kirschner: advise on Marketplace / carrier API integration
* Michael Henretty: advise on Gaia optimization
* Rina Jensen: advise content trends
* Rory Petty: advise on program design
* Michelle Thorne: Webmaker and Reps community
* Emily Goligoski: user research lead

==Key community members==
* Andre Garzia: technologist/community liaison coordinating Brazil pilots
* Ricardio Panaggio: technologist/community liaison coordinating Brazil pilots
* Aschickur Raman: technologist/community liaison coordinating Bangladesh pilots
* Mahay Alam Khan: technologist/community liaison coordinating Bangladesh pilots
* TBD: technologist/community liaison coordinating India pilots
* TBD: technologist/community liaison coordinating India pilots
* TBD: technologist/community liaison coordinating African pilots
* TBD: technologist/community liaison coordinating African pilots

==Executive support==

*Chris Beard
*Mark Surman
*Pete Scanlon
*Rick Fant

= Documentation and research =

* [https://www.dropbox.com/sh/i810i10a2v5eev7/AABky5kJ3iBb3SJ9D1fPfF0oa Introductory Slide Deck]
* [https://wiki.mozilla.org/AppMaker Appmaker]
* [https://www.dropbox.com/s/xzu0b1svjb8lokz/Mozilla_ConceptRefine.pdf Firefox OS Concept Refinement]
* [https://www.dropbox.com/s/z7hu056b9zgbooh/Mozilla_concept_documentation.pdf Firefox OS Demo Documentation: Mozillapps and Just For You]

Mobile Opportunity

2014-05-27T23:12:29Z

DavidA: /* How It Will Work */

== Summary ==

This is a cross-Mozilla research project investigating how to put the power of the web in more hands, in more places— particularly emerging digital economies.

__TOC__
= Roles =

* Responsible: Product Manager (TBD), Design Lead (TBD), Development Contractor (TBD)
* Accountable: David Ascher

= Project Budget =
* TBD

= Project Calendar =

See calendar of [https://wiki.mozilla.org/Mobile_Opportunity/Calendar planned activities]

== Tasks ==
<onlyinclude>
<bugzilla>
{
"whiteboard": "[mobile-opportunity]",
"status":["NEW","REOPENED","ASSIGNED"],
"include_fields": "id, summary, whiteboard, assigned_to, status, last_change_time",
"maxrows":"100",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>

= What, How, and Why =

== What We’re Going To Do Now ==
* Create prototypes for on-device app authoring (proposed owner: Bryan Clark)
* Test these prototypes in the field in key Firefox OS markets (proposed owner: new program manager hire)
* Produce competitive insights based on consumer segmentation in key markets (confirmed owner: Ria Joy)
* Secure 3 major philanthropic partnerships to fund and amplify project (i.e., GSMA, Gates, Mastercard, Omidyar, USAid). (confirmed owner: Ben Moskowitz)

== What We’re Going To Do Six Months From Now ==
* Lead a formal PRD for on-device apps authoring as part of Firefox OS (proposed owner: Maureen Hanratty/Tony Santos?)
* Weave into brand / marketing story and celebrate at MWC 2015 (confirmed owner: Pete Scanlon/Mary Ellen Muckerman)
* Commission, review and greenlight business plans, as appropriate (proposed owner: Rick Fant)

== How It Will Work ==

Create a “core project team” comprised of cross-section of FTEs on a 6 month special assignment.

The roles in this team are still TBD, but likely consist of at least:

* Product design: requirements gathering, stakeholder validation, etc (maybe Bryan Clark?)
* Project coordinator: ensuring strong communication within the team, to other Mozilla stakeholders, and to local teams
* Interaction & prototype design: everything from paper prototypes to wireframes that can be assessed in field tests and other user testing scenarios
* Developers, with a particular focus on rapid prototyping / iteration, good UX instinct

This team will work closely with Ben Moskowitz and David Ascher, and periodically report into the Steering Committee. No HR changes to take place for existing staff (they would be seconded to the project for a fixed duration).

== Why It Matters ==

On-device app authoring could dramatically grow the supply of local apps in emerging markets, which could differentiate Firefox OS and the web platform and drive both consumer and operator demand. Though risky, a breakthrough user-facing innovation like this could re-energize partner, contributor, and user interest in Mozilla and its products. Our window of opportunity to realize these kinds of breakthrough innovations is small.

= Resources =

==Advisors==

* Ben Moskowitz: program strategist, director of philanthropic partnerships
* Ria Joy: advise on partner research agenda, product strategy
* Harald Kirschner: advise on Marketplace / carrier API integration
* Michael Henretty: advise on Gaia optimization
* Rina Jensen: advise content trends
* Rory Petty: advise on program design
* Michelle Thorne: Webmaker and Reps community
* Emily Goligoski: user research lead

==Key community members==
* Andre Garzia: technologist/community liaison coordinating Brazil pilots
* Ricardio Panaggio: technologist/community liaison coordinating Brazil pilots
* Aschickur Raman: technologist/community liaison coordinating Bangladesh pilots
* Mahay Alam Khan: technologist/community liaison coordinating Bangladesh pilots
* TBD: technologist/community liaison coordinating India pilots
* TBD: technologist/community liaison coordinating India pilots
* TBD: technologist/community liaison coordinating African pilots
* TBD: technologist/community liaison coordinating African pilots

==Executive support==

*Chris Beard
*Mark Surman
*Pete Scanlon
*Rick Fant

= Documentation and research =

* [https://www.dropbox.com/sh/i810i10a2v5eev7/AABky5kJ3iBb3SJ9D1fPfF0oa Introductory Slide Deck]
* [https://wiki.mozilla.org/AppMaker Appmaker]
* [https://www.dropbox.com/s/xzu0b1svjb8lokz/Mozilla_ConceptRefine.pdf Firefox OS Concept Refinement]
* [https://www.dropbox.com/s/z7hu056b9zgbooh/Mozilla_concept_documentation.pdf Firefox OS Demo Documentation: Mozillapps and Just For You]

Mobile Opportunity

2014-05-27T22:58:02Z

DavidA:

== Summary ==

This is a cross-Mozilla research project investigating how to put the power of the web in more hands, in more places— particularly emerging digital economies.

__TOC__
= Roles =

* Responsible: Product Manager (TBD), Design Lead (TBD), Development Contractor
* Accountable: David Ascher
* Needed: Engineering vendor

= Project Budget =
* TBD

= Project Calendar =

See calendar of [https://wiki.mozilla.org/Mobile_Opportunity/Calendar planned activities]

== Tasks ==
<onlyinclude>
<bugzilla>
{
"whiteboard": "[mobile-opportunity]",
"status":["NEW","REOPENED","ASSIGNED"],
"include_fields": "id, summary, whiteboard, assigned_to, status, last_change_time",
"maxrows":"100",
"order": "last_change_time"
}
</bugzilla>
</onlyinclude>

= What, How, and Why =

== What We’re Going To Do Now ==
* Create prototypes for on-device app authoring (proposed owner: Bryan Clark)
* Test these prototypes in the field in key Firefox OS markets (proposed owner: new program manager hire)
* Produce competitive insights based on consumer segmentation in key markets (confirmed owner: Ria Joy)
* Secure 3 major philanthropic partnerships to fund and amplify project (i.e., GSMA, Gates, Mastercard, Omidyar, USAid). (confirmed owner: Ben Moskowitz)

== What We’re Going To Do Six Months From Now ==
* Lead a formal PRD for on-device apps authoring as part of Firefox OS (proposed owner: Maureen Hanratty/Tony Santos?)
* Weave into brand / marketing story and celebrate at MWC 2015 (confirmed owner: Pete Scanlon/Mary Ellen Muckerman)
* Commission, review and greenlight business plans, as appropriate (proposed owner: Rick Fant)

== How It Will Work ==

Create a “core project team” comprised of cross-section of FTEs on a 6 month special assignment. This team to be led by a product manager (Bryan Clark proposed), who will work closely with Ben Moskowitz and David Ascher, and periodically report into the Steering Committee. No HR changes to take place.

== Why It Matters ==

On-device app authoring could dramatically grow the supply of local apps in emerging markets, which could differentiate Firefox OS and the web platform and drive both consumer and operator demand. Though risky, a breakthrough user-facing innovation like this could re-energize partner, contributor, and user interest in Mozilla and its products. Our window of opportunity to realize these kinds of breakthrough innovations is small.

= Resources =

==Advisors==

* Ben Moskowitz: program strategist, director of philanthropic partnerships
* Ria Joy: advise on partner research agenda, product strategy
* Harald Kirschner: advise on Marketplace / carrier API integration
* Michael Henretty: advise on Gaia optimization
* Rina Jensen: advise content trends
* Rory Petty: advise on program design
* Michelle Thorne: Webmaker and Reps community
* Emily Goligoski: user research lead

==Key community members==
* Andre Garzia: technologist/community liaison coordinating Brazil pilots
* Ricardio Panaggio: technologist/community liaison coordinating Brazil pilots
* Aschickur Raman: technologist/community liaison coordinating Bangladesh pilots
* Mahay Alam Khan: technologist/community liaison coordinating Bangladesh pilots
* TBD: technologist/community liaison coordinating India pilots
* TBD: technologist/community liaison coordinating India pilots
* TBD: technologist/community liaison coordinating African pilots
* TBD: technologist/community liaison coordinating African pilots

==Executive support==

*Chris Beard
*Mark Surman
*Pete Scanlon
*Rick Fant

= Documentation and research =

* [https://www.dropbox.com/sh/i810i10a2v5eev7/AABky5kJ3iBb3SJ9D1fPfF0oa Introductory Slide Deck]
* [https://wiki.mozilla.org/AppMaker Appmaker]
* [https://www.dropbox.com/s/xzu0b1svjb8lokz/Mozilla_ConceptRefine.pdf Firefox OS Concept Refinement]
* [https://www.dropbox.com/s/z7hu056b9zgbooh/Mozilla_concept_documentation.pdf Firefox OS Demo Documentation: Mozillapps and Just For You]

User:Ckoehler/About wiki.mozilla.org

2014-05-09T23:10:07Z

DavidA: /* Comments */

{| class="wikitable"
|+ style="text-align:left; padding: 5px;" | Request for Comments
|-
| style="width: 20%; text-align: right; padding: 5px;" | '''date created''' || 2014-05-09
|-
| style="width: 20%; text-align: right; padding: 5px;" | '''comments deadline''' || style="color:red;" | 2014-05-26 14:00 UTC
|-
| style="width: 20%; text-align: right; padding: 5px;" | '''contributors''' || [[User:Ckoehler | Christie Koehler]], Lyre Calliope, Gordon Hemsley, Justin Crawford, Larissa Shapiro, Jennie Rose Halperin, Mark A. Hershberger, and Jason Crowe.
|-
| style="width: 20%; text-align: right; padding: 5px;" | '''status''' || draft
|-
| style="width: 20%; text-align: right; padding: 5px;" | '''To make comments:''' || Edit this page, putting your comments in the [[#Comments]] section. Include <nowiki>~~~~</nowiki> without the "nowiki" tags to include your signature.
|}

{| class="wikitable"
|-
| '''Preamble:''' The [[Contribute/Education/Wiki_Working_Group | Wiki Working Group]] has formed to kick-start a revitalization of the wiki and to create a framework for empowering the entire Mozilla community to participate in and sustain this revitalization effort. A first step in this revitalization effort is this '''About''' page, which seeks to clarify the ''purpose'', ''scope'' and ''governance'' of the Mozilla Wiki. Once adopted, this text will reside at [[About]] and serve as our guide for interacting and making decisions about wiki.mozilla.org.

We are actively seeking comments from our community until '''26 May 2014'''. Those comments will be considered and incorporated and this page adopted into the wiki by 15 June 2014. In review this document, please consider the following questions as you review and make your comments:

* what about the content does or does not make sense to you?
* what about the content does or does not resonate with you?
* to what extent does the content match your vision for wiki.mozilla.org?
* to what extend can you support the purpose, scope and governance structured described?
|}

== Purpose ==
This wiki (wiki.mozilla.org, AKA MozillaWiki or WikiMO) is the official public wiki of the Mozilla Project. It is the encyclopedia of the project and is intended to contain comprehensive and dynamic information about Mozilla products, initiatives and sub-projects.

Additionally, the wiki seeks to facilitate lively community interaction that empowers contributors to coordinate activities, find support, and make their projects accessible to other contributors across Mozilla.

== How is the Wiki a critical resource to the Mozilla Project? ==

'''The Wiki provides the most comprehensive, overall picture of Mozilla's mission, strategy, and history.''' Information on the wiki tells the story of Mozilla and makes the organization navigable in a way that no other single resource does. The wiki, along with [https://bugzilla.mozilla.org Bugzilla] and our [https://www.mozilla.org/about/forums/ forums], form the core of Mozilla's long-term institutional record.

'''The Wiki is a significant entry point for contributors into the Mozilla project.''' It serves as a primary and massively scalable on-boarding tool because it provides the opportunity for self-serve contribution pathways across all areas of the project. The wiki enables self-motivated individuals to take advantage of contribution opportunities immediately. The better organized the wiki, the more people are able to take advantage of these opportunities.

'''Publicly available wikis, code repositories, and bug trackers are essential to our collaborative environment and connect our project to the greater open source eco-system.''' These tools are part of the established canon of open source organizational tools because they make the knowledge and tools required to participate immediately available to those who are interested. Experienced open source participants benefit from Mozilla providing these tools because it is what they are accustomed to, and those new to open source benefit because it prepares them for working with other projects in the open source ecosystem.

== What content is appropriate for the Wiki? ==

* Any content pertaining to Mozilla's products, initiatives and sub-projects that is '''not''' end-user documentation or developer documentation.
* Any content pertaining to Mozilla's mission, strategy or history.
* Any content that supports Mozilla's mission or community.
* Any content that is related to the on-going planning, coordination or other contribution activities of Mozilla projects.
* Any content related to the discussion of content on the wiki (e.g. Talk/Discussion pages).
* Any content that is related to helping people use the Wiki.

Content appearing to be completely unrelated to Mozilla and not falling into any of the categories above may be deleted as spam or moved elsewhere.

'''End-user documentation''' is written for users of Mozilla's products and explains how are products work and how to use them. In general, this type of content belongs on [http://support.mozilla.org SUMO].

'''Developer documentation''' is written for programmers developing for Mozilla products like Firefox as well as the Open Web. This type of content includes technical reference information for programming languages and platforms and is most suited for [http://developer.mozilla.org MDN].

== Who own and maintains the Mozilla wiki? ==

The wiki is owned and maintained by the Mozilla community.

* '''Infrastructure''' for the wiki is provided by Mozilla Corp.
* '''Governance''' issues are managed by the [[Modules/Mozilla_Websites#WikiMo | WikiMo module]], a sub-module of Websites. Its current module owner is [[User:Ckoehler | Christie Koehler]] and module peers are [[User:CaptainCalliope | Lyre Calliope]] and [[User:GPHemsley | Gordon Hemsley]].
* '''Technical Support''' is provided jointly by the community and MoCo staff.
* '''Content''' is managed by the community. Information here is public and can be modified by anyone in the Mozilla community with sufficient interest and knowledge to improve it (and an account).

== Where can I report issues with wiki.mozilla.org? ==

* '''Technical''' issues should be reported via [https://bugzilla.mozilla.org/enter_bug.cgi?product=Websites&component=wiki.mozilla.org bugzilla]. These include server or client-side errors, styling issues, problems with accounts or logging in, and feature requests.
* '''Content''' issues should be addressed on the wiki itself using Talk/Discussion pages whenever possible.

General questions can be addressed to [https://www.mozilla.org/about/forums/#tools-wiki tools-wiki] or #wiki on irc.mozilla.org.

= Comments =

Tips for adding comments:
* Include <nowiki>~~~~</nowiki> (without "nowiki" tags) as the last text of your comment to include your signature.
* Indent text to reply with a colon <nowiki>:</nowiki>

Examples:

This is is the first comment! [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 12:53, 7 May 2014 (PDT)
: this is the first reply! [[User:Ckoehler|Christie Koehler (ckoehler)]] ([[User talk:Ckoehler|talk]]) 12:53, 7 May 2014 (PDT)

Add your comments and suggestions here:

'''About Developer documentation''': A lot of information on how to build and fix things are contained currently in the wiki and not the MDN. I'm faulty of that. Would you recommend that anything which is technically related and/or offer guidance on how to operate in the activity should be pushed to MDN. If yes it would be good to activate Inter wiki links to make it possible to benefit of redirections in between the two entities. For example in Web Compatibility how would we classify [[Compatibility/Guide|Guide]] and [[Compatibility/Mobile/WipeOutUAOverides#Updating_the_UA_override_list|Updating]]. I'm not sure it will be easy to do. Maybe a different way to go about it is to encourage people to think about it when they create a new page.[[User:Karlcow|Karlcow]] ([[User talk:Karlcow|talk]]) 15:40, 9 May 2014 (PDT)

'''About WikiMo''': The about page says currently "Governance issues are managed by the WikiMo module, a sub-module of Websites." but it doesn't explain what is WikiMo and the link goes to a table which is not really about Governance. Is there a more appropriate place on the wiki or elsewhere? [[User:Karlcow|Karlcow]] ([[User talk:Karlcow|talk]]) 15:46, 9 May 2014 (PDT)

'''David's comments''': The only thing that I’d add to the scope is that I think it’d be good to apply a bit of a product/UX lens to the wiki as a community infrastructure, because I believe it will result in more use, more people caring and valuing it, and a general virtuous cycle. Wikis in my experience work if a) the content is well gardened (just like any “content” site), and b) people find authoring & editing to be a fun, pleasant, productive experience (just like any other authoring product). Just because we say it's where stuff “should be” isn’t enough. To that end, I’ll opine that:

* performance of an editing tool is critical to its continued use — it’s true for IDEs, it’s true for word processors, and it’s a place where wikis have traditionally been fairly weak, because of their dawn in the earliest age of CGI, etc. I have the impression that perf on wiki.m.o writes has gone up, and that’s great, and we need to do more to improve perceived perf. As a thought-provoking point: editing an etherpad feels 100x faster to me (even if it’s obviously different).
* we need to encourage, train, and recognize & herald wiki gardeners. (Matt Thompson for example is doing a _stellar_ job of doing that and teaching others how to do that for Webmaker content).
* there’s a lot about wikimedia which feels hasn’t really kept up with our collective expectations around authoring environments. Case sensitivity of pages; wikimedia markup in general, clunky authoring environments, etc. There may be more configuration tweaks & add-ons that we could deploy, I’m not an expert there.
* the default skin is way better than it used to be and the pages are less painful to my eye anyway than before — we can still do more.
* having someone act as a product manager for wiki.m.o (and for example care and measure things like daily actives, etc. as a metric of utility of the wiki to the org) would be good — anyone can do that, and I and many others would be happy to coach that person on how to be a product manager with a soul if that coaching was desired.
* there are people with wiki.m.o superpowers, and we should figure out how to get those superpowers more evenly distributed. [and make it so that some of the things those folks can do don’t require super-anything]
* there’s an obvious elephant-in-the-room about wiki.m.o vs. Mana and why we need two. That duality doesn’t bug me too much, but I know it bugs others. Understanding the reason why people use one or the other feels like a good thing to get shared understanding of, even if not everyone will agree w/ the specific decisions.
[[User:DavidA|DavidA]] ([[User talk:DavidA|talk]]) 16:10, 9 May 2014 (PDT)

WeeklyUpdates/2014-02-10

2014-02-10T16:51:26Z

DavidA: /* Speakers */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of Mozilla [[Image:Tree.gif|Friends of Mozilla]] ==

*A BIG THANKS to Aaron Mandel for shooting great video b-roll of the Toronto office for the upcoming press activities around MWC.
*Thanks to Chris Peterson for donating some time to help the People Team learn more about trains, channels, and testing.
*Thank you to the incredible team of Mozilla Hispano contributors who answer all Firefox OS support questions in Spanish: AndresMorelos, willyaranda, Nukeador, Gioyik, lestherbj, magiksen, and Feiticeiro.
*Many thanks to the superheroes who localize Firefox OS support documentation: inma_610, Pedro García Rodríguez, deimidis, Guillermo López Leal, Angela Velo, RickieES, Nukeador, Maria Solà, and Ximena Lasserre. You are the amazing smiling face of Mozilla Support to the Spanish-speaking users of Firefox OS!

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
This Monday we having another session of making metal tags at lunch in
the SF Commons and MV office at 12:30PST.

The Crafty group wants to recognize contributors with handmade items.
We need you to tell us who you would like to recognize! Also, we would
love you to make crafts with us (no special skills required).

We will be creating handmade gifts. You give us the name, address and
even a very short message, we will send a gift. It would make it more
special if you came and made it yourself, but geographical and time
restrictions are understood and we are happy to be your hammer
swinging stand in. We can probably only do this for the first 20
responders. If there are more, maybe we can do it again!

For contributors you would like recognized we need:
-- Name
-- Physical mailing address of some sort (nearest Mozilla office the frequent?)
-- Some kind of short approx 15 character or less message or we can just
write a generic "Thank you". But the cool thing is that these can be
customized so think personal.
-- IRC handle? It fits nicely on a tag usually.

Please send this information to 831sabina.brown at gmail.com

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

* The '''Open Badges team''' will be at the [http://www.reconnectlearning.org/summit/ Summit to Reconnect Learning] Tuesday and Wednesday of this week - [https://wiki.mozilla.org/WeeklyUpdates/2014-02-10#Open_Badges more details below.]

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Project Status Updates (voice updates) ==

=== Firefox Desktop ===
''Speaker Location:''

=== Firefox Mobile ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:''

=== [https://webmaker.org/ Webmaker] ===
''Speaker Location: Lindsey Frost Cleary (Chattanooga)''

Gigabit Community Fund launches!
*Kick-off event in Chattanooga, Tennessee drew more than 200 educators, civic leaders, and community members to launch the fund, which will help establish Gigabit Hive Learning Communities in both Chattanooga and Kansas City, and enable local organizations to take advantage of their gigabit networks to build applications that have immediate impact on education and workforce development.
*Official launch in Kansas City is this Thursday!
*The Fund application window will open in late February. You can stay up to date at [http://mozilla.org/gigabit our awesome new website], or via twitter, @mozillagigabit.

=== [https://openbadges.org/ Open Badges] ===
''Speaker Location: nonverbal''

The Open Badges team will be making 4 big announcements at this week's [http://www.reconnectlearning.org/summit/ Summit to Reconnect Learning]:

*'''Big Players to issue Open Badges:''' We will be announcing 5 new, large organizations that will be committing to exploring the integration of Open Badges within their communities and platforms. The names are confidential until this Thursday, so we will fill you in on next week or keep an eye on @OpenBadges for real-time updates.
*'''Cities of Learning 2014:''' We will be announcing 10 cities who are committing to implementing the Cities of Learning (COL) badging model, based on the success of the Chicago Summer of Learning initiative last year.
*'''Cities of Learning Tech Package:''' To support the Cities of Learning initiative, we will be announcing the COL Tech package that will be powered by Mozilla, Digital Youth Network, and additional partners. This will include access to a shared technology infrastructure built off BadgeKit's foundational tools to support each cities' badge system needs.
*'''Badge Alliance:''' We will be announcing a new alliance that is forming to support the growing Open Badges ecosystem. More details to come next week.

=== [https://mozillascience.org/ Mozilla Science Lab] ===
''Speaker Location:''

=== Mozilla Reps ===
''Speaker Location:Gabes''

=== Firefox Student Ambassador ===
''Speaker Location: Written Update''

Congratulations to our January winners:
*App of the Month: Abin Abraham's [https://marketplace.firefox.com/app/diary My Diary] app
*Campus Affiliates Contest: AMU Firefox Club

Want weekly updates on what is going on in the program? Check out our [https://blog.mozilla.org/studentambassadors/ blog] for more information.

=== Grow Mozilla ===
''Speaker Location:''

=== Identity ===
''Speaker Location:''

=== Services ===
''Speaker Location:''

=== Firefox Marketplace ===
''Speaker Location:''

=== IT ===
''Speaker Location:''

=== Web Compatibility ===
''Speaker Location: ATX (miketaylr)''

* [https://bugzilla.mozilla.org/show_bug.cgi?id=809796 ESPN.com] now sends Firefox for Android to tier 1 mobile site. \o/
* [https://bugzilla.mozilla.org/show_bug.cgi?id=896014 Paypal checkout] for Firefox OS stays in mobile site now.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=958495 tripit.com], [https://bugzilla.mozilla.org/show_bug.cgi?id=964610 slate.fr], [https://bugzilla.mozilla.org/show_bug.cgi?id=827668 scribd.com], [https://bugzilla.mozilla.org/show_bug.cgi?id=884290 broadway.com], [https://bugzilla.mozilla.org/show_bug.cgi?id=828401 ingdirect.es] all now correctly send FxOS to mobile versions.
* [https://bugzilla.mozilla.org/show_bug.cgi?id=763518 wikipedia.org] mobile meta bug bites the dust (9 issues fixed).
* Significant progress on device detection framework bugs: [https://bugzilla.mozilla.org/show_bug.cgi?id=962160 962160] [https://bugzilla.mozilla.org/show_bug.cgi?id=957205 957205] [https://bugzilla.mozilla.org/show_bug.cgi?id=916250 916250] [https://bugzilla.mozilla.org/show_bug.cgi?id=963705 963705] all fixed (see [http://miketaylr.github.io/arewedetectableyet/ AreWeDetectableYet] to track progress).

[https://bugzilla.mozilla.org/form.mobile.compat Report mobile site compat bugs].

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
| Pete Scanlon
| Engagement
| MWC 2014 Update
| San Francisco - Commons
| No
|
| Last week's brownbag: https://air.mozilla.org/mwc-brownbag/ and http://www.mozilla.org/mwc/
|-
| Rick Fant, David Ascher
|
| Update about Labs
| San Francisco + Vidyo
| No
|
|
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location

|-
| ''Med Ali Batita , Wael Meji , Hamza Latrach , Ramzi Meguelbi''
| ''Marwa BATITA?''
| ''ISET Gbaes''

|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

==== Social Support ====

CloudServices/Presence

2013-11-07T17:09:11Z

DavidA: /* AppMaker */

{{LastUpdated}}

{{Draft}}

=''Presence''=

==Overview==
The goal of Mozilla Presence is to provide a way for applications to know when their users are online,
even if they don't have the application running.

XXX find a better sentence here

==Project Contacts==
''Principal Point of Contact'' - Tarek Ziadé tarek@mozilla.com

''IRC'' - #presence-wg

''Group Email'' - [https://mail.mozilla.org/listinfo/wg-presence wg-presence@mozilla.org]

==Goals==
How will you know things are working?
What problems does this solve?

==Use Cases==

=== Facebook ===

Jeff wants to appear online on Facebook (he's already determined on Facebook who can see him, etc).

He's already installed the Facebook app on his FFOS phone, he goes to the Settings and touch, "Authorize Presence",
his screen loads a doorhanger (provided by Mozilla Presence) asking if he wants to authorize the app.

Jeff clicks "Yes" on the doorhanger page, and the Facebook app waits while Facebook recieves the redirect, stores
his UID, and closes the doorhanger (and likely needs to do something else to register this with the device so that
it will appear in the Presence Settings page).

The next day, Jeff wakes up, and goes to check his e-mail on his phone. Upon seeing his idle drop, the phone's
simple-push client (which is always running) includes an 'O' in its next PING to simplepush to indicate the user
is now online. Mozilla Presence gets notified of this and acts on it to batch the status change to Facebook. The
batch of updates goes to Facebook including Jeff's, so Facebook knows that Jeff is now online, and updates its
database indicating this.

Jeff's friend Marsha goes to Facebook to see if any of her friends are online. Marsha sees that Jeff is now online
and sends a chat request. Facebook uses SimplePush to notify Jeff of the chat request. Jeff sees the chat request

=== AppMaker ===

Sue has signed up to be an appmaker tutor -- Bob is a new appmaker teacher, and is stuck in a workshop, Bob wants to know which of the tutors are available to help w/ a togetherJS session

Sue is an appmaker expert. She previously authorized AppMaker to see her Online Presence - as Jeff did in with
Facebook in the previous story. She also configured her notifications so any message coming from AppMaker
when she's online would display a message on her screen and let her start the app.

Bob is building a cool new application with his class in AppMaker and would like some input from someone. Appmaker maintains a mapping of which helpers are appropriate for which users (e.g. by language skills). He's currently working in AppMaker from his FFOS Phone and sees that Sue is online.

Bob clicks on Sue's name in his contact lists and hit "invite Sue for peer design session".
AppMaker sends a notification to Sue using the Simple Push service.

Sues gets the notification instantly on her phone via her simple-push client and joins Bob on the
design page.

AppMaker uses Together.js so Bob and Sue can interact live on the page.

=== Support ===

(This is about a tentative and unnamed Firefox OS support tool.)

Maria is a Mozillian who wants to helpful to other Firefox OS users. She signs up with a support application (an application that Mozilla creates). She indicates what she knows about, and what languages she speaks.

Javier wants to activate developer mode on his phone, but can't find the right setting. He goes into '''Help > Live Support'''. The phone sends a request to the support app: someone wants support with Settings in es-MX. The application looks in its database of contributors to see who has the appropriate expertise (and language) to help him, and who is online. Among the pool of possible people it selects Maria, and pings her to see if she can provide support. If she doesn't respond then another person is selected from the pool (or maybe many people are asked at once), and if someone else helps Javier then Maria is notified that her help is no longer needed.

Note that Maria would be participating under an alias specific to the support application (though not anonymous), and she will not be fielding support requests all the time (e.g., she may not provide support at work, only after hours).

=== Talkilla ===

XXX

=== SUMO ===

XXX See with Lloyd about the user story there (sumo experts summoned etc)

==Requirements==
* List of requirements
==Get Involved==

== Documents so far ==
[https://etherpad.mozilla.org/ServicesPresence Services Presence Etherpad]

[https://id.etherpad.mozilla.org/presence Identity Presence Etherpad]

=== Meeting Notes ===

[[Services/Roadmaps/Presence/Meetings/notes_20131014]]

[[Services/Roadmaps/Presence/Meetings/notes_20131031]]

=Design=
==Points of Contact==
Engineer - Name contact@info

== General Overview ==

This service is hooked onto SimplePush, such that when a client ping comes in that includes presence info (either O,
A, or U to indicate Online/Away/Unavailable based on the devices Presence policy dictated by the devices user
and its idel time), then SimplePush will broadcast that to Presence somehow, that client id XXYYY is now O/A/U or
whatever. Presence then updates its record and relays the status update to the services the user has authorized.

The service stores records for every user that has Presence 'activated'. The device is tied to the users FxA such
that if the device is lost, when they get a new one they will still identify the same. If/When a client needs to
re-register for SimplePush, the SimplePush client-id is sent to Presence to tie it to the existing FxA record.

Presence stores a set of data (rough schema):

Client-Mappings:
Client-ID | Corresponds to the client-id that is used for SimplePush
FxA-ID | The FxA of the presence user

Presence-Authentications
FxA | The FxA of the presence user
Service-ID | Service ID that the app developer registered for this service
UUID | A unique ID for this user on this service, to avoid leaking the FxA ID
Status | Boolean flag on whether the user currently wants presence broadcast to this service

When the user changes the toggle on their device to turn on/off Presence, their device must be able to
contact our server so that we can update their Presence choice in the Presence-Authentications table.
This is because Presence is broadcast in the background by the SimplePush UA, and we don't want to
have to include a list of all the 'apps' that should get the presence update in every ping request.

When Presence gets a status update from simplepush, it looks up the client-id in the Client-Mappings, then uses that
to lookup all the services in Presence-Authentications that the user wants notified of this change. It filters out
services that the user has currently chosen not to recieve presence. The remaining services have their webhook URL's
called with the UUID and presence change so that the services can decide what they want to do.

To avoid a call for every single status change, the Presence service may batch updates to the various services so
that the webhook URL for each service is only called every 30+ seconds with all the updates intended for it (in the
list POST format explained above).

== Architecture Overview ==

http://ziade.org/presence.jpg

# appmaker asks for a token
# appmaker register to the presence server to ask for presence info - basically a POST with the web hook + the token as an auth
## Bob decides to give appmaker Presence access.
## Bob is redirected with appmaker token to Presence service.
## Bob hits 'Yes' to grant appmaker access to his Presence
## Bob is redirected back to appmaker with token that includes Presence UID (the one you'll get with the update in step 5)
# bob updates his status with the presence
# sarah updates her status with the presence
# the presence service calls the webhook to notify status updates

=== Proposed Modifications to SimplePush ===
SimplePush protocol is [https://wiki.mozilla.org/WebAPI/SimplePush/Protocol defined here].

Principle changes to the protocol involve introducing a change to the "hello" and "ping" packets.

The "hello" packet needs to be modified to include a GUID as the user's Presence ID (PrID). This is required because SimplePush UserAgentIDs (UIAD) can change at any time, where the PrID is more "stable", but only active when the user opts into Presence.

In an effort to save bandwidth, keys are reduced to x + "p" + sub identifier.

old format:

{messageType": "hello", "uaid":"...", "channelIDs":[...]}

new format:

{"messageType": "hello", "uaid":"...", "channelIDs":[...], "'''xpi'''":"..."}

It is important to note that future simplepush reregistrations use the same "xpi" value (if defined). This will allow the SimplePush socket plugin monitor to associate the correct to the correct Presence server.

"ping" packets would use the optional long form and contain the Presence Status (xps).

{"messageType": "ping", "'''xps'''":"(UAO)?"}

A simplepush "ping" packet is exchanged between the client and server when the user's status changes. User's status is indicated by
* "A"way (user is idle or temporarily unavailable)
* "U"navailable (user has gone offline)
* "O"nline

This information would be picked up by the Presence Plug-in to SimplePush which would send the status change to the Presence monitoring system using ''TBD'' REST calls.

=== For App Developers ===

An app developer wishes to get presence information, the following can be addd to the app manifest:

{
"permissions": {
"push": {"description": "To receive notifications about the newest phone releases"},
"presence": {"description": "To broadcast presence"}
},
"messages": [
{"push": "/view_to_launch.html"},
{"push-register": "/view_to_launch.html"}
]
}

Note that the existing bits for SimplePush are retained, as Presence merely add's broadcast of the user's Presence
to the app.

The application developer must register their application separately with Mozilla Presence and set a "Webhook URL"
that will be called with presence updates for users that look like the following:

POST /some/webhook/callback

{[
["UID2949293", "away"],
["UID4823888", "online"],
["UID482838", "offline"],
["UID4828382", "online"]
]}

When the user grants access, your application will get a unique ID that you should associate with the user record
your application stores.

A doorhanger will be needed in applications to prompt the user to grant an application Presence notification data
should the user not grant it initially when installing the app (and for websites that don't necessarilly install
as 'apps').

Setup of a doorhanger will require the app developer to register their application with Mozilla Services and get
an application token. This application token can be used with Mozilla TokenServer to register access with the
Mozilla Presence server. The app developer may then enter the "Webhook URL" in their Settings page for Mozilla
Presence.

When a user signs-in to your application/website and you wish to ask for Presence notifications, you may redirect
the user to Mozilla Services asking for "Presence" access. The user will be prompted to grant access or deny and
redirected back to your application. If the user granted access, the redirect will include an encoded UID that you
should store and associate with the user as this UID will be the one sent in the Webhook calls.

App developers should account for the possibility that 'updates' may get lost, and automatically mark a user as
offline if no status is sent in an hour.

=== For Device Users ===

A separate Settings page is available, that looks similar to the iOS Notifications page, showing a list of apps and
websites that have been granted Presence access. The page also lets one set a "Presence Policy" that determines
what liveliness is communicated, for example:

Presence Policy

Show me online when I've used this device in the past:
5 - 10 - 15 - 20 (minutes)

Show me away when I haven't used this device in at least:
5 - 10 - 15 - 20 (minutes)

Show me offline when I haven't used this device in at least:
10 - 25 - 35 (minutes)

Perhaps these will be sliders, UX is not determined this is only a possible example of how the user determines
what type of 'livliness' data is sent based on whether they're using the device or not, and how recently.

A list of toggles for each app the user has granted access to will be here, so that a user may turn off Presence
for individual apps temporailly without fully revoking possible future Presence broadcasts to the app/website.



==Platform Requirements==
What are the things this needs (OS, language, databases, etc.)?

XXX explain here how simple push is running on the different platforms - Firefox OS : built-in, what about Desktop ? a separate service that wakes up Firefox ?

==Libraries Required==
List of external project dependencies. (Stuff that's not pulled in via the installation script)

==Code Repository==
Links to the published code bases
==Release Schedule==
Predicted code delivery dates
=QA=
==Points of Contact==
Engineer - Name contact@info
==Test Framework==
=Security and Privacy=
Fill out the security & privacy bug template: https://bugzilla.mozilla.org/form.moz-project-review
(https://wiki.mozilla.org/Websites/Kick-Off_Form)

For security reviews, there's:
https://wiki.mozilla.org/Security/ReviewProcess

==Points of Contact==
==Questionnaire Answers==
===1.1 Goal of Feature ===
===2. Potential Threat Vectors and Mitigation Points===
==Review Status==
''Bugzilla Tracking #'' -
see https://wiki.mozilla.org/Security/Reviews
==Issues and Resolutions==

=Operations=

==Points of Contact==
==Deployment Architecture==
''Bugzilla Tracking # '' -
==Escalation Paths==
==Lifespan Support Plans==
=Logging and Metrics=
==Points of Contact==
==Tracking Element Definitions==
==Data Retention Plans==
==Dashboard URL==
=Customer Support=
==Points of Contact==
==Sumo Tags==
==Review Meeting==

WeeklyUpdates/2013-11-04

2013-11-04T19:04:30Z

DavidA: /* Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} */

{{WeeklyUpdateNav}}
{{conf|8600}}

__TOC__

= All-hands Status Meeting Agenda =

Items in this section will be shared during the live all-hand status meeting.

== Friends of the Tree [[Image:Tree.gif|Friends of the Tree]] ==

* Happy Birthday to williamr from all of the Mozilla Community
* Many thanks to bgrins, Gijs, jryans, khuey, mccr8, njn, past, roc, smaug, and ttaubert for dropping everything to investigate and fix the leaks that were keeping the tree closed for 2 days last week.

== Upcoming Events ==

=== This Week ===

=== Monday, {{#time:d F|{{SUBPAGENAME}}}} ===
* 13:00 PST : [https://wiki.mozilla.org/WeeklyUpdates/2013-11-04 SecReview - Simple Push Server]
** vidyo and dial-in details available via the link

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===

* 10:30 PST : [https://appmaker.etherpad.mozilla.org/minutes Appmaker Weekly Meeting]
** come help us deliver upon the promise of Appmaker!
** vidyo and dial-in details available via the link -- 10:30 this week only, usually 10:00

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* 12:00 PST : Brownbag: Firefox OS Field Tests in Colombia: Results and Opportunities
** Learn about a User Experience Research trip to Colombia in August, 2013. We tested our phones on 24 middle-class Colombians for 3 weeks. Find out what happened! Open to Mozilla volunteers and paid staff.

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
* 9:00 PST : [[Manager_Hacking| Manager Hacking]]
** After skipping our October session because of the Summit, ManagerHacking is back for November. With 5 sessions under our belt, this seems like a good time to take stock of the program. To that end, we are interested in hearing what YOU want/need from a program like this. As such, the Nov session will be a planning/brainstorming session led by Dia on future topics and session structure (discussions, presentations, etc). This is your chance to influence the direction of this program!

=== Friday, {{#time:d F|{{SUBPAGENAME}} +4 days}} ===

* 12:00pm to 1:30pm: Community Building workshop in Portland Mozilla Space hosted by [https://mozillians.org/en-US/u/bkerensa/ Benjamin Kerensa]

=== Saturday, {{#time:d F|{{SUBPAGENAME}} +5 days}} ===

=== Sunday, {{#time:d F|{{SUBPAGENAME}} +6 days}} ===

=== Next Week ===

== Product Status Updates (voice updates) ==

=== Firefox Desktop ===
''Speaker Location: toronto (johnath)''
* FF25 looks solid
* Learn to love the '''feature''' keyword in bugzilla
* seer! {{bug|881804}}

=== Firefox Mobile ===
''Speaker Location: (remote) mfinkle''
* Tracking feedback on Fx25 release
* Landed more cleanup and performance improvements to Fx26 and Fx27
* Started planning work for Fx28. See [https://wiki.mozilla.org/Mobile/Notes/30-Oct-2013 team notes] and the [https://wiki.mozilla.org/Mobile/Roadmap#Project_funnel roadmap] for more details.

=== Thunderbird ===
''Speaker Location:''

=== Older Branch Work ===
''Speaker Location:''

=== Webmaker ===
''Speaker Location:'' no verbal update this week
* [https://blog.webmaker.org/mozfest-2013 Mozilla Festival debrief]
* [https://blog.webmaker.org/mozfest_demo_party What we made together at MozFest]

=== Mozilla Reps ===
''Speaker Location:''

=== Identity ===
''Speaker Location:''

=== Services ===
''Speaker Location:''

=== Firefox OS ===
''Speaker Location:' Sandip Kamat (Vidyo)'

* [https://blog.mozilla.org/blog/2013/10/31/telefonica-launches-firefox-os-smartphones-in-mexico-peru-and-uruguay/ Mozilla Blog (10/31/13): After Brazil, Firefox OS now in Mexico, Peru, Uruguay]. With that, FxOS devices are now available in parts of 3 continents (Europe, South America and North America). Thank you, all!
* Version 1.2 (koi+ bugs): Focus on driving [https://bugzilla.mozilla.org/buglist.cgi?j_top=OR&f1=cf_blocking_b2g&o1=equals&query_format=advanced&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&v1=koi%2B&list_id=8375175 1.2 blocker count] to 0. Code Complete 12/16/13. Only blocker bug-fixes accepted hereon!
* Version 1.3: We are in Sprint 4. Please pre-test for no performance regressions as you check-in code.
Sprint 4 = 10/28 - 11/08;
Sprint 5 = 11/11 - 11/22;
Sprint 6 = 11/25 - 12/06;
* Future Versions: FxOS Product long term Roadmap https://wiki.mozilla.org/B2G/Roadmap

=== Grow Mozilla ===
''Speaker Location: San Francisco''

'''Getting to a Million Mozillians'''

Here are some tips and suggestions for people who are interested in learning more about bringing new contributors in to your project.

* Who: You have connected with some volunteers and you're interested in learning about how to build on what's working so more people can join.
** Read Margaret's great [http://blog.margaretleibovic.com/post/57564605991/increasing-volunteer-participation-on-the-firefox-for blog post about increasing participation on the Firefox for Android team] that has 5 helpful tips in it
** Check out the [https://badges.mozilla.org/en-US/badges/awards recently awarded Mozilla badges] to get an idea of how some teams are recognizing contributors.
** Watch a couple of these videos that have been created by community builders for people interested in community building.

{| border="0"
|-
| style="vertical-align:top;" | [[Image:Cbt video jeff brian curtis.png|thumb|[http://www.youtube.com/watch?v=rdJx-90qaSA&feature=youtu.be Tips for Mozilla community mentoring, from the pros]]]
| style="vertical-align:top;" | [[Image:Cbt video margaret michelle rosana laura.png|thumb|[http://popcorn.webmadecontent.org/uur Remix of CBT: Video]]]
|}

{| border="0"
|-
| style="vertical-align:top;" | [[Image:Video community event.png|thumb|[http://www.youtube.com/watch?v=UI911cFMniA&feature=youtu.be How To Run A Mozilla Community Event]]]
| style="vertical-align:top;" | [[Image:Cbt video regnard.png|thumb|[http://popcorn.webmadecontent.org/uxr How To Work With 3 Types of Mozilla Volunteers]]]
|}

== 60 Seconds with Mozilla IT ==
''Speaker Location : San Francisco''

* Welcome Knowles, Opsec
* SRE team had an epic triage and their bug queue dropped by 40%
* Dumitru Gherman presented a session (with Emma Irwin) on Webmaker last week at MozFest
* Mike Poessy @ SFO servicedesk reduced imaging time for windows machines from a couple of hours to 20 mins
* Jake Watkins worked on https://github.com/dividehex/metric-collective, Mark and Q worked on improving Windows imaging for release engineering and Dustin helped setup Puppet for the Auto tools team.

== Speakers ==

The limit is 3 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation. If you plan on showing a video, you need to contact the Air Mozilla team before the day of the meeting or you will be deferred to the next week.

{| class="fullwidth-table"
|-
! Presenter
! Title
! Topic
! Location
! Share?
! Media
! More Details
|-
| Who Are You?
| What Do You Do?
| What are you going to talk about?
| Where are you presenting from? (Moz Space, your house, space)
| Will you be sharing your screen? (yes/no, other info)
| Links to slides or images you want displayed on screen
| Link to where audience can find out more information
|-
|Mathew Caldwell
|Recruiting Cheerleader
|Our new Careers site
|Mountain View
|Yes - My browser to show the new career site
|
|
|-
|Sylvie Veilleux
|VP IT
|Response to question - do we have a plan to migrate away from the proprietary Vidyo client + flash to something based on WebRTC for our meetings? If so, do we have a timeline for this?
|San Francisco (+ Jb remotely, if needed)
|
|
|
|-
|Mike Hoye
|Engineering Community Manager
|DashCon 2014: The Mozilla Dashboarding Convention
|Toronto
|Happening in the Vancouver MozSpace, January 14th, open to all.
|
|A longer post on the way dev-planning shortly.
|}

= Roundtable =

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we'll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

{| class="fullwidth-table"
|-
! Who are you?
! Area of question
! Question
|-
| ''What's your name? What do you work on?''
| ''Is your question about policy, a product, a Foundation initiative, etc.''
| ''What would you like to know?''

|-
|}

= Welcome! =

Let's say hello to some new Mozillians!

== Introducing New Volunteers ==
{| class="fullwidth-table"
|-
! New Volunteer(s)
! Introduced by
! Speaker location
! New Volunteer location
! Will be working on
|-
| ''Who is the new volunteer(s)?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where is the new person based?''
| ''What will the new person be doing?''
|-

|-
|}

== Introducing New Hires ==
{| class="fullwidth-table"
|-
! New Hire
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new hire?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
| Andreas Tolfsen
| Jonathan Griffin
| Toronto
| London
| Marionette and B2G Automation
|-
| Melinda Salazar
| Tony Santos
| Remote
| Remote
| UX Designer
|-
| Vance Chen
| Thomas Ho
| SFO (recorded)
| Taipei
| Firefox OS - Technical Account Manager
|-
|-
| Wilson Page
| Hema Koka
| Mountain View
| London
| Firefox OS - Frontend Software Engineer
|-
|}

== Introducing New Interns ==
{| class="fullwidth-table"
|-
! New Intern
! Introduced by
! Speaker location
! New Hire location
! Will be working on
|-
| ''Who is the new intern?''
| ''Who will be introducing that person?''
| ''Where is the introducer?''
| ''Where will the new person be working from?''
| ''What will the new person be working on?''
|-

|-
|}

= <meta> =

Notes and non-voice status updates that aren't part of the live meeting go here.

== Status Updates By Team (*non-voice* updates) ==

=== Firefox ===

=== Platform ===

=== Services ===

=== Messaging ===

=== Mobile ===

=== IT ===

=== Release Engineering ===

=== QA ===

==== Test Execution ====

==== WebQA ====

==== QA Community ====

=== Automation & Tools ===

=== Security ===

=== Engagement ===

==== PR ====

==== Events ====

WeeklyUpdates/2013-11-04

2013-11-04T06:50:56Z

DavidA: /* Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} */

WeeklyUpdates/2013-11-04

2013-11-04T06:49:56Z

DavidA: /* Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} */

AppMaker

2013-07-31T05:37:21Z

DavidA:

AppMaker is an exploration in whether we can make it fun for non-developers to quickly build working mobile web apps. We're building on inspiration such as Hypercard and Scratch, and technology such as the app APIs provided by Firefox OS, the Web Runtime, the Web Components spec, and others.

We're currently in the earliest phase of the project definition, building a prototype that we hope to test at Campus Party UK in Sept.

We hang out in #appmaker; meet every monday at 10am Pacific in David Ascher's Vidyo room; and have a mailing list at https://mail.mozilla.org/listinfo/appmaker.

AppMaker

2013-07-31T05:36:08Z

DavidA: Created page with "AppMaker is an exploration in whether we can make it fun for non-developers to quickly build working mobile web apps. We're currently in the earliest phase of the project def..."

AppMaker is an exploration in whether we can make it fun for non-developers to quickly build working mobile web apps.

We're currently in the earliest phase of the project definition, building a prototype that we hope to test at Campus Party UK in Sept.

We hang out in #appmaker; meet every monday at 10am Pacific in David Ascher's Vidyo room; and have a mailing list at https://mail.mozilla.org/listinfo/appmaker.

New page

2013-03-02T20:43:09Z

DavidA: Created page with "asdjasldkajs"

asdjasldkajs

Webmaker/2013plans

2012-11-19T20:45:52Z

DavidA: /* 4. Create a culture of executional excellence */

__NOTOC__
== Context ==
 
'''Vision:''' Build a generation of webmakers 
'''Long term goal:''' Move tens of millions of people from ''using'' the web to ''making'' the web. 

== Overarching goal for 2013 ==

[write this]

== Top level goals ==

Product: in 2013 we want Mozilla Webmaker to be: 
 
1. A popular way to make and remix web content 
2. Levels up your web skills every time you make something 
3. Powered by a global community of makers and mentors 
 
Ops: in order for this vision of Webmaker to succeed we need to: 
 
4. Create a culture of excellence (process + outcomes) 
5. Tee up solid long term funding and resource base 
6. Establish a regular flow of new product ideas 

== Product goals plus concrete objectives ==

''objectives = short term things we will do to pursue a goal, last less than a year''

=== 1. A popular way to make and remix web content ===
 
Metric: # of makers 
 
1.1 Visitors turned into makers (more than two visits post sign up) 
1.2 Personal gallery + social media let you share and showcase what you made 
1.3 Steady flow of starter projects based on popular internet topics and themes 
1.4 Webmaker.org becomes a way for finding and celebrating best 'makes' 
1.5 Simple way to pull your existing content in from mobile and social networks 

=== 2. Levels up web skills every time you make something ===
 
Metric: # of badges issued 
 
2.1 Full set of Webmaker badges covering all the skills we care about 
2.2 Playlists,  badge pathways and user dashboards making learning easier 
2.3 Tools and projects to learn javascript added to Webmaker.org 
2.4 Partners build our tools and badges into their sites, includes skills we don't teach 
2.5 L10N added as way to bring learninig and content to more people 

=== 3. Powered by a global community of makers and mentors ===
 
Metric: # of mentors 
 
3.1 Makers turned into mentors (organize 2+ events or volunteer online) 
3.2 Grassroots instructor community established,  like a year round summer code party 
3.3 Tools and support to help community make great content and learning projects 
3.4 Tools that make it easy to find local  teachers / events / clubs online 
3.5 More + better mentor how to guides: step by step guides for local organizing 

== Ops goals plus concrete objectives ==

''objectives = short term things we will do to pursue a goal, last less than a year''

=== 4. Create a culture of excellence in execution ===
 
Metric: # better conversions and user stickyness 
 
4.1 Regular ship cycle for Webmaker tools and content (the train) 
4.2 Project / product management system used by all MoFos 
4.3 Rigorous culture of testing, iteration and refinement based on metrics 
4.4 We make stuff people like: it's beautiful and compelling 

=== 5. Tee up solid long term funding and resource base ===
 
Metric: ratio of restricted to unrestricted funds 
 
5.1 Webmaker message successful w/ individual donors, $1M/in 2013 
5.2 First major gifts landed, most likely going to Hive in London and NYC 
5.3 Grants portfolio balanced, more big grants directly tied to Webmaker 

===6. Establish a regular flow of new product ideas===
 
Metric: ??? 
 
6.1 Prototype hackable games for learning 
6.2 Explore mobile webmaking beyond simple content capture 
6.3 Establish a culture and process for new ideas getting into product (Hive) 

==Planning Schedule==

'''Nov 20'''

* Outline process / top goals on Webmaker call

'''Nov 21'''
* Call with expanded management team

'''Nov 26'''
* 1st review of straw man budget

'''Nov 27-28'''
* Management team work sprint (Toronto)

'''Nov 30'''
* Roadmaps for each goal
* Key hire job descriptions written up
* 2nd review of budget

'''Dec 4 '''

* Share proposed plans w/ Webmaker call for feedback

'''Dec 5'''
* Lock board presentation re: strategy deck and budget

'''Dec 10'''
* Ship strategy deck and budget to board

'''Dec 12'''
* Board meeting

'''Dec 18'''
* Share outcomes of board meeting on Webmaker call

Webdev/Beer And Tell/October2012

2012-10-19T21:33:44Z

DavidA: /* Speakers */

= Date, Time, Location =

2PM Pacific, Friday October 19th

Webdev Vidyo channel (798).

If you need to call in:
+1 650 903 0800, x92 or +1 800 707 2533 (password on intranet)
Then enter 9798#

* Recording:
* Blog post:

= Liquid Consumed =

* [https://en.wikipedia.org/wiki/White_House_Honey_Ale White House Honey Ale] - groovecoder

= Memes produced =

= Speakers =
The limit is 5 minutes per speaker. It's like a lightning talk, but don't feel that you have to have slides in order to make a presentation.

<table class="fullwidth-table">

<tr>
<th> Presenter
</th>
<th> Topic
</th>
<th> Summary
</th>
<th> Links
</th>
<th> Beer
</th>
</tr>

<tr>
<td>lonnen</td>
<td>leeeeeeeeroyyy jennkinnnssss</td>
<td>introducing socorro's pre-integration testing bot</td>
<td>[https://github.com/Lonnen/leeroy some code?]</td>
<td>TBD</td>
</tr>

<tr>
<td>groovecoder</td>
<td>deckjs: remote & sandstone</td>
<td>It's got websockets, css transforms & transitions, SASS, node.js, and mozilla sandstone - how much hotter could it get?!</td>
<td>[http://beer-and-tell.jit.su/deck slides] 
[https://github.com/groovecoder/deckjs-theme-mozilla deckjs mozilla theme] 
[https://github.com/groovecoder/deckjs-remote#quickstart-with-slide-casting-boilerplate-presentation quick start]</td>
<td>[https://en.wikipedia.org/wiki/White_House_Honey_Ale White House Honey Ale]</td>
</tr>

<tr>
<td>jlongster</td>
<td>My reaction to jekyll</td>
<td>I'm hacking on a blogging platform in node with real-time editing, browserid, and other fun stuff</td>
<td>https://github.com/jlongster/boogie-woogie</td>
<td>TBA</td>
</tr>

<tr>
<td>ubernostrum</td>
<td>django_compat_lint</td>
<td>Quick little tool for identifying Django-version-compatibility issues in our code.</td>
<td>[https://github.com/ubernostrum/django-compat-lint Not much here yet, but it's a growing young thing]</td>
<td>BEER</td>
</tr>

<tr>
<td>jsocol (shoot, forgot an appt at 4, will try to get back in time)</td>
<td>The Best Data Structure</td>
<td>You all use git, so I won't need to explain directed acyclic graphs.</td>
<td>[https://github.com/jsocol/yodawg le codez]</td>
<td>TBD</td>
</tr>

<tr>
<td>peterbe</td>
<td>django-jingo-offline-compressor</td>
<td>All the good juice of django_compressor, jinja and offline build step</td>
<td>[https://github.com/peterbe/django-jingo-offline-compressor programkoden]</td>
<td>is wine an option?</td>
</tr>

<tr>
<td>andym</td>
<td>Will show another time.</td>
<td></td>
<td>[http://www.agmweb.ca/blog/andy/ blog post]</td>
<td>I did not write a blog engine for that blog post.</td>
</tr>

<tr>
<td>brianloveswords</td>
<td>habitat</td>
<td>A small node library for dealing with environment variables</td>
<td>[https://github.com/brianloveswords/habitat jabbahscarps]</td>
<td>Southern Tier 2XIPA</td>
</tr>

<tr>
<td>wenzel</td>
<td>pi-cam</td>
<td>Small Flask app turning my raspberry pi into a remote webcam</td>
<td>[https://github.com/fwenzel/pi-cam pi-cam]</td>
<td>Sierra Nevada</td>
</tr>

<tr>
<td>David Ascher</td>
<td>uptime</td>
<td>Self-serve uptime monitoring</td>
<td>http://uptime.mozillalabs.com</td>
<td></td>
</tr>

<tr>
<td>Name</td>
<td>Topic</td>
<td>Summary</td>
<td>Links to demo/code/etc.</td>
<td>Chimay Bleue</td>
</tr>

</table>

Vancouver

2012-10-18T22:19:33Z

DavidA: /* Vegetarian-friendly Options */

Collusion

2012-09-19T02:30:41Z

DavidA:

Collusion is an experimental add-on for Firefox and allows you to see all the third parties that are tracking your movements across the Web. It will show, in real time, how that data creates a spider-web of interaction between companies and other trackers.

= Coordination Pointers =

Weekly meetings will be Thursdays, 11am Pacific. Vidyo meeting room Collusion, dial-in details to be added shortly.

Code is on [https://github.com/mozilla/collusion Github]

Bug list is in the [https://github.com/mozilla/collusion/issues GitHub issue tracker].

Mailing list is [https://mail.mozilla.org/listinfo/collusion collusion@mozilla.org].

IRC channel is #collusion on irc.mozilla.org.

Development mailing list is [https://mail.mozilla.org/listinfo/collusion-dev collusion-dev@mozilla.org].

[https://github.com/disconnectme/chrollusion Chrome/Safari port]

[https://addons.mozilla.org/en-US/firefox/addon/collusion/ Latest released version of the add-on]

The original Collusion blog post by Atul Varma: http://www.toolness.com/wp/2011/07/collusion/

= Roadmap [DRAFT] =

* Collusion logo for web and t-shirts
* Standardize data format
* Revised look and feel
* Features
** Enable blocking filters (off and on)
** Show individual tracker info on tabs
* Harmonize cross-browser versions (Firefox, Chrome, Safari)
** parallel repos, contribute patches to each other
** common look and feel, features
* data safety
** Data sharing opt-in w/ public-facing database API
* Improve visualization
** Better indicators for sites who are trackers - Q: why is this node red? independently verifiable
* More and better discovery - idea: filters (Privacychoice.org)
* website improvements
** display data from global tracking db - for Collusion users add a "throw your coin in the fountain" feature
* improved branding/product description

= Guide to Collusion development =

TODO

Collusion

2012-09-19T02:28:46Z

DavidA: /* Links */

Collusion is an experimental add-on for Firefox and allows you to see all the third parties that are tracking your movements across the Web. It will show, in real time, how that data creates a spider-web of interaction between companies and other trackers.

For collusion updates, please follow the [http://mozilla-collusion.tumblr.com/ Collusion blog].

= Links =

Code is on [https://github.com/mozilla/collusion Github]

Bug list is in the [https://github.com/mozilla/collusion/issues GitHub issue tracker].

Mailing list is [https://mail.mozilla.org/listinfo/collusion collusion@mozilla.org].

Development mailing list is [https://mail.mozilla.org/listinfo/collusion-dev collusion-dev@mozilla.org].

[https://github.com/disconnectme/chrollusion Chrome/Safari port]

[https://addons.mozilla.org/en-US/firefox/addon/collusion/ Latest released version of the add-on]

The original Collusion blog post by Atul Varma: http://www.toolness.com/wp/2011/07/collusion/

= Roadmap [DRAFT] =

* Collusion logo for web and t-shirts
* Standardize data format
* Revised look and feel
* Features
** Enable blocking filters (off and on)
** Show individual tracker info on tabs
* Harmonize cross-browser versions (Firefox, Chrome, Safari)
** parallel repos, contribute patches to each other
** common look and feel, features
* data safety
** Data sharing opt-in w/ public-facing database API
* Improve visualization
** Better indicators for sites who are trackers - Q: why is this node red? independently verifiable
* More and better discovery - idea: filters (Privacychoice.org)
* website improvements
** display data from global tracking db - for Collusion users add a "throw your coin in the fountain" feature
* improved branding/product description

= Guide to Collusion development =

TODO

Websites/Active List

2012-06-19T20:54:43Z

DavidA: /* The Mozilla Blog */

= Details =

A list of Mozilla owned websites and the important details about each of these sites. Please refer to the [[Websites/Domain_List/Mozilla_Owned|Mozilla Owned] list, which is actively update via scripts and DNS queries.

If you do not see your website listed below, please add it in alphabetical order. Use the following template to document all Mozilla websites:

<nowiki>

== [http://wiki.mozilla.org/project-URL Project/Product Name] ==

*Prod URL:
*Stage URL:
*Code Repo:
*L10N Repo:
*Code: Language / Framework
*Licensing:
*Product Owner: Group; Person
*Dev Team: Group; Person
*QA Lead: Person
*Team Email: team-email@example.com
*Last reviewed: Person on mm/dd/yyyy

</nowiki>

= Websites/Applications =
== [[Websites/Affiliates|Affiliates]] ==

*Prod URL: https://affiliates.mozilla.org
*Stage URL: http://affiliates.allizom.org
*Dev URL: http://affiliates-dev.allizom.org
*Code Repo: http://github.com/mozilla/affiliates/
*L10N Repo: https://svn.mozilla.org/projects/l10n-misc/trunk/affiliates/locale/
*Code: Python / Playdoh (Django)
*Licensing: New BSD License
*Product Owner: cnovak
*Web Product Manager: cmore
*Dev Team: mkelly
*QA Lead: mbrandt
*Google Analytics?: Yes
*Last reviewed: malexis 4-4-12

== [[Japan/AMJ|AMJ / addons.mozilla.jp]] ==

*Prod URL: https://addons.mozilla.jp/
*Stage URL: nonpublic
*Code Repo: nonpublic
*L10N Repo: N/A
*Code: PHP
*Product Owner: Mozilla Japan
*Dev Team: Kohei Yoshino
*Team Email: webmaster@mozilla.jp

== [[Air Mozilla]] ==

*Prod URL: http://air.mozilla.org
*Stage URL: http://air.stage.mozilla.org/
*Code Repo:
*L10N Repo:
*Code: PHP / Wordpress
*Product Owner: Richard Milewski
*Dev Team:
*Team Email:
*Google Analytics?: Yes

== [[AMO|AMO / Add-Ons]] ==

*Prod URL: http://addons.mozilla.org
*Stage URL: http://addons.allizom.org
*Code Repo: https://github.com/jbalogh/zamboni/
*L10N Repo:
*Code: Python / Django
*Product Owner: Add-Ons; Justin Scott
*Dev Team: AMO Development; clouserw, potch
*QA Lead: krupa
*Team Email: amo-drivers@mozilla.org
*Last Reviewed: malexis 4-4-12

== [https://intranet.mozilla.org/Apps Apps] ==

*Prod URL: https://apps.mozillalabs.com/
*Stage URL:
*Code Repo: https://github.com/mozilla/openwebapps
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Justin Scott?
*Dev Team: Wil Clowser/AMO?
*QA Lead: Person
*Team Email:
*Last reviewed: malexis 4-4-12

== Brasstacks ==

*Prod URL: http://brasstacks.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Clint Talbert
*Dev Team: Clint Talbert, Jonathan Griffin, Mark Côté, Bob Clary
*QA Lead:
*Team Email:

== [[BMO / bugzilla.mozilla.org]] ==

*Prod URL: http://bugzilla.mozilla.org
*Stage URL: https://bugzilla-stage-tip.mozilla.org/ (public, sanitized) https://bugzilla-stage.mozilla.org/ (restricted access)
*Code Repo: http://bzr.mozilla.org/bmo/4.0/files
*L10N Repo: n/a
*Code: Perl
*Licensing: MPL
*Product Owner: dkl and glob
*Dev Team: dkl, glob, justdave, gerv
*QA Lead: Person
*Team Email:
*Last reviewed:

== Bouncer ==

*Prod URL: http://bounceradmin.mozilla.com
*Stage URL: https://tuxedo.stage.mozilla.com/
*Code Repo: https://github.com/fwenzel/tuxedo
*L10N Repo: --
*Code: Admin interface/API: Python / Django; sentry: perl; download.m.o: PHP
*Product Owner: IT; justdave
*Dev Team: Flux; wenzel, aricaud
*Team Email:
*Last reviewed: fwenzel on 2011.06.09

== [[Bugzilla]] ==

*Prod URL: http://www.bugzilla.org
*Stage URL: http://landfill.bugzilla.org/
*Code Repo: http://bzr.mozilla.org/bugzilla/
*L10N Repo: n/a
*Code:
*Licensing: MPL
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Builder / AMO Builder]] ==

*Prod URL: https://builder.addons.mozilla.org/
*Stage URL:
*Code Repo: https://github.com/mozilla/FlightDeck
*L10N Repo:
*Code: Python / Django
*Product Owner: Add-Ons; Justin Scott
*Dev Team: AMO Development; clouserw
*Team Email:
*Last Reviewed:

== [[Build Your Own Browser]] ==

*Prod URL: http://byob.mozilla.com/
*Stage URL: http://dm-partdist-stage01.mozilla.org/
*Code Repo: https://github.com/lmorchard/byob/
*L10N Repo: (no l10n, yet)
*Code: PHP / Kohana
*Product Owner: Kev Needham
*Dev Team:
*Team Email:

== [[CC - Case Conductor]] ==

*Prod URL: https://caseconductor.allizom.org/
*Stage URL: https://caseconductor.allizom.org/
*Code Repo:
**UI: https://github.com/mozilla/caseconductor
**Platform: https://github.com/mozilla/caseconductor
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Cameron Dawson
*Dev Team: Carl Meyer, Eric Meyer, Jonny Meyer
*QA Lead: Cameron Dawson
*Team Email: tcm@mozilla.com
*Last reviewed:

== [[Community Surveys Europe]] ==

*Prod URL: http://surveys.mozilla-europe.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Design/CreativeCollective|Creative Collective]] ==

*Prod URL: http://creative.mozilla.org
*Stage URL: http://mcc.stage.mozilla.org/
*Code Repo: http://svn.mozilla.org/projects/mcc/
*L10N Repo:
*Code: PHP / Kohana
*Product Owner: Engagement; Tara Shahian
*Dev Team: Flux; Ryan Snyder
*QA Lead: krupa
*Team Email:
*Last Reviewed: rysny on 2011.06.08

== [https://wiki.mozilla.org/Websites/Blog-The-Den Den, The (blog)] ==

*Prod URL: 
*Stage URL: blog.mozilla.com does not currently have a staging environment 
*Code Repo: [https://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content/themes/ https://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content/themes/] 
*L10N Repo: no l10n at this stage 
*Code: HTML, PHP, Wordpress 
*Product Owner: User Engagement; Carmen Collins & Jane Finette 
*Dev Team: silverorgange, Mike Alexis, Chrissie Brodigan
*QA Lead: 
*Team Email:
*Last Reviewed: cb on 2011.30.10 

== [[Demo Dashboard]] ==

*Prod URL: https://myapps.mozillalabs.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Websites/Despot|Despot]] ==

*Prod URL: http://despot.mozilla.org
*Stage URL: N/A
*Code Repo: mozilla/webtools/despot/ (CVS)
*L10N Repo: N/A
*Code: Perl
*Product Owner: Dave Miller
*Dev Team: Dave Miller, Reed Loden
*Team Email: N/A
*Last reviewed: cmore on 2011/06/13

== [[Doctor]] ==

*Prod URL: https://doctor.mozilla.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Donate]] ==

*Prod URL: https://donate.mozilla.org/
*Stage URL: No staging URL
*Code Repo:
*L10N Repo: http://viewvc.svn.mozilla.org/vc/projects/l10n-misc/trunk/joinmozilla/
*Code: Uses CRM with CMS functionality
*Product Owner: Ryan Merkley (ryan@mozillafoundation.org)
*Dev Team: Contractors
*Team Email:
*Contractor Ticket System: http://bsd.zendesk.com

== [[Drumbeat]] ==

*Prod URL: https://www.drumbeat.org/
*Stage URL: https://batucada.mozillalabs.com/
*Code Repo: https://github.com/paulosman/batucada
*L10N Repo: Not localized
*Code: Python / Django
*Product Owner: paulosman
*Dev Team: Drumbeat; paulosman
*Team Email: drumbeat-website@lists.mozilla.org
*Last Reviewed: paulosman on 2011.05.20

== [[DXR]] ==

*Prod URL: http://dxr.mozilla.org/
*Stage URL:
*Code Repo: http://hg.mozilla.org/webtools.dxr
*L10N Repo: Not localized
*Code: Python (among others)
*Licensing: MIT (among others)
*Product Owner:
*Dev Team: jcranmer
*Team Email:
*Last reviewed:

== [[Elmo]] ==

*Prod URL: https://l10n-stage-sj.mozilla.org/
*Stage URL: not set up yet
*Code Repo: https://github.com/mozilla/elmo
*L10N Repo: N/A
*Code: Python / Playdoh
*Licensing: MPL
*Product Owner: l10n-drivers; Axel Hecht, Stas Malolepszy
*Dev Team: Webtools; Peter Bengtsson, Laura Thomson
*QA Lead: Stephen Donner
*Team Email: tools-elmo@lists.mozilla.org
*Last reviewed: laura on 2011.6.13

 

== [[European Mozilla Community Blog]] ==

*Prod URL: http://blogs.mozilla-europe.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Extend Firefox]] ==

*Prod URL: http://extendfirefox.com/mobile-cup/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Firefox Flicks]] ==

*Prod URL:
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Kristin Baird, Chelsea Novak
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Firefox Heatmap]] ==

*Prod URL: https://heatmap.mozillalabs.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Firefox Input]] ==

*Prod URL: http://input.mozilla.com/
*Stage URL: http://input.allizom.org/
*Code Repo: https://github.com/mozilla/input.mozilla.com/
*L10N Repo: https://svn.mozilla.org/projects/reporter/locale/
*Code: Python / Django
*Product Owner: Engagement; Aakash Desai
*Dev Team: Flux; Dave Dash
*QA Lead: mbrandt, davehunt
*Team Email: input@mozilla.com
*Last Reviewed: ddash on 2011.08.04

== [[Firefox Nightly Builds]] ==

*Prod URL: http://nightly.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Firefox Start China]] ==

*Prod URL: http://zh-cn.start3.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Firefox Sync » Home]] ==

*Prod URL: https://services.mozilla.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Getfirebug Blog]] ==

*Prod URL: http://blog.getfirebug.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Get Firebug]] ==

*Prod URL: http://getfirebug.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Graphite]] ==

*Prod URL: http://graphite.mozilla.org
*Stage URL:
*Code Repo: https://github.com/jsocol/pystatsd
*L10N Repo:
*Code:
*Product Owner: WebDev
*Dev Team: WebDev; jbalogh, jsocol
*Team Email:

== [[Hacks]] ==

*Prod URL: http://hacks.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code: Wordpress plus static files (?)
*Product Owner:
*Dev Team:
*Team Email:

== [[InterFORest]] ==

*Prod URL: http://interforest.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Intlstore.mozilla.org]] ==

*Prod URL: http://intlstore.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner: Engagement; John Slater
*Dev Team:
*Team Email:

== [[Intranet.mozilla.org]] ==

*Prod URL: https://intranet.mozilla.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[ISP Database]] ==

*Prod URL: http://ispdb.mozillamessaging.com
*Stage URL: http://stage.ispdb.mozillamessaging.com/
*Code Repo: http://svn.mozilla.org/mozillamessaging.com/sites/ispdb.mozillamessaging.com/
*L10N Repo:
*Code: Python/Django
*Product Owner: [[User:Sancus|Sancus]]
*Dev Team: [[User:Sancus|Sancus]]
*Team Email: sancus@mozillamessaging.com

== [[JP Open Timetable]] ==

*Prod URL: http://opentimetable.jp
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Kraken JavaScript Benchmark]] ==

*Prod URL: http://krakenbenchmark.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Landfill: The Bugzilla Test Server]] ==

*Prod URL: http://landfill.bugzilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Learning Freedom and the Web]] ==

*Prod URL: http://learningfreedomandtheweb.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner: Ben Moskowitz (ben@mozillafoundation.org)
*Dev Team:
*Team Email:

== lists.mozilla-europe.org ==

*Prod URL: http://lists.mozilla-europe.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Litmus]] ==

*Prod URL: https://litmus.mozilla.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Lizard Feeder]] ==

*Prod URL: http://feeds.mozilla.org
*Stage URL: (none)
*Code Repo: http://svn.mozilla.org/projects/lizardfeeder/
*L10N Repo: (none)
*Code: Python, based on Planet Venus
*Product Owner: (none)
*Dev Team: lorchard
*Team Email: (none)

== [[Mozilla Cross-Reference]] ==

*Prod URL: http://mxr.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Modest / Mozilla Developer Street]] ==

*Prod URL: https://dev.mozilla.jp/
*Stage URL: N/A
*Code Repo: nonpublic
*L10N Repo: N/A
*Code: PHP / WordPress
*Product Owner: Mozilla Japan
*Dev Team: Tomoya Asai
*Team Email: webmaster@mozilla.jp

== [[MDN|Mozilla Developer Network / MDN]] ==

*Prod URL: https://developer.mozilla.org/
*Stage URL:
**https://developer-stage9.mozilla.org/
**https://kuma-stage.mozilla.org/
*Code: Python / Django, DekiWiki
*Code Repo:
**https://github.com/mozilla/kuma
*L10N Repo:
**http://svn.mozilla.org/projects/mdn/trunk/locale/
**http://svn.mozilla.org/projects/deki/trunk/mozilla/resources/
*Product Owner: Engagement, Sheppy
*Dev Team: MDN; luke crouch, lorchard
*Team Email: dev-mdn@lists.mozilla.org
*Last Reviewed: malexis 4-4-12

== [[Mozilla Europe Events Registration]] ==

*Prod URL: http://events.mozilla-europe.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla F1]] ==

*Prod URL: http://f1.mozillamessaging.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Firefox GB Download]] ==

*Prod URL: http://browserchoice.mozilla.com/lang/en-GB
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Firefox User Panel]] ==

*Prod URL: http://userpanel.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Hispano]] ==

*Prod URL: http://www.mozilla-hispano.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Japan]] ==

*Prod URL: http://mozilla.jp/
*Stage URL: nonpublic
*Code Repo: nonpublic; portions of the site are published with a CMS
*L10N Repo: N/A
*Code: PHP
*Product Owner: Mozilla Japan
*Dev Team: Kohei Yoshino
*Team Email: webmaster@mozilla.jp

== [[Mozilla Labs Design Challenge]] ==

*Prod URL: http://design-challenge.mozillalabs.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Labs Design Challenge]] ==

*Prod URL: http://www.designchallenges.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Labs Gaming]] ==

*Prod URL: https://gaming.mozillalabs.com/
*Stage URL:
*Code Repo: https://github.com/mozilla/doozer
*L10N Repo:
*Code: Python / Django
*Product Owner: Labs; -
*Dev Team: potch, jsocol (IT/Ops), r1cky
*Team Email:

== [[Labs|Mozilla Labs]] ==

*Prod URL: http://mozillalabs.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner: Labs; Todd Simpson
*Dev Team:
*Team Email:
*Last Reviewed:

== [[Mozilla Labs Test Pilot]] ==

*Prod URL: https://testpilot.mozillalabs.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Labs - Ubiquity]] ==

*Prod URL: http://ubiquity.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Messaging Blogs]] ==

*Prod URL: http://blogs.mozillamessaging.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Messaging]] ==

*Prod URL: http://noc.mozillamessaging.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla.org Archive]] ==

*Prod URL: http://www-archive.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla.org]] ==

*Prod URL: http://mozilla.org/
*Stage URL: http://www-stage.mozilla.org/
*Code Repo: http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/
*L10N Repo: n/a
*Code: PHP
*Product Owner:
* 
*Content Owner: David Boswell
* 
*Design Owner: John Slater
* 
*Technical Owner: TBD
*Dev Team: David Boswell and contractors
*Team Email: n/a
*Discuss Forum: http://groups.google.com/group/mozilla.dev.mozilla-org/topics

== [[Mozilla Pastebin]] ==

*Prod URL: http://pastebin.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Public License]] ==

*Prod URL: http://mpl.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Pulse]] ==

*Prod URL: http://pulse.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Jonathan Griffin
*Dev Team: Jonathan Griffin, a-team
*QA Lead:
*Team Email: tools-pulse@lists.mozilla.org
*Last reviewed:

== [[MozillaZine.jp]] ==

*Prod URL: http://forums.mozillazine.jp
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[MozillaZine.jp]] ==

*Prod URL: http://mozillazine.jp
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozillians]] ==

*Prod URL: http://mozillians.org
*Stage URL: https://mozillians-dev.allizom.org
*Code Repo: https://github.com/mozilla/mozillians
*L10N Repo: http://svn.mozilla.org/projects/l10n-misc/trunk/mozillians
*Code: Python, LDAP
*Product Owner: David Boswell
*Dev Team: davedash, tofumatt, Gerv Markham
*TPM: Austin King
*Team Email: team-mozillians AT mozilla DOT com
*Discussion Forum: http://groups.google.com/group/mozilla.mozillians/topics
*Planning wiki: [[Mozillians]]

== [[Perfomatic|Perfomatic Graph Server]] ==

*Prod URL: http://graphs.mozilla.org
*Stage URL: http://graphs.allizom.org
*Prod.next URL: http://graphs-new.mozilla.org
*Code Repo: https://github.com/rhelmer/graphs
*L10N Repo:
*Code: Python, JavaScript
*Product Owner: WebDev
*Dev Team: rhelmer
*Team Email: rhelmer@mozilla.com
*Last Reviewed: rhelmer on 2011.06.01

== [[Personas]] ==

*Prod URL: http://www.getpersonas.com/
*Stage URL: http://personas.stage.mozilla.com/
*Code Repo:
*L10N Repo:
*Code:
*Product Owner: :dria, clouserw
*Dev Team:
*QA Lead: vish_moz
*Team Email: personas@mozilla.com
*Last Reviewed: clouserw on 2011.05.20

== [[Planet Bugzilla]] ==

*Prod URL: http://planet.bugzilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Planet.firefox.com/]] ==

*Prod URL: http://planet.firefox.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team: fx-team
*Team Email: fx-team@mozilla.com

== [[Planet.firefox.com/mobile]] ==

*Prod URL: http://planet.firefox.com/mobile
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Planet Mozilla (de)]] ==

*Prod URL: http://planet.mozilla.de
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Planet.mozillamessaging.com]] ==

''we are in the process of changing this to "Planet Thunderbird" ''

*Prod URL: http://planet.mozillamessaging.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:
*Last Reviewed:

== [[Planet.mozilla.org]] ==

*Prod URL: http://planet.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Plugin Directory]] ==

*Prod URL: http://plugins.mozilla.org/
*Stage URL: http://plugins.stage.mozilla.com/
*Code Repo: http://github.com/lmorchard/plugindir
*L10N Repo:
*Code: PHP / Kohana / JavaScript
*Product Owner: Kev Needham
*Devs: AMO
*Team Email: pluginsposse AT mozilla DOT com
*Last Reviewed: rysny on 2011.06.09

== [[Popcorn]] ==

*Prod URL: http://mozillapopcorn.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:
*Last reviewed:

== [[Privacy]] ==

*Prod URL: http://www.mozilla.org/privacy/
*Stage URL: http://www-dev.allizom.org/en-US/privacy/
*Code Repo: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/en-US/privacy/
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Alex Fowler, Tom Lowenthal
*Dev Team: /firefox website team/silverorange
*QA Lead: /firefox website team/silverorange
*Team Email:
*Last reviewed:

== [[Public Website Health Status for Mozilla]] ==

*Prod URL: http://status.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[QMO|QMO / quality.mozilla.org]] ==

*Prod URL: http://quality.mozilla.org
*Stage URL: http://quality-new.stage.mozilla.com/
*Code Repo:
*L10N Repo:
*Code: PHP / Wordpress
*Product Owner: Metrics; Al Billings
*Dev Team: TPM, Chris More; Design, Craig Cook
*QA Lead: rbillings
*Team Email:
*Last Reviewed: rysny on 2011.06.08

== releases.mozilla.org ==

*Prod URL: http://releases.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Websites/ReMo_Mozilla_Reps|ReMo Mozilla Reps]] ==

*Prod URL:
*Stage URL:
*Dev URL: http://reps-dev.allizom.org/
*Code Repo: https://github.com/mozilla/remo
*L10N Repo: N/A
*Licensing: N/A
*Product Owner: Pierros Papadeas
*Dev Team: Giorgos Logiotatidis (Contractor)
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Rock Your Firefox]] ==

*Prod URL: http://rockyourfirefox.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Security]] ==

*Prod URL: https://securitywiki.mozilla.org/ (Members of Security-Group Only)
*Prod URL: https://wiki.mozilla.org/Security
*Code Repo: n/a
*L10N Repo: n/a
*Product Owner: Lucas Adamski
*Team Email: secteam@mozilla.com
*Last Reviewed:

== [[Socorro|Socorro / Crash Stats]] ==

*Prod URL: http://crash-stats.mozilla.com/
*Stage URL: http://crash-stats.stage.mozilla.com/
*Code Repo: http://code.google.com/p/socorro/
*L10N Repo: n/a
*Code: Python back-end; PHP / Kohana front-end
*Product Owner:
*Dev Team: Webtools; Laura Thomson
*QA Lead: mbrandt
*Team Email: socorro-dev@mozilla.com
*Last Reviewed: rysny on 2011.06.08

== [[Websites/Spark|Spark]] ==

*Prod URL: http://spark.mozilla.org/
*Stage URL: http://spark.allizom.org/
*Code Repo:
**https://github.com/mozilla/spark
**https://github.com/mozilla/spark-lib
*L10N Repo: http://svn.mozilla.org/projects/l10n-misc/trunk/spark
*Code: Python / Django
*Product Owner: Engagement; Caitlin Looney
*Dev Team: Flux; Ryan Snyder, Little Workshop (Dev)
*QA Lead: retornam
*Team Email:
*Last Reviewed: rysny on 2011.06.08

== [[Store.mozilla.org]] ==

*Prod URL: http://store.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Student Reps]] ==

*Prod URL: http://studentreps.mozilla.org
*Stage URL: http://studentreps.stage.mozilla.com
*Code Repo: https://svn.mozilla.org/studentreps
*L10N Repo:
*Code: PHP
*Product Owner:
*Dev Team: craigcook
*Team Email:

== [[Sumo|SUMO / Mozilla Support]] ==

*Prod URL: http://support.mozilla.org/
*Stage URL: http://support.allizom.org/
*Code Repo: https://github.com/mozilla/kitsune
*L10N Repo: http://viewvc.svn.mozilla.org/vc/projects/sumo/locales
*Code: Python / Django
*Product Owner: Kadir Topal
*Dev Team: jsocol, rrosario, timw, willkg
*QA Lead: rbillings
*Team Email: sumo-dev@mozilla.com
*Last Reviewed: James Socol on 2012-03-01

== [[The Mozilla Blog]] ==

*Prod URL: http://blog.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code: PHP; Wordpress
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead:
*Team Email:
*Last reviewed: rysny on 2011.06.09

== [http://wiki.mozilla.org/Thimble Thimble] ==

*Prod URL: http://thimble.webmaker.org
*Stage URL: http://webpagemaker.allizom.org/
*Code Repo: http://github.com/mozilla/webpagemaker/
*L10N Repo: none yet
*Code: Python / Playdoh
*Licensing: MPL2
*Product Owner: Mozilla Foundation ; Michelle Levesque
*Dev Team: Mozilla Foundation ; MoFoDev
*QA Lead: Mozilla Foundation
*Team Email: mozwebpagemaker@googlegroups.com
*Last reviewed:

== [[Thunderbird Support]] ==

*Prod URL: http://support.mozillamessaging.com
*Stage URL: http://support-stage.mozillamessaging.com/
*Code Repo: https://github.com/sancus/kitsune
*L10N Repo: http://svn.mozilla.org/projects/sumo/locales/
*Code: Python/Django, fork of Kitsune
*Product Owner: Thunderbird; Roland Tanglao; Jennifer Zickerman
*Dev Team: [[User:Sancus|Sancus]]
*Team Email: sancus@mozillamessaging.com

== [[Tinderbox]] ==

*Prod URL: http://tinderbox.mozilla.org
*Stage URL: http://tinderbox-stage.mozilla.org
*Code Repo: CVS mozilla/webtools/tinderbox
*L10N Repo: None
*Code: Perl
*Licensing: NPL 1.1
*Product Owner: webtools
*Dev Team: whoever is slowest
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Tools.mozilla.com]] ==

*Prod URL: http://tools.mozilla.com
*Stage URL:
*Code Repo: https://svn.mozilla.org/projects/openweb/
*L10N Repo:
*Code:
*Product Owner: Webdev (?)
*Dev Team: Laura
*Team Email:

== [[Verbatim]] ==

*Prod URL: https://localize.mozilla.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Videos.mozilla.org]] ==

*Prod URL: http://videos.mozilla.org
*Stage URL: --
*Code Repo: https://videos-origin.mozilla.org
*L10N Repo: --
*Code: -- (just a file listing on the CDN, access via webdav)
*Product Owner: IT
*Dev Team: IT
*Team Email:
*Last reviewed: fwenzel on 2011.06.09

== [[Viewvc.svn.mozilla.org]] ==

*Prod URL: http://viewvc.svn.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [http://wiki.mozilla.org/Webmaker Webmaker] ==

*Prod URL: www.webmaker.org
*Stage URL: https://make-stage.mozillalabs.com
*Code Repo: https://github.com/rossbruniges/make.mozilla.org
*L10N Repo: None yet
*Code: Python / Playdoh
*Licensing:
*Product Owner: Mozilla Foundation ; Matt Thompson;
*Dev Team: Mozilla Foundation; Ross Bruniges
*QA Lead: Mozilla Foundation
*Team Email:
*Last reviewed:

(note: thimble.webmaker.org is its own site)

== Web o' Wonder ==

*Prod URL: http://developer.mozilla.org/demos/
*Stage URL: http://webofwonder.allizom.org/en-US/
*Code Repo: https://github.com/mozilla/webowonder
*L10N Repo:
*Code: Python / Django
*Product Owner: Engagement; Laura Mesa
*Dev Team: Flux; Austin King, Jason Grlicky
*QA Lead: retornam
*Team Email:
*Last Reviewed: Ryan Snyder on 2011.06.09

== [[Webtools.mozilla.org]] ==

*Prod URL: http://webtools.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== WikiMo / wiki.mozilla.org ==

*Prod URL: http://wiki.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== Wiki Mozilla Japan ==

*Prod URL: http://wiki.mozilla-japan.org/yakugo/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

Websites/Active List

2012-06-19T20:50:12Z

DavidA: /* Viewvc.svn.mozilla.org */

= Details =

A list of Mozilla owned websites and the important details about each of these sites. Please refer to the [[Websites/Domain_List/Mozilla_Owned|Mozilla Owned] list, which is actively update via scripts and DNS queries.

If you do not see your website listed below, please add it in alphabetical order. Use the following template to document all Mozilla websites:

<nowiki>

== [http://wiki.mozilla.org/project-URL Project/Product Name] ==

*Prod URL:
*Stage URL:
*Code Repo:
*L10N Repo:
*Code: Language / Framework
*Licensing:
*Product Owner: Group; Person
*Dev Team: Group; Person
*QA Lead: Person
*Team Email: team-email@example.com
*Last reviewed: Person on mm/dd/yyyy

</nowiki>

= Websites/Applications =
== [[Websites/Affiliates|Affiliates]] ==

*Prod URL: https://affiliates.mozilla.org
*Stage URL: http://affiliates.allizom.org
*Dev URL: http://affiliates-dev.allizom.org
*Code Repo: http://github.com/mozilla/affiliates/
*L10N Repo: https://svn.mozilla.org/projects/l10n-misc/trunk/affiliates/locale/
*Code: Python / Playdoh (Django)
*Licensing: New BSD License
*Product Owner: cnovak
*Web Product Manager: cmore
*Dev Team: mkelly
*QA Lead: mbrandt
*Google Analytics?: Yes
*Last reviewed: malexis 4-4-12

== [[Japan/AMJ|AMJ / addons.mozilla.jp]] ==

*Prod URL: https://addons.mozilla.jp/
*Stage URL: nonpublic
*Code Repo: nonpublic
*L10N Repo: N/A
*Code: PHP
*Product Owner: Mozilla Japan
*Dev Team: Kohei Yoshino
*Team Email: webmaster@mozilla.jp

== [[Air Mozilla]] ==

*Prod URL: http://air.mozilla.org
*Stage URL: http://air.stage.mozilla.org/
*Code Repo:
*L10N Repo:
*Code: PHP / Wordpress
*Product Owner: Richard Milewski
*Dev Team:
*Team Email:
*Google Analytics?: Yes

== [[AMO|AMO / Add-Ons]] ==

*Prod URL: http://addons.mozilla.org
*Stage URL: http://addons.allizom.org
*Code Repo: https://github.com/jbalogh/zamboni/
*L10N Repo:
*Code: Python / Django
*Product Owner: Add-Ons; Justin Scott
*Dev Team: AMO Development; clouserw, potch
*QA Lead: krupa
*Team Email: amo-drivers@mozilla.org
*Last Reviewed: malexis 4-4-12

== [https://intranet.mozilla.org/Apps Apps] ==

*Prod URL: https://apps.mozillalabs.com/
*Stage URL:
*Code Repo: https://github.com/mozilla/openwebapps
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Justin Scott?
*Dev Team: Wil Clowser/AMO?
*QA Lead: Person
*Team Email:
*Last reviewed: malexis 4-4-12

== Brasstacks ==

*Prod URL: http://brasstacks.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Clint Talbert
*Dev Team: Clint Talbert, Jonathan Griffin, Mark Côté, Bob Clary
*QA Lead:
*Team Email:

== [[BMO / bugzilla.mozilla.org]] ==

*Prod URL: http://bugzilla.mozilla.org
*Stage URL: https://bugzilla-stage-tip.mozilla.org/ (public, sanitized) https://bugzilla-stage.mozilla.org/ (restricted access)
*Code Repo: http://bzr.mozilla.org/bmo/4.0/files
*L10N Repo: n/a
*Code: Perl
*Licensing: MPL
*Product Owner: dkl and glob
*Dev Team: dkl, glob, justdave, gerv
*QA Lead: Person
*Team Email:
*Last reviewed:

== Bouncer ==

*Prod URL: http://bounceradmin.mozilla.com
*Stage URL: https://tuxedo.stage.mozilla.com/
*Code Repo: https://github.com/fwenzel/tuxedo
*L10N Repo: --
*Code: Admin interface/API: Python / Django; sentry: perl; download.m.o: PHP
*Product Owner: IT; justdave
*Dev Team: Flux; wenzel, aricaud
*Team Email:
*Last reviewed: fwenzel on 2011.06.09

== [[Bugzilla]] ==

*Prod URL: http://www.bugzilla.org
*Stage URL: http://landfill.bugzilla.org/
*Code Repo: http://bzr.mozilla.org/bugzilla/
*L10N Repo: n/a
*Code:
*Licensing: MPL
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Builder / AMO Builder]] ==

*Prod URL: https://builder.addons.mozilla.org/
*Stage URL:
*Code Repo: https://github.com/mozilla/FlightDeck
*L10N Repo:
*Code: Python / Django
*Product Owner: Add-Ons; Justin Scott
*Dev Team: AMO Development; clouserw
*Team Email:
*Last Reviewed:

== [[Build Your Own Browser]] ==

*Prod URL: http://byob.mozilla.com/
*Stage URL: http://dm-partdist-stage01.mozilla.org/
*Code Repo: https://github.com/lmorchard/byob/
*L10N Repo: (no l10n, yet)
*Code: PHP / Kohana
*Product Owner: Kev Needham
*Dev Team:
*Team Email:

== [[CC - Case Conductor]] ==

*Prod URL: https://caseconductor.allizom.org/
*Stage URL: https://caseconductor.allizom.org/
*Code Repo:
**UI: https://github.com/mozilla/caseconductor
**Platform: https://github.com/mozilla/caseconductor
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Cameron Dawson
*Dev Team: Carl Meyer, Eric Meyer, Jonny Meyer
*QA Lead: Cameron Dawson
*Team Email: tcm@mozilla.com
*Last reviewed:

== [[Community Surveys Europe]] ==

*Prod URL: http://surveys.mozilla-europe.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Design/CreativeCollective|Creative Collective]] ==

*Prod URL: http://creative.mozilla.org
*Stage URL: http://mcc.stage.mozilla.org/
*Code Repo: http://svn.mozilla.org/projects/mcc/
*L10N Repo:
*Code: PHP / Kohana
*Product Owner: Engagement; Tara Shahian
*Dev Team: Flux; Ryan Snyder
*QA Lead: krupa
*Team Email:
*Last Reviewed: rysny on 2011.06.08

== [https://wiki.mozilla.org/Websites/Blog-The-Den Den, The (blog)] ==

*Prod URL: 
*Stage URL: blog.mozilla.com does not currently have a staging environment 
*Code Repo: [https://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content/themes/ https://svn.mozilla.org/projects/blog.mozilla.com/trunk/wp-content/themes/] 
*L10N Repo: no l10n at this stage 
*Code: HTML, PHP, Wordpress 
*Product Owner: User Engagement; Carmen Collins & Jane Finette 
*Dev Team: silverorgange, Mike Alexis, Chrissie Brodigan
*QA Lead: 
*Team Email:
*Last Reviewed: cb on 2011.30.10 

== [[Demo Dashboard]] ==

*Prod URL: https://myapps.mozillalabs.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Websites/Despot|Despot]] ==

*Prod URL: http://despot.mozilla.org
*Stage URL: N/A
*Code Repo: mozilla/webtools/despot/ (CVS)
*L10N Repo: N/A
*Code: Perl
*Product Owner: Dave Miller
*Dev Team: Dave Miller, Reed Loden
*Team Email: N/A
*Last reviewed: cmore on 2011/06/13

== [[Doctor]] ==

*Prod URL: https://doctor.mozilla.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Donate]] ==

*Prod URL: https://donate.mozilla.org/
*Stage URL: No staging URL
*Code Repo:
*L10N Repo: http://viewvc.svn.mozilla.org/vc/projects/l10n-misc/trunk/joinmozilla/
*Code: Uses CRM with CMS functionality
*Product Owner: Ryan Merkley (ryan@mozillafoundation.org)
*Dev Team: Contractors
*Team Email:
*Contractor Ticket System: http://bsd.zendesk.com

== [[Drumbeat]] ==

*Prod URL: https://www.drumbeat.org/
*Stage URL: https://batucada.mozillalabs.com/
*Code Repo: https://github.com/paulosman/batucada
*L10N Repo: Not localized
*Code: Python / Django
*Product Owner: paulosman
*Dev Team: Drumbeat; paulosman
*Team Email: drumbeat-website@lists.mozilla.org
*Last Reviewed: paulosman on 2011.05.20

== [[DXR]] ==

*Prod URL: http://dxr.mozilla.org/
*Stage URL:
*Code Repo: http://hg.mozilla.org/webtools.dxr
*L10N Repo: Not localized
*Code: Python (among others)
*Licensing: MIT (among others)
*Product Owner:
*Dev Team: jcranmer
*Team Email:
*Last reviewed:

== [[Elmo]] ==

*Prod URL: https://l10n-stage-sj.mozilla.org/
*Stage URL: not set up yet
*Code Repo: https://github.com/mozilla/elmo
*L10N Repo: N/A
*Code: Python / Playdoh
*Licensing: MPL
*Product Owner: l10n-drivers; Axel Hecht, Stas Malolepszy
*Dev Team: Webtools; Peter Bengtsson, Laura Thomson
*QA Lead: Stephen Donner
*Team Email: tools-elmo@lists.mozilla.org
*Last reviewed: laura on 2011.6.13

 

== [[European Mozilla Community Blog]] ==

*Prod URL: http://blogs.mozilla-europe.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Extend Firefox]] ==

*Prod URL: http://extendfirefox.com/mobile-cup/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Firefox Flicks]] ==

*Prod URL:
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Kristin Baird, Chelsea Novak
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Firefox Heatmap]] ==

*Prod URL: https://heatmap.mozillalabs.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Firefox Input]] ==

*Prod URL: http://input.mozilla.com/
*Stage URL: http://input.allizom.org/
*Code Repo: https://github.com/mozilla/input.mozilla.com/
*L10N Repo: https://svn.mozilla.org/projects/reporter/locale/
*Code: Python / Django
*Product Owner: Engagement; Aakash Desai
*Dev Team: Flux; Dave Dash
*QA Lead: mbrandt, davehunt
*Team Email: input@mozilla.com
*Last Reviewed: ddash on 2011.08.04

== [[Firefox Nightly Builds]] ==

*Prod URL: http://nightly.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Firefox Start China]] ==

*Prod URL: http://zh-cn.start3.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Firefox Sync » Home]] ==

*Prod URL: https://services.mozilla.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Getfirebug Blog]] ==

*Prod URL: http://blog.getfirebug.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Get Firebug]] ==

*Prod URL: http://getfirebug.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Graphite]] ==

*Prod URL: http://graphite.mozilla.org
*Stage URL:
*Code Repo: https://github.com/jsocol/pystatsd
*L10N Repo:
*Code:
*Product Owner: WebDev
*Dev Team: WebDev; jbalogh, jsocol
*Team Email:

== [[Hacks]] ==

*Prod URL: http://hacks.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code: Wordpress plus static files (?)
*Product Owner:
*Dev Team:
*Team Email:

== [[InterFORest]] ==

*Prod URL: http://interforest.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Intlstore.mozilla.org]] ==

*Prod URL: http://intlstore.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner: Engagement; John Slater
*Dev Team:
*Team Email:

== [[Intranet.mozilla.org]] ==

*Prod URL: https://intranet.mozilla.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[ISP Database]] ==

*Prod URL: http://ispdb.mozillamessaging.com
*Stage URL: http://stage.ispdb.mozillamessaging.com/
*Code Repo: http://svn.mozilla.org/mozillamessaging.com/sites/ispdb.mozillamessaging.com/
*L10N Repo:
*Code: Python/Django
*Product Owner: [[User:Sancus|Sancus]]
*Dev Team: [[User:Sancus|Sancus]]
*Team Email: sancus@mozillamessaging.com

== [[JP Open Timetable]] ==

*Prod URL: http://opentimetable.jp
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Kraken JavaScript Benchmark]] ==

*Prod URL: http://krakenbenchmark.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Landfill: The Bugzilla Test Server]] ==

*Prod URL: http://landfill.bugzilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Learning Freedom and the Web]] ==

*Prod URL: http://learningfreedomandtheweb.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner: Ben Moskowitz (ben@mozillafoundation.org)
*Dev Team:
*Team Email:

== lists.mozilla-europe.org ==

*Prod URL: http://lists.mozilla-europe.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Litmus]] ==

*Prod URL: https://litmus.mozilla.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Lizard Feeder]] ==

*Prod URL: http://feeds.mozilla.org
*Stage URL: (none)
*Code Repo: http://svn.mozilla.org/projects/lizardfeeder/
*L10N Repo: (none)
*Code: Python, based on Planet Venus
*Product Owner: (none)
*Dev Team: lorchard
*Team Email: (none)

== [[Mozilla Cross-Reference]] ==

*Prod URL: http://mxr.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Modest / Mozilla Developer Street]] ==

*Prod URL: https://dev.mozilla.jp/
*Stage URL: N/A
*Code Repo: nonpublic
*L10N Repo: N/A
*Code: PHP / WordPress
*Product Owner: Mozilla Japan
*Dev Team: Tomoya Asai
*Team Email: webmaster@mozilla.jp

== [[MDN|Mozilla Developer Network / MDN]] ==

*Prod URL: https://developer.mozilla.org/
*Stage URL:
**https://developer-stage9.mozilla.org/
**https://kuma-stage.mozilla.org/
*Code: Python / Django, DekiWiki
*Code Repo:
**https://github.com/mozilla/kuma
*L10N Repo:
**http://svn.mozilla.org/projects/mdn/trunk/locale/
**http://svn.mozilla.org/projects/deki/trunk/mozilla/resources/
*Product Owner: Engagement, Sheppy
*Dev Team: MDN; luke crouch, lorchard
*Team Email: dev-mdn@lists.mozilla.org
*Last Reviewed: malexis 4-4-12

== [[Mozilla Europe Events Registration]] ==

*Prod URL: http://events.mozilla-europe.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla F1]] ==

*Prod URL: http://f1.mozillamessaging.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Firefox GB Download]] ==

*Prod URL: http://browserchoice.mozilla.com/lang/en-GB
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Firefox User Panel]] ==

*Prod URL: http://userpanel.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Hispano]] ==

*Prod URL: http://www.mozilla-hispano.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Japan]] ==

*Prod URL: http://mozilla.jp/
*Stage URL: nonpublic
*Code Repo: nonpublic; portions of the site are published with a CMS
*L10N Repo: N/A
*Code: PHP
*Product Owner: Mozilla Japan
*Dev Team: Kohei Yoshino
*Team Email: webmaster@mozilla.jp

== [[Mozilla Labs Design Challenge]] ==

*Prod URL: http://design-challenge.mozillalabs.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Labs Design Challenge]] ==

*Prod URL: http://www.designchallenges.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Labs Gaming]] ==

*Prod URL: https://gaming.mozillalabs.com/
*Stage URL:
*Code Repo: https://github.com/mozilla/doozer
*L10N Repo:
*Code: Python / Django
*Product Owner: Labs; -
*Dev Team: potch, jsocol (IT/Ops), r1cky
*Team Email:

== [[Labs|Mozilla Labs]] ==

*Prod URL: http://mozillalabs.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner: Labs; Todd Simpson
*Dev Team:
*Team Email:
*Last Reviewed:

== [[Mozilla Labs Test Pilot]] ==

*Prod URL: https://testpilot.mozillalabs.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Labs - Ubiquity]] ==

*Prod URL: http://ubiquity.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Messaging Blogs]] ==

*Prod URL: http://blogs.mozillamessaging.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Messaging]] ==

*Prod URL: http://noc.mozillamessaging.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla.org Archive]] ==

*Prod URL: http://www-archive.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla.org]] ==

*Prod URL: http://mozilla.org/
*Stage URL: http://www-stage.mozilla.org/
*Code Repo: http://viewvc.svn.mozilla.org/vc/projects/mozilla.org/
*L10N Repo: n/a
*Code: PHP
*Product Owner:
* 
*Content Owner: David Boswell
* 
*Design Owner: John Slater
* 
*Technical Owner: TBD
*Dev Team: David Boswell and contractors
*Team Email: n/a
*Discuss Forum: http://groups.google.com/group/mozilla.dev.mozilla-org/topics

== [[Mozilla Pastebin]] ==

*Prod URL: http://pastebin.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Public License]] ==

*Prod URL: http://mpl.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozilla Pulse]] ==

*Prod URL: http://pulse.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Jonathan Griffin
*Dev Team: Jonathan Griffin, a-team
*QA Lead:
*Team Email: tools-pulse@lists.mozilla.org
*Last reviewed:

== [[MozillaZine.jp]] ==

*Prod URL: http://forums.mozillazine.jp
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[MozillaZine.jp]] ==

*Prod URL: http://mozillazine.jp
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Mozillians]] ==

*Prod URL: http://mozillians.org
*Stage URL: https://mozillians-dev.allizom.org
*Code Repo: https://github.com/mozilla/mozillians
*L10N Repo: http://svn.mozilla.org/projects/l10n-misc/trunk/mozillians
*Code: Python, LDAP
*Product Owner: David Boswell
*Dev Team: davedash, tofumatt, Gerv Markham
*TPM: Austin King
*Team Email: team-mozillians AT mozilla DOT com
*Discussion Forum: http://groups.google.com/group/mozilla.mozillians/topics
*Planning wiki: [[Mozillians]]

== [[Perfomatic|Perfomatic Graph Server]] ==

*Prod URL: http://graphs.mozilla.org
*Stage URL: http://graphs.allizom.org
*Prod.next URL: http://graphs-new.mozilla.org
*Code Repo: https://github.com/rhelmer/graphs
*L10N Repo:
*Code: Python, JavaScript
*Product Owner: WebDev
*Dev Team: rhelmer
*Team Email: rhelmer@mozilla.com
*Last Reviewed: rhelmer on 2011.06.01

== [[Personas]] ==

*Prod URL: http://www.getpersonas.com/
*Stage URL: http://personas.stage.mozilla.com/
*Code Repo:
*L10N Repo:
*Code:
*Product Owner: :dria, clouserw
*Dev Team:
*QA Lead: vish_moz
*Team Email: personas@mozilla.com
*Last Reviewed: clouserw on 2011.05.20

== [[Planet Bugzilla]] ==

*Prod URL: http://planet.bugzilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Planet.firefox.com/]] ==

*Prod URL: http://planet.firefox.com/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team: fx-team
*Team Email: fx-team@mozilla.com

== [[Planet.firefox.com/mobile]] ==

*Prod URL: http://planet.firefox.com/mobile
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Planet Mozilla (de)]] ==

*Prod URL: http://planet.mozilla.de
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Planet.mozillamessaging.com]] ==

''we are in the process of changing this to "Planet Thunderbird" ''

*Prod URL: http://planet.mozillamessaging.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:
*Last Reviewed:

== [[Planet.mozilla.org]] ==

*Prod URL: http://planet.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Plugin Directory]] ==

*Prod URL: http://plugins.mozilla.org/
*Stage URL: http://plugins.stage.mozilla.com/
*Code Repo: http://github.com/lmorchard/plugindir
*L10N Repo:
*Code: PHP / Kohana / JavaScript
*Product Owner: Kev Needham
*Devs: AMO
*Team Email: pluginsposse AT mozilla DOT com
*Last Reviewed: rysny on 2011.06.09

== [[Popcorn]] ==

*Prod URL: http://mozillapopcorn.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:
*Last reviewed:

== [[Privacy]] ==

*Prod URL: http://www.mozilla.org/privacy/
*Stage URL: http://www-dev.allizom.org/en-US/privacy/
*Code Repo: http://viewvc.svn.mozilla.org/vc/projects/mozilla.com/trunk/en-US/privacy/
*L10N Repo:
*Code:
*Licensing:
*Product Owner: Alex Fowler, Tom Lowenthal
*Dev Team: /firefox website team/silverorange
*QA Lead: /firefox website team/silverorange
*Team Email:
*Last reviewed:

== [[Public Website Health Status for Mozilla]] ==

*Prod URL: http://status.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[QMO|QMO / quality.mozilla.org]] ==

*Prod URL: http://quality.mozilla.org
*Stage URL: http://quality-new.stage.mozilla.com/
*Code Repo:
*L10N Repo:
*Code: PHP / Wordpress
*Product Owner: Metrics; Al Billings
*Dev Team: TPM, Chris More; Design, Craig Cook
*QA Lead: rbillings
*Team Email:
*Last Reviewed: rysny on 2011.06.08

== releases.mozilla.org ==

*Prod URL: http://releases.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Websites/ReMo_Mozilla_Reps|ReMo Mozilla Reps]] ==

*Prod URL:
*Stage URL:
*Dev URL: http://reps-dev.allizom.org/
*Code Repo: https://github.com/mozilla/remo
*L10N Repo: N/A
*Licensing: N/A
*Product Owner: Pierros Papadeas
*Dev Team: Giorgos Logiotatidis (Contractor)
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Rock Your Firefox]] ==

*Prod URL: http://rockyourfirefox.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Security]] ==

*Prod URL: https://securitywiki.mozilla.org/ (Members of Security-Group Only)
*Prod URL: https://wiki.mozilla.org/Security
*Code Repo: n/a
*L10N Repo: n/a
*Product Owner: Lucas Adamski
*Team Email: secteam@mozilla.com
*Last Reviewed:

== [[Socorro|Socorro / Crash Stats]] ==

*Prod URL: http://crash-stats.mozilla.com/
*Stage URL: http://crash-stats.stage.mozilla.com/
*Code Repo: http://code.google.com/p/socorro/
*L10N Repo: n/a
*Code: Python back-end; PHP / Kohana front-end
*Product Owner:
*Dev Team: Webtools; Laura Thomson
*QA Lead: mbrandt
*Team Email: socorro-dev@mozilla.com
*Last Reviewed: rysny on 2011.06.08

== [[Websites/Spark|Spark]] ==

*Prod URL: http://spark.mozilla.org/
*Stage URL: http://spark.allizom.org/
*Code Repo:
**https://github.com/mozilla/spark
**https://github.com/mozilla/spark-lib
*L10N Repo: http://svn.mozilla.org/projects/l10n-misc/trunk/spark
*Code: Python / Django
*Product Owner: Engagement; Caitlin Looney
*Dev Team: Flux; Ryan Snyder, Little Workshop (Dev)
*QA Lead: retornam
*Team Email:
*Last Reviewed: rysny on 2011.06.08

== [[Store.mozilla.org]] ==

*Prod URL: http://store.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Student Reps]] ==

*Prod URL: http://studentreps.mozilla.org
*Stage URL: http://studentreps.stage.mozilla.com
*Code Repo: https://svn.mozilla.org/studentreps
*L10N Repo:
*Code: PHP
*Product Owner:
*Dev Team: craigcook
*Team Email:

== [[Sumo|SUMO / Mozilla Support]] ==

*Prod URL: http://support.mozilla.org/
*Stage URL: http://support.allizom.org/
*Code Repo: https://github.com/mozilla/kitsune
*L10N Repo: http://viewvc.svn.mozilla.org/vc/projects/sumo/locales
*Code: Python / Django
*Product Owner: Kadir Topal
*Dev Team: jsocol, rrosario, timw, willkg
*QA Lead: rbillings
*Team Email: sumo-dev@mozilla.com
*Last Reviewed: James Socol on 2012-03-01

== [[The Mozilla Blog]] ==

*Prod URL: http://blog.mozilla.com
*Stage URL:
*Code Repo:
*L10N Repo:
*Code: PHP; Wordpress
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead:
*Team Email:
*Last reviewed: rysny on 2011.06.09

== [[Thunderbird Support]] ==

*Prod URL: http://support.mozillamessaging.com
*Stage URL: http://support-stage.mozillamessaging.com/
*Code Repo: https://github.com/sancus/kitsune
*L10N Repo: http://svn.mozilla.org/projects/sumo/locales/
*Code: Python/Django, fork of Kitsune
*Product Owner: Thunderbird; Roland Tanglao; Jennifer Zickerman
*Dev Team: [[User:Sancus|Sancus]]
*Team Email: sancus@mozillamessaging.com

== [[Tinderbox]] ==

*Prod URL: http://tinderbox.mozilla.org
*Stage URL: http://tinderbox-stage.mozilla.org
*Code Repo: CVS mozilla/webtools/tinderbox
*L10N Repo: None
*Code: Perl
*Licensing: NPL 1.1
*Product Owner: webtools
*Dev Team: whoever is slowest
*QA Lead: Person
*Team Email:
*Last reviewed:

== [[Tools.mozilla.com]] ==

*Prod URL: http://tools.mozilla.com
*Stage URL:
*Code Repo: https://svn.mozilla.org/projects/openweb/
*L10N Repo:
*Code:
*Product Owner: Webdev (?)
*Dev Team: Laura
*Team Email:

== [[Verbatim]] ==

*Prod URL: https://localize.mozilla.org/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [[Videos.mozilla.org]] ==

*Prod URL: http://videos.mozilla.org
*Stage URL: --
*Code Repo: https://videos-origin.mozilla.org
*L10N Repo: --
*Code: -- (just a file listing on the CDN, access via webdav)
*Product Owner: IT
*Dev Team: IT
*Team Email:
*Last reviewed: fwenzel on 2011.06.09

== [[Viewvc.svn.mozilla.org]] ==

*Prod URL: http://viewvc.svn.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== [http://wiki.mozilla.org/Webmaker Webmaker] ==

*Prod URL: www.webmaker.org
*Stage URL: https://make-stage.mozillalabs.com
*Code Repo: https://github.com/rossbruniges/make.mozilla.org
*L10N Repo: None yet
*Code: Python / Playdoh
*Licensing:
*Product Owner: Mozilla Foundation ; Matt Thompson;
*Dev Team: Mozilla Foundation; Ross Bruniges
*QA Lead: Mozilla Foundation
*Team Email:
*Last reviewed:

(note: thimble.webmaker.org is its own site)

== Web o' Wonder ==

*Prod URL: http://developer.mozilla.org/demos/
*Stage URL: http://webofwonder.allizom.org/en-US/
*Code Repo: https://github.com/mozilla/webowonder
*L10N Repo:
*Code: Python / Django
*Product Owner: Engagement; Laura Mesa
*Dev Team: Flux; Austin King, Jason Grlicky
*QA Lead: retornam
*Team Email:
*Last Reviewed: Ryan Snyder on 2011.06.09

== [[Webtools.mozilla.org]] ==

*Prod URL: http://webtools.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

== WikiMo / wiki.mozilla.org ==

*Prod URL: http://wiki.mozilla.org
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Product Owner:
*Dev Team:
*Team Email:

== Wiki Mozilla Japan ==

*Prod URL: http://wiki.mozilla-japan.org/yakugo/
*Stage URL:
*Code Repo:
*L10N Repo:
*Code:
*Licensing:
*Product Owner:
*Dev Team:
*QA Lead: Person
*Team Email:
*Last reviewed:

Thimble

2012-06-18T23:48:00Z

DavidA: /* Coordination */

== Summary ==

=== Mission ===

Thimble creates and hosts web pages for novice HTML authors, as part of the [http://webmaker.org/ Mozilla webmaker initiative]

=== Coordination ===

* [https://etherpad.mozilla.org/webpagemaker-meeting meeting notes and dial-in info: wednesdays at 8am Pacific / 11am Eastern]
* [https://groups.google.com/forum/?fromgroups#!forum/webpagemaker google group/mailing list]
* [https://github.com/mozilla/webpagemaker github repo]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Thimble security bugs go here]
* [http://webpagemaker-dev.allizom.org/ dev site]
* [http://webpagemaker.allizom.org/ staging site]
* [http://thimbletest.org/ user testing site]
* we hang out in #thimble and #webpagemaker

=== Links ===
* [https://etherpad.mozilla.org/thimbleraci Roles]
* [https://etherpad.mozilla.org/webpagemaker-meeting webpagemaker-meeting]
* [https://etherpad.mozilla.org/webmaker-for-summer-campaign webmaker-for-summer-campaign]
* [https://etherpad.mozilla.org/webpagemaker-pitch webpagemaker-pitch]
* [https://mozlearning.etherpad.mozilla.org/design-principles design-principles]
* [https://etherpad.mozilla.org/webmaker-rfc webmaker-rfc]
* [https://etherpad.mozilla.org/assessment-builder assessment-builder]

Thimble

2012-06-18T23:47:23Z

DavidA: /* Coordination */

== Summary ==

=== Mission ===

Thimble creates and hosts web pages for novice HTML authors, as part of the [http://webmaker.org/ Mozilla webmaker initiative]

=== Coordination ===

* [https://etherpad.mozilla.org/webpagemaker-meeting meeting notes and dial-in info: wednesdays at 8am Pacific / 11am Eastern]
* [https://groups.google.com/forum/?fromgroups#!forum/webpagemaker google group/mailing list]
* [https://github.com/mozilla/webpagemaker github repo]
* [https://bugzilla.mozilla.org/enter_bug.cgi?product=Thimble security bugs go here]
* [http://webpagemaker-dev.allizom.org/ dev site]
* [http://thimbletest.org/ user testing site]

=== Links ===
* [https://etherpad.mozilla.org/thimbleraci Roles]
* [https://etherpad.mozilla.org/webpagemaker-meeting webpagemaker-meeting]
* [https://etherpad.mozilla.org/webmaker-for-summer-campaign webmaker-for-summer-campaign]
* [https://etherpad.mozilla.org/webpagemaker-pitch webpagemaker-pitch]
* [https://mozlearning.etherpad.mozilla.org/design-principles design-principles]
* [https://etherpad.mozilla.org/webmaker-rfc webmaker-rfc]
* [https://etherpad.mozilla.org/assessment-builder assessment-builder]

MoTown

2012-06-14T05:57:18Z

DavidA: /* Communications */

MoTown is two things: it hopes to be a reference implementation of a provider for the SocialAPI, and to be a useful service for people involved in the Mozilla project.

== Links ==

* [[Labs/SocialAPI | Intro to SocialAPI]]
* [https://github.com/mozilla/motown github repo for motown]
* [https://github.com/mozilla/socialapi-dev github repo for social API]
* [https://github.com/mozilla/socialapi-dev/blob/develop/docs/socialAPI.md API docs]

== Communications ==

* We hang out in the #motown IRC channel
* We meet Wednesdays at 2pm Pacific, in the Motown Vidyo room
* [https://etherpad.mozilla.org/motown-minutes Meeting Minutes]

== Credits ==

Andrew Sutherland came up with the name.

MoTown

2012-06-14T05:57:02Z

DavidA: /* Communications */

MoTown is two things: it hopes to be a reference implementation of a provider for the SocialAPI, and to be a useful service for people involved in the Mozilla project.

== Links ==

* [[Labs/SocialAPI | Intro to SocialAPI]]
* [https://github.com/mozilla/motown github repo for motown]
* [https://github.com/mozilla/socialapi-dev github repo for social API]
* [https://github.com/mozilla/socialapi-dev/blob/develop/docs/socialAPI.md API docs]

== Communications ==

* We hang out in the #motown IRC channel
* We meet Wednesdays at 2pm Pacific, in the Motown Vidyo room
* [[https://etherpad.mozilla.org/motown-minutes Meeting Minutes]]

== Credits ==

Andrew Sutherland came up with the name.