MozillaWiki - User contributions [en]

MozWeek/Whistler2019/Contributor nominations

2019-03-18T23:30:56Z

Groter: remove people

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful contributors, collaborators, and volunteers join the event, integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Whistler All Hands.

== Goals ==
The goals of the nomination process are:

# Invite contributors, collaborators and volunteers who are important to the success of and have a high level of commitment to specific projects, teams or Mozilla overall
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Mozilla teams are thinking about contributors strategically
# A process that has legitimacy with contributors and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || March 19 || April 1
|-
| 2) Review and final prioritization || April 1 || April 5
|-
| 3) Invitations go out || April 5 || -
|-
| 4) Registration and flight booking → information about this will be on another page || April 5 || April 15
|-
| 5) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || April 5 || June 17
|}

''Important note''
* We are emphasizing greater gender balance for nominated contributors -- based on the past, our hope is to have 30% non-male contributors attending

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting contributor nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox/Product || Mike Hoye (mhoye)
|-
| Emerging Technologies || Nancy Hang (nhang)
|-
| Operations (incl Open Innovation) || Lucy Harris (lharris)
|}

''Organization Designates will be accountable for:''
* Creating/curating a contributor nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited

== Number of Contributors ==
We have space for roughly 90 contributors.

== Criteria for contributor nominees ==
[[All_Hands/Whistler2019/Contributor_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a contributor or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

MozWeek/Whistler2019/Contributor nominee criteria

2019-03-18T23:15:26Z

Groter: new page

Below are guidelines for which contributors should nominated for the 2019 Whistler All Hands.

== Must have for all contributors at All Hands: ==
# '''Impact:''' have made or are able to make a significant impact on Mozilla project or team goals
# '''Commitment:''' have demonstrated that they will make a sustained contribution to a project, team, or Mozilla in 2019, after the All Hands

== Nomination Criteria ==
There should be a very high bar for all nominees

* Currently contributing to or collaborating on a strategically relevant project or initiative
* Consistently involved
* Making high impact, unique contributions that would be hard to achieve without their involvement

=== Not criteria ===
Attending an All Hands is not a reward -- purely wanting to recognize someone for their past contribution is not a nomination criteria.

MozWeek/Whistler2019/Contributor nominations

2019-03-18T23:13:53Z

Groter: Created new page

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful contributors, collaborators, and volunteers join the event, integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Whistler All Hands.

== Goals ==
The goals of the nomination process are:

# Invite contributors, collaborators and volunteers who are important to the success of and have a high level of commitment to specific projects, teams or Mozilla overall
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Mozilla teams are thinking about contributors strategically
# A process that has legitimacy with contributors and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || March 19 || April 1
|-
| 2) Review and final prioritization || April 1 || April 5
|-
| 3) Invitations go out || April 5 || -
|-
| 4) Registration and flight booking → information about this will be on another page || April 5 || April 15
|-
| 5) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || April 5 || June 17
|}

''Important note''
* We are emphasizing greater gender balance for nominated contributors -- based on the past, our hope is to have 30% non-male contributors attending

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting contributor nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox/Product || Mike Hoye (mhoye)
|-
| Emerging Technologies || Nancy Hang (nhang)
|-
| People || Lizz Noonan (lmn)
|-
| Operations (incl Open Innovation) || Lucy Harris (lharris)
|}

''Organization Designates will be accountable for:''
* Creating/curating a contributor nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited

== Number of Contributors ==
We have space for roughly 90 contributors.

== Criteria for contributor nominees ==
[[All_Hands/Whistler2019/Contributor_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a contributor or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

Diversity and Inclusion for Communities and Contributors

2019-03-04T12:23:06Z

Groter: small changes to fix links

=Overview=
The heart of Mozilla is people, and we are committed to being a diverse and inclusive community - one that invites in, and empowers everyone no matter their gender, sexual orientation, nationality, age, ability, socioeconomic status or religion (or lack thereof).

'''At Mozilla''', we think of diversity as the mix of people, and inclusion as how we enable that diverse mix to work effectively together - to innovate and have impact on the mission we care so much about.

'''On the Open Innovation Team''', we see our role helping elevate knowledge and leadership for D&I in Open Source as an opportunity to improve diversity in open source overall. Through collaboration and open knowledge sharing, 2019 will be about building bridges and surfacing critical problems and voices for the better of all open communities everywhere.

== Discussion ==
* [https://groups.google.com/forum/?hl=en-gb#!forum/diversity--inclusion-in-open-source Diversity & Inclusion in Open Source Mailing List]
* #OpenSourceDiversity (Social Media)

== D&I in Open Communities - Call ==
=== Future Calls ===

* [https://events.mozilla.org/applyingdidatametricsinopensou February 21 2019: '''Applying D&I Data & Metrics in Open Source - A Mozilla Case Study''']
* [https://events.mozilla.org/everydayactionstobeabetterally March 7 2019: '''Everyday Actions to Be a Better Ally''']
* [[Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_03_21_2019| March 21 2019: '''Open Source Maintainer - Strategies for Helping Diverse People Step into Technical Leadership''']]
* [[Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_04_04_2019| April 4, 2019: '''Data, Metrics, Ethics''']]
---
* [[ Date TBD, '''2019: Emilie Nicolas''']]

=== Past Calls ===
* [[Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_11_09_2018|November 9th Kim Christen and Jane Anderson 'TK Labels']]
* [[Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_09_04_2018|September 4th Jess Mitchell 'Inclusive design and thinking differently']]
* [[Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_07_14_2018|July 14th 'Gender-biases Embedded in the Software ']] talk streamed from Mozilla Portland office, to coincide with the [http://www.communityleadershipsummit.com/ Community Leadership Summit].
* [[Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_06_27_2018|August 1st 'Open Governance']] - governance topics with a lens on inclusion by [https://wiki.mozilla.org/Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_06_27_2018#June_27.2C_2018_-_Inclusive_Open_Source_Governance/ Open Source Archetype];
* June 6th [https://wiki.mozilla.org/Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_06_06_2018 We See you! Inclusive Communities & Events]
* May 2nd, "[https://wiki.mozilla.org/Diversity_and_Inclusion_for_Communities_and_Contributors/DI_Call_05_02_2018 All Things 'Code of Conduct']"
* April 4th, 9AM PDT ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180404T09&p1=1091&ah=1 Covert to local time]) "'''Diversity & Inclusion in Open Source (all topics)'''", [https://public.etherpad-mozilla.org/p/open-source-community-call Etherpad Agenda], Streaming Link, Live Captioning
* February 28th, 9AM PST ([https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180228T1700 Convert to local time]) Agenda [https://public.etherpad-mozilla.org/p/open-source-community-call Etherpad] , [https://www.youtube.com/watch?v=U3aPHZpgAls Streaming Link], [https://www.streamtext.net/player?event=MozillaDiversityInclusion Live Captioning]

== Inclusion Resources ==

==== Assessment Tools ====

'''[https://github.com/mozilla/diversity/blob/master/evaluation_tools/governance-basic.md (Basic) Inclusive Governance Checklist]'''
A simple way to review your open source project for inclusive design.

'''[https://github.com/chaoss/wg-diversity-inclusion/blob/master/focus-areas/leadership/assets/leadership-principles.md Inclusive Leadership Principles ]'''
Ensure your community leadership (or roles of influence) are setup for success.

'''[https://mozilla.github.io/diversity-coc-review.io/ Code of Conduct Assessment Tool]
Evaluate your Code of Conduct.

==== D&I Data & Metrics ====
All of Mozilla's D&I Data & Metrics works has been ported to the CHAOSS D&I Working Group, where we continue to collaborate. The working group holds weekly calls, details are in the [README https://github.com/chaoss/wg-diversity-inclusion/blob/master/README.md.

=== Code of Conduct Enforcement ===

==== Standards, Best Practices ====

'''[https://github.com/mozilla/diversity/blob/master/code-of-conduct-enforcement/consequence-ladder.md Consequence Ladder]'''
How Mozilla issues consequences when our Code of Conduct (CPG) is violated.

'''[https://github.com/mozilla/diversity/blob/master/code-of-conduct-enforcement/investigation/working-group/role-groups.md Decision Making - Role Groups & RASCI]'''
How Mozilla make decisions in cases that are more complex, or span multiple stakeholders.

'''[https://github.com/mozilla/diversity/blob/master/code-of-conduct-enforcement/investigation/working-group/incident-investigation-template.md Incident Report Template]'''
How we track more complex investigation.

'''[https://docs.google.com/document/d/1rQoxKgOBkH1WfC4bDcXq_0y5MK7RWbbeDk4uqNjQMBc/edit Triage Rules]'''
How we triage cases.

==== Communication Templates ====

* [https://github.com/mozilla/diversity/blob/master/code-of-conduct-enforcement/investigation/communication/reported-request-for-clarification.md Request for more information]
* [https://github.com/mozilla/diversity/blob/master/code-of-conduct-enforcement/investigation/communication/reporter-investigation-started.md Your report was received]
* Reported - [https://github.com/mozilla/diversity/tree/master/code-of-conduct-enforcement/decisions/communication/decision-comms/reported decision per ladder leve]l
* Reporter - [https://github.com/mozilla/diversity/tree/master/code-of-conduct-enforcement/decisions/communication/decision-comms/reporter decision per ladder]

== Project and Initiative Repos ==

* [https://github.com/mozilla/diversity/ Mozilla CoC, and other resource Diversity and Inclusion Repo]
* [https://github.com/mozilla/maintainer-cohortMaintainer Cohort]
* [https://github.com/chaoss/wg-diversity-inclusion/ CHAOSS D&I Working Group]
* [https://github.com/mozilla/diversity-coc-review Code of Conduct Review Tool Repo]

== Blogs & Reports 2018 ==
* [https://docs.google.com/presentation/d/13UxBGj2lI66SLjl6sp4NE3DH2ndT0k5QM0pPyyzZXuY/edit#slide=id.g39181845f1_0_14 D&I in Open Source - What I learned from a survey of 204 open source projects]
* [https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415 How We're Making Code of Conduct Real - and Scaling it https://medium.com/mozilla-open-innovation/how-were-making-code-of-conduct-enforcement-real-and-scaling-it-3e382cf94415]
* [https://medium.com/@sunnydeveloper/what-we-learned-about-gender-identity-in-open-source-d9acea0b7586 What we learneda bout gender identity in Open Source]
* [https://medium.com/@sunnydeveloper/squash-inclusion-bugs-982a3e5ee29d This December - Squash Open Source Inclusion Bugs! ]

== 2017 Research & Strategy Report ==

* [https://docs.google.com/document/d/1ZK7l4e9-UVTMacxmmCzA8pDqVfsZOahkBC6eIOsRQyc/edit State of Diversity & Inclusion in Mozilla's Communities]

== Blogs 2017 ==
* [https://medium.com/@sunnydeveloper/what-we-learned-about-gender-identity-in-open-source-d9acea0b7586 What we learned about gender identity in Open Source]
* [https://medium.com/mozilla-open-innovation/a-time-for-action-innovating-for-diversity-inclusion-in-open-source-communities-6922fef4675e A Time for Action - Innovating for D&I in Open Source] (Series Intro)
* [https://medium.com/mozilla-open-innovation/reflection-inclusive-organizing-for-open-source-communities-9c44f0b689c1 Inclusive Organizing for Communities]
* [https://medium.com/mozilla-open-innovation/we-see-you-reaching-diverse-audiences-in-foss-4e83efc86425 We See You! Reaching Diverse Audiences in FOSS]
* [https://medium.com/mozilla-open-innovation/frameworks-for-governance-incentive-and-consequence-in-foss-e1de6c091bdc Frameworks for Governance, Incentive & Consequence]

=== Event Links ===
* [https://medium.com/@sunnydeveloper/take-action-innovation-requires-diversity-ossummit-foss-opensource-de24d8bf853d Open Source Summit Blog] (w/ industry links)

MozWeek/Orlando2018/Contributor nominations

2018-09-04T14:41:00Z

Groter: change date

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful contributors, collaborators, and volunteers join the event, integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Orlando All Hands.

== Goals ==
The goals of the nomination process are:

# Invite contributors, collaborators and volunteers who are important to the success of and have a high level of commitment to specific projects, teams or Mozilla overall
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Mozilla teams are thinking about contributors strategically
# A process that has legitimacy with contributors and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || Sept 4 || Sept 14
|-
| 2) Applications -- very lightweight application sent to '''all nominees''' to ensure nominees are available and want to attend || Sept 17 || Sept 26
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 26 || Sept 28
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Sept 28 || -
|-
| 5) Invitations go out || Sept 28 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Sept 28 || Oct 12
|-
| 7) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || Sept 28 || Dec 3
|}

''Important note''
* We are emphasizing greater gender balance for nominated contributors

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting contributor nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox/Product || Mike Hoye (mhoye)
|-
| Emerging Technologies || Nancy Hang (nhang)
|-
| IT/Policy/Strategy/WPR || Michael Van Kleeck (mvk)
|-
| Marketing || Michal Dziewonski (vesper)
|-
| People || Lizz Noonan (lmn)
|-
| Open Innovation || Konstantina Papadea (kpapadea)
|}

''Organization Designates will be accountable for:''
* Creating/curating a contributor nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited

== Number of Contributors ==
We have space for roughly 90 contributors.

== Criteria for contributor nominees ==
[[All_Hands/Orlando2018/Contributor_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a contributor or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

MozWeek/Orlando2018

2018-09-03T12:40:58Z

Groter: added link to contributor participation process

'''What is it?''' -- Multiple team meetings, 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!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''

=='''Dates, Location and Weather'''==
Monday, December 3 - Friday, December 7, 2018 (travel days are Monday the 3rd & Saturday the 8th) in Orlando, FL.

We are staying at [http://swandolphin.com/ Swan & Dolphin].

''*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. This needs to pre-approved and pre-arranged.''

=='''Registration'''==
This is an invite-only event. All full time and Upwork employees are expected to attend this all company event. Contractors, Vendors and seasonal employees are included on a case by case evaluation based upon team needs.

Advance registration is required. Attendees will need to wear their event badge at all times, including to evening events. We will have security at our events who will be ensuring everyone in our space should be there.

=====New Hires=====
We have a process to identify new hires each Monday and will invite them to book travel. No action necessary from managers other than to let them know about the event. Please work closely with your recruiting manager as they are aware of all deadlines.

All new hires must have a start date of November 16 and able to register/book travel by November 1.

==== Volunteer contributor participation ====
The process for this is [[All Hands/Orlando2018/Contributor_nominations|outlined on this page]].

All nominations will be done by employees, with a coordinator from each of the Firefox, Emerging Technologies, Marketing, Open Innovation and Operations parts of the organization. There will be no open call for nominations from volunteer Mozillians.

Please note: The information on this wiki primarily applies to Full time and contractor staff. If you have questions about how specifics apply to you, please email groter@mozilla.com and bmark@mozilla.com.

=='''Week at a Glance'''==

====Monday====
*Monday is primarily your travel day. You'll be able to pick up your registration stuff between 12:00 pm and 9:00 pm, as well as attend the *Welcome Reception from 6:00 pm - 9:00 pm.

====Tuesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Evening out to enjoy Orlando (or any part of Disney World should you [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes purchase passes]).

====Wednesday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*All company evening event at [https://www.kennedyspacecenter.com/ Kennedy Space Center] (incl guests)

====Thursday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Evening out to enjoy Orlando (or any part of Disney World should you [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes purchase passes]).

====Friday====
*Centrally located breakfast (incl guests) & lunch (no guests)
*Closing event at [https://www.universalorlando.com/web/en/us/universal-orlando-resort/the-wizarding-world-of-harry-potter/hub/index.html The Wizarding World of Harry Potter] at Universal Studios from 7:00 pm - 12:00 am. We'll have transportation to/from the venue and hotel.

====Saturday====
*Centrally located breakfast (incl guests)
*Departure day only. No scheduled activities.

=='''Food, Drink & Events'''==
Breakfast, lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday and lunch is provided Tuesday - Friday. Menus will be posted here closer to the event.

Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.

====Evening Events====
We have evening events on the Monday, Wednesday and Friday nights.

====Tuesday & Thursday Night Dinners====
You'll be on your own for Tuesday & Thursday and will have a similar expense policy from San Francisco ($60/night - $120 total to include food, beverage, transportation, exchange fees, etc). We will not be providing [https://wiki.mozilla.org/All_Hands/Orlando2018#Disney_Park_Passes park passes] or Disney gift cards.

Here is how this will work:

For both of these evenings, once your meetings have concluded, you and your team, friends, new acquaintances, are free to explore and to find somewhere great to eat that suits you. Each of you can expense a total of $120 over the two days (or $60/night).

This amount includes:
*Meal cost, including tax & gratuity
*Any beverages
*Transportation to/from the restaurant
*Conversion fees (for credit cards) or cash withdrawal fees

Anything over the $120 for the two evenings will be your own expense. The fine print:
*If your team is hosting an evening event 1 of the nights and the payment is coordinated (meaning, you don’t have to open your wallet and pay), you can expense up to $60 for the other night.
*You will be asked (later) to submit an Mozlando only expense report. You can submit ONE report for Orlando only and must be submitted no later than December 31, 2018.
*If your manager approves expenses above the $60 per night, that expense will go directly to your travel budget in your cost center.

Volunteer Contributors will have a separate process that will be communicated directly.

=====Restaurants & Reservations=====
*All restaurants in Orlando recommend advance reservations.
The hotel has several onsite [https://www.swandolphin.com/feedback/dining.html restaurants].

*[https://disneyworld.disney.go.com/dining/ DisneyWorld] has a searchable database of all of their restaurants - by park (ticketed or not) + cuisine, dining type, price range and rating.

*[https://www.timeout.com/orlando/restaurants/best-restaurants-in-orlando 26 of the best restaurants in Orlando] because Orlando is about more than theme parks and chain eateries—as proven by these overall best local restaurants.

=====Disney Park Passes=====
We will not be providing Disney Park Passes for evenings. Purchase discounted passes [https://www.mydisneygroup.com/mozilla here] and for more information, see [https://wiki.mozilla.org/All_Hands/Orlando2018#Discounted_Disney_Park_Passes here].

=='''Safety & Security'''==
=====Alcohol at Events=====
To better support and sustain an environment (and workplace culture) where people feel safe and included, we plan make a set of changes regarding alcohol at our events. In all cases, our approach will align with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).
*All participants were/are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.
*We will '''limit bar-servings to beer and wine''' and ensure an equal number and quality (i.e. not just Coke) of non-alcoholic drink options are available and displayed.
*When teams undertake smaller, “off campus” adventures (team dinners or events), leaders will be asked (and reminded) to be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.
*Clearly outlined, communicated (to event teams, HR and managers) and understood '''escalation process''' for behavior that might be deemed counter to the spirit of our CPG.

=====Device Security=====
If you are traveling to the Mozlando All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Physical Security=====
Badges are required to access all meeting spaces and evening events.

=='''Hotel'''==
Hotels are reserved during registration. Mozilla will pay for your hotel room with a check in date of Monday, December 3 and a check-out of Saturday, December 8. A link to self-book any pre/post stays at your hotel will be available, should that be part of your plan. Please do not book your hotel through Egencia.

====Payment on Check-in====
Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US hotel standard and we aren't able to waive it (we tried).

We recommend providing a credit card. You can provide a debit card, but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating.

====Pre/post====
A link to self-book any pre/post stays at your hotel will be available to book pre (Nov 30, Dec 1-2) & post nights (Dec 8-10). If you'd like it in advance of the communication, email bmark@mozilla.com

=='''Travel'''==
The Mozlando 2018 Egencia portal will open in late August and booking instructions will be emailed. The deadline to book travel is September 14.

To access, log into Egencia using your LDAP, click Book → Meetings → Mozlando 2018. If you don’t see Mozlando 2018, email bmark@mozilla.com and I’ll add you. Please do not book outside the portal. Please fly into and out of Orlando International Airport (MCO).

Should you need to reach someone for special circumstances or changes that can't be done online:
*Call: +1 (877) 264-1622 or +1 (417) 521-0273; Monday - Friday 9 am - 6 pm Eastern (2 pm - 11 pm UTC). If you call outside these hours, you will get an after hours agent, who may not be as helpful.
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday 9 am - 6 pm Eastern (2 pm - 11 pm UTC).

'''Important Details:'''
Everyone should plan to arrive in Orlando on Monday, December 3rd and leave on Saturday, December 8th. Anyone who plans to arrive ahead of that or to stay longer, regardless of the reason, must follow the "arriving early/departing late guidelines." These guidelines also apply if you want to fly in or out of airports other than your home airport and Orlando (anything custom). A few notes:
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, your manager must confirm your participation before you will be able to book travel. You will receive a separate email shortly if you have already been approved.
*Volunteers will be handled separate from this process.
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.
*If you would like to invite someone who is a partner, facilitator or some other category that isn't an employee or volunteer, email bmark@mozilla.com.
*Change fees will be covered by Mozilla for business reasons only.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, December 3 and leave on Saturday, December 8. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, November 30 and Monday, December 18, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).
* If you live in a country where work travel is prohibited on Sunday, you may travel on Saturday, December 1 and Saturday, December 8, if you’d prefer (not required). You will get your Monday, December 3 and 10 off. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).
* If you plan to spend some extra personal time in Orlando or nearby (choosing to arrive before Monday, December 3 or depart after Saturday, December 8), you'll need to create an itinerary in Egencia for standard dates/locations within the Mozlando 2018 Portal and compare to the custom dates/locations you'd like. Please share the difference via email to bmark@mozilla.com or through the approval comment box when you submit the flight. '''You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of MCO w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.''' This scenario also applies for routing through different airports to/from Orlando than your home airport (ex. a layover in Chicago for a few days, or flying out of MIA instead of MCO). In all cases, flights in and out of Orlando should be booked via Egencia.
* If you are attending the Sunday/Monday CI event (by invite), you can arrive on Sunday, December 2.
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is '''no unilateral''' "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center). This policy does not apply to volunteer contributors, any jetlag recovery costs must be self funded.

====Booking Family Travel====
Whether your family will accompany you on your flight or join us later; and you have two options: direct with the airline (recommended) or through Egencia.

'''Direct (recommended):'''

First, figure out which flights you want to be on as an employee in Egencia. Hold them in Egencia. Find the flights you want for your family on the airline site and book them. Go back to Egencia and book your flights. Once you have both sets of confirmation numbers, call the airline and ask them to LINK your two reservations. This shows that you are traveling together and shouldn't be moved. When you call, you can also ask the airline agent to assign seats together. By booking your family direct on the airline, it gives them "priority" with the airline over people who book via a third party (expedia, booking.com, kayak, etc). These aren't guarantees, but they do help.

'''Via Egencia:'''

We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com

'''Notes:'''

* If your family is arriving on a different flights than you but would like to take advantage of the shuttles on Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.
* No matter how you book, give yourself a lot of time at MCO on departure. This airport can chaotic (almost everyone leaving is a family with young kids) so not being in a hurry helps stress-levels.
* We are unable to accommodate volunteer contributor families/guests.

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo & MoFo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.

=====''Air Travel Fine Print''=====
Change fees will be covered by Mozilla for business reasons only. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.

Mozilla will '''not''' reimburse for Business/First class upgrades or tickets. ''Mozilla Frequent Flyer perks do not apply for All Hands''.

Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

=='''Ground Transportation'''==
====Airport Shuttle====
All Mozillians and guests who have flights arriving anytime on Monday, December 3rd in Orlando International Airport (MCO) and out on Saturday, December 8th, will be transferred to/from the hotel. If you arrive into another airport; or on a different date - ground transportation is on your own. If your family is arriving on different flights than you but would like to take advantage of the shuttles on Monday & Saturday, email their itinerary to mozilla@shworldwide.com.

=====Arrivals to Orlando Int’l Airport (MCO)=====
Everyone will be greeted in Baggage Claim (regardless if you check a bag). At the bottom of the escalator in the baggage claim level, look for a greeter holding up a Mozilla/Mozlando sign. Please identify yourself to the greeter and they will direct you to the shuttles. Transfer time from the airport to the hotel is approximately 20 minutes.

''For Domestic Arrivals''

Upon arrival, proceed to the baggage claim area of your respective airline. There are two separate baggage claims – A or B. Please listen for the announcements from your airline flight attendants or while you are on the shuttle from the gates to the main terminal, for your baggage claim. Once you exit past Security, look to the left and right to see the large A or B to find your respective baggage claim.

''For International Arrivals''

Upon arrival, you will proceed thru Customs. Some International flights allow you to take your luggage directly from Customs to the main terminal and some require you to put it on the luggage carousel and re-collect it in the main baggage claim. Regardless if you collect your luggage at Customs or not, you have to take the shuttle to the main terminal. Once there, please proceed down the escalator to the Baggage Claim, Level 2.
(Do not go directly to Level 1.)

=====Departures from Dolphin Hotel to Orlando Int’l Airport (MCO)=====
Everyone departing on Saturday, December 8th, will receive shuttle transportation to MCO. You will be met by transportation staff in the hotel lobbies and assisted onto the shuttles. More details about departures will be sent via email.

Regardless of international or domeestic, plan to depart the hotel 3 hours prior to your flight time.

=====Bringing family?=====
If you are bringing family and are all arriving on Monday, December 3rd and departing Saturday, December 8th, you may all use our company-arranged transportation provided you request it ahead of time (for your guests). You will do this during registration.

=====Arriving early and/or leaving late (w/ or w/out family)?=====
If you arrive other than December 3rd or depart other than December 8th, with or without guests, you will have to cover and arrange your own ground transportation, to and from MCO, including rental cars and parking.

'''Recommended Airport Shuttle:'''
Mears Transportation http://www.mearstransportation.com/global/orlando/
Loading is on Level One at the airport, clearly marked, and the shuttle makes 1-3 stops at hotels in the same proximity.

Additional help is here:
*Transportation Information (airport and parks) http://swananddolphin.com/aboutus/transportation.html
*Transportation FAQ: http://swananddolphin.com/feedback/transportation.html
*Transportation booking (via Swan & Dolphin): https://swandolphinconcierge.com/

Exceptions are those attending the CI meeting on Monday. Transportation will be arranged for you.

=='''Accessibility'''==
====Evenings====
The Monday Night reception is at the Swan & Dolphin hotel, accessible by elevators and escalators. Both offsite evening events are accessible, specific details to be shared soon.

====Listen Systems====
We will have Listen Systems available for the Plenary on Tuesday. Visit the AV booth at the back of the room to pick one up.

=='''Immigration'''==
'''Any''' questions on immigration should be sent to immigration@mozilla.com.

If you are from a country that requires a B-1/B-2 business visitor visa to enter the US, please plan for it early as government processing times constantly change.

Please visit the following website to learn more about the visa application process and timing for your country: http://travel.state.gov/content/visas/english/visit/visitor.html#overview. Current estimated processing times at the US Embassies and Consulates abroad can be found at: https://travel.state.gov/content/visas/en/general/wait-times.html/

Some travelers may be eligible to travel to the United States without first applying for a B-1/B-2 visa, if they are eligible for the Visa Waiver Program (VWP or "ESTA"). You are eligible to apply for admission under the Visa Waiver Program (VWP) if you:

*Intend to enter the United States for 90 days or less for business, pleasure or transit
*Have a valid passport lawfully issued to you by a Visa Waiver Program country: http://www.esta.us/visa_waiver_countries.html
*Have authorization to travel via the Electronic System for Travel Authorization: https://esta.cbp.dhs.gov/
*Arrive via a Visa Waiver Program signatory carrier (all commercial airlines meet this requirement)
*Have a return or onward ticket
*Travel may not terminate in contiguous territory or adjacent islands unless the traveler is a resident of one of those areas

=====Employee Travel FAQ=====
This [https://mana.mozilla.org/wiki/display/PR/Travel+FAQ FAQ] addresses questions about how to handle security concerns and electronic devices at the border and how to engage with US Customs & Border Protection (CBP). While it specifically focuses on concerns related to travel to the United States, much of this guidance is applicable to travel elsewhere. Mana access required.

=====Pocket Letter=====
A pocket letter is recommended to keep on hand for those who are entering the United States. It should accompany you whether or not you are required to have a visa to enter. You may request a copy of that letter when you register. Please contact immigration@mozilla.com if you require a specific letter for your visa application or if you have any questions regarding your citizenship, visa capabilities or travel related questions.

=====ESTA Point of Contact=====
In the ESTA application you need to give a "U.S. Point of Contact Information".

Please list Casey McGill as your US Point of Contact.
Address: 331 East Evelyn Avenue, Mountain View, CA 94041 Phone: 408.505.3028

=='''Mozlando 2018 All Hands Expense Policy'''==
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Mozlando All Hands Expense Report). Each expense must be tagged with "Orlando 2018"

2. It must contain only those expenses relative to the All Hands Event in Orlando.

3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses

4. The deadline to submit the Orlando All Hands Expense Report is '''January 31, 2018'''.

5. Expenses related to team events, parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved.

'''The intention of our all hands are to centrally organize a structure that includes:'''
*Meals (two/day + snacks)
*Transportation
*Accommodations
*Some number of social events

Expenses submitted can not exceed the approved amounts. Any social events that are not part of our central plan will generally be self-organized and funded by participants.

=====Cell phone reimbursement policy=====
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense.

=====Internet reimbursement policy=====
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons.

If you have questions about any of this, please reach out to bmark@mozilla.com

=='''Families/Guests in Orlando'''==
Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made.

Please note that what are able to do for families varies by each location.

Please note: we are unable to accommodate volunteer contributor families/guests.

====Quick summary logistics====

=====Air Travel=====

Employees do need to book via Egencia regardless of how families are booked. See Air Travel above for specifics and recommendations.

=====Hotel=====

They are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates.

=====Breakfast=====

Family members who are registered for the event and registered with the hotel are invited to join us for breakfast each morning. Breakfast will be provided on Tuesday, December 3rd - Saturday, December 8th.

=====Lunch & Dinner=====

Family will be on their own for lunch daily and dinner on Tuesday & Thursday.

=====Monday, Wednesday & Friday Night Events=====

Family members who are registered for the event and registered with the hotel, are invited to join us for our three evening events.

=====Family Friendly Activities=====

The [https://www.swandolphin.com/activities/index.html hotel] offers several options and [https://www.swandolphin.com/kids/index.html child specific] options.

=====Evening Childcare Services=====

[https://www.swandolphin.com/kids/campdolphin.html Camp Dolphin] is available nightly from 5:00 pm - 12:00 am. Reservations are required for Camp Dolphin's evening program. The cost is $12 per hour, per child. A kids meal from Picabu can be included for an additional $10. Here is the [https://www.swandolphin.com/feedback/child.html FAQ].

===Discounted Disney Park Passes===
https://www.mydisneygroup.com/mozilla

This site will EXPIRE for Advance Purchase Sales on December 2, 2018.

These "Meeting and Convention" tickets offer advance purchase savings of 10% on our Full-Multi-Day (2 days or longer) Tickets and include one (1) complimentary +1 FUN visit to an additional Disney Experience at any one (1) of the following (additional details are listed on the website):
*Disney’s Typhoon Lagoon Water Park
*Disney’s Blizzard Beach Water Park
*Disney’s Winter Summerland or Disney’s Fantasia Gardens Miniature Golf Courses (before 4 p.m.)
*Greens Fees for one round of golf at Disney’s Oak Trail Golf Course, our 9-hole walking course

The site also contains our partial-day tickets, which are discounted off of our full 1-Day tickets. "Meeting and Convention" Tickets purchased here will be valid from November 27 - December 14, 2018.

Please note, the ticket prices on the ticket store reflect any applicable discounts and include tax. These tickets are not available for purchase to the general public and are not sold at our theme park ticket windows. Since these Meeting & Convention partial-day and multi-day tickets are not available for purchase at our Theme Park Ticket Windows, you are only able to purchase them here: https://www.mydisneygroup.com/mozilla

Discounts do not apply for Mickey's Very Merry Christmas Party at Magic Kingdom (each Sun, Tue, Thur, Fri in December).

=====Disney FastPasses=====
All of the Meeting & Convention tickets include the ability to pre-select up to three FastPasses per theme park visit day. Details on how to create a My Disney Experience Account and pre-select FastPasses can be found here: https://www.mydisneygroup.com/mozilla under PLAN YOUR VISIT tab.

=='''Extracurricular Activities'''==
Costs for these activities are self-funded and can not be expensed. Feel free to add activities and invite others.

*[https://wiki.mozilla.org/All_Hands/Orlando2018#Discounted_Disney_Park_Passes Disney Park Passes]
* [https://disneyworld.disney.go.com/en_CA/special-offers/multi-day-tickets/details/ Disney gives 20% off 4+ Day Passes for Canadian Residents (may be a better deal than the corporate portal)]
*[https://docs.google.com/spreadsheets/d/1Wi_BZxCtsRAXH0bEzpA880m8OhpnGk73-y1P0aqQyrg/edit#gid=225771109 Spreadsheet with lots of Disney info]

MozWeek/Orlando2018/Contributor nominee criteria

2018-09-03T12:39:25Z

Groter: Created page

Below are guidelines for which contributors should nominated for the 2018 Orlando All Hands.

== Must have for all contributors at All Hands: ==
# '''Impact:''' have made or are able to make a significant impact on Mozilla project or team goals
# '''Commitment:''' have demonstrated that they will make a sustained contribution to a project, team or Mozilla in 2019, after the All Hands

== Nomination Criteria ==
There should be a very high bar for all nominees

* Currently contributing to or collaborating on a strategically relevant project or initiative
* Consistently involved
* Making high impact, unique contributions that would be hard to achieve without their involvement

=== Not criteria ===
Attending an All Hands is not a reward -- purely wanting to recognize someone for their past contribution is not a nomination criteria.

MozWeek/Orlando2018/Contributor nominations

2018-09-03T12:37:16Z

Groter: Created page

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful contributors, collaborators, and volunteers join the event, integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Orlando All Hands.

== Goals ==
The goals of the nomination process are:

# Invite contributors, collaborators and volunteers who are important to the success of and have a high level of commitment to specific projects, teams or Mozilla overall
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Mozilla teams are thinking about contributors strategically
# A process that has legitimacy with contributors and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || Sept 4 || Sept 16
|-
| 2) Applications -- very lightweight application sent to '''all nominees''' to ensure nominees are available and want to attend || Sept 17 || Sept 26
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 26 || Sept 28
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Sept 28 || -
|-
| 5) Invitations go out || Sept 28 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Sept 28 || Oct 12
|-
| 7) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || Sept 28 || Dec 3
|}

''Important note''
* We are emphasizing greater gender balance for nominated contributors

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting contributor nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox/Product || Mike Hoye (mhoye)
|-
| Emerging Technologies || Nancy Hang (nhang)
|-
| IT/Policy/Strategy/WPR || Michael Van Kleeck (mvk)
|-
| Marketing || Michal Dziewonski (vesper)
|-
| People || Lizz Noonan (lmn)
|-
| Open Innovation || Konstantina Papadea (kpapadea)
|}

''Organization Designates will be accountable for:''
* Creating/curating a contributor nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited

== Number of Contributors ==
We have space for roughly 90 contributors.

== Criteria for contributor nominees ==
[[All_Hands/Orlando2018/Contributor_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a contributor or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

Attending Your First Mozilla Event

2018-06-01T16:05:00Z

Groter: /* After the event */ added checking email for feedback survey

Congratulations on your invite to attend a Mozilla event! This a guide to help you prepare and get the most from the event as well as some tips to help you make the most of it on your return home.

=Before the event=

* Establish your personal goals. Think about how you can make the most of this opportunity.
* Plan meetings with people and teams in advance. When you are there, the time will go very quickly and organising in advance is courteous to the people you want to meet.
* Make sure you plan in a little downtime. Attending a Mozilla event is very exciting and there are lots and to see and do, but give yourself the chance to rest and gather your thoughts.
* Watch video footage from previous events on [[Air_Mozilla|Air Mozilla]] and try to catch the most recent Monthly Internal Call before you go. It will give you the background of the event and will make sure you are up to date with recent project announcements.
* Do not worry if you do not have stickers on your laptop or a Mozilla t-shirt. Chances are this may change by the end of the event and chances are you are not the only person going to their first event.
* There is no dress code. You are being invited for how you think, what you have done and what you may be able to do – not for your wardrobe.
* Be respectful towards staff – this is their day job.
* Read the [https://www.mozilla.org/about/governance/policies/participation/ Community Participation Guidelines].
* Read the [https://www.mozilla.org/about/governance/policies/participation/ Community Participation Guidelines] again.
* Make sure you have (and contribute to) your team’s schedule.
* You will not be a tourist, but read a little about the host location for the event. Understanding local customs and laws, as well as foods and drink, will help remove any concerns as will looking at maps of the local area.
* Plan your travel, make sure you have all the documents you need. Make sure you have your passport, identification, flight itinerary, hotel confirmation and any additional ESTA or visa requirements.

=During the event=

* Attend meetings you are invited to, are mandatory for you or are related to your teams goals.
* Arrive at meetings on time. You do not want to miss anything, but it is also disruptive to others if you come into a room late.
* Try to attend something random. If you are non-technical, speak to the technical people. If you are happy looking at code speak to people that are not. You will learn so much and even if you do not agree with them, you will come away with new opinions and views.
* Do not keep silent all week or stay at the back of the room – participate! Don’t be the person who does not do or say anything all week.
* Say thank you.
* Nothing wrong with taking a little time out to be quiet or get some fresh air. Don’t let stress or a disagreement ruin your event, take a step back, chill out a little and go back in refreshed and with a clear mind.
* Drink plenty of water.
* During week-long events, watch out for Thursdays – at this point in an event, tiredness can creep up on you.
* Try to keep a balanced diet, do try to eat some chocolate or sugar to balance out the savoury food.
* Do not go round taking all the stickers – share and make new friends.
* Make sure you get some sleep.

=After the event=

* You may feel a bit down or exhausted, that is completely natural after working with great people and something you care about.
* Keep in touch with people you met at the event. Work with them and follow up on meetings.
* Work on the goals you set out beforehand or modify them to focus on what you are bringing back with you.
* Look at the event pictures and any video footage, it will bring back good memories.
* Pass on what what you have learned (subject to any material that is covered by your NDA) to your functional or regional community.
* Check your email for a post-event survey, and provide honest feedback

WeeklyUpdates/2018-04-16

2018-04-16T17:53:16Z

Groter: /* Welcome! */ added intro

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org/channels/project-meeting/ 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]] ==

* Big thanks to all the Tech Speakers who've been out and about: including Kristi, Daniele in Albania and Italy, and Viswaprasath, who delivered an add-ons workshop in India; Abhiram, who recorded some Rust training last week for lynda.com in LA, and Andrzej, Vigneshwer, Florian G., Srushtika, and Sumanth, who spoke in Hungary, in the UK (Bristol & London), as well as Vietnam. Props to Hui Jing Chen, who'll speak at Smashing Conf in SF on Wed, and Kristi and Shagufta, who also have talks later this week.

== Upcoming Events ==

=== This Week ===

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

=== Tuesday, {{#time:d F|{{SUBPAGENAME}} +1 day}} ===
* [[WebExtensions/Triage|WebExtensions APIs triage]]
** 17:30 UTC / 10:30am PDT | ACE Vidyo room

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* [[Add-ons/Contribute/Triage|Add-ons Good First Bugs triage]]
** 15:30 UTC / 8:30am PDT | ACE Vidyo Room

=== 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 ===

== 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
|-
| Caitlin Neiman
| Add-ons Community Manager
| Apply to join the Featured Extensions Advisory Board
| MTV
| No
| https://mzl.la/2qsfe4O
| https://mzl.la/2qsfe4O
|-
| Andrew Krug
| Security Engineer, Identity and Access Management
| Weekly IT MinIT
| Remote from Ashland, Oregon
| No
| https://drive.google.com/file/d/1xT79VLwJ3QF-dhqtTAT7AYrQnJDML2a8/view?usp=sharing
| https://wiki.mozilla.org/IT/WeeklyMinIT
|-
| Bradley Cohen
| Team Lead, Mozilla Consumer marketing
| IRL Podcast update and Webby nomination
| Remote from Portland, Oregon
| No
| https://vote.webbyawards.com/PublicVoting#/2018/podcasts-digital-audio/features/best-branded-podcast-or-segment
| https://vote.webbyawards.com/PublicVoting#/2018/podcasts-digital-audio/features/best-branded-podcast-or-segment
|-
|}

= 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.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
| Their Name
| Your Name
| Intro location
| Their Location
| Their Role
|-
| Olga Rolf
| Mark Edwards
| San Francisco
| San Francisco
| Sr. Project Manager - IT
|-
| Sarah Chu
| Mark Edwards
| San Francisco
| San Francisco
| Project Manager - IT
|-
| Eugene Ivanov
| George Roter
| Berlin
| Remote - Boston
| Technical Crowdsourcing Lead, Open Innovation
|-

|}

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

MozWeek/SanFrancisco2018/Contributor nominations

2018-04-02T19:19:57Z

Groter:

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful contributors, collaborators, and volunteers join the event, integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the San Francisco All Hands.

== Goals ==
The goals of the nomination process are:

# Invite contributors, collaborators and volunteers who are important to the success of and have a high level of commitment to specific projects, teams or Mozilla overall
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Mozilla teams are thinking about contributors strategically
# A process that has legitimacy with contributors and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || Apr 3 || Apr 10
|-
| 2) Applications -- very lightweight application sent to '''all nominees''' to ensure nominees are available and want to attend || Apr 12 || Apr 20
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Apr 20 || Apr 24
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Apr 25 || -
|-
| 5) Invitations go out || Apr 26 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Apr 26 || May 4
|-
| 7) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || Apr 26 || Jun 11
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the past All Hands had 30% non-male genders among contributor participants)

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting contributor nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox/Product || Mike Hoye (mhoye)
|-
| Emerging Technologies || Azita Rashed (arashed)
|-
| Marketing || Michal Dziewonski (vesper)
|-
| People || Larissa Shapiro (lshapiro)
|-
| Open Innovation || Konstantina Papadea (kpapadea)
|}

''Organization Designates will be accountable for:''
* Creating/curating a contributor nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited

== Number of Contributors ==
We have space for roughly 70 contributors.

== Criteria for contributor nominees ==
[[All_Hands/SanFrancisco2018/Contributor_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a contributor or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

MozWeek/SanFrancisco2018

2018-04-02T18:59:21Z

Groter: Updated section on Contributors

'''What is it?''' -- Multiple team meetings, 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!

'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor or intern, please inquire to your coordinator. '''''

=='''Dates, Location and Weather'''==
Monday, June 11 - Friday, June 15, 2018 (travel days are Monday the 11th & Saturday the 16th) in San Francisco, CA.

We are staying at [http://www.marriott.com/hotels/travel/sfodt-san-francisco-marriott-marquis/ San Francisco Marriott Marquis].

''*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. This needs to be pre-approved and pre-arranged.''

Weather:
* National Weather Service: [http://forecast.weather.gov/MapClick.php?smap=1&lat=37.785&lon=-122.410&unit=1&mp=1 forecast in ⁰C], [http://forecast.weather.gov/MapClick.php?smap=1&lat=37.785&lon=-122.410&mp=1 forecast in ⁰F]
* Temperatures ''in downtown San Francisco'' in late June are likely to have nighttime lows around 10-13 ⁰C / 50-56 ⁰F and daytime highs around 16-24 ⁰C / 61-75 ⁰F. But the weather is very occasionally warmer with highs around 27⁰C / 81⁰F.
* Weather in San Francisco in the summer is variable; it can become substantially cooler and foggier in the late afternoon; be prepared for temperatures to fall to 13⁰C / 56⁰F and the winds to pick up in the afternoon. Be prepared by carrying a warmer layer with you.
* Weather in other parts of the Bay Area can be much warmer than in San Francisco, even if you're only traveling 15km away. Look at the weather forecasts for where you're going. It's entirely possible for it to be 19⁰C / 66⁰F in San Francisco and simultaneously be 32⁰C / 90⁰F in Orinda. But if you're right on the ocean, the air temperature is likely to match the water temperature, which is probably around 12⁰C / 54⁰F.

=='''Registration'''==
This is an invitation-only event.

Advance registration is required. Attendees, guests and local guests will need to wear their event badge at all times, including to evening events.

=====New Hires=====
We have a process to identify new hires each Monday and will invite them to book travel. No action necessary from managers other than to let them know about the event. Please work closely with your recruiting manager as they are aware of all deadlines.

Monday, May 7 is the deadline for hiring. Friday, May 11 i s the deadline that all new hires who must travel to the all hands but be registered and have travel booked. Friday, May 18 is the deadline for Bay Area/local new hires who do not need hotel or to travel need to be registered. All new hires must start on or before May 29.

==== Contributors participation ====
The process for this is [[All Hands/SanFrancisco2018/Contributor_nominations|outlined on this page]].

All nominations will be done by employees, with a coordinator from each of the Firefox/Product, Emerging Technologies, Marketing, Open Innovation and People parts of the organization. There will be no open call for nominations from contributors or volunteer Mozillians.

Please note: The information on this wiki primarily applies to fulltime and contractor staff. If you have questions about how specifics apply to you, please email groter@mozilla.com and bmark@mozilla.com.

=='''Week at a Glance'''==
=====Monday=====
Monday is primarily your travel day. You'll be able to pick up your registration stuff between 12:00 pm and 9:00 pm, as well as attend the Welcome Reception at the City View at Meteron from 6:00 pm - 9:00 pm.

=====Tuesday=====
We'll start Tuesday with a Plenary session.

=====Friday=====
Our closing party with be at the Exploratorium from 7:00 pm- 11:00 pm. We'll provide transportation to/from the hotel & venue + if the weather is nice, you could walk (about 1.7 miles).

=====Saturday=====
Departure day only. No scheduled activities.

===San Francisco All Hands Event Calendar===
Link coming soon. Events will be live by early May.

=====Create an account=====
We don’t recommend using the same email & password as anything like bank accounts, etc. We care about your security!

If you already have a Sched account from past All Hands, it still works, just log in with that.

=====Add items to your calendar=====
Just hit the circle on any agenda item to add it to your calendar (you do need to have an account & be logged in to do this)

You can also share a link to meetings to invite others. Go into the meeting and copy the short link. You can email that out to anyone and they can quickly add it to their calendar.

=====Subscribe to GCal Calendar Link=====
Click on the mobile phone on the right hand side of the screen. All the calendar options are available here.
You have the option to choose ALL meetings or YOUR meetings. Unless you have 400 items on your calendar, just select your calendar. It will add anything on your calendar to your GCal (also an option for Outlook and iCal). It syncs once per day.

The "only syncs once per day" only applies to Google Calendar. With almost all other clients (like Apple Calendar, Outlook, or the calendar app on your phone) you can set the refresh interval, and Sched's instructions recommend 1 hour.

Warning: This is a link that utilizes your username for the .ics file.

=====From Mobile=====
Visit from any mobile device - bookmark or add to your homescreen for quick access. There is a bonus icon you get by doing this. It caches the last time you opened the page offline and refreshes anytime you are connected.

=====Cool things=====
'''Filters'''

We have better (much needed) filtering functionality. You can filter by:
Departments (ex: Firefox)
AND
Functional Teams (ex: Dev Tools or EngOps)

*Search by Room, Speaker/Leader

'''Further Filtering'''
*Audience - who should be there (ex: Team only or Invite)
*Homerooms (you can quickly see what is happening in homerooms, by team) - why do you care? If you have a cross team meeting in their room, its a quick way to search
*Views - Lots of view options. It defaults to the simple view, but there are quite a few options.

=='''Food & Drink'''==
Breakfast, lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday and lunch is provided Tuesday - Friday.

Allergies/preferences: We will ensure that all food/environmental allergies are taken into consideration and will always have gluten-free and vegan options. If you have severe allergies that we need to know about; you can indicate in registration.

===Monday Night===
We will provide dinner at the Welcome Reception from 6:00 pm - 9:00 pm at City View by Meteron at the Welcome Reception. Since most of Monday is a travel day, you'll be on your own for meals except dinner.

===Tuesday, Wednesday & Thursday Nights===
Tuesday, Wednesday and Thursday evenings will be of your own to structure as you wish. Given how much you all seemed to like a more flexible dining experience, these three evenings will be of your own to structure as you wish.

Here is how this will work:

For each of these three evenings, once your meetings have concluded, you and your team, friends, new acquaintances, are free to explore San Francisco and to find somewhere great to eat that suits you. Each of you can expense a total of $180 over the three days (or $60/night).

This amount includes:
* Meal cost, including tax & gratuity
* Any beverages
* Transportation to/from the restaurant
* Conversion fees (for credit cards) or cash withdrawal fees

Anything over the $180 for the three evenings will be your own expense. The fine print:
* If your team is hosting an evening event 1 of the 3 nights and the payment is coordinated (meaning, you don’t have to open your wallet and pay), you can expense up to $120 for the other 2 nights ($60 for each of the 2 nights you did have to open your wallet and pay).
* You will be asked (later) to submit a San Francisco only expense report. You can submit ONE report for San Francisco only and must be submitted no later than August 31, 2017.
* If your manager approves expenses above the $60 per night, that expense will go directly to your travel budget in your cost center.

Volunteer Contributors & Interns will have a separate process that will be communicated directly.

===Friday Night===
We will provide dinner at the Closing Party from 7:00 pm - 11:00 pm at The Exploratorium.

====What you need====
Your SF All Hands name badge and Identification (you may be carded for alcohol).

=='''Photos'''==
==== Red Lanyards ====
If you see someone with a red lanyard, please don't take photos of them. They have opted out of being in photography. We'll have these available at the registration desk.

=='''Safety & Security'''==
=====Meeting Security=====
You'll need to have your badge on at all times in the hotel, as will your partners, vendors and family members anytime they are in the spaces.

=====Device Security=====
If you are traveling to the San Francisco All Hands with a device that has Mozilla data (laptop, personal cell phone/tablet with @mozilla gmail, etc) on it and your device has been retained for further inspection by border agents, or if your device has been inspected outside your immediate presence - and you believe your credentials have been compromised - you must notify the Enterprise Information Security team as soon as possible at infosec@mozilla.com or by calling Mozilla End User Services at +1 650-963-8811. (This number will be staffed 24x7)

We will work with you to reset your credentials and help you get your device back to a known good state either by getting you a new one (if it’s been taken), or by resetting it back to a verifiable Mozilla-approved installation.

=====Safety Tips=====
SF Travel team also has some [https://sftravel.ent.box.com/s/p2ve63e1ctn74e0ai2x48mmgr9fdlvul tips about safety] in the city, including safety numbers and local hospitals.

=='''Hotel'''==
Hotel rooms are reserved for all employees & volunteers to stay all week, including employees based in San Francisco (just as if we were somewhere you don't live). We are hopeful Mozilla-locals will stay with the rest of us in the hotel - it's really part of what makes these events great. You will have the option to opt out of hotel in registration if you are local to the Bay Area and wish to commute.

A few things to note:
*Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US-resort standard and we aren't able to waive it (we tried). Please reach out to mozilla@shworldwide.com if this creates a hardship for you.
*If you have any changes or questions about your reservation, email mozilla@shworldwide.com. The hotel cannot make changes to All Hands reservations (other than to add your guests - see #4) so we’d like very much if you didn’t try (it complicates things).
*If you have guests joining you for all or part of the week, you will be responsible for adding them to your reservation (and covering any additional fees). To do this, you will need your confirmation number(s) and to know how old your kids are. Details on how to add them will come a few weeks after registration closes.

====Payment on Check-in====
Everyone will be required to present a form of payment on check-in for incidentals at $50 per day. This is a US hotel standard and we aren't able to waive it (we tried).

We recommend providing a credit card. You can provide a debit card, but they do put a hold of funds on your card and has been problematic for some international travelers in the past. If you are not able to provide a credit or debit card, email mozilla@shworldwide.com and we'll work with the hotel on accommodating.

====Pre/post====
Links will be provided when you are invited to register in mid-April to book hotel 3 days pre and 3 days post at our negotiated rate. The pre/post reservations will require the use of an LDAP email* so we can link them to your All Hands reservation. Rooms booked by any method except this link will not be linked to your main reservation.

Rates start $179+tax/fees & for double occupancy.

====Parking====
Self-Parking is available at several lots nearby. The Marriott Marquis offers valet only - please do not park valet. Mozilla will not reimburse for parking, plan to commute the way you normally would in the city. If you have questions about parking, email bmark@mozilla.com.

=='''Travel'''==
Booking travel is now open. Please book itineraries by Friday, April 13, 2018.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, June 11 and leave on Saturday, June 16. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, June 8 and Monday, June 18, if you’d prefer (not required). For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).
* If you plan to spend some extra personal time in San Francisco (choosing to arrive before Monday, June 11 or depart after Saturday, June 16), you'll need to create an itinerary in Egencia for standard dates/locations within the San Francisco June 2018 Portal and compare to the custom dates you'd like. Please share the difference via email to bmark@mozilla.com before submitting the flight. You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of SFO w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.
* If you are attending the Monday Core Influencer's event (by invite).
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is no unilateral "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own, and expense the manager approved amount (which is coded to your cost center).

====Booking Family Travel====
Once travel has opened to staff, you may book family, whether they will accompany you on your flight or join us later; and you have two options: Direct or through Egencia.

If you choose to book family through Egencia, please first book your own flight and then call Egencia with your airline confirmation number (staff do have to go through Egencia). Otherwise, you can book family direct (either through the airline or through another third party) and call the ticketing airline(s) with both confirmation numbers and ask them to link your reservations, so they know you are traveling together. They should also be able to assign seats together. You will avoid the limited hours Egencia offers and avoid paying their ticketing fee.

If you prefer to book your family through Egencia, you can pay (including the Egencia booking fees) and coordinate with your own travel (recommend to book and then call/email Egencia with your itinerary number to match for family). Note that booking through Egencia does not put you on the same reservation, nor guarantee the reservations will be linked (you would still need to call the airline to link them).
* '''Call:''' +1 (877) 264-1622 or +1 (417) 521-0273; Monday - Friday 9 am - 6 pm EST. If you call outside these hours, you will get an after hours agent, who may not be as helpful.

====Travel Insurance====
Mozilla provides emergency medical accident and illness cover for all global MoCo employees/interns and their dependents. You can view more information on [https://mana.mozilla.org/wiki/display/PR/Travel+Insurance+-+Business Mana]. This coverage begins at the time the you leave home to start your business trip. It also has a provision for a 14 day extension for leisure travel outside of the business travel. If you have additional questions, please email benefits@mozilla.com.

Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members.

=====''Air Travel Fine Print''=====
Change fees will be covered by Mozilla for '''business reasons only'''. If you need a change and have manager approval, email bmark@mozilla.com prior to requesting the change with Egencia. Once you have approval, call Egencia to make the change at +1 (702) 939-2530 or +1-877-264-1622 (note this will not be possible without prior approval so be sure to get that by way of an email from your manager to Brianna Mark). If you are changing for personal reasons, the change in airfare, change fee and Egencia fee is your responsibility.

Mozilla will not reimburse for Business/First class upgrades or tickets.

Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.

=====Airport Shuttle=====
All Mozillians and guests who have flights arriving anytime on Monday, June 11th in San Francisco International Airport (SFO) and out on Saturday, June 16th, will be transferred to the hotel. If you arrive into another airport (OAK or SJC) or on a different date, ground transportation is on your own.

'''Arrivals to San Francisco International Airport (SFO)'''

The airport has four terminals: Terminal 1, 2 & 3, and the International Terminal. For domestic flights In Terminals 1, 2 & 3 and the International Terminal (there are domestic flights), everyone will be greeted at the bottom of the escalator in the baggage claim for your terminal (even if you have no checked bags). Please identify yourself to the greeter and they will direct you to the shuttles for your terminal.

For International Flights into the International terminal, you will collect your luggage and pass through customs. Once through customs, you will walk directly out to the main lobby, where you’ll find a greeter and they will direct your to your shuttle.

Transfer time from the airport to the hotel is approximately 40-60 minutes.

'''Departures from San Francisco International Airport (SFO)'''

Everyone departing on Saturday, June 16th, will receive transportation to SFO. You will be met by transportation staff in the Marriott hotel lobby and assisted onto the shuttles.

If you have questions about arrivals or departures, please email mozilla@shworldwide.com.

====Alternate Transportation Options====
For those arriving or departing on dates other than June 11 and 16.
*[http://www.bart.gov/stations/powl BART] goes from SFO to the Powell Street Station for $8.95. Tickets can be purchased at the airport or in advance.
*[http://www.samtrans.com/schedulesandmaps/timetables/292.html SamTrans bus Route 292] goes from SFO to Mission St. & 5th St. only for [http://www.samtrans.com/fares/farechart.html $2.25 (inbound) or $4 (outbound)].
*[https://www.supershuttle.com/locations/sanfranciscosfo/ Super Shuttle]. Shared shuttle service. Book in advance.

Other options can be found on the [https://www.flysfo.com/to-from/ground-transportation SFO website].

====Mountain View Office Shuttle====
We will provide a shuttle from the Mountain View office on Monday, June 11th (1:00 pm and 3:00 pm). They will depart from the main entrance. We will return to Mountain View on Saturday, June 16 (10:00 am and 12:30 pm). They will depart the Marriott.

You can get dropped off or park at the office until 10:00 pm Sunday, June17. There will be normal security patrols however, you should remove valuables from view and secure your vehicle.

====From the Bay Area but not taking the Mountain View Office Shuttle?====
Our expectation is that you commute to the hotel just as you would to the office in the Bay Area. If you normally take the BART or MUNI, do that. If you normally drive and pay for parking - that's up to you but hotel parking is not a reimbursable expense for the All Hands.

=='''Accessibility'''==

'''Marriott Marquis'''

The guestroom tower has accessible elevators, and accessible rooms (on request). The main entrance and pathway to hotel registration are accessible. All meeting space can be access via elevators.

====Evenings====
The Monday Night reception is at City View, which is located on the 4th floor of the METREON and is accessible from the ground floor via 2 passenger elevators and escalators. There is ADA access from all building entrances as well.. The Friday Night Party is at [https://www.exploratorium.edu/visit/accessibility Exploratorium], which has access to all levels by elevator.

=='''Immigration'''==
'''Any''' questions on immigration should be sent to immigration@mozilla.com.

If you are from a country that requires a B-1/B-2 business visitor visa to enter the US, please plan for it early as government processing times constantly change.

Please visit the following website to learn more about the visa application process and timing for your country: http://travel.state.gov/content/visas/english/visit/visitor.html#overview. Current estimated processing times at the US Embassies and Consulates abroad can be found at: https://travel.state.gov/content/visas/en/general/wait-times.html/

Some travelers may be eligible to travel to the United States without first applying for a B-1/B-2 visa, if they are eligible for the Visa Waiver Program (VWP or "ESTA"). You are eligible to apply for admission under the Visa Waiver Program (VWP) if you:

*Intend to enter the United States for 90 days or less for business, pleasure or transit
*Have a valid passport lawfully issued to you by a Visa Waiver Program country: http://www.esta.us/visa_waiver_countries.html
*Have authorization to travel via the Electronic System for Travel Authorization: https://esta.cbp.dhs.gov/
*Arrive via a Visa Waiver Program signatory carrier (all commercial airlines meet this requirement)
*Have a return or onward ticket
*Travel may not terminate in contiguous territory or adjacent islands unless the traveler is a resident of one of those areas

=====Employee Travel FAQ=====
This [https://mana.mozilla.org/wiki/display/PR/Travel+FAQ FAQ] addresses questions about how to handle security concerns and electronic devices at the border and how to engage with US Customs & Border Protection (CBP). While it specifically focuses on concerns related to travel to the United States, much of this guidance is applicable to travel elsewhere. Mana access required.

=====Pocket Letter=====
A pocket letter is recommended to keep on hand for those who are entering the United States. It should accompany you whether or not you are required to have a visa to enter. You may request a copy of that letter when you register online. Please contact immigration@mozilla.com if you require a specific letter for your visa application or if you have any questions regarding your citizenship, visa capabilities or travel related questions.

=====ESTA Point of Contact=====
In the ESTA application you need to give a "U.S. Point of Contact Information".

Please list Casey McGill as your US Point of Contact.
Address: 331 East Evelyn Avenue, Mountain View, CA 94041 Phone: 408.505.3028

=='''San Francisco All Hands Expense Policy'''==
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. San Francisco All Hands Expense Report)

2. It must contain only those expenses relative to the All Hands Event (5-10 days of pre-post activity only)

3. If your submitted expense report for All Hands is submitted outside these guidelines, it will be rejected and you will be asked to re-submit with only All Hands Expenses

4. The deadline to submit the San Francisco All Hands Expense Report is '''July 31, 2018'''.

5. Expenses related to team events, parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved.

'''The intention of our all hands are to centrally organize a structure that includes:'''
*Meals (two/day + snacks)
*Transportation^
*Accommodations
*Some number of social events

Due to the nature of the San Francisco, employees will be expensing specific meals. The amount that can be expensed will be communicated and expenses submitted can not exceed the approved amounts. Any social events that are not part of our central plan will generally be self-organized and funded by participants.

^Transportation for those based in the Bay Area is limited to "commuting" as you normally would. Expenses for commuting are not reimbursable. We have provided shuttles from the MV office for those based in the south bay. For those who that doesn't make sense to use, commute using your normal means. We will not reimburse for hotel parking.

=====Cell phone reimbursement policy=====
Cell phone reimbursement must be approved by your manager prior to submitting the expense. Teams will decide for their staff what is appropriate to expense.

=====Internet reimbursement policy=====
Internet will be provided in all guestrooms and meeting space in all hotels. If you opt to upgrade/add service, those costs are not reimbursable, unless previously approved by your manager and are for business reasons.

If you have questions about any of this, please reach out to bmark@mozilla.com

=='''Families/Guests in San Francisco'''==

Of course our focus, for the majority of the week, will be on Mozilla. Everyone is expected to be present and engaged each day, during work hours (as your schedule dictates). Please do what you can to make sure your loved ones understand the kind of commitment you’ve made. Family should not join you during your work sessions and meals. Please note that what are able to do for families varies by each location.

====Quick summary logistics====

'''Air Travel''': Family travel can be booked/coordinated through Egencia by calling direct; or on your own. Employees do need to book via Egencia regardless of how families are booked.

'''Hotel''': They are welcome to stay with you, however, any additional room expenses will be yours to cover. All room rates are based upon single occupancy and costs to add guests vary by hotel. Breakfast is not included in any of the guest room rates. Once hotel reservations are made, we will provide a link or contact add guests.

Meals: Breakfast will be provided to All Hands registered guests, for lunch families are on their own. They are invited to join our Monday & Friday evening festivities, we just ask that you let us know they'll be there in registration.

=='''Extracurricular Activities'''==
Costs for these activities are self-funded and can not be expensed. Feel free to add activities and invite others.

MozWeek/SanFrancisco2018/Contributor nominations

2018-04-02T18:59:07Z

Groter:

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful contributors, collaborators, and volunteers join the event, integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the San Francisco All Hands.

== Goals ==
The goals of the nomination process are:

# Invite contributors, collaborators and volunteers who are important to the success of and have a high level of commitment to specific projects, teams or Mozilla overall
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Mozilla teams are thinking about contributors strategically
# A process that has legitimacy with contributors and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || Apr 3 || Apr 11
|-
| 2) Applications -- very lightweight application sent to '''all nominees''' to ensure nominees are available and want to attend || Apr 12 || Apr 20
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Apr 20 || Apr 24
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Apr 25 || -
|-
| 5) Invitations go out || Apr 26 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Apr 26 || May 4
|-
| 7) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || Apr 26 || Jun 11
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the past All Hands had 30% non-male genders among contributor participants)

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting contributor nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox/Product || Mike Hoye (mhoye)
|-
| Emerging Technologies || Azita Rashed (arashed)
|-
| Marketing || Michal Dziewonski (vesper)
|-
| People || Larissa Shapiro (lshapiro)
|-
| Open Innovation || Konstantina Papadea (kpapadea)
|}

''Organization Designates will be accountable for:''
* Creating/curating a contributor nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited

== Number of Contributors ==
We have space for roughly 70 contributors.

== Criteria for contributor nominees ==
[[All_Hands/SanFrancisco2018/Contributor_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a contributor or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

MozWeek/SanFrancisco2018/Contributor nominations

2018-04-02T18:55:47Z

Groter: Created page with "== Introduction == Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful contributors, collabora..."

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful contributors, collaborators, and volunteers join the event, integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the San Francisco All Hands.

== Goals ==
The goals of the nomination process are:

# Invite contributors, collaborators and volunteers who are important to the success of and have a high level of commitment to specific projects, teams or Mozilla overall
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Mozilla teams are thinking about contributors strategically
# A process that has legitimacy with contributors and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || Apr 3 || Apr 11
|-
| 2) Applications -- very lightweight application sent to '''all nominees''' to ensure nominees are available and want to attend || Apr 12 || Apr 20
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Apr 20 || Apr 24
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Apr 25 || -
|-
| 5) Invitations go out || Apr 26 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Apr 26 || May 4
|-
| 7) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || Apr 26 || Jun 11
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the past All Hands had 30% non-male genders among contributor participants)

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting contributor nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox || Mike Hoye (mhoye)
|-
| Emerging Technologies || Azita Rashed (arashed)
|-
| Marketing || Michal Dziewonski (vesper)
|-
| People/Operations || Larissa Shapiro (lshapiro)
|-
| Open Innovation || Konstantina Papadea (kpapadea)
|}

''Organization Designates will be accountable for:''
* Creating/curating a contributor nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited

== Number of Contributors ==
We have space for roughly 70 contributors.

== Criteria for contributor nominees ==
[[All_Hands/SanFrancisco2018/Contributor_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a contributor or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

MozWeek/SanFrancisco2018/Contributor nominee criteria

2018-04-02T18:55:03Z

Groter: Created page with "Below are guidelines for which contributors should nominated for the 2018 San Francisco All Hands. == Must have for all contributors at All Hands: == # '''Impact:''' have mad..."

Below are guidelines for which contributors should nominated for the 2018 San Francisco All Hands.

== Must have for all contributors at All Hands: ==
# '''Impact:''' have made or are able to make a significant impact on Mozilla project or team goals
# '''Commitment:''' have demonstrated that they will make a sustained contribution to a project, team or Mozilla in 2018, after the All Hands

== Nomination Criteria ==
There should be a very high bar for all nominees

* Currently contributing to or collaborating on a strategically relevant project or initiative
* Consistently involved (meetings, regular contributions, generally available)
* Making high impact, unique contributions that would be hard to achieve without their involvement

=== Not criteria ===
Attending an All Hands is not a reward -- purely wanting to recognize someone for their past contribution is not a nomination criteria.

Innovation/Projects/Mission-Driven Mozillians Strategy

2017-11-16T00:15:22Z

Groter: changed decision making

'''What is the Non-Coding Communities strategies project?'''

This project, driven by the Community Development Team, aims at catalysing a Mozilla-wide decision and strategy for where and how we invest in our non-coding communities and contributors.

=== Background ===

This project is based on the [https://wiki.mozilla.org/Innovation/Projects/Open_Innovation_Strategy Open Innovation strategy research project], and informed by the D&I community research, as well as additional interviews & research with key staff members and volunteers.

[Additional background https://discourse.mozilla.org]

=== Who’s Involved ===

'''The project is being driven by''' - Lucy Harris & Ruben Martin (with support from George Roter)

'''The decision-maker is''' - George Roter

'''Agreement is to be sought from''' - Katharina Borchert, Patrick Finch, Chris Beard, Mitchell Baker and the Reps Module Owner

'''Input & Consultation'''- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, Haiyya, D&I Staff, Mozilla Foundation Staff.

=== Approach ===

The approach is to generate two documents

# A proposal that clearly outlines the impact of non-code communities and proposes an a cohesive approach to investment to Mozilla Leadership
# A strategy and roadmap for implementing structures and processes to optimize the health and impact of non-coding communities.

The proposal is generated by the input group and shared with decision makers for feedback.

The strategy is generated through a series of discussions with members of Mozilla communities.

Both proposal & strategy will be based around the following 11 topic areas:

* '''Regional/local/geographic identities''': Approach, formation, visibility
* '''Diversity and Inclusion''': How do we ensure D&I across everything we do?
* '''Metrics''': How do we measure activity across all areas?
* '''Accountability''': What are the expectations around accountability in different volunteer and staff roles?
* '''Volunteer Leadership''': How do we approach leadership roles?
* '''Recognition''': What’s our strategy for recognizing and motivating contributors?
* '''Systems - tools & Comms''': What’s the strategy around the tools that enable contributions? How do we communicate with volunteers?
* '''Opportunity Matching''': How do we surface, present and decide on opportunities to contribute?
* '''Competitive Advantage''': What are the key factors where contributions provide a unique value? How do we leverage them?
* '''Staff Support''': What’s our strategy around community-facing staff and workflows?
* '''Onboarding''': How do we welcome and approach volunteers into their first contribution?

=== Timeline ===

* Q3, 2017 - Work with input group to create initial proposal
* Q4, 2017 - Leadership input to proposal & framing for initial implementation conversations (topic 1: volunteer leadership)
* Q1, 2018 - Additional implementation conversations, roadmap generation and early infrastructure and framework creation.

MozWeek/Austin/Volunteer nominations

2017-09-18T16:19:43Z

Groter: /* Organization Designates */ added marketing designate

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer contributors join the event, to be integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Austin All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer contributors who can make a high impact contribution (and who have future potential) and have high commitment to specific projects, teams or Mozilla
# Have volunteer contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer contributors strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 15 || Sept 26
|-
| 2) Applications -- very lightweight application sent to '''all nominees''' to ensure nominees are available and want to attend || Sept 27 || Oct 4
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Oct 4 || Oct 6
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 9 || -
|-
| 5) Invitations go out || Oct 10 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 10 || Oct 20
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 10 || Dec 11
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the San Francisco All Hands had 30% non-male genders among volunteer contributor participants)

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting volunteer nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox || Mike Hoye
|-
| Emerging Technologies || Azita Rashed
|-
| Marketing || Madalina Ana
|-
| People/Operations || Larissa Shapiro
|-
| Open Innovation || Lucy Harris
|}

''Organization Designates will be accountable for:''
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare volunteer contributors who have been invited

== Number of Volunteer Contributors ==
We have space for roughly 100 volunteer contributors.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/Austin/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

WeeklyUpdates/2017-09-18

2017-09-18T12:35:58Z

Groter: added contact info

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org/channels/project-meeting/ 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]] ==

== Upcoming Events ==

=== This Week ===

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

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

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* '''[https://indiewebcamp.com/events/2017-09-20-homebrew-website-club Homebrew Website Club Meetup]''' (nearly every Wednesday somewhere) Be a part of the open web with your own website.
** '''Virtual EU (UTC+2)''', '''Baltimore (<abbr title="Maryland">MD</abbr>)''', '''Frederick (<abbr title="Maryland">MD</abbr>)''' {{new!}}, '''San Francisco''' (@[[MozSF]] commons hosted by Tantek)
** 17:30-18:30 Quiet Writing Hour, finish that blog post, wiki edit, etc.!
** 18:30-19:30 IndieWeb meetup, demos, & hack night <blockquote>Create or update your personal web site! Share what you've gotten working.Join a community with like-minded interests. Bring friends that want a personal site!</blockquote> Any questions? See '''[https://indiewebcamp.com/events/2017-09-20-homebrew-website-club the event wiki page for details]''' and check out the Slack or IRC: https://indieweb.org/discuss

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
*SUMO Day Firefox Focus in Social and in the [https://support.mozilla.org Support Forums]:
**Sign up today: [https://public.etherpad-mozilla.org/p/sumo-day Etherpad with all the details] and see you there!
**Curious about how support works at mozilla? Contact guigs@mozilla.com
**Who the heck is SUMO?[https://support.mozilla.org/en-US/get-involved Read more here]

* '''[https://indiewebcamp.com/events/2017-09-21-homebrew-website-club Homebrew Website Club Meetup]''' ''Thursday'' exception for:
** '''Berlin (Germany)'''
** 18:30 - 19:00 (GMT +2) Warm-up
** 19:00 - 21:00 (GMT +2) IndieWeb Show-and-tell
** Venue and more details on '''[https://indieweb.org/events/2017-09-21-homebrew-website-club the event wiki page]'''

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

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

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

=== Next Week ===
==== September 30th and October 1st ====
* '''[https://2017.indieweb.org/nyc IndieWebCamp New York City!]''' - the fifth IndieWebCamp in NYC for all web creatives, makers, designers, developers and anyone else who loves growing the open web!
** 10:00-17:00 both Saturday and Sunday
** Talks, Brainstorming Sessions, Design and Hacking Sessions
** Free to sign-up: https://2017.indieweb.org/nyc
** Any questions? Ask on Slack or IRC: https://indieweb.org/discuss

== 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
|-
| Larissa Shapiro
| Head of Diversity and Inclusion
| D&I Update! (featuring Voice and Influence and Outreachy programs)
| Mountain View Commons
| Just chatting
|
| Voice and Influence: https://womensleadership.stanford.edu/voice Outreachy: https://wiki.mozilla.org/Outreachy
|-
| George Roter
| Open Innovation Team
| Volunteer nomination process for upcoming All Hands in Austin
| my home
| nope
|
| [[All Hands/Austin/Volunteer nominations|https://wiki.mozilla.org/All_Hands/Austin/Volunteer_nominations]] or find me @geroter (IRC, Slack, Telegram, Twitter, etc)
|}

= 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.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
|}

= Fireside Chat =
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.

===This Week===

'''Name''', "Title"

===Topics===

You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.

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

WeeklyUpdates/2017-09-18

2017-09-18T12:33:46Z

Groter: added an agenda item

{{WeeklyUpdateNav}}
* Every Monday @ 11:00am Pacific Time (19:00 UTC)
* https://air.mozilla.org/channels/project-meeting/ 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]] ==

== Upcoming Events ==

=== This Week ===

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

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

=== Wednesday, {{#time:d F|{{SUBPAGENAME}} +2 days}} ===
* '''[https://indiewebcamp.com/events/2017-09-20-homebrew-website-club Homebrew Website Club Meetup]''' (nearly every Wednesday somewhere) Be a part of the open web with your own website.
** '''Virtual EU (UTC+2)''', '''Baltimore (<abbr title="Maryland">MD</abbr>)''', '''Frederick (<abbr title="Maryland">MD</abbr>)''' {{new!}}, '''San Francisco''' (@[[MozSF]] commons hosted by Tantek)
** 17:30-18:30 Quiet Writing Hour, finish that blog post, wiki edit, etc.!
** 18:30-19:30 IndieWeb meetup, demos, & hack night <blockquote>Create or update your personal web site! Share what you've gotten working.Join a community with like-minded interests. Bring friends that want a personal site!</blockquote> Any questions? See '''[https://indiewebcamp.com/events/2017-09-20-homebrew-website-club the event wiki page for details]''' and check out the Slack or IRC: https://indieweb.org/discuss

=== Thursday, {{#time:d F|{{SUBPAGENAME}} +3 days}} ===
*SUMO Day Firefox Focus in Social and in the [https://support.mozilla.org Support Forums]:
**Sign up today: [https://public.etherpad-mozilla.org/p/sumo-day Etherpad with all the details] and see you there!
**Curious about how support works at mozilla? Contact guigs@mozilla.com
**Who the heck is SUMO?[https://support.mozilla.org/en-US/get-involved Read more here]

* '''[https://indiewebcamp.com/events/2017-09-21-homebrew-website-club Homebrew Website Club Meetup]''' ''Thursday'' exception for:
** '''Berlin (Germany)'''
** 18:30 - 19:00 (GMT +2) Warm-up
** 19:00 - 21:00 (GMT +2) IndieWeb Show-and-tell
** Venue and more details on '''[https://indieweb.org/events/2017-09-21-homebrew-website-club the event wiki page]'''

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

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

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

=== Next Week ===
==== September 30th and October 1st ====
* '''[https://2017.indieweb.org/nyc IndieWebCamp New York City!]''' - the fifth IndieWebCamp in NYC for all web creatives, makers, designers, developers and anyone else who loves growing the open web!
** 10:00-17:00 both Saturday and Sunday
** Talks, Brainstorming Sessions, Design and Hacking Sessions
** Free to sign-up: https://2017.indieweb.org/nyc
** Any questions? Ask on Slack or IRC: https://indieweb.org/discuss

== 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
|-
| Larissa Shapiro
| Head of Diversity and Inclusion
| D&I Update! (featuring Voice and Influence and Outreachy programs)
| Mountain View Commons
| Just chatting
|
| Voice and Influence: https://womensleadership.stanford.edu/voice Outreachy: https://wiki.mozilla.org/Outreachy
|-
| George Roter
| Open Innovation Team
| Volunteer nomination process for upcoming All Hands in Austin
| my home
| nope
|
| [[All Hands/Austin/Volunteer nominations|https://wiki.mozilla.org/All_Hands/Austin/Volunteer_nominations]]
|}

= 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.

{| class="fullwidth-table wikitable"
|-
! ''Who is being introduced?''
! ''Who are you? (the introducer)''
! ''Where are you doing the introduction?''
! ''Where are they from?''
! ''How will they be part of Mozilla?''
|-

|-
|}

= Fireside Chat =
A chance to hear from leadership at Mozilla, and have a short Q&A about a specific topic.

===This Week===

'''Name''', "Title"

===Topics===

You can submit questions in advance on the Moderator page (link), or ask them live on Air Mozilla using a Mozilla Space mic or in #airmozilla on IRC.

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

MozWeek/Austin

2017-09-18T12:26:45Z

Groter: /* Contributors participation */ Updated the volunteer nomination link

MozWeek/Austin/Volunteer nominations

2017-09-18T12:22:57Z

Groter: small change in dates

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer contributors join the event, to be integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Austin All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer contributors who can make a high impact contribution (and who have future potential) and have high commitment to specific projects, teams or Mozilla
# Have volunteer contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer contributors strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 15 || Sept 26
|-
| 2) Applications -- very lightweight application sent to '''all nominees''' to ensure nominees are available and want to attend || Sept 27 || Oct 4
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Oct 4 || Oct 6
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 9 || -
|-
| 5) Invitations go out || Oct 10 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 10 || Oct 20
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 10 || Dec 11
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the San Francisco All Hands had 30% non-male genders among volunteer contributor participants)

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting volunteer nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox || Mike Hoye
|-
| Emerging Technologies || Azita Rashed
|-
| Marketing || TBD
|-
| People/Operations || Larissa Shapiro
|-
| Open Innovation || Lucy Harris
|}

''Organization Designates will be accountable for:''
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare volunteer contributors who have been invited

== Number of Volunteer Contributors ==
We have space for roughly 100 volunteer contributors.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/Austin/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

MozWeek/Austin/Volunteer nominee criteria

2017-09-14T22:23:40Z

Groter: Created

Below are guidelines for which contributors should nominated for the 2017 Austin All Hands.

== Must have for all volunteer contributors at All Hands: ==
# '''Impact:''' have made or are able to make a significant impact on Mozilla project or team goals
# '''Commitment:''' have demonstrated that they will make a sustained contribution to a project, team or Mozilla in 2018, after the All Hands

== Nomination Criteria ==
There should be a very high bar for all nominees

* Currently contributing to a priority project or initiative
* Consistently involved (meetings, regular contributions, generally available)
* Making high impact, unique contributions that would be hard to achieve without their involvement

=== Not criteria ===
Attending an All Hands is not a reward -- purely wanting to recognize someone for their past contribution is not a nomination criteria.

MozWeek/Austin/Volunteer nominations

2017-09-14T22:20:47Z

Groter: Created page

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer contributors join the event, to be integrated with employees. The [[Innovation|Open Innovation Team]] is accountable for the process of getting the "right" people to the All Hands, and has established a best practice for this.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Austin All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer contributors who can make a high impact contribution (and who have future potential) and have high commitment to specific projects, teams or Mozilla
# Have volunteer contributors and employees working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer contributors strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 15 || Sept 25
|-
| 2) Applications -- very lightweight application sent to '''all nominees''' to ensure nominees are available and want to attend || Sept 26 || Oct 4
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Oct 4 || Oct 6
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 9 || -
|-
| 5) Invitations go out || Oct 10 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 10 || Oct 20
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 10 || Dec 11
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the San Francisco All Hands had 30% non-male genders among volunteer contributor participants)

== Open Nominations ==
There will be '''no "open nominations" from non-employees''' this time.

== Organization Designates ==
The following individuals are collecting volunteer nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox || Mike Hoye
|-
| Emerging Technologies || Azita Rashed
|-
| Marketing || TBD
|-
| People/Operations || Larissa Shapiro
|-
| Open Innovation || Lucy Harris
|}

''Organization Designates will be accountable for:''
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions (if needed)
* Ensuring a good process across their organization to be in contact with/prepare volunteer contributors who have been invited

== Number of Volunteer Contributors ==
We have space for roughly 100 volunteer contributors.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/Austin/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].

Contribute

2017-05-03T15:34:14Z

Groter: small formatting change

Thanks for your interest in contributing to Mozilla!

Here we’ve compiled a directory of ways you can get involved and contribute to Mozilla and some featured projects to get you started:

==Contribution areas==
Not exactly what you’re looking for?

Here is a list of projects in Mozilla organized by contribution area. Click the contribution topics to reveal the teams and projects below:

{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Coding
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| General - Firefox || Firefox ||rowspan="2"| #introduction ||rowspan="2"| jdm ||rowspan="2"| [https://mozillians.org/en-US/u/jdm/ Josh Matthews] ||rowspan="2"| [https://developer.mozilla.org/en-US/docs/Introduction Introduction] ||rowspan="2"| N/A ||rowspan="2"| N/A
|-
| General - Firefox OS || Firefox OS
|-
| Webdev || Websites ||#webdev || groovecoder || [https://mozillians.org/en-US/u/groovecoder/ Luke Crouch] || [http://whatcanidoformozilla.org/ what can I do for Mozilla] || [[Webdev/GetInvolved]] || N/A
|-
| AddOns || Firefox Add-ons ||amo, addons, extdev, addon-reviewers || rowspan="2"|amyt || rowspan="2"|[https://mozillians.org/en-US/u/amyt/ Amy Tsay] || [https://addons.mozilla.org/en-US/firefox/ addons.mozilla.org] || [[Add-ons/Contribute]] || N/A
|-
| Marketplace || HTML5 Apps ||Marketplace || N/A || [[Marketplace/Contributing]] || N/A
|-
| Web Compatability || Diagnosing Web Compatability Issues ||webcompat || bear || [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [http://webcompat.com/contributors webcompat.com/contributors] || N/A || N/A
|-
| Cloud Services || Online Services ||services-dev || telliott || [https://mozillians.org/en-US/u/telliott/ Toby Elliot] || [https://github.com/mozilla-services github.com/mozilla-services] || [[CloudServices/Sync]] || N/A
|-
| Science Lab || Collaborate ||sciencelab || abbycabs || [https://mozillians.org/en-US/u/Abby/ Abby Cabunoc Mayes] || [https://www.mozillascience.org/collaborate/ mozillascience.org/collaborate] || [[ScienceLab]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Testing
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| General || Testing for Firefox and Firefox OS ||qa || marcia || [https://mozillians.org/en-US/u/marcia/ Marcia Knous] || [https://quality.mozilla.org/ quality.mozilla.org] || N/A || [https://oneanddone.mozilla.org/ one and done tool]
|-
| AddOns ||Testing for Firefox Add-Ons || addons, amo ||rowspan="2"| amyt ||rowspan="2"| [https://mozillians.org/en-US/u/amyt/ Amy Tsay] ||[https://addons.mozilla.org/en-US/firefox/ addons.mozilla.org] || [[Marketplace/Contributing/Addons]] || N/A
|-
| Marketplace ||Testing for HTML 5 Apps || marketplace || N/A || [[Marketplace/Contributing/Apps]] || N/A
|-
| Web Compatability ||Testing Web Compatability Issues || webcompat || bear || [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [http://webcompat.com/contributors webcompat.com/contributors] || N/A || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Activism
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Advocacy ||Mozilla Advocacy || foundation || davesteer || [https://mozillians.org/en-US/u/davesteeer/ Dave Steer] [https://mozillians.org/en-US/u/stacy/ Stacy Martin] || N/A || [[Privacy/PriMo]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Localization
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Product Localization ||Product Localization ||rowspan="3"| l10n ||rowspan="3"|gueroJeff ||rowspan="3"|[https://mozillians.org/en-US/u/gueroJeff/ Jeff Beatty] ||rowspan="3"| [http://l10n.mozilla.org l10n.mozilla.org]|| [[L10n:Contribute#Mozilla_products]] [[L10n:Localization_Process]]
|-
| Web Localization ||Web Localization || [[L10n:Contribute#Mozilla_web_sites]] [[L10n:Web_parts]]
|-
| Localization Tools Dev ||Localization Tools Dev || [[Contribute#Mozilla_l10n_development_projects]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Helping
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| User Support ||SUMO || sumo || madalina vesper || [https://mozillians.org/en-US/u/mana/ Madalina Ana] [https://mozillians.org/u/mdziewonski/ Michal Dziewonski]|| [https://goo.gl/forms/32a6gaAY1Qr9SDHQ2 https://goo.gl/forms/32a6gaAY1Qr9SDHQ2] || [[Support]] || [http://blog.mozilla.org/sumo/ blog.mozilla.org/sumo]
|-
| Web Compatibility ||Help Make Websites Firefox Compatible || webcompat || bear|| [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [http://webcompat.com/contributors webcompat.com/contributors] || [[Compatibility]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Writing
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Social Media ||Comms Squared Example || N/A || N/A || [https://mozillians.org/en-US/u/lnapoli/ Laura Napoli] || N/A || [[CommSquared]] || N/A
|-
| Journalism, Open News ||Journalism || N/A || N/A || N/A || [http://opennews.org/ opennews.org] || [[OpenNews]] || N/A
|-
| Tech Documentation for Users ||Technical Documentation for Users || sumo || vesper || [https://mozillians.org/u/mdziewonski/ Michal Dziewonski] || [https://support.mozilla.org/get-involved get involved] || [[Support]] || [http://blog.mozilla.org/sumo/ SuMo blog]
|-
| Tech Documentation for Developers ||Technical Documentation for Developers || mdn || jswisher || [https://mozillians.org/en-US/u/jms/ Janet Swisher] || [https://developer.mozilla.org/en-US/docs/MDN/Getting_started Getting_started]|| [[MDN]] || N/A
|-
| AddOns ||Technical Documentation for Add-Ons ||rowspan="2"| marketplace || rowspan="2"|amyt || rowspan="2"|[https://mozillians.org/en-US/u/amyt/ Amy Tsay] || rowspan="2"|N/A || [[Marketplace/Contributing/Addons]] || N/A
|-
| Marketplace ||Technical Documentation for HTML5 Apps || [[Marketplace/Contributing/Apps]]|| N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Learning
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
|Webmaker ||Mozilla Learning || webmaker || OpenMatt || [https://mozillians.org/en-US/u/OpenMatt/ Matt Thompson] || [https://webmaker.org/en-US/getinvolved webmaker.org/getinvolved] || [[Webmaker]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Teaching
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Mozilla Learning Networks ||Teach the Web || teachtheweb || amirad || [https://mozillians.org/en-US/u/amiradhalla/ Amira Dhalla] || [http://teach.mozilla.org teach.mozilla.org] || [[Learning/Networks]] || N/A
|-
| Fellowships ||Open News Fellowship || N/A || kissane || [https://mozillians.org/en-US/u/erink/ Erin Kissane]|| [http://opennews.org/what/community/eventsupport/ opennews.org/eventsupport] || [[OpenNews]] || N/A
|-
| Hive ||City-based learning networks || foundation || N/A || [https://mozillians.org/en-US/u/CLAW/ Chris Lawrence] || [https://hivelearningnetworks.org/start-a-hive/ hivelearningnetworks.org/start-a-hive] || [[Webmaker/Hive]] || N/A
|-
| Science Lab ||Mozilla Study Groups || sciencelab || billmills || Bill Mills || [http://mozillascience.github.io/studyGroupHandbook/ mozillascience.github.io] || [[ScienceLab]]|| N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;margin:0"
!colspan="9"|Fellowship
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Mozilla Developer Network ||MDN Fellowship || mdn || diane || [https://mozillians.org/en-US/u/diane1/ Diane Tate] || [http://developer.mozilla.org/fellowship developer.mozilla.org/fellowship] || [[MDN/DeveloperFellowship]] || [https://blog.mozilla.org/community/2015/05/14/mdnfellowsannouncement/ mdn fellowship announcement blog]
|-
| Mozilla Science Lab ||Mozilla Science Fellow || sciencelab || kaythaney || [https://mozillians.org/en-US/u/kaythaney/ Kaitlin Thaney] || [https://www.mozillascience.org/training training]|| [[ScienceLab ]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Metrics
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Mozilla Foundation ||Dashboard Zero || foundation || adamlofting || [https://mozillians.org/en-US/u/adamlofting/ Adam Lofting] || N/A || [[Foundation/Metrics/Contribute ]] || [https://github.com/adamlofting/dashboard-zero github.com/dashboard-zero]
|}

To get started, choose a project based on the area or the project you’d like to contribute to and click on the links for details on how to get involved. If you need help contact the project’s steward on IRC or click on the steward’s name to find more ways to get in touch with them.

There are lots of ways you can get involved with each of these teams so if you can’t find what you’re looking for be sure to visit their webpages for more information.

Still can’t find what you’re looking for? Leave a note on [https://discourse.mozilla-community.org/c/participation the Participation category in Discourse].

''Looking for content from the old page? You can find it in the archive [[Contributearchive|HERE]].''

Contribute

2017-05-03T15:32:47Z

Groter: Small set of updates

Thanks for your interest in contributing to Mozilla!

Here we’ve compiled a directory of ways you can get involved and contribute to Mozilla and some featured projects to get you started:

==Contribution areas==
Not exactly what you’re looking for?

Here is a list of projects in Mozilla organized by contribution area. Click the contribution topics to reveal the teams and projects below:

{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Coding
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| General - Firefox || Firefox ||rowspan="2"| #introduction ||rowspan="2"| jdm ||rowspan="2"| [https://mozillians.org/en-US/u/jdm/ Josh Matthews] ||rowspan="2"| [https://developer.mozilla.org/en-US/docs/Introduction Introduction] ||rowspan="2"| N/A ||rowspan="2"| N/A
|-
| General - Firefox OS || Firefox OS
|-
| Webdev || Websites ||#webdev || groovecoder || [https://mozillians.org/en-US/u/groovecoder/ Luke Crouch] || [http://whatcanidoformozilla.org/ what can I do for Mozilla] || [[Webdev/GetInvolved]] || N/A
|-
| AddOns || Firefox Add-ons ||amo, addons, extdev, addon-reviewers || rowspan="2"|amyt || rowspan="2"|[https://mozillians.org/en-US/u/amyt/ Amy Tsay] || [https://addons.mozilla.org/en-US/firefox/ addons.mozilla.org] || [[Add-ons/Contribute]] || N/A
|-
| Marketplace || HTML5 Apps ||Marketplace || N/A || [[Marketplace/Contributing]] || N/A
|-
| Web Compatability || Diagnosing Web Compatability Issues ||webcompat || bear || [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [http://webcompat.com/contributors webcompat.com/contributors] || N/A || N/A
|-
| Cloud Services || Online Services ||services-dev || telliott || [https://mozillians.org/en-US/u/telliott/ Toby Elliot] || [https://github.com/mozilla-services github.com/mozilla-services] || [[CloudServices/Sync]] || N/A
|-
| Science Lab || Collaborate ||sciencelab || abbycabs || [https://mozillians.org/en-US/u/Abby/ Abby Cabunoc Mayes] || [https://www.mozillascience.org/collaborate/ mozillascience.org/collaborate] || [[ScienceLab]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Testing
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| General || Testing for Firefox and Firefox OS ||qa || marcia || [https://mozillians.org/en-US/u/marcia/ Marcia Knous] || [https://quality.mozilla.org/ quality.mozilla.org] || N/A || [https://oneanddone.mozilla.org/ one and done tool]
|-
| AddOns ||Testing for Firefox Add-Ons || addons, amo ||rowspan="2"| amyt ||rowspan="2"| [https://mozillians.org/en-US/u/amyt/ Amy Tsay] ||[https://addons.mozilla.org/en-US/firefox/ addons.mozilla.org] || [[Marketplace/Contributing/Addons]] || N/A
|-
| Marketplace ||Testing for HTML 5 Apps || marketplace || N/A || [[Marketplace/Contributing/Apps]] || N/A
|-
| Web Compatability ||Testing Web Compatability Issues || webcompat || bear || [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [http://webcompat.com/contributors webcompat.com/contributors] || N/A || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Activism
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Advocacy ||Mozilla Advocacy || foundation || davesteer || [https://mozillians.org/en-US/u/davesteeer/ Dave Steer] [https://mozillians.org/en-US/u/stacy/ Stacy Martin] || N/A || [[Privacy/PriMo]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Localization
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Product Localization ||Product Localization ||rowspan="3"| l10n ||rowspan="3"|gueroJeff ||rowspan="3"|[https://mozillians.org/en-US/u/gueroJeff/ Jeff Beatty] ||rowspan="3"| [http://l10n.mozilla.org l10n.mozilla.org]|| [[L10n:Contribute#Mozilla_products]] [[L10n:Localization_Process]]
|-
| Web Localization ||Web Localization || [[L10n:Contribute#Mozilla_web_sites]] [[L10n:Web_parts]]
|-
| Localization Tools Dev ||Localization Tools Dev || [[Contribute#Mozilla_l10n_development_projects]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Helping
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| User Support ||SUMO || sumo || madalina vesper || [https://mozillians.org/en-US/u/mana/ Madalina Ana] [https://mozillians.org/u/mdziewonski/ Michal Dziewonski]|| [https://goo.gl/forms/32a6gaAY1Qr9SDHQ2 https://goo.gl/forms/32a6gaAY1Qr9SDHQ2] || [[Support]] || [http://blog.mozilla.org/sumo/ blog.mozilla.org/sumo]
|-
| Web Compatibility ||Help Make Websites Firefox Compatible || webcompat || bear|| [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [http://webcompat.com/contributors webcompat.com/contributors] || [[Compatibility]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Writing
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Social Media ||Comms Squared Example || N/A || N/A || [https://mozillians.org/en-US/u/lnapoli/ Laura Napoli] || N/A || [[CommSquared]] || N/A
|-
| Journalism, Open News ||Journalism || N/A || N/A || N/A || [http://opennews.org/ opennews.org] || [[OpenNews]] || N/A
|-
| Tech Documentation for Users ||Technical Documentation for Users || sumo || vesper || [https://mozillians.org/u/mdziewonski/ Michal Dziewonski] || [https://support.mozilla.org/get-involved get involved] || [[Support]] || [http://blog.mozilla.org/sumo/ SuMo blog]
|-
| Tech Documentation for Developers ||Technical Documentation for Developers || mdn || jswisher || [https://mozillians.org/en-US/u/jms/ Janet Swisher] || [https://developer.mozilla.org/en-US/docs/MDN/Getting_started Getting_started]|| [[MDN]] || N/A
|-
| AddOns ||Technical Documentation for Add-Ons ||rowspan="2"| marketplace || rowspan="2"|amyt || rowspan="2"|[https://mozillians.org/en-US/u/amyt/ Amy Tsay] || rowspan="2"|N/A || [[Marketplace/Contributing/Addons]] || N/A
|-
| Marketplace ||Technical Documentation for HTML5 Apps || [[Marketplace/Contributing/Apps]]|| N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Learning
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
|Webmaker ||Mozilla Learning || webmaker || OpenMatt || [https://mozillians.org/en-US/u/OpenMatt/ Matt Thompson] || [https://webmaker.org/en-US/getinvolved webmaker.org/getinvolved] || [[Webmaker]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Teaching
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Mozilla Learning Networks ||Teach the Web || teachtheweb || amirad || [https://mozillians.org/en-US/u/amiradhalla/ Amira Dhalla] || [http://teach.mozilla.org teach.mozilla.org] || [[Learning/Networks]] || N/A
|-
| Fellowships ||Open News Fellowship || N/A || kissane || [https://mozillians.org/en-US/u/erink/ Erin Kissane]|| [http://opennews.org/what/community/eventsupport/ opennews.org/eventsupport] || [[OpenNews]] || N/A
|-
| Hive ||City-based learning networks || foundation || N/A || [https://mozillians.org/en-US/u/CLAW/ Chris Lawrence] || [https://hivelearningnetworks.org/start-a-hive/ hivelearningnetworks.org/start-a-hive] || [[Webmaker/Hive]] || N/A
|-
| Science Lab ||Mozilla Study Groups || sciencelab || billmills || Bill Mills || [http://mozillascience.github.io/studyGroupHandbook/ mozillascience.github.io] || [[ScienceLab]]|| N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;margin:0"
!colspan="9"|Fellowship
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Mozilla Developer Network ||MDN Fellowship || mdn || diane || [https://mozillians.org/en-US/u/diane1/ Diane Tate] || [http://developer.mozilla.org/fellowship developer.mozilla.org/fellowship] || [[MDN/DeveloperFellowship]] || [https://blog.mozilla.org/community/2015/05/14/mdnfellowsannouncement/ mdn fellowship announcement blog]
|-
| Mozilla Science Lab ||Mozilla Science Fellow || sciencelab || kaythaney || [https://mozillians.org/en-US/u/kaythaney/ Kaitlin Thaney] || [https://www.mozillascience.org/training training]|| [[ScienceLab ]] || N/A
|-
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"
!colspan="9"|Metrics
|-
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address
|-
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources
|-
| Mozilla Foundation ||Dashboard Zero || foundation || adamlofting || [https://mozillians.org/en-US/u/adamlofting/ Adam Lofting] || N/A || [[Foundation/Metrics/Contribute ]] || [https://github.com/adamlofting/dashboard-zero github.com/dashboard-zero]
|}

To get started, choose a project based on the area or the project you’d like to contribute to and click on the links for details on how to get involved. If you need help contact the project’s steward on IRC or click on the steward’s name to find more ways to get in touch with them.

There are lots of ways you can get involved with each of these teams so if you can’t find what you’re looking for be sure to visit their webpages for more information.

Still can’t find what you’re looking for? Leave a note on [https://discourse.mozilla-community.org/c/participation the Participation category in Discourse].

'''Looking for content from the old page? You can find it in the archive [[Contributearchive|HERE]]'''.

Strategy/2017 Strategy Projects overview

2017-04-27T16:22:27Z

Groter: /* 6 special projects to help shape where Mozilla is headed */ added membership model

== Overview ==
During the first half of this year, alongside [https://blog.mozilla.org/blog/2017/04/19/first-big-bytes-project-quantum/ growing Firefox] and [https://www.mozilla.org/en-US/technology/ new technology and product areas], we are undertaking a number of interrelated special projects that will help shape where Mozilla is headed and connect the energies of our diverse, global community.

== The whole picture ==
[[File:Strategy projects and layers.png|600px]]

== Context ==
To situate these projects, we need to understand what is in place today:

# The [https://www.mozilla.org/en-US/about/manifesto/ Mozilla Manifesto] -- principles that articulate our vision for the Internet.

# [https://www.mozilla.org/en-US/mission/ Mozilla’s Mission] -- our purpose and primary objectives.

Both of these are enduring, not time-bound and driven by our core beliefs. They are also at quite a high level of abstraction -- many different directions, strategies and projects can fit underneath them.

We also have [https://discourse.mozilla-community.org/t/mozilla-2017-topline-strategy-narrative-and-objectives-key-results-okrs-as-of-jan-2017/13357 overall and product strategies and goals] that are generally updated each year with objectives each quarter.

== 6 special projects to help shape where Mozilla is headed ==
In the first half of 2017 we are adding to these with a few projects that will increase clarity about ''who we are, how we work together, what we are focusing on, and key strategies we will employ''.

1) [[Strategy/True_North_Project|True North]] - a tangible, actionable bridge between our collective long-term, enduring core beliefs as laid out in the Mission, Vision, and Manifesto and our immediate product strategy

2) [https://discourse.mozilla-community.org/t/mozillas-worldview/14320 Mozilla’s Worldview] - an articulation of aspects of Mozilla that identifies who we already are and how we work together, but that aren’t clearly articulated in the Mozilla Manifesto

3) [[Innovation/Projects/Open_Innovation_Strategy|Mozilla Corporation (MoCo) Open Innovation Strategy]] - recommendations for how MoCo can better invest in and execute on being “open” in our products and technologies

4) [https://discourse.mozilla-community.org/t/community-participation-guidelines-draft-community-feedback/13816 Community Participation Guidelines v2] - a vision for how diverse people will participate in Mozilla’s communities, along with behavioral expectations, processes to raise concerns, and consequences for unacceptable behavior

5) [[Diversity_and_Inclusion_Strategy_for_Participation|Diversity and Inclusion for Community Participation Strategy]] - a set of priorities for the next 2-3 years on how we will improve practices in communities to create a truly open and inclusive Mozilla where a diversity of contributors can thrive and grow to their full potential

5) [[Strategy/Membership_exploration_2017|Membership Model exploration]] - evaluating if a membership model, premium services or philanthropic models are viable for creating deeper engagement with users around our core issues, delivering long-term value to our users and delivering financial sustainability to Mozilla

== How you can be involved ==
Broad participation by diverse Mozillians in all of these projects is important. This includes having a good mix of volunteer contributors and collaborators. Here’s how you can be involved in any or all of these projects:

'''A) Contribute to research:''' You will soon receive an email from Ruben Martin (some of you know him as Nukeador) inviting you to participate in research about our communities and contributors. Please complete the survey contained in that email as it is a big part of the Open Innovation project.

'''B) Engage directly:''' Follow the links above to each project to understand how to get involved. Each is set up a bit differently.

'''C) Join the conversation:''' Subscribe to [https://discourse.mozilla-community.org/c/mozillians “Watching” the Mozillians category on Discourse] (see the drop-down icon in the top right corner directly under the menu bar). We will be hosting a number of conversations there in the coming weeks, and it is the place where updates will be posted.

=== Communities Advisory Group ===
Consider applying to be part of the Communities Advisory Group of ~20 volunteer Mozillians, a group we are assembling specifically to engage with this set of projects (it will be dissolved afterward).

'''Requirements for applicants'''
* willing and able to spend about 10 hours a month for the next few months to be more regularly and deeply consulted on these projects (reading materials along with synchronous and asynchronous interactions)
* some experience and skill in contributing to strategic topics and conversations
* passion for Mozilla and being part of shaping its overall direction

'''Criteria for selection'''
We are looking to compose a group with a diversity of perspectives. In particular, we will seek a balance between gender identities, geographical locations and languages, areas of involvement in Mozilla, professional background and longevity of involvement.

In addition, we will evaluate applications based on:
* experience in organizational or product strategy
* experience relevant to the strategy projects currently being undertaken
* demonstration of a high level of thinking about the issues facing Mozilla
* commitment to Mozilla

'''Applications are due by May 5th.'''

[https://goo.gl/forms/FEFPTIpnj6TDxPHA2 Fill out this form to apply.]

Strategy/Membership exploration 2017

2017-04-26T19:00:50Z

Groter: Created

== Membership Overview & Thesis ==

The internet and the browser market has seen a breadth of dynamic changes in the market over the past 10 years. However, as a mission-based organization, our key principles have not changed. As part of these changes, it is critical that we constantly assess how we add value, how we engage with our users and how our business model will adapt to future changes. The purpose of this program was to to address this and evaluating if a membership model, premium services or philanthropic models are an alternative to create a deeper engagement with users around our core issues, deliver long-term value to our users and deliver financial sustainability to Mozilla.

== Process - How are we going about this? ==

There are three key goals for a membership offering:

# Deeper engagement / Social impact
# User value
# Revenue diversification

Our overall approach and process is to be highly user driven. Digging deep on user needs / demands. Understanding how they make decisions around the context of our values and technology. To this end, it was important to break down the project into discernible "chunks".

'''Phase 0: Understand the market'''

How have other advocacy organizations structured themselves? How did they grow? What value did they give to users? How did they most effectively use those users?

'''Phase 1: Understand the user segment we are targeting'''

Mozilla is strategically targeting the Conscious Chooser segment for growth. How do these users view membership? How do they make decisions based on value/values? How do they view our values? How important are our values in their decision making?

'''Phase 2: Concept validation with users'''

With the insight learned from Phase 1, can create some concepts and validate them with users.

== Ways to engage ==

If you are interested in this program, get in touch with Mark Crandon (mcrandon@mozilla.com). Watch the [https://discourse.mozilla-community.org/c/mozillians Mozillians category on Discourse] for updates on this work.

Strategy/2017 Strategy Projects overview

2017-04-26T18:53:07Z

Groter: /* Communities Advisory Group */ added form

== Overview ==
During the first half of this year, alongside [https://blog.mozilla.org/blog/2017/04/19/first-big-bytes-project-quantum/ growing Firefox] and [https://www.mozilla.org/en-US/technology/ new technology and product areas], we are undertaking a number of interrelated special projects that will help shape where Mozilla is headed and connect the energies of our diverse, global community.

== The whole picture ==
[[File:Strategy projects and layers.png|600px]]

== Context ==
To situate these projects, we need to understand what is in place today:

# The [https://www.mozilla.org/en-US/about/manifesto/ Mozilla Manifesto] -- principles that articulate our vision for the Internet.

# [https://www.mozilla.org/en-US/mission/ Mozilla’s Mission] -- our purpose and primary objectives.

Both of these are enduring, not time-bound and driven by our core beliefs. They are also at quite a high level of abstraction -- many different directions, strategies and projects can fit underneath them.

We also have [https://discourse.mozilla-community.org/t/mozilla-2017-topline-strategy-narrative-and-objectives-key-results-okrs-as-of-jan-2017/13357 overall and product strategies and goals] that are generally updated each year with objectives each quarter.

== 6 special projects to help shape where Mozilla is headed ==
In the first half of 2017 we are adding to these with a few projects that will increase clarity about ''who we are, how we work together, what we are focusing on, and key strategies we will employ''.

1) [[Strategy/True_North_Project|True North]] - a tangible, actionable bridge between our collective long-term, enduring core beliefs as laid out in the Mission, Vision, and Manifesto and our immediate product strategy

2) [https://discourse.mozilla-community.org/t/mozillas-worldview/14320 Mozilla’s Worldview] - an articulation of aspects of Mozilla that identifies who we already are and how we work together, but that aren’t clearly articulated in the Mozilla Manifesto

3) [[Innovation/Projects/Open_Innovation_Strategy|Mozilla Corporation (MoCo) Open Innovation Strategy]] - recommendations for how MoCo can better invest in and execute on being “open” in our products and technologies

4) [https://discourse.mozilla-community.org/t/community-participation-guidelines-draft-community-feedback/13816 Community Participation Guidelines v2] - a vision for how diverse people will participate in Mozilla’s communities, along with behavioral expectations, processes to raise concerns, and consequences for unacceptable behavior

5) [[Diversity_and_Inclusion_Strategy_for_Participation|Diversity and Inclusion for Community Participation Strategy]] - a set of priorities for the next 2-3 years on how we will improve practices in communities to create a truly open and inclusive Mozilla where a diversity of contributors can thrive and grow to their full potential

5) Membership Model exploration - evaluating if a membership model, premium services or philanthropic models are viable for creating deeper engagement with users around our core issues, delivering long-term value to our users and delivering financial sustainability to Mozilla

== How you can be involved ==
Broad participation by diverse Mozillians in all of these projects is important. This includes having a good mix of volunteer contributors and collaborators. Here’s how you can be involved in any or all of these projects:

'''A) Contribute to research:''' You will soon receive an email from Ruben Martin (some of you know him as Nukeador) inviting you to participate in research about our communities and contributors. Please complete the survey contained in that email as it is a big part of the Open Innovation project.

'''B) Engage directly:''' Follow the links above to each project to understand how to get involved. Each is set up a bit differently.

'''C) Join the conversation:''' Subscribe to [https://discourse.mozilla-community.org/c/mozillians “Watching” the Mozillians category on Discourse] (see the drop-down icon in the top right corner directly under the menu bar). We will be hosting a number of conversations there in the coming weeks, and it is the place where updates will be posted.

=== Communities Advisory Group ===
Consider applying to be part of the Communities Advisory Group of ~20 volunteer Mozillians, a group we are assembling specifically to engage with this set of projects (it will be dissolved afterward).

'''Requirements for applicants'''
* willing and able to spend about 10 hours a month for the next few months to be more regularly and deeply consulted on these projects (reading materials along with synchronous and asynchronous interactions)
* some experience and skill in contributing to strategic topics and conversations
* passion for Mozilla and being part of shaping its overall direction

'''Criteria for selection'''
We are looking to compose a group with a diversity of perspectives. In particular, we will seek a balance between gender identities, geographical locations and languages, areas of involvement in Mozilla, professional background and longevity of involvement.

In addition, we will evaluate applications based on:
* experience in organizational or product strategy
* experience relevant to the strategy projects currently being undertaken
* demonstration of a high level of thinking about the issues facing Mozilla
* commitment to Mozilla

'''Applications are due by May 5th.'''

[https://goo.gl/forms/FEFPTIpnj6TDxPHA2 Fill out this form to apply.]

Strategy/2017 Strategy Projects overview

2017-04-26T18:26:51Z

Groter: /* How you can be involved */ small changes

== Overview ==
During the first half of this year, alongside [https://blog.mozilla.org/blog/2017/04/19/first-big-bytes-project-quantum/ growing Firefox] and [https://www.mozilla.org/en-US/technology/ new technology and product areas], we are undertaking a number of interrelated special projects that will help shape where Mozilla is headed and connect the energies of our diverse, global community.

== The whole picture ==
[[File:Strategy projects and layers.png|600px]]

== Context ==
To situate these projects, we need to understand what is in place today:

# The [https://www.mozilla.org/en-US/about/manifesto/ Mozilla Manifesto] -- principles that articulate our vision for the Internet.

# [https://www.mozilla.org/en-US/mission/ Mozilla’s Mission] -- our purpose and primary objectives.

Both of these are enduring, not time-bound and driven by our core beliefs. They are also at quite a high level of abstraction -- many different directions, strategies and projects can fit underneath them.

We also have [https://discourse.mozilla-community.org/t/mozilla-2017-topline-strategy-narrative-and-objectives-key-results-okrs-as-of-jan-2017/13357 overall and product strategies and goals] that are generally updated each year with objectives each quarter.

== 6 special projects to help shape where Mozilla is headed ==
In the first half of 2017 we are adding to these with a few projects that will increase clarity about ''who we are, how we work together, what we are focusing on, and key strategies we will employ''.

1) [[Strategy/True_North_Project|True North]] - a tangible, actionable bridge between our collective long-term, enduring core beliefs as laid out in the Mission, Vision, and Manifesto and our immediate product strategy

2) [https://discourse.mozilla-community.org/t/mozillas-worldview/14320 Mozilla’s Worldview] - an articulation of aspects of Mozilla that identifies who we already are and how we work together, but that aren’t clearly articulated in the Mozilla Manifesto

3) [[Innovation/Projects/Open_Innovation_Strategy|Mozilla Corporation (MoCo) Open Innovation Strategy]] - recommendations for how MoCo can better invest in and execute on being “open” in our products and technologies

4) [https://discourse.mozilla-community.org/t/community-participation-guidelines-draft-community-feedback/13816 Community Participation Guidelines v2] - a vision for how diverse people will participate in Mozilla’s communities, along with behavioral expectations, processes to raise concerns, and consequences for unacceptable behavior

5) [[Diversity_and_Inclusion_Strategy_for_Participation|Diversity and Inclusion for Community Participation Strategy]] - a set of priorities for the next 2-3 years on how we will improve practices in communities to create a truly open and inclusive Mozilla where a diversity of contributors can thrive and grow to their full potential

5) Membership Model exploration - evaluating if a membership model, premium services or philanthropic models are viable for creating deeper engagement with users around our core issues, delivering long-term value to our users and delivering financial sustainability to Mozilla

== How you can be involved ==
Broad participation by diverse Mozillians in all of these projects is important. This includes having a good mix of volunteer contributors and collaborators. Here’s how you can be involved in any or all of these projects:

'''A) Contribute to research:''' You will soon receive an email from Ruben Martin (some of you know him as Nukeador) inviting you to participate in research about our communities and contributors. Please complete the survey contained in that email as it is a big part of the Open Innovation project.

'''B) Engage directly:''' Follow the links above to each project to understand how to get involved. Each is set up a bit differently.

'''C) Join the conversation:''' Subscribe to [https://discourse.mozilla-community.org/c/mozillians “Watching” the Mozillians category on Discourse] (see the drop-down icon in the top right corner directly under the menu bar). We will be hosting a number of conversations there in the coming weeks, and it is the place where updates will be posted.

=== Communities Advisory Group ===
Consider applying to be part of the Communities Advisory Group of ~20 volunteer Mozillians, a group we are assembling specifically to engage with this set of projects (it will be dissolved afterward).

'''Requirements for applicants'''
* willing and able to spend about 10 hours a month for the next few months to be more regularly and deeply consulted on these projects (reading materials along with synchronous and asynchronous interactions)
* some experience and skill in contributing to strategic topics and conversations
* passion for Mozilla and being part of shaping its overall direction

'''Criteria for selection'''
We are looking to compose a group with a diversity of perspectives. In particular, we will seek a balance between gender identities, geographical locations and languages, areas of involvement in Mozilla, professional background and longevity of involvement.

In addition, we will evaluate applications based on:
* experience in organizational or product strategy
* experience relevant to the strategy projects currently being undertaken
* demonstration of a high level of thinking about the issues facing Mozilla
* commitment to Mozilla

'''Applications are due by May 5th.'''
Fill out this form to apply.

Strategy/2017 Strategy Projects overview

2017-04-26T18:24:20Z

Groter: /* Overview */ small change

== Overview ==
During the first half of this year, alongside [https://blog.mozilla.org/blog/2017/04/19/first-big-bytes-project-quantum/ growing Firefox] and [https://www.mozilla.org/en-US/technology/ new technology and product areas], we are undertaking a number of interrelated special projects that will help shape where Mozilla is headed and connect the energies of our diverse, global community.

== The whole picture ==
[[File:Strategy projects and layers.png|600px]]

== Context ==
To situate these projects, we need to understand what is in place today:

# The [https://www.mozilla.org/en-US/about/manifesto/ Mozilla Manifesto] -- principles that articulate our vision for the Internet.

# [https://www.mozilla.org/en-US/mission/ Mozilla’s Mission] -- our purpose and primary objectives.

Both of these are enduring, not time-bound and driven by our core beliefs. They are also at quite a high level of abstraction -- many different directions, strategies and projects can fit underneath them.

We also have [https://discourse.mozilla-community.org/t/mozilla-2017-topline-strategy-narrative-and-objectives-key-results-okrs-as-of-jan-2017/13357 overall and product strategies and goals] that are generally updated each year with objectives each quarter.

== 6 special projects to help shape where Mozilla is headed ==
In the first half of 2017 we are adding to these with a few projects that will increase clarity about ''who we are, how we work together, what we are focusing on, and key strategies we will employ''.

1) [[Strategy/True_North_Project|True North]] - a tangible, actionable bridge between our collective long-term, enduring core beliefs as laid out in the Mission, Vision, and Manifesto and our immediate product strategy

2) [https://discourse.mozilla-community.org/t/mozillas-worldview/14320 Mozilla’s Worldview] - an articulation of aspects of Mozilla that identifies who we already are and how we work together, but that aren’t clearly articulated in the Mozilla Manifesto

3) [[Innovation/Projects/Open_Innovation_Strategy|Mozilla Corporation (MoCo) Open Innovation Strategy]] - recommendations for how MoCo can better invest in and execute on being “open” in our products and technologies

4) [https://discourse.mozilla-community.org/t/community-participation-guidelines-draft-community-feedback/13816 Community Participation Guidelines v2] - a vision for how diverse people will participate in Mozilla’s communities, along with behavioral expectations, processes to raise concerns, and consequences for unacceptable behavior

5) [[Diversity_and_Inclusion_Strategy_for_Participation|Diversity and Inclusion for Community Participation Strategy]] - a set of priorities for the next 2-3 years on how we will improve practices in communities to create a truly open and inclusive Mozilla where a diversity of contributors can thrive and grow to their full potential

5) Membership Model exploration - evaluating if a membership model, premium services or philanthropic models are viable for creating deeper engagement with users around our core issues, delivering long-term value to our users and delivering financial sustainability to Mozilla

== How you can be involved ==
The participation of a diversity of Mozillians in all of these projects is important, and this includes having a good mix of volunteer contributors and collaborators. Here’s how you can be involved in any or all of these projects:

A) You may receive an email from Ruben Martin (some of you know him as Nukeador) asking you to participate in research about our communities and contributors. Please complete that survey as it a big part of the Open Innovation project.

B) Follow the links above to each project to understand how to get involved. Each is set up a bit differently.

C) Subscribe to [https://discourse.mozilla-community.org/c/mozillians “Watching” the Mozillians category on Discourse] (see the drop-down icon in the top right corner directly under the menu bar). We will be hosting a number of conversations there in the coming weeks, and it is the place where updates will be posted.

=== Communities Advisory Group ===
Consider applying to be part of the Communities Advisory Group of ~20 volunteer Mozillians, an ad hoc group we are assembling specifically to engage with this set of projects (it will be dissolved afterward).

'''Requirements for applicants'''
* willing and able to spend about 10 hours a month for the next few months to be more regularly and deeply consulted on these projects (reading materials along with synchronous and asynchronous interactions)
* some experience and skill in contributing to strategic topics and conversations
* passion for Mozilla and being part of shaping its overall direction

'''Criteria for selection'''
We are looking to compose a group with a diversity of perspectives. In particular, we will seek a balance between gender identities, geographical locations and languages, areas of involvement in Mozilla, professional background and longevity of involvement.

In addition, we will evaluate applications based on:
* experience in organizational or product strategy
* experience relevant to the strategy projects currently being undertaken
* demonstration of a high level of thinking about the issues facing Mozilla
* commitment to Mozilla

'''Applications are due by May 1st.'''
Fill out this form to apply.

Strategy/2017 Strategy Projects overview

2017-04-26T18:23:00Z

Groter: /* 5 projects focused on Mozilla’s future */ small changes

== Overview ==
During the first half of this year, we are undertaking a number of projects that will shape the future of Mozilla. This page is an overview of those projects and how they fit with one another.

== The whole picture ==
[[File:Strategy projects and layers.png|600px]]

== Context ==
To situate these projects, we need to understand what is in place today:

# The [https://www.mozilla.org/en-US/about/manifesto/ Mozilla Manifesto] -- principles that articulate our vision for the Internet.

# [https://www.mozilla.org/en-US/mission/ Mozilla’s Mission] -- our purpose and primary objectives.

Both of these are enduring, not time-bound and driven by our core beliefs. They are also at quite a high level of abstraction -- many different directions, strategies and projects can fit underneath them.

We also have [https://discourse.mozilla-community.org/t/mozilla-2017-topline-strategy-narrative-and-objectives-key-results-okrs-as-of-jan-2017/13357 overall and product strategies and goals] that are generally updated each year with objectives each quarter.

== 6 special projects to help shape where Mozilla is headed ==
In the first half of 2017 we are adding to these with a few projects that will increase clarity about ''who we are, how we work together, what we are focusing on, and key strategies we will employ''.

1) [[Strategy/True_North_Project|True North]] - a tangible, actionable bridge between our collective long-term, enduring core beliefs as laid out in the Mission, Vision, and Manifesto and our immediate product strategy

2) [https://discourse.mozilla-community.org/t/mozillas-worldview/14320 Mozilla’s Worldview] - an articulation of aspects of Mozilla that identifies who we already are and how we work together, but that aren’t clearly articulated in the Mozilla Manifesto

3) [[Innovation/Projects/Open_Innovation_Strategy|Mozilla Corporation (MoCo) Open Innovation Strategy]] - recommendations for how MoCo can better invest in and execute on being “open” in our products and technologies

4) [https://discourse.mozilla-community.org/t/community-participation-guidelines-draft-community-feedback/13816 Community Participation Guidelines v2] - a vision for how diverse people will participate in Mozilla’s communities, along with behavioral expectations, processes to raise concerns, and consequences for unacceptable behavior

5) [[Diversity_and_Inclusion_Strategy_for_Participation|Diversity and Inclusion for Community Participation Strategy]] - a set of priorities for the next 2-3 years on how we will improve practices in communities to create a truly open and inclusive Mozilla where a diversity of contributors can thrive and grow to their full potential

5) Membership Model exploration - evaluating if a membership model, premium services or philanthropic models are viable for creating deeper engagement with users around our core issues, delivering long-term value to our users and delivering financial sustainability to Mozilla

== How you can be involved ==
The participation of a diversity of Mozillians in all of these projects is important, and this includes having a good mix of volunteer contributors and collaborators. Here’s how you can be involved in any or all of these projects:

A) You may receive an email from Ruben Martin (some of you know him as Nukeador) asking you to participate in research about our communities and contributors. Please complete that survey as it a big part of the Open Innovation project.

B) Follow the links above to each project to understand how to get involved. Each is set up a bit differently.

C) Subscribe to [https://discourse.mozilla-community.org/c/mozillians “Watching” the Mozillians category on Discourse] (see the drop-down icon in the top right corner directly under the menu bar). We will be hosting a number of conversations there in the coming weeks, and it is the place where updates will be posted.

=== Communities Advisory Group ===
Consider applying to be part of the Communities Advisory Group of ~20 volunteer Mozillians, an ad hoc group we are assembling specifically to engage with this set of projects (it will be dissolved afterward).

'''Requirements for applicants'''
* willing and able to spend about 10 hours a month for the next few months to be more regularly and deeply consulted on these projects (reading materials along with synchronous and asynchronous interactions)
* some experience and skill in contributing to strategic topics and conversations
* passion for Mozilla and being part of shaping its overall direction

'''Criteria for selection'''
We are looking to compose a group with a diversity of perspectives. In particular, we will seek a balance between gender identities, geographical locations and languages, areas of involvement in Mozilla, professional background and longevity of involvement.

In addition, we will evaluate applications based on:
* experience in organizational or product strategy
* experience relevant to the strategy projects currently being undertaken
* demonstration of a high level of thinking about the issues facing Mozilla
* commitment to Mozilla

'''Applications are due by May 1st.'''
Fill out this form to apply.

File:Strategy projects and layers.png

2017-04-25T21:32:10Z

Groter: Groter uploaded a new version of "File:Strategy projects and layers.png"

File:Strategy projects and layers.png

2017-04-25T21:29:09Z

Groter: Groter uploaded a new version of "File:Strategy projects and layers.png"

Strategy/2017 Strategy Projects overview

2017-04-21T19:57:14Z

Groter: Created page

== Overview ==
During the first half of this year, we are undertaking a number of projects that will shape the future of Mozilla. This page is an overview of those projects and how they fit with one another.

== The whole picture ==
[[File:Strategy projects and layers.png|600px]]

== Context ==
To situate these projects, we need to understand what is in place today:

# The [https://www.mozilla.org/en-US/about/manifesto/ Mozilla Manifesto] -- principles that articulate our vision for the Internet.

# [https://www.mozilla.org/en-US/mission/ Mozilla’s Mission] -- our purpose and primary objectives.

Both of these are enduring, not time-bound and driven by our core beliefs. They are also at quite a high level of abstraction -- many different directions, strategies and projects can fit underneath them.

We also have [https://discourse.mozilla-community.org/t/mozilla-2017-topline-strategy-narrative-and-objectives-key-results-okrs-as-of-jan-2017/13357 overall and product strategies and goals] that are generally updated each year with objectives each quarter.

== 5 projects focused on Mozilla’s future ==
In the first half of 2017 we are adding to these with a few projects that will increase clarity about ''who we are, how we work together, what we are focusing on, and key strategies we will employ''.

'''At the highest level, alongside our manifesto and mission, we are adding two elements:'''

1) [https://discourse.mozilla-community.org/t/mozillas-worldview/14320 Mozilla’s Worldview] - an articulation of aspects of Mozilla that identifies who we already are and how we work together, but that aren’t clearly articulated in the Mozilla Manifesto

2) [https://discourse.mozilla-community.org/t/community-participation-guidelines-draft-community-feedback/13816 Community Participation Guidelines v2] - a vision for how diverse people will participate in Mozilla’s communities, along with behavioral expectations, processes to raise concerns, and consequences for unacceptable behavior

'''Next, a layer that links our aspirations and more immediate strategies:'''

3) [[Strategy/True_North_Project|True North]] - a tangible, actionable bridge between our collective long-term, enduring core beliefs as laid out in the Mission, Vision, and Manifesto and our immediate product strategy

'''And finally, a layer of medium-to-long-term strategies that cut across Mozilla:'''

4) [[Innovation/Projects/Open_Innovation_Strategy|Mozilla Corporation (MoCo) Open Innovation Strategy]] - recommendations for how MoCo can better invest in and execute on being “open” in our products and technologies

4a) [[Diversity_and_Inclusion_Strategy_for_Participation|Diversity and Inclusion for Community Participation Strategy]] - a set of priorities for the next 2-3 years on how we will improve practices in communities to create a truly open and inclusive Mozilla where a diversity of contributors can thrive and grow to their full potential

5) Membership Model exploration - evaluating if a membership model, premium services or philanthropic models are viable for creating deeper engagement with users around our core issues, delivering long-term value to our users and delivering financial sustainability to Mozilla

== How you can be involved ==
The participation of a diversity of Mozillians in all of these projects is important, and this includes having a good mix of volunteer contributors and collaborators. Here’s how you can be involved in any or all of these projects:

A) You may receive an email from Ruben Martin (some of you know him as Nukeador) asking you to participate in research about our communities and contributors. Please complete that survey as it a big part of the Open Innovation project.

B) Follow the links above to each project to understand how to get involved. Each is set up a bit differently.

C) Subscribe to [https://discourse.mozilla-community.org/c/mozillians “Watching” the Mozillians category on Discourse] (see the drop-down icon in the top right corner directly under the menu bar). We will be hosting a number of conversations there in the coming weeks, and it is the place where updates will be posted.

=== Communities Advisory Group ===
Consider applying to be part of the Communities Advisory Group of ~20 volunteer Mozillians, an ad hoc group we are assembling specifically to engage with this set of projects (it will be dissolved afterward).

'''Requirements for applicants'''
* willing and able to spend about 10 hours a month for the next few months to be more regularly and deeply consulted on these projects (reading materials along with synchronous and asynchronous interactions)
* some experience and skill in contributing to strategic topics and conversations
* passion for Mozilla and being part of shaping its overall direction

'''Criteria for selection'''
We are looking to compose a group with a diversity of perspectives. In particular, we will seek a balance between gender identities, geographical locations and languages, areas of involvement in Mozilla, professional background and longevity of involvement.

In addition, we will evaluate applications based on:
* experience in organizational or product strategy
* experience relevant to the strategy projects currently being undertaken
* demonstration of a high level of thinking about the issues facing Mozilla
* commitment to Mozilla

'''Applications are due by May 1st.'''
Fill out this form to apply.

File:Strategy projects and layers.png

2017-04-21T19:38:43Z

Groter:

Strategy/True North Project

2017-04-21T14:26:58Z

Groter: Created page

== True North ==
A '''True North''' provides a tangible, actionable bridge between our collective long-term, enduring core beliefs as laid out in the Mission, Vision, and Manifesto and our immediate product strategy.

[[File:True North 1.png|600px]]

True Norths can take a few different forms - they can be oriented around one or more of:
* Goal or outcome: Some end-state we want to see in the world
* Role: The function we want to serve in carrying out our Mission
* Domain: A specific topic

True North statements, when completed, will generally include a high-level understanding of the activities that should be done:
* Build: End-to-end product / program offerings that are taken to market
* Catalyze: Spark others to action (e.g., through demos, reference architectures) by working on technologies, but not as full-blown offerings
* Advocate: Issues to use the full Mozilla voice to push for

== The process ==
[[File:True North 2.png|600px]]

There are 2 phases to this work:
* Phase 1 (Now through mid-April): Start with a wide aperture, consolidate to ~10 ideas, then narrow to a shortlist of ~4 candidates
* Phase 2 (Mid-April through mid-June): Select one True North

== Team ==
'''Final decision maker:''' Mitchell Baker

'''Project Owners:'''
* Mitchell Baker
* Chris Beard
* Mark Surman

'''Core Team:'''
* Mitchell Baker
* Chris Beard
* Mark Surman
* Mark Mayo
* Sean White
* Denelle Dixon-Thayer
* Bob Lisbonne
* Karim Lakhani
* David Slater
* John Jensen

== Getting Involved ==
There will be specific outreach on this project on Discourse in the [https://discourse.mozilla-community.org/c/mozillians Mozillians category].

In the meantime, for specific questions or input contact John Jensen (jjenson@mozilla.com) or Irina Sandu (isandu@mozilla.com).

File:True North 2.png

2017-04-21T14:16:42Z

Groter:

File:True North 1.png

2017-04-21T14:13:16Z

Groter:

Participation

2017-01-26T19:05:01Z

Groter: /* The Staff Team */

{{Participation}}
==Participation at Mozilla==

<div style="display:block;border-radius:10px;background-color:rgb(227, 220, 200);padding:20px;margin-top:20px;">
[[Image:Mozilla_Participation.svg|right]]

== Who We Are ==

=== Our Mission ===

The Participation Team develops community leaders and contributors who will invent, shape and defend the internet, and activates them to supercharge Mozilla’s products and our movement.

We do this by:
* Designing and implementing specific participation initiatives -- in partnership with teams around Mozilla -- that adapt and advance global best-practice on participation
* Recruiting and investing in core contributors mobilizers/leaders, and developing diverse, local and global communities that make individual contribution more impactful
* Delivering software/systems and practices that increase the impact of participation across Mozilla

=== Participation Team Principles ===

These are the principles that guide our actions. We chose a manifesto in order to capture the many complex elements of our participatory mission.

# Participation is when people can freely contribute their energies, time and ideas to support Mozilla’s mission
# In order to keep the web open and participatory it must be shaped by organizations, like Mozilla, who are equally open and participatory
# Participation is at the core of Mozilla’s history and identity and provides a key advantage for Mozilla as an organization
# Participation cannot exist without a culture of openness that allows contributors the opportunity to shape and build Mozilla’s programs and products at every level
# Participation must provide value for both Mozilla and Mozillians (participants)
</div>

== What We Do ==

=== Strategy & Reports ===

* [[1H Reflectionshttps://docs.google.com/presentation/d/1PzbBsdALKpdthQATpHFl4F2ZR4z9C0q2J_xfUfqQUkg/edit#slide=id.g14a79da9b2_0_2374|1H Reflections]]
* [https://docs.google.com/presentation/d/1GKmLHalIgNdlAdo-_8dDNjoyw1S4juaV1ZwiR6TPV_g/edit#slide=id.g155bcc95a4_3_781 2H Strategic Plan]
* The [https://docs.google.com/spreadsheets/d/1MhIEeP5bYoYBNN3GFinT640faUyqOuWrnUohmmLvn_0/edit#gid=1128436325 2016 Participation Strategic Plan] guides our work for the year.

=== Working in the open ===

The team is using an agile, scrum-like process called Heartbeats (modeled from the Mozilla Foundation team) to manage our week-to-week work. This involves 3-week Heartbeats, with a number of focused projects during each Heartbeat that link to the quarter goals.

Our workflow uses GitHub + Google Docs + Etherpads. Anyone can comment, follow-along or get involved — [https://github.com/mozilla/participation-org/issues]. We welcome feedback on the process and approach.

You can also follow along with what we’re doing on the [https://blog.mozilla.org/community/category/participation/ Blog] and by following [https://twitter.com/mozparticipate @MozParticipate on Twitter].

A Github Milestone = [https://github.com/mozilla/participation-org/milestones Heartbeat].

== Joining the Discussion! ==

If you'd like to get regular updates and discussions about Participation at Mozilla we have a [https://discourse.mozilla-community.org/c/participation section at Mozilla’s discourse] that you can use as a mailing list as well as an online forum. In fact, once it’s set up you can respond to threads by emails and it will be publish directly into the topic.

=== The Team ===

==== Head of Core Contributors, Participation ====
* [https://mozillians.org/u/geroter/ George Roter], Team Leader

==== Community Development ====

* [https://mozillians.org/u/lucyeoh/ Lucy Harris] - Manager
* [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis]
* [https://mozillians.org/u/emmairwin/ Emma Irwin]
* [https://mozillians.org/u/kinger/ Brian King]
* [https://mozillians.org/u/nukeador/ Rubén Martín]
* [https://mozillians.org/u/deimidis/ Guillermo Movia]
* [https://mozillians.org/u/couci/ Konstantina Papadea]
* [https://mozillians.org/u/FrancJP/ Francisco Picolini]

==== Participation Systems ====
* [https://mozillians.org/en-US/u/hmitsch/ Henrik Mitsch] - Manager
* [https://mozillians.org/en-US/u/jgiannelos/ John Giannelos]
* [https://mozillians.org/en-US/u/akatsoulas/ Anastasios Katsoulas]
* [https://mozillians.org/u/arielle/ Arielle Kilroy]
* [https://mozillians.org/en-US/u/comzeradd/ Nikos Roussos]

Participation

2017-01-26T18:57:13Z

Groter: /* The Team */ changes to the team

{{Participation}}
==Participation at Mozilla==

<div style="display:block;border-radius:10px;background-color:rgb(227, 220, 200);padding:20px;margin-top:20px;">
[[Image:Mozilla_Participation.svg|right]]

== Who We Are ==

=== Our Mission ===

The Participation Team develops community leaders and contributors who will invent, shape and defend the internet, and activates them to supercharge Mozilla’s products and our movement.

We do this by:
* Designing and implementing specific participation initiatives -- in partnership with teams around Mozilla -- that adapt and advance global best-practice on participation
* Recruiting and investing in core contributors mobilizers/leaders, and developing diverse, local and global communities that make individual contribution more impactful
* Delivering software/systems and practices that increase the impact of participation across Mozilla

=== Participation Team Principles ===

These are the principles that guide our actions. We chose a manifesto in order to capture the many complex elements of our participatory mission.

# Participation is when people can freely contribute their energies, time and ideas to support Mozilla’s mission
# In order to keep the web open and participatory it must be shaped by organizations, like Mozilla, who are equally open and participatory
# Participation is at the core of Mozilla’s history and identity and provides a key advantage for Mozilla as an organization
# Participation cannot exist without a culture of openness that allows contributors the opportunity to shape and build Mozilla’s programs and products at every level
# Participation must provide value for both Mozilla and Mozillians (participants)
</div>

== What We Do ==

=== Strategy & Reports ===

* [[1H Reflectionshttps://docs.google.com/presentation/d/1PzbBsdALKpdthQATpHFl4F2ZR4z9C0q2J_xfUfqQUkg/edit#slide=id.g14a79da9b2_0_2374|1H Reflections]]
* [https://docs.google.com/presentation/d/1GKmLHalIgNdlAdo-_8dDNjoyw1S4juaV1ZwiR6TPV_g/edit#slide=id.g155bcc95a4_3_781 2H Strategic Plan]
* The [https://docs.google.com/spreadsheets/d/1MhIEeP5bYoYBNN3GFinT640faUyqOuWrnUohmmLvn_0/edit#gid=1128436325 2016 Participation Strategic Plan] guides our work for the year.

=== Working in the open ===

The team is using an agile, scrum-like process called Heartbeats (modeled from the Mozilla Foundation team) to manage our week-to-week work. This involves 3-week Heartbeats, with a number of focused projects during each Heartbeat that link to the quarter goals.

Our workflow uses GitHub + Google Docs + Etherpads. Anyone can comment, follow-along or get involved — [https://github.com/mozilla/participation-org/issues]. We welcome feedback on the process and approach.

You can also follow along with what we’re doing on the [https://blog.mozilla.org/community/category/participation/ Blog] and by following [https://twitter.com/mozparticipate @MozParticipate on Twitter].

A Github Milestone = [https://github.com/mozilla/participation-org/milestones Heartbeat].

== Joining the Discussion! ==

If you'd like to get regular updates and discussions about Participation at Mozilla we have a [https://discourse.mozilla-community.org/c/participation section at Mozilla’s discourse] that you can use as a mailing list as well as an online forum. In fact, once it’s set up you can respond to threads by emails and it will be publish directly into the topic.

=== The Staff Team ===

==== Head of Core Contributors, Participation ====
* [https://mozillians.org/u/geroter/ George Roter], Team Leader

==== Community Development ====

* [https://mozillians.org/u/lucyeoh/ Lucy Harris] - Manager
* [https://mozillians.org/en-US/u/bacharakis/ Christos Bacharakis]
* [https://mozillians.org/u/emmairwin/ Emma Irwin]
* [https://mozillians.org/u/kinger/ Brian King]
* [https://mozillians.org/u/nukeador/ Rubén Martín]
* [https://mozillians.org/u/deimidis/ Guillermo Movia]
* [https://mozillians.org/u/couci/ Konstantina Papadea]
* [https://mozillians.org/u/FrancJP/ Francisco Picolini]

==== [[Participation Systems]] ====
* [https://mozillians.org/en-US/u/hmitsch/ Henrik Mitsch] - Manager
* [https://mozillians.org/en-US/u/jgiannelos/ John Giannelos]
* [https://mozillians.org/en-US/u/akatsoulas/ Anastasios Katsoulas]
* [https://mozillians.org/u/arielle/ Arielle Kilroy]
* [https://mozillians.org/en-US/u/comzeradd/ Nikos Roussos]

MozWeek/2016 Hawaii/Volunteer nominations

2016-09-20T16:14:30Z

Groter: /* Organization Designates */ added mozjapan

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer Mozillians join the event, to be integrated with employees. The [[Participation|Participation Team]] is accountable for the process of getting the "right" people to the All Hands, and has largely established a best practice for this. We will be making small refinements for the 2016 Hawaii All Hands.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Hawaii All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer Mozillians who can make a high impact contribution (and who have future potential), have high commitment, and ideally are able to mobilize other volunteers
# Have volunteer and staff Mozillians working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer Mozillians strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 0) Organizations confirm Organization Designate (person responsible for nomination communication, process and decisions) || Sept 8 || Sept 12
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 14 || Sept 20
|-
| 2) Applications -- very lightweight application sent to '''all nominess''' to ensure nominees are available and want to attend || Sept 20 || Sept 27
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 28 || Sept 30
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 3 || Oct 4
|-
| 5) Invitations go out || Oct 5 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 5 || Oct 14
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 15 || Dec 5
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the London All Hands was the only one to exceed 25% non-male genders among volunteer Mozillian participants)

== Major difference from London process ==
Because of a limited number of spots at this All Hands, there will be '''no "open nominations" from non-staff''' this time.

== Organization Designates ==
The following individuals are collecting volunteer nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox || Mike Hoye and Amy Tsay
|-
| Platform || David Bolter
|-
| Connected Devices || Michael Henretty
|-
| Emerging Technologies || Azita Rashed
|-
| Marketing || Maura Tuohy
|-
| People || Larissa Shapiro
|-
| IT || Guillaume Destuynder
|-
| Open Innovation || Patrick Finch
|-
| Participation || Ruben Martin
|-
| Office of the Chair || Jane Finette
|-
| Mozilla Leadership Network (Foundation) || Kaitlin Thaney
|-
| Advocacy (Foundation) + Policy || Sara Haghdoosti
|-
| Technology (Foundation) || Simon Wex
|-
| Mozilla Japan || Noriatsu Kudo
|}

''Organization Designates will be accountable for:''
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions
* Ensuring a good process across their organization to be in contact with/prepare volunteer Mozillians who have been invited

== Number of Volunteer Mozillians per Organizational Area ==
Space is limited at this All Hands, and so we won't have clarity on the total number of volunteer Mozillians we can invite until September 30th.

Following that date, we will publish the "formula" on how we allocate spots per organization area, along with the number of invitees per area.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/2016_Hawaii/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter] or [https://mozillians.org/en-US/u/FrancJP/ Francisco Picolini].

MozWeek/2016 Hawaii/Volunteer nominations

2016-09-16T08:19:37Z

Groter: /* Organization Designates */ added IT

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer Mozillians join the event, to be integrated with employees. The [[Participation|Participation Team]] is accountable for the process of getting the "right" people to the All Hands, and has largely established a best practice for this. We will be making small refinements for the 2016 Hawaii All Hands.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Hawaii All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer Mozillians who can make a high impact contribution (and who have future potential), have high commitment, and ideally are able to mobilize other volunteers
# Have volunteer and staff Mozillians working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer Mozillians strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 0) Organizations confirm Organization Designate (person responsible for nomination communication, process and decisions) || Sept 8 || Sept 12
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 14 || Sept 20
|-
| 2) Applications -- very lightweight application sent to '''all nominess''' to ensure nominees are available and want to attend || Sept 20 || Sept 27
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 28 || Sept 30
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 3 || Oct 4
|-
| 5) Invitations go out || Oct 5 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 5 || Oct 14
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 15 || Dec 5
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the London All Hands was the only one to exceed 25% non-male genders among volunteer Mozillian participants)

== Major difference from London process ==
Because of a limited number of spots at this All Hands, there will be '''no "open nominations" from non-staff''' this time.

== Organization Designates ==
The following individuals are collecting volunteer nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox || Mike Hoye and Amy Tsay
|-
| Platform || David Bolter
|-
| Connected Devices || Michael Henretty
|-
| Emerging Technologies || Azita Rashed
|-
| Marketing || Maura Tuohy
|-
| People || Larissa Shapiro
|-
| IT || Guillaume Destuynder
|-
| Open Innovation || Patrick Finch
|-
| Participation || Ruben Martin
|-
| Office of the Chair || Jane Finette
|-
| Mozilla Leadership Network (Foundation) || Kaitlin Thaney
|-
| Advocacy (Foundation) + Policy || Sara Haghdoosti
|-
| Technology (Foundation) || Simon Wex
|}

''Organization Designates will be accountable for:''
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions
* Ensuring a good process across their organization to be in contact with/prepare volunteer Mozillians who have been invited

== Number of Volunteer Mozillians per Organizational Area ==
Space is limited at this All Hands, and so we won't have clarity on the total number of volunteer Mozillians we can invite until September 30th.

Following that date, we will publish the "formula" on how we allocate spots per organization area, along with the number of invitees per area.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/2016_Hawaii/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter] or [https://mozillians.org/en-US/u/FrancJP/ Francisco Picolini].

MozWeek/2016 Hawaii

2016-09-14T17:35:55Z

Groter: /* Participation of Volunteers */ added link to volunteer process

=='''Dates, Location and Weather'''==
Monday, December 5 - Friday, December 9, 2016 (travel days are Monday the 5th & Saturday the 10th*) in Waikoloa, Hawaii.

We are staying at [http://www.hiltonwaikoloavillage.com/ Hilton Waikoloa Village]. It is a large 64 acre resort. Here is a [http://www.hiltonwaikoloavillage.com/assets/files/resortmap.pdf 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. This needs to pre-approved and pre-arranged.''

=====Weather=====
[https://weather.com/weather/monthly/l/USHI0090:1:US Average temperatures range] from lows of 61 to highs of 78 Fahrenheit (16 to 25 degrees Celsius).

=====Culture=====
To learn more about the Hawaiian Culture before we go, here are a few sites that may be of interest: (feel free to add some if you find more)
*http://www.polynesia.com/polynesian_culture/hawaii/#.V3V5WY6hnr4
*http://www.urbandictionary.com/define.php?term=Hawaiian%20Time
*https://en.wikipedia.org/wiki/Customs_and_etiquette_in_Hawaii

=='''Registration'''==
This is an invite-only event.

=====New Hires=====
We have a process to identify new hires each week and will invite them to book travel (and register, once that’s live) on a steady basis. No action necessary from managers other than to let them know about the event. Due to hotel booking requirements the final day to ask for a new hire to attend is November 1, pending availability.

=====Participation of Volunteers=====
The process for nominating volunteers is outlined here: [[All Hands/2016 Hawaii/Volunteer nominations]]

=='''Travel'''==
Please do not book any travel to Hawaii until you receive an announcement via email. Personal expenses may not be approved.

====Arriving Early/Departing Late Guidelines====

Our standard travel guidelines apply (pre-populated in Egencia) when booking with a few additional budget constraints. Anything booked outside of them will require approval. Most people will arrive on Monday, December 5th and leave on Saturday, December 10th. Here are some exceptions:
* If you live in a country where work travel is prohibited on weekends, you may travel on Friday, December 2nd and Monday, December 12th, if you’d prefer (not required).
* If you plan to spend some extra personal time in Hawaii (choosing to arrive before Monday, December 5th or depart after Saturday, December 10th), you'll need to pull an itinerary for standard dates/locations within the Hawaii Portal. You can sway up to +$100 over and Mozilla will cover it. Otherwise you'll need to come with an alternate itinerary that fits within the pricing (like a round trip in and out of KOA w/ longer dates, and you personally book & cover the rest). We do not have the ability for employees to reimburse Mozilla for any overage.
* If you are attending the Monday Core Influencer's event (by invite).
* If you would like to arrive early to recover from jetlag, you will need manager approval for any additional costs associated with the extension. There is no unilateral "All Hands" approval based upon timezone to arrive early. For hotel, you will book and pay on your own (per hotel instructions below), and expense the manager approved amount (which is coded to your cost center).

====Hotel====

We are all staying at the [http://www.hiltonwaikoloavillage.com/ Hilton Waikoloa Village]. "Every employee has one room. If you are bringing family members, each room can fit up to 4 people with an extra charge of $50 per extra guest (for the 3rd and 4th guests). Unfortunately the hotel is sold out and we do not have any extra rooms for additional family members beyond that during the week. There are other hotels in the area, see below under family for some options.

A link is available to book hotel 3 days pre and 3 days post at our negotiated rate (email bmark@ for the link) - keep in mind those will be subject to availability. The pre/post reservations will require the use of an LDAP email* so we can link them to your All Hands reservation. Please note that by selecting a specific room type now, ''may'' mean a room move once rooms are assigned for the week. We'll do our absolute best to keep you in the same room type all week.

Three room type options:
*Resort View $195 + tax
*Partial Ocean View $215 + tax
*Ocean View $235 + tax

Theses rates are based on single/double occupancy. There is an extra person charge of $50 per a 3rd and 4th adult to share the same room. They do not charge for children 18 years and younger to share the same room using existing bedding. Standard rooms maximum occupancy is 4.

Make sure to book the same room type pre & post (it will be two reservations).

A Daily resort charges plus tax per night will be added to the room rate and includes: High Speed Internet Access / Wifi Access; Play station 3 access with unlimited movies & games; Hawaiian Cultural activities; 20% discount on lagoon beach toys, and 10% discount on Ocean sports cruises.

They require a credit card to confirm the reservation and '''cancellation will be 14 days prior to arrival to avoid a one night penalty charge'''.

A few links of interest:
*[http://www3.hilton.com/en/hotels/hawaii/hilton-waikoloa-village-KOAHWHH/about/amenities.html Amenities]
*[http://www.hiltonwaikoloavillage.com/resort-experiences/dolphin-quest Dolphin Quest] Book online using promo code: GH339345MOZI16 and you will 10% off, or call and mention you are with Mozilla.
*[http://www.hiltonwaikoloavillage.com/about-the-resort/interactive-resort-map Resort Map]

=====The Basics=====
*Hotel Check-in: 3:00 pm
*Hotel Check-out: 12:00 pm
*The entire hotel is Non-Smoking. Smoking is only allowed in designated smoking areas.

====Family====
Each employee has one room at the Hilton Waikoloa. If you are bringing family members, each room can fit up to 4 people .
Here are other hotels in the area that might work for you:

1. Aston Waikoloa Colony Villas 
2. Aston Shores at Waikoloa 
3. Vista Waikoloa 
4. The Fairmont Orchid

====Booking Family Travel====
To book travel for family, whether they will accompany you on your flight or join us later, please call or email Egencia (vs. booking via the link above). You can pay for your family directly (including the Egencia booking fees) and coordinate with your own travel (which can be billed to Mozilla).
* '''Call:''' +1 (877) 264-1622 or +1 (417) 521-0273; Monday - Friday 9 am - 6 pm EST. If you call outside these hours, you will get an after hours agent, who may not be as helpful.
* '''Email:''' egegrp@expedia.com. The email is monitored Monday - Friday 9 am - 6 pm EST. If you email, you will eventually need to call with a credit card (for fares & fees for family) and personal details of travelers, but the email can get the flights set-up. The agents will need to following information in the initial email to search for flights: Departure City (hometown) & Arrival City (should be KOA), Travel dates & Number of people traveling together + legal names

=='''Ground Transportation'''==
We will be providing ground transportation from Kailua Kona Airport (KOA) on Sunday, December 4th and Monday, December 5th. Returns to the airport will be provided on Saturday, December 10th.

Options for transportation outside of those dates can be found on the hotel website: http://www.hiltonwaikoloavillage.com/about-the-resort/transportation

=='''Food & Drink'''==
All Meals will be provided and paid for centrally. Any other food or drink expenses (including room service and in-room minibar charges) will be the responsibility of the attendee. Overview of the resort dining options can be found [http://www.hiltonwaikoloavillage.com/dining here], including [http://www.hiltonwaikoloavillage.com/assets/files/dining/GlutenFree.pdf gluten free] dining information.

=='''Immigration'''==
'''Any''' questions on immigration should be sent to immigration@mozilla.com.

If you are from a country that requires a B-1/B-2 business visitor visa to enter the US, please plan for it early as government processing time constantly change.

Please visit the following website to learn more about the visa application process and timing for your country: http://travel.state.gov/content/visas/english/visit/visitor.html#overview

Current Processing times at the US Embassies and Consulates abroad can be found at: https://travel.state.gov/content/visas/en/general/wait-times.html/

Some travelers may be eligible to travel to the United States without first applying for a B-1/B-2 visa, if they are eligible for the Visa Waiver Program (VWP or "ESTA"). You are eligible to apply for admission under the Visa Waiver Program (VWP) if you:

*Intend to enter the United States for 90 days or less for business, pleasure or transit
*Have a valid passport lawfully issued to you by a Visa Waiver Program country: http://www.esta.us/visa_waiver_countries.html
*Have authorization to travel via the Electronic System for Travel Authorization: http://www.esta.us/index.html
*Arrive via a Visa Waiver Program signatory carrier (all commercial airlines meet this requirement)
*Have a return or onward ticket
*Travel may not terminate in contiguous territory or adjacent islands unless the traveler is a resident of one of those areas

=====Pocket Letter=====
A pocket letter is recommended to keep on hand for those who are entering the United States. It should accompany you whether or not you are required to have a visa to enter. You may request a copy of that letter when you register online. Please contact immigration@mozilla.com if you require a specific letter for your visa application or if you have any questions regarding your citizenship, visa capabilities or travel related questions.

=====ESTA Point of Contact=====
In the ESTA application you need to give a "U.S. Point of Contact Information".

Please list Heather Durham as your US Point of Contact.
Address: 331 East Evelyn Avenue, Mountain View, CA 94041 Phone: 408.505.3028

=='''Extracurricular Activities'''==
Costs for these activities are self-funded and can not be expensed. Feel free to add activities and invite others.

[http://www.hiltonwaikoloavillage.com/resort-experiences/dolphin-quest Dolphin Quest] Book online using promo code: GH339345MOZI16 and you will 10% off, or call and mention you are with Mozilla.

[https://public.etherpad-mozilla.org/p/kona-day-hike Hiking!]

MozWeek/2016 Hawaii/Volunteer nominations

2016-09-14T13:44:36Z

Groter: /* Process outline */ small changes

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer Mozillians join the event, to be integrated with employees. The [[Participation|Participation Team]] is accountable for the process of getting the "right" people to the All Hands, and has largely established a best practice for this. We will be making small refinements for the 2016 Hawaii All Hands.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Hawaii All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer Mozillians who can make a high impact contribution (and who have future potential), have high commitment, and ideally are able to mobilize other volunteers
# Have volunteer and staff Mozillians working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer Mozillians strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 0) Organizations confirm Organization Designate (person responsible for nomination communication, process and decisions) || Sept 8 || Sept 12
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 14 || Sept 20
|-
| 2) Applications -- very lightweight application sent to '''all nominess''' to ensure nominees are available and want to attend || Sept 20 || Sept 27
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 28 || Sept 30
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 3 || Oct 4
|-
| 5) Invitations go out || Oct 5 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 5 || Oct 14
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 15 || Dec 5
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the London All Hands was the only one to exceed 25% non-male genders among volunteer Mozillian participants)

== Major difference from London process ==
Because of a limited number of spots at this All Hands, there will be '''no "open nominations" from non-staff''' this time.

== Organization Designates ==
The following individuals are collecting volunteer nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox || Mike Hoye and Amy Tsay
|-
| Platform || David Bolter
|-
| Connected Devices || Michael Henretty
|-
| CTO || Azita Rashed
|-
| Marketing || Maura Tuohy
|-
| People || Larissa Shapiro
|-
| Open Innovation || Patrick Finch
|-
| Participation || Ruben Martin
|-
| Office of the Chair || Jane Finette
|-
| Mozilla Leadership Network (Foundation) || Kaitlin Thaney
|-
| Advocacy (Foundation) + Policy || Sara Haghdoosti
|-
| Technology (Foundation) || Simon Wex
|}

''Organization Designates will be accountable for:''
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions
* Ensuring a good process across their organization to be in contact with/prepare volunteer Mozillians who have been invited

== Number of Volunteer Mozillians per Organizational Area ==
Space is limited at this All Hands, and so we won't have clarity on the total number of volunteer Mozillians we can invite until September 30th.

Following that date, we will publish the "formula" on how we allocate spots per organization area, along with the number of invitees per area.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/2016_Hawaii/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter] or [https://mozillians.org/en-US/u/FrancJP/ Francisco Picolini].

MozWeek/2016 Hawaii/Volunteer nominations

2016-09-14T13:42:33Z

Groter: /* Organization Designates */ added people

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer Mozillians join the event, to be integrated with employees. The [[Participation|Participation Team]] is accountable for the process of getting the "right" people to the All Hands, and has largely established a best practice for this. We will be making small refinements for the 2016 Hawaii All Hands.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Hawaii All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer Mozillians who can make a high impact contribution (and who have future potential), have high commitment, and ideally are able to mobilize other volunteers
# Have volunteer and staff Mozillians working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer Mozillians strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 0) Organizations confirm Organization Designate (person responsible for nomination communication, process and decisions) || Sept 8 || Sept 12
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 12 || Sept 18
|-
| 2) Applications -- very lightweight application sent to '''all nominess''' to ensure nominees are available and want to attend || Sept 19 || Sept 25
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 26 || Sept 30
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 3 || Oct 4
|-
| 5) Invitations go out || Oct 5 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 5 || Oct 14
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 15 || Dec 5
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the London All Hands was the only one to exceed 25% non-male genders among volunteer Mozillian participants)

== Major difference from London process ==
Because of a limited number of spots at this All Hands, there will be '''no "open nominations" from non-staff''' this time.

== Organization Designates ==
The following individuals are collecting volunteer nominations from employees for their respective parts of the organization. You will have heard from them, but please reach out directly if you want to nominate a volunteer.

{| class="wikitable"
|-
! Organization !! Name of Org Designate(s)
|-
| Firefox || Mike Hoye and Amy Tsay
|-
| Platform || David Bolter
|-
| Connected Devices || Michael Henretty
|-
| CTO || Azita Rashed
|-
| Marketing || Maura Tuohy
|-
| People || Larissa Shapiro
|-
| Open Innovation || Patrick Finch
|-
| Participation || Ruben Martin
|-
| Office of the Chair || Jane Finette
|-
| Mozilla Leadership Network (Foundation) || Kaitlin Thaney
|-
| Advocacy (Foundation) + Policy || Sara Haghdoosti
|-
| Technology (Foundation) || Simon Wex
|}

''Organization Designates will be accountable for:''
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions
* Ensuring a good process across their organization to be in contact with/prepare volunteer Mozillians who have been invited

== Number of Volunteer Mozillians per Organizational Area ==
Space is limited at this All Hands, and so we won't have clarity on the total number of volunteer Mozillians we can invite until September 30th.

Following that date, we will publish the "formula" on how we allocate spots per organization area, along with the number of invitees per area.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/2016_Hawaii/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter] or [https://mozillians.org/en-US/u/FrancJP/ Francisco Picolini].

MozWeek/2016 Hawaii/Volunteer nominations

2016-09-08T10:31:16Z

Groter: /* Process outline */

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer Mozillians join the event, to be integrated with employees. The [[Participation|Participation Team]] is accountable for the process of getting the "right" people to the All Hands, and has largely established a best practice for this. We will be making small refinements for the 2016 Hawaii All Hands.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Hawaii All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer Mozillians who can make a high impact contribution (and who have future potential), have high commitment, and ideally are able to mobilize other volunteers
# Have volunteer and staff Mozillians working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer Mozillians strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 0) Organizations confirm Organization Designate (person responsible for nomination communication, process and decisions) || Sept 8 || Sept 12
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 12 || Sept 18
|-
| 2) Applications -- very lightweight application sent to '''all nominess''' to ensure nominees are available and want to attend || Sept 19 || Sept 25
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 26 || Sept 30
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 3 || Oct 4
|-
| 5) Invitations go out || Oct 5 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 5 || Oct 14
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 15 || Dec 5
|}

''Important note''
* We are emphasizing greater gender balance (by having this as an emphasis, the London All Hands was the only one to exceed 25% non-male genders among volunteer Mozillian participants)

== Major difference from London process ==
Because of a limited number of spots at this All Hands, there will be '''no "open nominations" from non-staff''' this time.

== Organization Designates ==
Coming soon. Organization Designates will be accountable for:
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions
* Ensuring a good process across their organization to be in contact with/prepare volunteer Mozillians who have been invited

== Number of Volunteer Mozillians per Organizational Area ==
Space is limited at this All Hands, and so we won't have clarity on the total number of volunteer Mozillians we can invite until September 30th.

Following that date, we will publish the "formula" on how we allocate spots per organization area, along with the number of invitees per area.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/2016_Hawaii/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter] or [https://mozillians.org/en-US/u/FrancJP/ Francisco Picolini].

MozWeek/2016 Hawaii/Volunteer nominations

2016-09-08T10:25:09Z

Groter: /* Process outline */

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer Mozillians join the event, to be integrated with employees. The [[Participation|Participation Team]] is accountable for the process of getting the "right" people to the All Hands, and has largely established a best practice for this. We will be making small refinements for the 2016 Hawaii All Hands.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Hawaii All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer Mozillians who can make a high impact contribution (and who have future potential), have high commitment, and ideally are able to mobilize other volunteers
# Have volunteer and staff Mozillians working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer Mozillians strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 0) Organizations confirm Organization Designate (person responsible for nomination communication, process and decisions) || Sept 8 || Sept 12
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 12 || Sept 18
|-
| 2) Applications -- very lightweight application sent to '''all nominess''' to ensure nominees are available and want to attend || Sept 19 || Sept 25
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 26 || Sept 30
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 3 || Oct 4
|-
| 5) Invitations go out || Oct 5 || -
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 5 || Oct 14
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 15 || Dec 5
|}

''Important note''
# We are emphasizing greater gender balance (by having this as an emphasis, the London All Hands was the only one to exceed 25% non-male genders among volunteer Mozillian participants)

== Major difference from London process ==
Because of a limited number of spots at this All Hands, there will be '''no "open nominations" from non-staff''' this time.

== Organization Designates ==
Coming soon. Organization Designates will be accountable for:
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions
* Ensuring a good process across their organization to be in contact with/prepare volunteer Mozillians who have been invited

== Number of Volunteer Mozillians per Organizational Area ==
Space is limited at this All Hands, and so we won't have clarity on the total number of volunteer Mozillians we can invite until September 30th.

Following that date, we will publish the "formula" on how we allocate spots per organization area, along with the number of invitees per area.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/2016_Hawaii/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter] or [https://mozillians.org/en-US/u/FrancJP/ Francisco Picolini].

MozWeek/2016 Hawaii/Volunteer nominations

2016-09-08T10:15:28Z

Groter: created

== Introduction ==
Since our first All Hands in Portland (previously called coincidental work week), we've aimed to have highly committed and impactful volunteer Mozillians join the event, to be integrated with employees. The [[Participation|Participation Team]] is accountable for the process of getting the "right" people to the All Hands, and has largely established a best practice for this. We will be making small refinements for the 2016 Hawaii All Hands.

(For your reference: This current process is largely based on [[All_Hands/2016_London/Volunteer_Nominations#Lessons_Learned_from_past_All_Hands|lessons we've synthesized]] from the past gatherings.)

This page outlines the nomination and selection process that will be used for the Hawaii All Hands.

== Goals ==
The goals of the nomination process are:

# Invite volunteer Mozillians who can make a high impact contribution (and who have future potential), have high commitment, and ideally are able to mobilize other volunteers
# Have volunteer and staff Mozillians working in an integrated way -- during and immediately before and after the All Hands
# Have teams thinking about volunteer Mozillians strategically
# A process that has legitimacy with volunteers and employees

== Process outline ==
{| class="wikitable"
|-
! Step !! Start date !! End date
|-
| 0) Organizations confirm Organization Designate (person responsible for nomination communication, process and decisions) || Sept 8 || Sept 12
|-
| 1) Team nominations -- staff nominate volunteer Mozillians (different process by team ... run by Organization Designate) || Sept 12 || Sept 18
|-
| 2) Applications -- very lightweight application sent to '''all nominess''' to ensure nominees are available and want to attend || Sept 19 || Sept 25
|-
| 3) Final prioritization -- by individual team Organization Designates based on lists of nominees who have confirmed availability || Sept 26 || Sept 30
|-
| 4) Final selection -- based on total number of spots available, formula for allocating spots per team, and prioritization of people by team || Oct 3 || Oct 4
|-
| 5) Invitations go out || Oct 5 ||
|-
| 6) Registration and flight booking → information about this will be on another page || Oct 5 || Oct 14
|-
| 7) Working with volunteers and teams on their plans for integration/communication → plan for this will be on another page || Oct 15 || Dec 5
|}

''Important note''
# We are emphasizing greater gender balance (by having this as an emphasis, the London All Hands was the only one to exceed 25% non-male genders among volunteer Mozillian participants)

== Major difference from London process ==
Because of a limited number of spots at this All Hands, there will be '''no "open nominations" from non-staff''' this time.

== Organization Designates ==
Coming soon. Organization Designates will be accountable for:
* Creating/curating a volunteer nomination process for their part of Mozilla
* Communicating within their organization about this process
* Making final prioritization decisions
* Ensuring a good process across their organization to be in contact with/prepare volunteer Mozillians who have been invited

== Number of Volunteer Mozillians per Organizational Area ==
Space is limited at this All Hands, and so we won't have clarity on the total number of volunteer Mozillians we can invite until September 30th.

Following that date, we will publish the "formula" on how we allocate spots per organization area, along with the number of invitees per area.

== Criteria for volunteer Mozillian nominees ==
[[All_Hands/2016_Hawaii/Volunteer_nominee_criteria|Guidance and criteria are here]].

== Contact ==
Please first get in touch with your Organization Designate if you have questions about how to nominate a volunteer Mozillian or how the selection process will proceed.

If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter] or [https://mozillians.org/en-US/u/FrancJP/ Francisco Picolini].

MozWeek/2016 Hawaii/Volunteer nominee criteria

2016-09-08T09:41:40Z

Groter: /* Individual contributor criteria */ refined

Below are guidelines for which contributors should nominated for the 2016 Hawaii All Hands.

== Must have for all volunteer Mozillians at All Hands: ==
# '''Impact:''' have made or are able to make a significant impact on Mozilla goals
# '''Commitment:''' have demonstrated that they will make a sustained contribution to a team and Mozilla in 2017, after the All Hands

== Nomination Criteria ==
For this All Hands, we are making the distinction between 1) Mobilizers (those who cause/organize others to make contributions) and 2) Individual Contributors. Because of the nature of this All Hands (limited space and largely aimed at 2017 planning), we're asking teams to put an emphasis on Mobilizers and be strategic about Individual Contributors.

There should be a very high bar for all nominees

===Mobilizer criteria ===
* Highly aligned with Mozilla and team goals and core projects/initiatives
* Demonstrated success (and attribution) in mobilizing large numbers of contributions/contributors
* Clear magnifying effect on staff impact/time (i.e. will take 1 staff hour and convert it to many hours of impactful effort)
* Strategic -- will be able to contribute substantially to crafting or refining Participation/Community plans and programs

=== Individual contributor criteria ===
* Currently working on a core project or initiative
* Consistently involved (meetings, regular contributions, generally available)
* Making high impact, unique contributions that would be hard to achieve without their involvement

=== Not criteria ===
Attending an All Hands is not a reward -- purely wanting to recognize someone for their past contribution is not a nomination criteria.

MozWeek/2016 Hawaii/Volunteer nominee criteria

2016-09-08T09:40:20Z

Groter: Created page

Below are guidelines for which contributors should nominated for the 2016 Hawaii All Hands.

== Must have for all volunteer Mozillians at All Hands: ==
# '''Impact:''' have made or are able to make a significant impact on Mozilla goals
# '''Commitment:''' have demonstrated that they will make a sustained contribution to a team and Mozilla in 2017, after the All Hands

== Nomination Criteria ==
For this All Hands, we are making the distinction between 1) Mobilizers (those who cause/organize others to make contributions) and 2) Individual Contributors. Because of the nature of this All Hands (limited space and largely aimed at 2017 planning), we're asking teams to put an emphasis on Mobilizers and be strategic about Individual Contributors.

There should be a very high bar for all nominees

===Mobilizer criteria ===
* Highly aligned with Mozilla and team goals and core projects/initiatives
* Demonstrated success (and attribution) in mobilizing large numbers of contributions/contributors
* Clear magnifying effect on staff impact/time (i.e. will take 1 staff hour and convert it to many hours of impactful effort)
* Strategic -- will be able to contribute substantially to crafting or refining Participation/Community plans and programs

=== Individual contributor criteria ===
* Currently working on a core project or initiative
* Consistently involved (meetings, regular contributions, generally available)
* Making high impact contributions that would be hard to achieve otherwise

=== Not criteria ===
Attending an All Hands is not a reward -- purely wanting to recognize someone for their past contribution is not a nomination criteria.