https://wiki.mozilla.org/api.php?action=feedcontributions&user=Lucyeoh&feedformat=atomMozillaWiki - User contributions [en]2024-03-28T19:41:00ZUser contributionsMediaWiki 1.27.4https://wiki.mozilla.org/index.php?title=NDA-Slack/Etiquette-Guide&diff=1225336NDA-Slack/Etiquette-Guide2020-03-23T14:04:22Z<p>Lucyeoh: </p>
<hr />
<div>= A Basic Guide for New Mozilla Slack Participants. = <br />
<br />
=== Quick Guide: ===<br />
<br />
Mozilla’s Slack is the easiest way to interact and contact people to collaborate on Mozilla projects. As such, it is primarily a professional environment, and while there are social channels, the function of most channels is getting work done. As such we require that everyone in Slack adheres to a high-standard of professionalism and respect in their behavior. '''Any behavior deemed disruptive, unprofessional, or disrespectful will result in your immediate removal and exclusion from Slack.''' Below we will share some guidelines and best practices to help you be successful on Mozilla’s Slack.<br />
<br />
=== Before getting started: ===<br />
<br />
* Review and remember both expected, and unacceptable behaviors listed in [https://www.mozilla.org/about/governance/policies/participation/ Mozilla’s Community Participation Guidelines (CPG)]. If you see anyone violating the CPG, please send a message to inclusion at mozilla.com. <br />
* Remember that all information on Mozilla Slack are classified as "[[NDA|Mozilla Confidential - Staff and NDA'd Mozillians Only]]”. That means all information here is confidential and should absolutely not be shared without prior permission from the project owner.<br />
* Make sure your username and avatar image are appropriate for the workspace. Names and avatar images in Mozilla's Slack should be not be explicit or sexual in anyway. <br />
* If you have any questions or require additional support - please contact slack-onboarding or your Manager or Inviter.<br />
* If you need a Slack admin quickly, you can @slackadmin to hail all the admins. Please use this sparingly because it will notify all admins.<br />
<br />
=== Getting started on Mozilla Slack: ===<br />
<br />
* Tell people who you are - edit your Slack profile, adding your *full name* and *contribution area* (in section _What I do_) also please include the link to your Mozillians profile in the corresponding Slack profile field. <br />
* Read the _Channel Details_ as they might tell you about a channel's purpose and etiquette.<br />
* On high-traffic channels it's a good practice to read along (or “lurk”) for a little before jumping in to get a feeling for channel culture.<br />
* Be mindful when mentioning specific users, @here or @channel in your messages, especially in channels with high numbers of members (like #announcements). <br />
* Using Slack’s threading feature for longer discussions by hovering over the message and clicking Start a thread. The right sidebar in Slack will open, and you can add your reply. <br />
* '''When in doubt ask!''' If you’re not sure what you can or cannot share, have a question, or are not sure where to start, hit us up on #slack-onboarding.<br />
<br />
=== Navigating the Channels: === <br />
<br />
* '''Work or Project focused''' - These channels usually are named after the product they work on and are similar to a quiet office. They are used to talk about work on a specific product or project, you can ask questions, but stay on topic. People are usually busy in these channels and can’t always answer right away - please be especially patient in these channels. E.g. #firefox<br />
* '''Team focused''' - Different teams at Mozilla have different channels for their team to communicate work stuff. If you have a question for a specific team this is a good way to reach them but remember people are busy and in different time zones so you may have to wait a bit and it’s often helpful to have a specific person in mind. E.g. #openinnovation <br />
* '''Closed or Private Channels''' - You may be invited to join a private or closed channel, here’s it’s easy to ask the person who invited you what the goals of the channel are and how you can contribute effectively. Make sure you know what can be shared inside and out of that channel before you share. <br />
* '''#ServiceDesk''' - This channel is for Mozilla employees to access internal IT support. While it's a public channel, due to time and resource constraints, requests for technical support by volunteers cannot be made through this channel. If you need technical support reach out to your community manager and/or the staff voucher who invited you to the NDA/Slack group. <br />
* '''#Announcements''' - The name says it all! Avoid posting to #announcements unless the message is really an announcement that is relevant to all Participants. Please only post announcements there and please comment to those in threads to minimize the impact to the 1000+ people who cannot leave that channel.<br />
* '''Social channels''' - These channels are like a watering hole for people to share random, funny, or interesting things. This is a great place to share something you’re excited about, a funny meme, or a new project you’ve been working. #random, #community-talk #Canada<br />
<br />
=== Joining a new channel: === <br />
'''Be respectful'''<br />
* Be mindful when using @channel or @here, not everyone is awake or online in that channel. <br />
* When contacting an individual, remember that having a Slack status as “available” doesn't necessarily mean that they have the ability to respond to you right away. If you’re not sure how to get a question answered it is ok to ask if that person knows who or what channel you can ask that question. <br />
* Please be civil, remember the Community Participation Guidelines and keep the mutual respect and safety of the channel you are participating in. Make sure you can calmly and logically communicate before hitting send. <br />
* Past decisions about product changes are not up for debate. <br />
'''Be professional'''<br />
* If a person does not respond right away, give it 15 mins then move on. Try another channel. Try an email, or try an advocate for some advice on what to try next. It is ok to ask if that person knows who or what channel you can ask that question. <br />
'''Do not be disruptive'''<br />
'''Please do not spam the channel'''<br />
* Slack is a little different from irc, Ping, pong is not required, just a mention and a question ;-)<br />
* Do not bump a message or repeat a message if you have already sent a mention to the whole channel<br />
* If it is getting too complicated for a public channel take it to a private message by using Slack’s threading feature or using direct messages.<br />
<br />
=== Additional Slack Info === <br />
* Message retention is set to 180 days. This does mean that messages are moderately ephemeral. Slack is not a filing system so if something happens there that you need for posterity, it is up to you to capture it.<br />
* Authentication sessions are set to 30 days. This means that you should only need to re-authenticate to Slack every 30 days.<br />
* In an effort to minimize confusion and help people find what they are looking for, empty and dead channels will be archived. * If there is no real content, they will be culled.<br />
* A dead channel is one that has not seen activity in a specific time (to be determined but likely a month).<br />
* As such, if you have a channel that is only relevant every-so-often, please state that in the channel description and we can keep it around.<br />
* If you only need a channel once a year for a week, please consider archiving it at the end of its validity period.<br />
* Since content only exists for 6 months, a "temporary" channel doesn't make sense to keep around until the next year.<br />
Archived channels are searchable but do not accept new messages.<br />
<br />
== A Helpful Analogy: == <br />
<br />
So this is your first time on the Mozilla Slack? Let me tell you a story before you enter for the first time. Can you close your eyes for a sec? Bear with me. Ok, now imagine when you log into Slack that you are walking into an office building where people are quietly working in each of their cubicles. Each of them have different emojis on their head phones and they each have their own typing pace. Some are in meetings with people in Europe and others are in a meeting room drawing on a dry erase board. <br />
<br />
You walk in to the office and you are trying to find out where you can post your bug in Firefox or where to get the attention of a developer to help fix your issue. Before you do that, there are a couple of things you may want to keep in mind. First, find the right channel and the right person.<br />
<br />
You do a quick search and you ask, what is that channel used for? <br />
<br />
* Once in the room, please first take the temperature of the room, <br />
* Do some scroll back and read a bit about what is being discussed in the channel. <br />
* What is the channel description?<br />
* What time zones are the people in that channel in? <br />
* What are a majority of the last 20 messages about, is it similar to what you want to contribute to that channel or conversation? <br />
* How am I doing? Am I capable of adding productively to this discussion? <br />
<br />
Open your eyes now. If you can answer all of those questions and you answered yes to the last one, proceed to post your questions. Please keep in mind, since it is your first time, this might feel a bit like a cold call. Don’t worry, that feeling will go away. <br />
<br />
Onwards you go to login to Slack, just remember to keep it clean, respectful and professional!</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Contributor_nominations&diff=1224763All Hands/Contributor nominations2020-03-06T14:53:03Z<p>Lucyeoh: </p>
<hr />
<div><br />
<br />
== Introduction ==<br />
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.<br />
<br />
This page outlines the nomination and selection process that will be used for all Mozilla All Hands.<br />
<br />
== Goals ==<br />
The goals of the nomination process are:<br />
<br />
# 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<br />
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands<br />
# Mozilla teams are thinking about contributors strategically<br />
# A process that has legitimacy with contributors and employees<br />
<br />
== Process outline ==<br />
{| class="wikitable"<br />
|-<br />
! Step !! Starts !! Duration<br />
|-<br />
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || 3.5 months in advance || 2 Weeks<br />
|-<br />
| 2) Review and final prioritization || 3 months in advance || 1 week<br />
|-<br />
| 3) HR, Legal and CPG compliance screening || 3 months in advance || 1 week<br />
|-<br />
| 4) Invitations go out & Volunteer registration opens || 2 months in advance || 2 week2<br />
|-<br />
| 5) Registration and flight booking → information about this will be on another page || || <br />
|-<br />
| 6) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || || <br />
|}<br />
<br />
''Important note''<br />
* We are emphasizing greater gender balance for nominated contributors -- based on the past, our hope is to have 30% non-male contributors attending<br />
<br />
== Open Nominations ==<br />
There will be '''no "open nominations" from non-employees'''. Nominations must come directly from employees.<br />
<br />
== Organization Designates ==<br />
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.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Organization !! Name of Org Designate(s)<br />
|-<br />
| Firefox/Product || Mike Hoye (mhoye)<br />
|-<br />
| Emerging Technologies || Nancy Hang (nhang)<br />
|-<br />
| Operations (incl Open Innovation) || Lucy Harris (lharris)<br />
|}<br />
<br />
''Organization Designates will be accountable for:''<br />
* Creating/curating a contributor nomination process for their part of Mozilla<br />
* Communicating within their organization about this process<br />
* Making final prioritization decisions (if needed)<br />
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited<br />
<br />
== Number of Contributors ==<br />
We have space for roughly 60 contributors.<br />
<br />
== Criteria for contributor nominees ==<br />
[[All_Hands/Berlin2020/Contributor_nominee_criteria|Guidance and criteria are here]].<br />
<br />
== Contact ==<br />
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.<br />
<br />
If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/lucyeoh/ Lucy].</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Contributor_nominations&diff=1224749All Hands/Contributor nominations2020-03-06T14:31:53Z<p>Lucyeoh: </p>
<hr />
<div><br />
<br />
== Introduction ==<br />
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.<br />
<br />
This page outlines the nomination and selection process that will be used for all Mozilla All Hands.<br />
<br />
== Goals ==<br />
The goals of the nomination process are:<br />
<br />
# 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<br />
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands<br />
# Mozilla teams are thinking about contributors strategically<br />
# A process that has legitimacy with contributors and employees<br />
<br />
== Process outline ==<br />
{| class="wikitable"<br />
|-<br />
! Step !! Starts !! Duration<br />
|-<br />
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || 3.5 months in advance || 2 Weeks<br />
|-<br />
| 2) Review and final prioritization || 3 months in advance || 1 week<br />
|-<br />
| 3) HR, Legal and CPG compliance screening || 3 months in advance || 1 week<br />
|-<br />
| 4) Invitations go out & Volunteer registration opens || 2 months in advance || 2 week2<br />
|-<br />
| 5) Registration and flight booking → information about this will be on another page || || <br />
|-<br />
| 6) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || || <br />
|}<br />
<br />
''Important note''<br />
* We are emphasizing greater gender balance for nominated contributors -- based on the past, our hope is to have 30% non-male contributors attending<br />
<br />
== Open Nominations ==<br />
There will be '''no "open nominations" from non-employees'''. Nominations must come directly from employees.<br />
<br />
== Organization Designates ==<br />
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.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Organization !! Name of Org Designate(s)<br />
|-<br />
| Firefox/Product || Mike Hoye (mhoye)<br />
|-<br />
| Emerging Technologies || Nancy Hang (nhang)<br />
|-<br />
| Operations (incl Open Innovation) || Lucy Harris (lharris)<br />
|}<br />
<br />
''Organization Designates will be accountable for:''<br />
* Creating/curating a contributor nomination process for their part of Mozilla<br />
* Communicating within their organization about this process<br />
* Making final prioritization decisions (if needed)<br />
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited<br />
<br />
== Number of Contributors ==<br />
We have space for roughly 60 contributors.<br />
<br />
== Criteria for contributor nominees ==<br />
[[All_Hands/Berlin2020/Contributor_nominee_criteria|Guidance and criteria are here]].<br />
<br />
== Contact ==<br />
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.<br />
<br />
If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Contributor_nominee_criteria&diff=1224264All Hands/Contributor nominee criteria2020-02-26T19:57:14Z<p>Lucyeoh: Created page with " == Guiding Principles == We want to make sure everyone who is invited to the All Hands feels like they are there for a specific purpose, that they’ll have meaningful things..."</p>
<hr />
<div><br />
== Guiding Principles ==<br />
We want to make sure everyone who is invited to the All Hands feels like they are there for a specific purpose, that they’ll have meaningful things to contribute to during the week that takes advantage of the All Hands setting, and benefits from their skills and experiences. <br />
<br />
== Must have for all contributors at All Hands: ==<br />
# Must be working on a project/program that will be advanced at the All Hands<br />
# The contributor's presence at the All Hands meaningfully advances this work (i.e. allows strategic planning, insight gathering, brainstorming, etc.)<br />
# Their contributions are strategically important and will have impact on the team's goals<br />
# Their contribution is required for the majority of the All Hands week<br />
<br />
== Additional Criteria (at least one must apply): ==<br />
# They’re working on a project that will majorly advance at this All Hands<br />
# The contributor provides unique value to this work<br />
# Their presence is a required part of an ecosystem strategy<br />
# The work requires the circumstances of the All Hands to complete<br />
<br />
== Exclusions ==<br />
We are not able to bring contributors with whom we have had a business relationship (former staff, contractors, interns etc.) in the past 3-6 months. We also cannot bring contributors who are about to sign a contract with Mozilla. If you have questions please contact your organizations delegate. Note we do not have a business relationship with Outreachy Interns so they can be invited as volunteers.<br />
<br />
=== Not criteria ===<br />
Attending an All Hands is not a reward -- wanting to recognize someone for their past contribution is not a nomination criteria.<br />
<br />
=== Considerations ===<br />
<br />
Part of increasing the impact of our contributor communities involves increasing their diversity. You can help improve this even more by nominating people from diverse backgrounds (gender and other dimensions of diversity).</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=NDA&diff=1221800NDA2020-01-03T15:13:09Z<p>Lucyeoh: /* How long does an NDA last: */</p>
<hr />
<div>== <big>Confidentiality Agreement FAQ</big> == <br />
<br />
==== What is a Confidentiality Agreement: ====<br />
<br />
A Confidentiality Agreement (or NDA) is a legal agreement between volunteers and Mozilla that will allow us to share confidential information with contributors that we don’t, or aren’t yet ready to share with the general public. For example, NDA’d Mozillians have access to the videos on Air Mozilla, which are closed to the public because they contain confidential information. <br />
<br />
In order for the NDA group to grow and succeed it requires everyone who enters it to make a commitment to share the trust conferred by admission into this group. <br />
<br />
'''You can view the full text of the NDA [https://drive.google.com/file/d/0B-IbEs3PKNPKVzlqWGQ0bWRkcTQ/view?usp=sharing here].'''<br />
<br />
Contributors can also request that information shared with you under the NDA be made public through this form [http://mzl.la/reclassify mzl.la/reclassify].<br />
<br />
NOTE: This NDA process is exclusively for volunteer Mozillians. To NDA a contractor, vendor, intern, or anyone else Mozilla has a business relationship with, please file [http://sso.mozilla.com/casa a casa ticket].<br />
<br />
==== What are your obligations under the NDA ====<br />
<br />
* You will only use Confidential Information to perform your Activities on behalf of Mozilla.<br />
* You will not publicly disclose or share the Confidential Information with any other persons, except with other Mozilla employees or other volunteers under an NDA with Mozilla as noted below.<br />
<br />
You will:<br />
* a) only share the Confidential Information if the person disclosing the information tells you<br />
* that it can be shared,<br />
* b) only share the Confidential Information with the specific group or individuals Mozilla<br />
* authorizes you to share with; and<br />
* c) use appropriate judgment and access restrictions to prevent unauthorized disclosure.<br />
<br />
By signing an NDA, in addition to agreeing to comply with the terms of the NDA (above) you are agreeing to respect and adhere to [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla’s Community Participation Guidelines] (“CPG”). Violation of these guidelines can result in you being removed from the NDA group, either temporarily or in perpetuity.<br />
<br />
==== What do I need to get an NDA? ====<br />
<br />
In addition to a staff member who can vouch for your contributions and ability to maintain the parameters of the NDA (the details of which are blow) you will need to have the following: <br />
<br />
* A [https://mozillians.org/en-US/ Mozillians.org profile] <br />
* Setup [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|multifactor authentication]] on their profile<br />
<br />
==== How long does an NDA last: ====<br />
<br />
NDA’s expire after one year, in order to make sure that those on the list are regularly active. One year from the acceptance date, inviters will have the opportunity to re-invite volunteers to the NDA group. You can request to leave the NDA group at any time. Please note that your obligations continue for as long as the information remains confidential, even if the NDA ends. Only when the information is publicly announced or made publicly available by Mozilla (or<br />
its partner) is the information no longer considered Confidential Information. If you’re unsure, ask the persons who provided you with the Confidential Information or email Mozilla’s Legal Team.<br />
<br />
==== What happens once I get my invitation: ==== <br />
Your invitation will arrive to the email associated with your Mozillians profile. Once you receive your invitation, please read and think carefully about the NDA before you agree to its terms and if you have any questions please do not hesitate to reach out to your inviter!<br />
<br />
'''Note that you will need to have [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|Multi-Factor Authentication]] set-up on your Mozillians profile in order to receive your NDA invitation. Instructions for how to set it up can be found [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|Multi-Factor Authentication|here]].''' <br />
<br />
Once you have received and accepted the terms of the NDA you will: <br />
* Automatically be added to the NDA Group on Mozillians<br />
* You will have access to the [https://discourse.mozilla-community.org/c/mozillians/nda NDA-restricted discourse category], a safe space for internal conversations (staff and nda volunteers).<br />
* You will also automatically have access to view NDA-restricted [https://air.mozilla.org/ Air Mozilla] and you will be able to access the #moco channel on IRC from the Air Mozilla page.<br />
* You will receive internal confidential emails with updates pertaining to Mozilla.<br />
* You may also have additional confidential information shared with you personally, so please be aware or check with the disclosure before you re-share any information.<br />
* You may now be invited to additional access groups such as Slack, based on the tools you need to contribute effectively.<br />
<br />
==== Leaving the NDA group: ==== <br />
If you would like to stop receiving confidential information at any time, or can no longer contribute your time as a volunteer, before the end of your one year period you can ask your inviter to remove you from the group or email legal-notices@mozilla.com to end your NDA. Inviters can also remove contributors from the NDA group at any time if that contributor is no longer actively contributing to Mozilla, or if there is a violation of trust or the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines].<br />
<br />
== Who Can Get an NDA == <br />
<br />
They are distributed by invitation to volunteer individuals who are deeply involved with Mozilla and are trusted by the administrators of a Mozilla Community. Reps, L10N, Security and SUMO each have their own procedure for assessing activity and distributing NDA’s (vendors, contractors, and anyone else Mozilla has a business relationship with should file a [https://sso.mozilla.com/casa a CASA ticket] instead). Staff can also nominate contributors to receive an NDA if they believe that a contributor who is actively contributing to Mozilla, they know or have worked with, whose capacity to contribute would be improved by receiving information or having access to Mozilla tools that are not public, and whose capacity to keep the parameters of the NDA are not in doubt.<br />
<br />
Here is the information for each of these groups. <br />
<br />
===== Reps =====<br />
All active Reps are under NDA and receive invitations as part of entry into the program. [https://mozillians.org/en-US/u/nukeador/ Reps Staff] access activity each year for the purposes of renewal. You can read more about how to become a Rep [https://reps.mozilla.org/ here].<br />
<br />
===== SUMO =====<br />
[https://support.mozilla.org/en-US/kb/meet-team/ SUMO admins] determine activity and send invitations to active SUMO members. You can [https://support.mozilla.org/en-US/get-involved read more about how to become a member of SUMO here]. The Mozilla Support Community requires an NDA for product updates and support related communications and participation in the Social Support program that answers brand questions. Check out how to get involved at https://support.mozilla.com and Support. If you have participated for a while or would benefit from a more involved please send a request for an NDA with this form: bit.ly/2Ihl1Rh <br />
<br />
===== L10N =====<br />
You can read more about how to get involved with localization (L10N) [https://wiki.mozilla.org/L10n:Contribute in this page]. If you're an active localizer and want to know more about NDA, please get in touch directly with [https://wiki.mozilla.org/L10n:Mozilla_Team l10n drivers].<br />
<br />
===== Tech Speakers =====<br />
All active Mozilla Tech Speakers are invited to sign Mozilla’s NDA (Non-Disclosure Agreement). This will give you access to timely information about future product plans, releases, organizational announcements, and confidential Mozilla meetings. You can learn more about the Tech Speakers program [https://wiki.mozilla.org/TechSpeakers/ here].<br />
<br />
===== Security Contributors =====<br />
Non-Staff working as part of the Bugzilla Security Group will be invited to join the NDA group. <br />
<br />
===== Research Contributors =====<br />
Non-Staff contributing to Research organization projects such as Rust, Servo, WebVR/WebAR, Daala, and Deep Speech may contact larsberg.<br />
<br />
===== Add-ons Contributors ===== <br />
There are many ways to [[Add-ons/Contribute|contribute]] to Mozilla's [[Add-ons|add-ons projects]]. If you are an active contributor and want to learn more about NDA, please contact [https://mozillians.org/en-US/u/caitmuenster Caitlin Neiman]. <br />
<br />
===== Mozilla Community Web Services ===== <br />
Active MCWS volunteers will be invited to sign Mozilla’s NDA in order to provision and administer some of the Mozilla-hosted web services open to our communities.<br />
<br />
===== All Hands Contributors =====<br />
Volunteers invited by a staff member to attend an All Hands will be invited to sign an NDA. An NDA will be required to participate in some parts of the All Hands. Invitations will be sent shortly before the event, and volunteers will be removed from the NDA group after the All Hands if they are not also covered by one of the long-term contribution areas (above). <br />
<br />
--<br />
<br />
===== Staff Vouching ===== <br />
In order to receive an NDA, if you are not in any of these groups, you must be invited by a staff member. Staff members can vouch for contributors using [http://goo.gl/forms/RoR5kv9ouJ this form].<br />
<br />
Staff should only NDA people who: "Are actively contributing to Mozilla, who you know or have worked with in the past, whose capacity to contribute would be improved by receiving information or having access to Mozilla tools that are not public, and whose capacity to keep the parameters of the NDA you do not doubt. <br />
<br />
<br />
Please note that contributors must have a Mozillians.org account and multi-factor authentication to be added to the NDA Group. Former staff will require an additional screening by the people partner team before an NDA will be granted. <br />
<br />
Staff: Please note that you will accountable for your invitee and you will have to renew their NDA at the end of one year. In order to accommodate for changes in position or employment you must also list a “back-up” inviter who will assume responsibility for your contributors should you leave the organization.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=NDA&diff=1221799NDA2020-01-03T15:12:12Z<p>Lucyeoh: /* What happens once I get my invitation: */</p>
<hr />
<div>== <big>Confidentiality Agreement FAQ</big> == <br />
<br />
==== What is a Confidentiality Agreement: ====<br />
<br />
A Confidentiality Agreement (or NDA) is a legal agreement between volunteers and Mozilla that will allow us to share confidential information with contributors that we don’t, or aren’t yet ready to share with the general public. For example, NDA’d Mozillians have access to the videos on Air Mozilla, which are closed to the public because they contain confidential information. <br />
<br />
In order for the NDA group to grow and succeed it requires everyone who enters it to make a commitment to share the trust conferred by admission into this group. <br />
<br />
'''You can view the full text of the NDA [https://drive.google.com/file/d/0B-IbEs3PKNPKVzlqWGQ0bWRkcTQ/view?usp=sharing here].'''<br />
<br />
Contributors can also request that information shared with you under the NDA be made public through this form [http://mzl.la/reclassify mzl.la/reclassify].<br />
<br />
NOTE: This NDA process is exclusively for volunteer Mozillians. To NDA a contractor, vendor, intern, or anyone else Mozilla has a business relationship with, please file [http://sso.mozilla.com/casa a casa ticket].<br />
<br />
==== What are your obligations under the NDA ====<br />
<br />
* You will only use Confidential Information to perform your Activities on behalf of Mozilla.<br />
* You will not publicly disclose or share the Confidential Information with any other persons, except with other Mozilla employees or other volunteers under an NDA with Mozilla as noted below.<br />
<br />
You will:<br />
* a) only share the Confidential Information if the person disclosing the information tells you<br />
* that it can be shared,<br />
* b) only share the Confidential Information with the specific group or individuals Mozilla<br />
* authorizes you to share with; and<br />
* c) use appropriate judgment and access restrictions to prevent unauthorized disclosure.<br />
<br />
By signing an NDA, in addition to agreeing to comply with the terms of the NDA (above) you are agreeing to respect and adhere to [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla’s Community Participation Guidelines] (“CPG”). Violation of these guidelines can result in you being removed from the NDA group, either temporarily or in perpetuity.<br />
<br />
==== What do I need to get an NDA? ====<br />
<br />
In addition to a staff member who can vouch for your contributions and ability to maintain the parameters of the NDA (the details of which are blow) you will need to have the following: <br />
<br />
* A [https://mozillians.org/en-US/ Mozillians.org profile] <br />
* Setup [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|multifactor authentication]] on their profile<br />
<br />
==== How long does an NDA last: ====<br />
<br />
NDA’s expire after one year, in order to make sure that those on the list are regularly active. One year from the acceptance date, inviters will have the opportunity to re-invite volunteers to the NDA group. <br />
<br />
==== What happens once I get my invitation: ==== <br />
Your invitation will arrive to the email associated with your Mozillians profile. Once you receive your invitation, please read and think carefully about the NDA before you agree to its terms and if you have any questions please do not hesitate to reach out to your inviter!<br />
<br />
'''Note that you will need to have [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|Multi-Factor Authentication]] set-up on your Mozillians profile in order to receive your NDA invitation. Instructions for how to set it up can be found [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|Multi-Factor Authentication|here]].''' <br />
<br />
Once you have received and accepted the terms of the NDA you will: <br />
* Automatically be added to the NDA Group on Mozillians<br />
* You will have access to the [https://discourse.mozilla-community.org/c/mozillians/nda NDA-restricted discourse category], a safe space for internal conversations (staff and nda volunteers).<br />
* You will also automatically have access to view NDA-restricted [https://air.mozilla.org/ Air Mozilla] and you will be able to access the #moco channel on IRC from the Air Mozilla page.<br />
* You will receive internal confidential emails with updates pertaining to Mozilla.<br />
* You may also have additional confidential information shared with you personally, so please be aware or check with the disclosure before you re-share any information.<br />
* You may now be invited to additional access groups such as Slack, based on the tools you need to contribute effectively.<br />
<br />
==== Leaving the NDA group: ==== <br />
If you would like to stop receiving confidential information at any time, or can no longer contribute your time as a volunteer, before the end of your one year period you can ask your inviter to remove you from the group or email legal-notices@mozilla.com to end your NDA. Inviters can also remove contributors from the NDA group at any time if that contributor is no longer actively contributing to Mozilla, or if there is a violation of trust or the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines].<br />
<br />
== Who Can Get an NDA == <br />
<br />
They are distributed by invitation to volunteer individuals who are deeply involved with Mozilla and are trusted by the administrators of a Mozilla Community. Reps, L10N, Security and SUMO each have their own procedure for assessing activity and distributing NDA’s (vendors, contractors, and anyone else Mozilla has a business relationship with should file a [https://sso.mozilla.com/casa a CASA ticket] instead). Staff can also nominate contributors to receive an NDA if they believe that a contributor who is actively contributing to Mozilla, they know or have worked with, whose capacity to contribute would be improved by receiving information or having access to Mozilla tools that are not public, and whose capacity to keep the parameters of the NDA are not in doubt.<br />
<br />
Here is the information for each of these groups. <br />
<br />
===== Reps =====<br />
All active Reps are under NDA and receive invitations as part of entry into the program. [https://mozillians.org/en-US/u/nukeador/ Reps Staff] access activity each year for the purposes of renewal. You can read more about how to become a Rep [https://reps.mozilla.org/ here].<br />
<br />
===== SUMO =====<br />
[https://support.mozilla.org/en-US/kb/meet-team/ SUMO admins] determine activity and send invitations to active SUMO members. You can [https://support.mozilla.org/en-US/get-involved read more about how to become a member of SUMO here]. The Mozilla Support Community requires an NDA for product updates and support related communications and participation in the Social Support program that answers brand questions. Check out how to get involved at https://support.mozilla.com and Support. If you have participated for a while or would benefit from a more involved please send a request for an NDA with this form: bit.ly/2Ihl1Rh <br />
<br />
===== L10N =====<br />
You can read more about how to get involved with localization (L10N) [https://wiki.mozilla.org/L10n:Contribute in this page]. If you're an active localizer and want to know more about NDA, please get in touch directly with [https://wiki.mozilla.org/L10n:Mozilla_Team l10n drivers].<br />
<br />
===== Tech Speakers =====<br />
All active Mozilla Tech Speakers are invited to sign Mozilla’s NDA (Non-Disclosure Agreement). This will give you access to timely information about future product plans, releases, organizational announcements, and confidential Mozilla meetings. You can learn more about the Tech Speakers program [https://wiki.mozilla.org/TechSpeakers/ here].<br />
<br />
===== Security Contributors =====<br />
Non-Staff working as part of the Bugzilla Security Group will be invited to join the NDA group. <br />
<br />
===== Research Contributors =====<br />
Non-Staff contributing to Research organization projects such as Rust, Servo, WebVR/WebAR, Daala, and Deep Speech may contact larsberg.<br />
<br />
===== Add-ons Contributors ===== <br />
There are many ways to [[Add-ons/Contribute|contribute]] to Mozilla's [[Add-ons|add-ons projects]]. If you are an active contributor and want to learn more about NDA, please contact [https://mozillians.org/en-US/u/caitmuenster Caitlin Neiman]. <br />
<br />
===== Mozilla Community Web Services ===== <br />
Active MCWS volunteers will be invited to sign Mozilla’s NDA in order to provision and administer some of the Mozilla-hosted web services open to our communities.<br />
<br />
===== All Hands Contributors =====<br />
Volunteers invited by a staff member to attend an All Hands will be invited to sign an NDA. An NDA will be required to participate in some parts of the All Hands. Invitations will be sent shortly before the event, and volunteers will be removed from the NDA group after the All Hands if they are not also covered by one of the long-term contribution areas (above). <br />
<br />
--<br />
<br />
===== Staff Vouching ===== <br />
In order to receive an NDA, if you are not in any of these groups, you must be invited by a staff member. Staff members can vouch for contributors using [http://goo.gl/forms/RoR5kv9ouJ this form].<br />
<br />
Staff should only NDA people who: "Are actively contributing to Mozilla, who you know or have worked with in the past, whose capacity to contribute would be improved by receiving information or having access to Mozilla tools that are not public, and whose capacity to keep the parameters of the NDA you do not doubt. <br />
<br />
<br />
Please note that contributors must have a Mozillians.org account and multi-factor authentication to be added to the NDA Group. Former staff will require an additional screening by the people partner team before an NDA will be granted. <br />
<br />
Staff: Please note that you will accountable for your invitee and you will have to renew their NDA at the end of one year. In order to accommodate for changes in position or employment you must also list a “back-up” inviter who will assume responsibility for your contributors should you leave the organization.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=NDA&diff=1221798NDA2020-01-03T15:10:25Z<p>Lucyeoh: /* What are your obligations under the NDA */</p>
<hr />
<div>== <big>Confidentiality Agreement FAQ</big> == <br />
<br />
==== What is a Confidentiality Agreement: ====<br />
<br />
A Confidentiality Agreement (or NDA) is a legal agreement between volunteers and Mozilla that will allow us to share confidential information with contributors that we don’t, or aren’t yet ready to share with the general public. For example, NDA’d Mozillians have access to the videos on Air Mozilla, which are closed to the public because they contain confidential information. <br />
<br />
In order for the NDA group to grow and succeed it requires everyone who enters it to make a commitment to share the trust conferred by admission into this group. <br />
<br />
'''You can view the full text of the NDA [https://drive.google.com/file/d/0B-IbEs3PKNPKVzlqWGQ0bWRkcTQ/view?usp=sharing here].'''<br />
<br />
Contributors can also request that information shared with you under the NDA be made public through this form [http://mzl.la/reclassify mzl.la/reclassify].<br />
<br />
NOTE: This NDA process is exclusively for volunteer Mozillians. To NDA a contractor, vendor, intern, or anyone else Mozilla has a business relationship with, please file [http://sso.mozilla.com/casa a casa ticket].<br />
<br />
==== What are your obligations under the NDA ====<br />
<br />
* You will only use Confidential Information to perform your Activities on behalf of Mozilla.<br />
* You will not publicly disclose or share the Confidential Information with any other persons, except with other Mozilla employees or other volunteers under an NDA with Mozilla as noted below.<br />
<br />
You will:<br />
* a) only share the Confidential Information if the person disclosing the information tells you<br />
* that it can be shared,<br />
* b) only share the Confidential Information with the specific group or individuals Mozilla<br />
* authorizes you to share with; and<br />
* c) use appropriate judgment and access restrictions to prevent unauthorized disclosure.<br />
<br />
By signing an NDA, in addition to agreeing to comply with the terms of the NDA (above) you are agreeing to respect and adhere to [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla’s Community Participation Guidelines] (“CPG”). Violation of these guidelines can result in you being removed from the NDA group, either temporarily or in perpetuity.<br />
<br />
==== What do I need to get an NDA? ====<br />
<br />
In addition to a staff member who can vouch for your contributions and ability to maintain the parameters of the NDA (the details of which are blow) you will need to have the following: <br />
<br />
* A [https://mozillians.org/en-US/ Mozillians.org profile] <br />
* Setup [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|multifactor authentication]] on their profile<br />
<br />
==== How long does an NDA last: ====<br />
<br />
NDA’s expire after one year, in order to make sure that those on the list are regularly active. One year from the acceptance date, inviters will have the opportunity to re-invite volunteers to the NDA group. <br />
<br />
==== What happens once I get my invitation: ==== <br />
Your invitation will arrive to the email associated with your Mozillians profile. Once you receive your invitation, please read and think carefully about the NDA before you agree to its terms and if you have any questions please do not hesitate to reach out to your inviter!<br />
<br />
'''Note that you will need to have [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|Multi-Factor Authentication]] set-up on your Mozillians profile in order to receive your NDA invitation. Instructions for how to set it up can be found [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|Multi-Factor Authentication|here]].''' <br />
<br />
Once you have received and accepted the terms of the NDA you will: <br />
* Automatically be added to the NDA Group on Mozillians<br />
* You will have access to the [https://discourse.mozilla-community.org/c/mozillians/nda NDA-restricted discourse category], a safe space for internal conversations (staff and nda volunteers).<br />
* You will also automatically have access to view NDA-restricted [https://air.mozilla.org/ Air Mozilla] and you will be able to access the #moco channel on IRC from the Air Mozilla page.<br />
* You will receive internal confidential emails with updates pertaining to Mozilla.<br />
* You may also have additional confidential information shared with you personally, so please be aware or check with the disclosure before you re-share any information.<br />
* You may also be given access to the Mozilla Slack instance, please discuss this with your inviter if this is something you think would meaningfully improve your ability to contribute effectively.<br />
<br />
==== Leaving the NDA group: ==== <br />
If you would like to stop receiving confidential information at any time, or can no longer contribute your time as a volunteer, before the end of your one year period you can ask your inviter to remove you from the group or email legal-notices@mozilla.com to end your NDA. Inviters can also remove contributors from the NDA group at any time if that contributor is no longer actively contributing to Mozilla, or if there is a violation of trust or the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines].<br />
<br />
== Who Can Get an NDA == <br />
<br />
They are distributed by invitation to volunteer individuals who are deeply involved with Mozilla and are trusted by the administrators of a Mozilla Community. Reps, L10N, Security and SUMO each have their own procedure for assessing activity and distributing NDA’s (vendors, contractors, and anyone else Mozilla has a business relationship with should file a [https://sso.mozilla.com/casa a CASA ticket] instead). Staff can also nominate contributors to receive an NDA if they believe that a contributor who is actively contributing to Mozilla, they know or have worked with, whose capacity to contribute would be improved by receiving information or having access to Mozilla tools that are not public, and whose capacity to keep the parameters of the NDA are not in doubt.<br />
<br />
Here is the information for each of these groups. <br />
<br />
===== Reps =====<br />
All active Reps are under NDA and receive invitations as part of entry into the program. [https://mozillians.org/en-US/u/nukeador/ Reps Staff] access activity each year for the purposes of renewal. You can read more about how to become a Rep [https://reps.mozilla.org/ here].<br />
<br />
===== SUMO =====<br />
[https://support.mozilla.org/en-US/kb/meet-team/ SUMO admins] determine activity and send invitations to active SUMO members. You can [https://support.mozilla.org/en-US/get-involved read more about how to become a member of SUMO here]. The Mozilla Support Community requires an NDA for product updates and support related communications and participation in the Social Support program that answers brand questions. Check out how to get involved at https://support.mozilla.com and Support. If you have participated for a while or would benefit from a more involved please send a request for an NDA with this form: bit.ly/2Ihl1Rh <br />
<br />
===== L10N =====<br />
You can read more about how to get involved with localization (L10N) [https://wiki.mozilla.org/L10n:Contribute in this page]. If you're an active localizer and want to know more about NDA, please get in touch directly with [https://wiki.mozilla.org/L10n:Mozilla_Team l10n drivers].<br />
<br />
===== Tech Speakers =====<br />
All active Mozilla Tech Speakers are invited to sign Mozilla’s NDA (Non-Disclosure Agreement). This will give you access to timely information about future product plans, releases, organizational announcements, and confidential Mozilla meetings. You can learn more about the Tech Speakers program [https://wiki.mozilla.org/TechSpeakers/ here].<br />
<br />
===== Security Contributors =====<br />
Non-Staff working as part of the Bugzilla Security Group will be invited to join the NDA group. <br />
<br />
===== Research Contributors =====<br />
Non-Staff contributing to Research organization projects such as Rust, Servo, WebVR/WebAR, Daala, and Deep Speech may contact larsberg.<br />
<br />
===== Add-ons Contributors ===== <br />
There are many ways to [[Add-ons/Contribute|contribute]] to Mozilla's [[Add-ons|add-ons projects]]. If you are an active contributor and want to learn more about NDA, please contact [https://mozillians.org/en-US/u/caitmuenster Caitlin Neiman]. <br />
<br />
===== Mozilla Community Web Services ===== <br />
Active MCWS volunteers will be invited to sign Mozilla’s NDA in order to provision and administer some of the Mozilla-hosted web services open to our communities.<br />
<br />
===== All Hands Contributors =====<br />
Volunteers invited by a staff member to attend an All Hands will be invited to sign an NDA. An NDA will be required to participate in some parts of the All Hands. Invitations will be sent shortly before the event, and volunteers will be removed from the NDA group after the All Hands if they are not also covered by one of the long-term contribution areas (above). <br />
<br />
--<br />
<br />
===== Staff Vouching ===== <br />
In order to receive an NDA, if you are not in any of these groups, you must be invited by a staff member. Staff members can vouch for contributors using [http://goo.gl/forms/RoR5kv9ouJ this form].<br />
<br />
Staff should only NDA people who: "Are actively contributing to Mozilla, who you know or have worked with in the past, whose capacity to contribute would be improved by receiving information or having access to Mozilla tools that are not public, and whose capacity to keep the parameters of the NDA you do not doubt. <br />
<br />
<br />
Please note that contributors must have a Mozillians.org account and multi-factor authentication to be added to the NDA Group. Former staff will require an additional screening by the people partner team before an NDA will be granted. <br />
<br />
Staff: Please note that you will accountable for your invitee and you will have to renew their NDA at the end of one year. In order to accommodate for changes in position or employment you must also list a “back-up” inviter who will assume responsibility for your contributors should you leave the organization.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1221797All Hands/Berlin2020/contributors2020-01-03T14:48:44Z<p>Lucyeoh: </p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
<br />
===Registration:===<br />
This is an invite-only event. Details of the nomination process for contributors are [[All_Hands/Contributor_nominations|here]]. Please note the nomination process for the Berlin 2020 All Hands is now closed. <br />
Once you have booked flights, please register. The link to register is in your email. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Please note that we are unable to accommodate volunteer contributor families/guests at our All Hands. While you can travel with your family all arrangements will need to be made independently and they will not be able to attend any events or meetings associated with the All Hands. As all volunteers have roommates, we can not guarantee the ability for your family to stay with you. You can request a single room in registration but single rooms will not be confirmed until December. <br />
<br />
We are not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
* '''Flights''' - you'll need to book them separately (not through egencia) and you can call the airline once all the bookings are done to request moving your seats together. If your visa is rejected we will not be able to cover flight cancellation costs for your partner. <br />
* '''Exceptions''' may only be made for underage contributors who are required to have a legal guardian present.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Travel expenses policy===<br />
<br />
Reimbursement will only be made for the following expenses.<br />
*Getting to/from home to your airport: We ask that you use the most economical option whether that be mileage/parking, public transportation or ride shares. <br />
*We will reimburse for bag checking fees for one bag. <br />
*If you have a layover longer than 3 hours you can reimburse up to $30USD for food in transit. <br />
*For early arrivals on Monday January 27th or late departures on Saturday February 1st you can expense up to $30USD for lunch. <br />
*We will cover the cost of 1 visa attempt (if there are additional costs related to obtaining your visa please make a request in advance to see whether or not we will reimburse). <br />
<br />
We will not reimburse the following: <br />
*Private town-car services or car rentals.<br />
*Travel insurance. <br />
*Seat/class upgrades.<br />
*Airline change fees or change in fares that result in changes.<br />
*Passport expenses (new passports, renewals, etc.)<br />
<br />
===Reimbursements===<br />
<br />
Reimbursements should be made by opening a Bugzilla request, instructions to follow. <br />
Every All Hands Expenses must be submitted on one (and only one) bug. <br />
All expenses must be filed by March 1st, 2020. <br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1221796All Hands/Berlin2020/contributors2020-01-03T14:44:57Z<p>Lucyeoh: /* Travel expenses policy */</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
<br />
===Registration:===<br />
This is an invite-only event. Details of the nomination process for contributors are [[All_Hands/Contributor_nominations|here]]. Please note the nomination process for the Berlin 2020 All Hands is now closed. <br />
Once you have booked flights, please register. The link to register is in your email. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Please note that we are unable to accommodate volunteer contributor families/guests at our All Hands. While you can travel with your family all arrangements will need to be made independently and they will not be able to attend any events or meetings associated with the All Hands. As all volunteers have roommates, we can not guarantee the ability for your family to stay with you. You can request a single room in registration but single rooms will not be confirmed until December. <br />
<br />
We are not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
* '''Flights''' - you'll need to book them separately (not through egencia) and you can call the airline once all the bookings are done to request moving your seats together. If your visa is rejected we will not be able to cover flight cancellation costs for your partner. <br />
* '''Exceptions''' may only be made for underage contributors who are required to have a legal guardian present.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Travel expenses policy===<br />
<br />
Reimbursement will only be made for the following expenses.<br />
*Getting to/from home to your airport: We ask that you use the most economical option whether that be mileage/parking, public transportation or ride shares. <br />
*We will reimburse for bag checking fees for one bag. <br />
*If you have a layover longer than 3 hours you can reimburse up to $30USD for food in transit. <br />
*For early arrivals on Monday January 27th or late departures on Saturday February 1st you can expense up to $30USD for lunch. <br />
*We will cover the cost of 1 visa attempt (if there are additional costs related to obtaining your visa please make a request in advance to see whether or not we will reimburse). <br />
<br />
We will not reimburse the following: <br />
*Private town-car services or car rentals.<br />
*Travel insurance. <br />
*Seat/class upgrades.<br />
*Airline change fees or change in fares that result in changes.<br />
*Passport expenses (new passports, renewals, etc.)<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Contributor_nominations&diff=1221795All Hands/Contributor nominations2020-01-03T14:10:04Z<p>Lucyeoh: </p>
<hr />
<div>'''<span>Please note the nomination process for the Berlin 2020 All Hands is now closed.</span>'''<br />
<br />
== Introduction ==<br />
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.<br />
<br />
This page outlines the nomination and selection process that will be used for all Mozilla All Hands.<br />
<br />
== Goals ==<br />
The goals of the nomination process are:<br />
<br />
# 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<br />
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands<br />
# Mozilla teams are thinking about contributors strategically<br />
# A process that has legitimacy with contributors and employees<br />
<br />
== Process outline ==<br />
{| class="wikitable"<br />
|-<br />
! Step !! Starts !! Duration<br />
|-<br />
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || 3.5 months in advance || 2 Weeks<br />
|-<br />
| 2) Review and final prioritization || 3 months in advance || 1 week<br />
|-<br />
| 3) HR, Legal and CPG compliance screening || 3 months in advance || 1 week<br />
|-<br />
| 4) Invitations go out & Volunteer registration opens || 2 months in advance || 2 week2<br />
|-<br />
| 5) Registration and flight booking → information about this will be on another page || || <br />
|-<br />
| 6) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || || <br />
|}<br />
<br />
''Important note''<br />
* We are emphasizing greater gender balance for nominated contributors -- based on the past, our hope is to have 30% non-male contributors attending<br />
<br />
== Open Nominations ==<br />
There will be '''no "open nominations" from non-employees'''. Nominations must come directly from employees.<br />
<br />
== Organization Designates ==<br />
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.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Organization !! Name of Org Designate(s)<br />
|-<br />
| Firefox/Product || Mike Hoye (mhoye)<br />
|-<br />
| Emerging Technologies || Nancy Hang (nhang)<br />
|-<br />
| Operations (incl Open Innovation) || Lucy Harris (lharris)<br />
|}<br />
<br />
''Organization Designates will be accountable for:''<br />
* Creating/curating a contributor nomination process for their part of Mozilla<br />
* Communicating within their organization about this process<br />
* Making final prioritization decisions (if needed)<br />
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited<br />
<br />
== Number of Contributors ==<br />
We have space for roughly 60 contributors.<br />
<br />
== Criteria for contributor nominees ==<br />
[[All_Hands/Berlin2020/Contributor_nominee_criteria|Guidance and criteria are here]].<br />
<br />
== Contact ==<br />
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.<br />
<br />
If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Contributor_nominations&diff=1221794All Hands/Contributor nominations2020-01-03T14:09:50Z<p>Lucyeoh: /* Process outline */</p>
<hr />
<div>'''<span>Please note the nomination process for the Berlin 2020 All Hands is now closed.</span>'''<br />
<br />
== Introduction ==<br />
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.<br />
<br />
This page outlines the nomination and selection process that will be used for all Mozilla All Hands.<br />
<br />
== Goals ==<br />
The goals of the nomination process are:<br />
<br />
# 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<br />
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands<br />
# Mozilla teams are thinking about contributors strategically<br />
# A process that has legitimacy with contributors and employees<br />
<br />
== Process outline ==<br />
{| class="wikitable"<br />
|-<br />
! Step !! Starts !! Duration<br />
|-<br />
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || 3.5 months in advance || 2 Weeks<br />
|-<br />
| 2) Review and final prioritization || 3 months in advance || 1 week<br />
|-<br />
| 3) HR, Legal and CPG compliance screening || 3 months in advance || 1 week<br />
|-<br />
| 4) Invitations go out & Volunteer registration opens || 2 months in advance || 2 week2<br />
|-<br />
| 5) Registration and flight booking → information about this will be on another page || || <br />
|-<br />
| 5) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || || <br />
|}<br />
<br />
''Important note''<br />
* We are emphasizing greater gender balance for nominated contributors -- based on the past, our hope is to have 30% non-male contributors attending<br />
<br />
== Open Nominations ==<br />
There will be '''no "open nominations" from non-employees'''. Nominations must come directly from employees.<br />
<br />
== Organization Designates ==<br />
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.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Organization !! Name of Org Designate(s)<br />
|-<br />
| Firefox/Product || Mike Hoye (mhoye)<br />
|-<br />
| Emerging Technologies || Nancy Hang (nhang)<br />
|-<br />
| Operations (incl Open Innovation) || Lucy Harris (lharris)<br />
|}<br />
<br />
''Organization Designates will be accountable for:''<br />
* Creating/curating a contributor nomination process for their part of Mozilla<br />
* Communicating within their organization about this process<br />
* Making final prioritization decisions (if needed)<br />
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited<br />
<br />
== Number of Contributors ==<br />
We have space for roughly 60 contributors.<br />
<br />
== Criteria for contributor nominees ==<br />
[[All_Hands/Berlin2020/Contributor_nominee_criteria|Guidance and criteria are here]].<br />
<br />
== Contact ==<br />
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.<br />
<br />
If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=NDA-Slack/Etiquette-Guide&diff=1220622NDA-Slack/Etiquette-Guide2019-11-25T16:24:43Z<p>Lucyeoh: /* Quick Guide: */</p>
<hr />
<div>= A Basic Guide for New Mozilla Slack Participants. = <br />
<br />
=== Quick Guide: ===<br />
<br />
Mozilla’s Slack is the easiest way to interact and contact people to collaborate on Mozilla projects. As such, it is primarily a professional environment, and while there are social channels, the function of most channels is getting work done. As such we require that everyone in Slack adheres to a high-standard of professionalism and respect in their behavior. '''Any behavior deemed disruptive, unprofessional, or disrespectful will result in your immediate removal and exclusion from Slack.''' Below we will share some guidelines and best practices to help you be successful on Mozilla’s Slack.<br />
<br />
=== Before getting started: ===<br />
<br />
* Review and remember both expected, and unacceptable behaviors listed in [https://www.mozilla.org/about/governance/policies/participation/ Mozilla’s Community Participation Guidelines (CPG)]. If you see anyone violating the CPG, please send a message to inclusion at mozilla.com. <br />
* Remember that all information on Mozilla Slack are classified as "[[NDA|Mozilla Confidential - Staff and NDA'd Mozillians Only]]”. That means all information here is confidential and should absolutely not be shared without prior permission from the project owner.<br />
* If you have any questions or require additional support - please contact slack-onboarding or your Manager or Inviter.<br />
* If you need a Slack admin quickly, you can @slackadmin to hail all the admins. Please use this sparingly because it will notify all admins.<br />
<br />
=== Getting started on Mozilla Slack: ===<br />
<br />
* Tell people who you are - edit your Slack profile, adding your *full name* and *contribution area* (in section _What I do_) also please include the link to your Mozillians profile in the corresponding Slack profile field. <br />
* Read the _Channel Details_ as they might tell you about a channel's purpose and etiquette.<br />
* On high-traffic channels it's a good practice to read along (or “lurk”) for a little before jumping in to get a feeling for channel culture.<br />
* Be mindful when mentioning specific users, @here or @channel in your messages, especially in channels with high numbers of members (like #announcements). <br />
* Using Slack’s threading feature for longer discussions by hovering over the message and clicking Start a thread. The right sidebar in Slack will open, and you can add your reply. <br />
* '''When in doubt ask!''' If you’re not sure what you can or cannot share, have a question, or are not sure where to start, hit us up on #slack-onboarding.<br />
<br />
=== Navigating the Channels: === <br />
<br />
* '''Work or Project focused''' - These channels usually are named after the product they work on and are similar to a quiet office. They are used to talk about work on a specific product or project, you can ask questions, but stay on topic. People are usually busy in these channels and can’t always answer right away - please be especially patient in these channels. E.g. #firefox<br />
* '''Team focused''' - Different teams at Mozilla have different channels for their team to communicate work stuff. If you have a question for a specific team this is a good way to reach them but remember people are busy and in different time zones so you may have to wait a bit and it’s often helpful to have a specific person in mind. E.g. #openinnovation <br />
* '''Closed or Private Channels''' - You may be invited to join a private or closed channel, here’s it’s easy to ask the person who invited you what the goals of the channel are and how you can contribute effectively. Make sure you know what can be shared inside and out of that channel before you share. <br />
* '''#ServiceDesk''' - This channel is for Mozilla employees to access internal IT support. While it's a public channel, due to time and resource constraints, requests for technical support by volunteers cannot be made through this channel. If you need technical support reach out to your community manager and/or the staff voucher who invited you to the NDA/Slack group. <br />
* '''#Announcements''' - The name says it all! Avoid posting to #announcements unless the message is really an announcement that is relevant to all Participants. Please only post announcements there and please comment to those in threads to minimize the impact to the 1000+ people who cannot leave that channel.<br />
* '''Social channels''' - These channels are like a watering hole for people to share random, funny, or interesting things. This is a great place to share something you’re excited about, a funny meme, or a new project you’ve been working. #random, #community-talk #Canada<br />
<br />
=== Joining a new channel: === <br />
'''Be respectful'''<br />
* Be mindful when using @channel or @here, not everyone is awake or online in that channel. <br />
* When contacting an individual, remember that having a Slack status as “available” doesn't necessarily mean that they have the ability to respond to you right away. If you’re not sure how to get a question answered it is ok to ask if that person knows who or what channel you can ask that question. <br />
* Please be civil, remember the Community Participation Guidelines and keep the mutual respect and safety of the channel you are participating in. Make sure you can calmly and logically communicate before hitting send. <br />
* Past decisions about product changes are not up for debate. <br />
'''Be professional'''<br />
* If a person does not respond right away, give it 15 mins then move on. Try another channel. Try an email, or try an advocate for some advice on what to try next. It is ok to ask if that person knows who or what channel you can ask that question. <br />
'''Do not be disruptive'''<br />
'''Please do not spam the channel'''<br />
* Slack is a little different from irc, Ping, pong is not required, just a mention and a question ;-)<br />
* Do not bump a message or repeat a message if you have already sent a mention to the whole channel<br />
* If it is getting too complicated for a public channel take it to a private message by using Slack’s threading feature or using direct messages.<br />
<br />
=== Additional Slack Info === <br />
* Message retention is set to 180 days. This does mean that messages are moderately ephemeral. Slack is not a filing system so if something happens there that you need for posterity, it is up to you to capture it.<br />
* Authentication sessions are set to 30 days. This means that you should only need to re-authenticate to Slack every 30 days.<br />
* In an effort to minimize confusion and help people find what they are looking for, empty and dead channels will be archived. * If there is no real content, they will be culled.<br />
* A dead channel is one that has not seen activity in a specific time (to be determined but likely a month).<br />
* As such, if you have a channel that is only relevant every-so-often, please state that in the channel description and we can keep it around.<br />
* If you only need a channel once a year for a week, please consider archiving it at the end of its validity period.<br />
* Since content only exists for 6 months, a "temporary" channel doesn't make sense to keep around until the next year.<br />
Archived channels are searchable but do not accept new messages.<br />
<br />
== A Helpful Analogy: == <br />
<br />
So this is your first time on the Mozilla Slack? Let me tell you a story before you enter for the first time. Can you close your eyes for a sec? Bear with me. Ok, now imagine when you log into Slack that you are walking into an office building where people are quietly working in each of their cubicles. Each of them have different emojis on their head phones and they each have their own typing pace. Some are in meetings with people in Europe and others are in a meeting room drawing on a dry erase board. <br />
<br />
You walk in to the office and you are trying to find out where you can post your bug in Firefox or where to get the attention of a developer to help fix your issue. Before you do that, there are a couple of things you may want to keep in mind. First, find the right channel and the right person.<br />
<br />
You do a quick search and you ask, what is that channel used for? <br />
<br />
* Once in the room, please first take the temperature of the room, <br />
* Do some scroll back and read a bit about what is being discussed in the channel. <br />
* What is the channel description?<br />
* What time zones are the people in that channel in? <br />
* What are a majority of the last 20 messages about, is it similar to what you want to contribute to that channel or conversation? <br />
* How am I doing? Am I capable of adding productively to this discussion? <br />
<br />
Open your eyes now. If you can answer all of those questions and you answered yes to the last one, proceed to post your questions. Please keep in mind, since it is your first time, this might feel a bit like a cold call. Don’t worry, that feeling will go away. <br />
<br />
Onwards you go to login to Slack, just remember to keep it clean, respectful and professional!</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/CommunityDevelopment&diff=1220612Innovation/CommunityDevelopment2019-11-25T16:01:26Z<p>Lucyeoh: </p>
<hr />
<div>Mozilla's '''Community Development Team''' works to build, grow and engage Mozilla's global, diverse, volunteer communities. <br />
<br />
We do that in the following ways: <br />
<br />
* Providing '''community facing-staff at Mozilla with support and resources''' they need to be effective in managing their communities i.e. [https://mana.mozilla.org/wiki/display/OIT/Community+Development+Resources Community Management Breakfasts], [[Diversity and Inclusion Resourceshttps://wiki.mozilla.org/Diversity_and_Inclusion_for_Communities_and_Contributors#Overview|diversity and inclusion resources]], [https://discourse.mozilla.org/t/2019-mozilla-communities-contributors-survey-and-state-of-the-rebel-alliance-report/37430 State of the Rebel Alliance Reports].<br />
* Creating and maintaining '''centralized services, tools and policies''' that enable contributors and staff to collaborate effectively i.e. [[Diversity_and_Inclusion_for_Communities_and_Contributors|Code of Conduct enforcement]], [[wiki.mozilla.org/NDA|NDA]] & [[NDA-Slack|Slack Access]], [https://discourse.mozilla.org/ Discourse], [https://activate.mozilla.community/newsletter community mailing lists]. <br />
* '''Running community programs''' such as: [[Reps]], [https://ossn.club/ OSSN] (the open source student network), [https://activate.mozilla.community/ Activate], [https://activate.mozilla.community/en-US/campaigns Community Campaigns (including Alpha/Beta Testing programs)]. <br />
<br />
We are also consult on community strategy and are [[Innovation/Projects/Mission-Driven_Mozillians_Strategy|always working]] to build a better modern unified contributor experience for Mozillians.<br />
<br />
If you need to get in touch you can email us at community(dash)development(at)mozilla(dotcom).</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Contribute&diff=1220565Contribute2019-11-22T16:32:56Z<p>Lucyeoh: </p>
<hr />
<div>Thanks for your interest in contributing to Mozilla! The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community. As such, we require all those who participate to agree to adhere to the [http://Community%20Participation%20Guidelineshttps://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] in order to help us create a safe and positive community experience for all. <br />
<br />
== Quick Start: == <br />
<br />
'''To make a technical contribution''':<br />
<br />
* Contribute to the Mozilla code base -> [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction Introduction] <br />
* Find your first code contribution -> [http://codetribute.mozilla.org codetribute.mozilla.org]<br />
* Contribute documentation to the Mozilla Developer Network -> [https://developer.mozilla.org/en-US/ developer.mozilla.org]<br />
* Contribute your design to an open design community -> [https://github.com/mozilla/OpenDesign/ github.com/mozilla/OpenDesign/]<br />
<br />
'''To make a non-technical contribution''':<br />
* Localize Mozilla into your language -> [https://pontoon.mozilla.org/ pontoon.mozilla.org] <br />
* Help support users from the comfort of your couch by answering questions and/or writing and translating support articles -> [https://support.mozilla.org/en-US/get-involved support.mozilla.org]<br />
* Support Mozilla's mission - find impactful, fun ways to get involved right away on Activate Mozilla -> [https://activate.mozilla.community/ activate.mozilla.community]<br />
<br />
== Specialist Programs & Funding Programs: == <br />
''As a critical part of the mission, Mozilla invests in innovators and projects working to make the internet more open, inclusive, decentralized, and secure. These programs each have their own set of requirements and application process, please read carefully.''<br />
<br />
Available by application: <br />
* [https://events.mozilla.org/techspeakers/ Tech Speakers] - For volunteer technical advocates and educators who are interested in informing others about the open web and Mozilla products and technologies.<br />
* [https://reps.mozilla.org/ Reps program] - For contributors who are already regularly organizing community events and mobilizing in their communities.<br />
* [https://foundation.mozilla.org/fellowships/ Fellowships] - For web activists, open-source researchers and scientists, and technology policy experts who work on the front lines of the internet health movement.<br />
* [https://research.mozilla.org/ Research Grants & Sponsorships] - For universities, labs and research-focused registered non-profits working to make the internet a better place.<br />
* [https://foundation.mozilla.org/en/awards/ Mozilla Awards] - For open source projects that contribute to Mozilla’s work and to the health of the Internet.<br />
* [https://www.mozilla.org/en-US/moss/ Mozilla's Open Source Support Awards]- provide catalytic funding to open source technologists. <br />
* [https://careers.mozilla.org/university/ Student Internships] - For university/college students looking to intern with Mozilla. <br />
* [https://wiki.mozilla.org/Outreachy Outreachy] - For members of under-represented groups who want to intern in free and open source software. <br />
* [https://wiki.mozilla.org/SummerOfCode Summer of Code] - For student developers who want to work with an open source organization on a 3 month programming project during their break from school.<br />
* [http://ossn.club/ Open Source Student Network] - A Network of university and college Clubs and students who are passionate about Open Source and eager to learn about, contribute to and create Open Source projects.<br />
* [https://wiki.mozilla.org/Engagement/Developer_Engagement/Event_request_guidelines Developer Engagement Events] - for people seeking speakers or sponsorship for developer-oriented events. <br />
<br />
<br />
Still can’t find what you’re looking for? Check out the conversations on [https://discourse.mozilla.org/ the Mozilla Discourse].<br />
<br />
<br />
''Looking for content from the old page? You can find it in the archive [[Contributearchive|HERE]].''</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=NDA&diff=1220533NDA2019-11-21T17:52:37Z<p>Lucyeoh: /* What is a Confidentiality Agreement: */</p>
<hr />
<div>== <big>Confidentiality Agreement FAQ</big> == <br />
<br />
==== What is a Confidentiality Agreement: ====<br />
<br />
A Confidentiality Agreement (or NDA) is a legal agreement between volunteers and Mozilla that will allow us to share confidential information with contributors that we don’t, or aren’t yet ready to share with the general public. For example, NDA’d Mozillians have access to the videos on Air Mozilla, which are closed to the public because they contain confidential information. <br />
<br />
In order for the NDA group to grow and succeed it requires everyone who enters it to make a commitment to share the trust conferred by admission into this group. <br />
<br />
'''You can view the full text of the NDA [https://drive.google.com/file/d/0B-IbEs3PKNPKVzlqWGQ0bWRkcTQ/view?usp=sharing here].'''<br />
<br />
Contributors can also request that information shared with you under the NDA be made public through this form [http://mzl.la/reclassify mzl.la/reclassify].<br />
<br />
NOTE: This NDA process is exclusively for volunteer Mozillians. To NDA a contractor, vendor, intern, or anyone else Mozilla has a business relationship with, please file [http://sso.mozilla.com/casa a casa ticket].<br />
<br />
==== What are your obligations under the NDA ====<br />
<br />
* You will only use Confidential Information to perform your Activities on behalf of Mozilla.<br />
* You will not publicly disclose or share the Confidential Information with any other<br />
* persons, except with other Mozilla employees or other volunteers under an NDA with Mozilla as<br />
* noted below.<br />
You will:<br />
* a) only share the Confidential Information if the person disclosing the information tells you<br />
* that it can be shared,<br />
* b) only share the Confidential Information with the specific group or individuals Mozilla<br />
* authorizes you to share with; and<br />
* c) use appropriate judgment and access restrictions to prevent unauthorized disclosure.<br />
<br />
By signing an NDA, in addition to agreeing to comply with the terms of the NDA (above) you are agreeing to respect and adhere to [https://www.mozilla.org/en-US/about/governance/policies/participation/ Mozilla’s Community Participation Guidelines] (“CPG”). Violation of these guidelines can result in you being removed from the NDA group, either temporarily or in perpetuity.<br />
<br />
==== What do I need to get an NDA? ====<br />
<br />
In addition to a staff member who can vouch for your contributions and ability to maintain the parameters of the NDA (the details of which are blow) you will need to have the following: <br />
<br />
* A [https://mozillians.org/en-US/ Mozillians.org profile] <br />
* Setup [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|multifactor authentication]] on their profile<br />
<br />
==== How long does an NDA last: ====<br />
<br />
NDA’s expire after one year, in order to make sure that those on the list are regularly active. One year from the acceptance date, inviters will have the opportunity to re-invite volunteers to the NDA group. <br />
<br />
==== What happens once I get my invitation: ==== <br />
Your invitation will arrive to the email associated with your Mozillians profile. Once you receive your invitation, please read and think carefully about the NDA before you agree to its terms and if you have any questions please do not hesitate to reach out to your inviter!<br />
<br />
'''Note that you will need to have [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|Multi-Factor Authentication]] set-up on your Mozillians profile in order to receive your NDA invitation. Instructions for how to set it up can be found [[IAM/Frequently_asked_questions#Q:_How_can_I_set_up_two-factor_authentication_.282FA.29_for_my_github_account.2C_using_an_app_on_my_phone_.28Android.2FiOS.2FBlackberry.29.3F|Multi-Factor Authentication|here]].''' <br />
<br />
Once you have received and accepted the terms of the NDA you will: <br />
* Automatically be added to the NDA Group on Mozillians<br />
* You will have access to the [https://discourse.mozilla-community.org/c/mozillians/nda NDA-restricted discourse category], a safe space for internal conversations (staff and nda volunteers).<br />
* You will also automatically have access to view NDA-restricted [https://air.mozilla.org/ Air Mozilla] and you will be able to access the #moco channel on IRC from the Air Mozilla page.<br />
* You will receive internal confidential emails with updates pertaining to Mozilla.<br />
* You may also have additional confidential information shared with you personally, so please be aware or check with the disclosure before you re-share any information.<br />
* You may also be given access to the Mozilla Slack instance, please discuss this with your inviter if this is something you think would meaningfully improve your ability to contribute effectively.<br />
<br />
==== Leaving the NDA group: ==== <br />
If you would like to stop receiving confidential information at any time, or can no longer contribute your time as a volunteer, before the end of your one year period you can ask your inviter to remove you from the group or email legal-notices@mozilla.com to end your NDA. Inviters can also remove contributors from the NDA group at any time if that contributor is no longer actively contributing to Mozilla, or if there is a violation of trust or the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines].<br />
<br />
== Who Can Get an NDA == <br />
<br />
They are distributed by invitation to volunteer individuals who are deeply involved with Mozilla and are trusted by the administrators of a Mozilla Community. Reps, L10N, Security and SUMO each have their own procedure for assessing activity and distributing NDA’s (vendors, contractors, and anyone else Mozilla has a business relationship with should file a [https://sso.mozilla.com/casa a CASA ticket] instead). Staff can also nominate contributors to receive an NDA if they believe that a contributor who is actively contributing to Mozilla, they know or have worked with, whose capacity to contribute would be improved by receiving information or having access to Mozilla tools that are not public, and whose capacity to keep the parameters of the NDA are not in doubt.<br />
<br />
Here is the information for each of these groups. <br />
<br />
===== Reps =====<br />
All active Reps are under NDA and receive invitations as part of entry into the program. [https://mozillians.org/en-US/u/nukeador/ Reps Staff] access activity each year for the purposes of renewal. You can read more about how to become a Rep [https://reps.mozilla.org/ here].<br />
<br />
===== SUMO =====<br />
[https://support.mozilla.org/en-US/kb/meet-team/ SUMO admins] determine activity and send invitations to active SUMO members. You can [https://support.mozilla.org/en-US/get-involved read more about how to become a member of SUMO here]. The Mozilla Support Community requires an NDA for product updates and support related communications and participation in the Social Support program that answers brand questions. Check out how to get involved at https://support.mozilla.com and Support. If you have participated for a while or would benefit from a more involved please send a request for an NDA with this form: bit.ly/2Ihl1Rh <br />
<br />
===== L10N =====<br />
You can read more about how to get involved with localization (L10N) [https://wiki.mozilla.org/L10n:Contribute in this page]. If you're an active localizer and want to know more about NDA, please get in touch directly with [https://wiki.mozilla.org/L10n:Mozilla_Team l10n drivers].<br />
<br />
===== Tech Speakers =====<br />
All active Mozilla Tech Speakers are invited to sign Mozilla’s NDA (Non-Disclosure Agreement). This will give you access to timely information about future product plans, releases, organizational announcements, and confidential Mozilla meetings. You can learn more about the Tech Speakers program [https://wiki.mozilla.org/TechSpeakers/ here].<br />
<br />
===== Security Contributors =====<br />
Non-Staff working as part of the Bugzilla Security Group will be invited to join the NDA group. <br />
<br />
===== Research Contributors =====<br />
Non-Staff contributing to Research organization projects such as Rust, Servo, WebVR/WebAR, Daala, and Deep Speech may contact larsberg.<br />
<br />
===== Add-ons Contributors ===== <br />
There are many ways to [[Add-ons/Contribute|contribute]] to Mozilla's [[Add-ons|add-ons projects]]. If you are an active contributor and want to learn more about NDA, please contact [https://mozillians.org/en-US/u/caitmuenster Caitlin Neiman]. <br />
<br />
===== Mozilla Community Web Services ===== <br />
Active MCWS volunteers will be invited to sign Mozilla’s NDA in order to provision and administer some of the Mozilla-hosted web services open to our communities.<br />
<br />
===== All Hands Contributors =====<br />
Volunteers invited by a staff member to attend an All Hands will be invited to sign an NDA. An NDA will be required to participate in some parts of the All Hands. Invitations will be sent shortly before the event, and volunteers will be removed from the NDA group after the All Hands if they are not also covered by one of the long-term contribution areas (above). <br />
<br />
--<br />
<br />
===== Staff Vouching ===== <br />
In order to receive an NDA, if you are not in any of these groups, you must be invited by a staff member. Staff members can vouch for contributors using [http://goo.gl/forms/RoR5kv9ouJ this form].<br />
<br />
Staff should only NDA people who: "Are actively contributing to Mozilla, who you know or have worked with in the past, whose capacity to contribute would be improved by receiving information or having access to Mozilla tools that are not public, and whose capacity to keep the parameters of the NDA you do not doubt. <br />
<br />
<br />
Please note that contributors must have a Mozillians.org account and multi-factor authentication to be added to the NDA Group. Former staff will require an additional screening by the people partner team before an NDA will be granted. <br />
<br />
Staff: Please note that you will accountable for your invitee and you will have to renew their NDA at the end of one year. In order to accommodate for changes in position or employment you must also list a “back-up” inviter who will assume responsibility for your contributors should you leave the organization.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Community_Portal&diff=1220528Innovation/Projects/Community Portal2019-11-21T14:54:59Z<p>Lucyeoh: </p>
<hr />
<div><br />
== What is the Community Portal ==<br />
'''The Mozillian Community Portal''' is an initiative led by the Community Development Team in Open Innovation. It is part of the [[Innovation/Projects/Mission-Driven_Mozillians_Strategy|Mission Driven Mozillians project]] the goal of which is to work with teams and communities to create modern structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
[[File:Communityportal2.jpg|500px|right]]<br />
<br />
== Goal ==<br />
<br />
The goal of the community portal is to create a central place for Mozillians to be able to find, discover opportunities and collaborate across community members & groups.<br />
<br />
The portal will be a place for people to host and discover: <br />
* events<br />
* groups<br />
* contribution opportunities<br />
* individual profiles<br />
<br />
View the full designs [https://www.figma.com/proto/7P5C9UtORoEfdi4SZjAMz5/Mozilla-v2.0?node-id=1253%3A101655&viewport=965%2C800%2C0.5&scaling=min-zoom here]. <br />
<br />
[[File:Screen Shot 2019-11-21 at 9.51.20 AM.png|600px|center]]<br />
<br />
<br />
[[File:Wireframe Events Page.png|500px|right]]<br />
<br />
<br />
Development will be through an open process starting in August 2019, with an estimated V1 release date in early 2020. <br />
<br />
'''We publish weekly updates on the development of the portal on [https://discourse.mozilla.org/c/community-portal discourse].'''<br />
<br />
'''Find the [https://discourse.mozilla.org/t/frequently-asked-questions-portal-edition-faq/43224/4 FAQ] here.'''<br />
<br />
Please contact Lucy for more information about the new portal.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Community_Portal&diff=1220527Innovation/Projects/Community Portal2019-11-21T14:54:27Z<p>Lucyeoh: /* Goal */</p>
<hr />
<div><br />
== What is the Community Portal ==<br />
'''The Mozillian Community Portal''' is an initiative led by the Community Development Team in Open Innovation. It is part of the [[Innovation/Projects/Mission-Driven_Mozillians_Strategy|Mission Driven Mozillians project]] the goal of which is to work with teams and communities to create modern structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
[[File:Communityportal2.jpg|500px|right]]<br />
<br />
== Goal ==<br />
<br />
The goal of the community portal is to create a central place for Mozillians to be able to find, discover opportunities and collaborate across community members & groups.<br />
<br />
The portal will be a place for people to host and discover: <br />
* events<br />
* groups<br />
* contribution opportunities<br />
* individual profiles<br />
<br />
View the full designs [https://www.figma.com/proto/7P5C9UtORoEfdi4SZjAMz5/Mozilla-v2.0?node-id=1253%3A101655&viewport=965%2C800%2C0.5&scaling=min-zoom here]. <br />
<br />
[[File:Screen Shot 2019-11-21 at 9.51.20 AM.png|600px|center]]<br />
<br />
<br />
[[File:Wireframe Events Page.png|500px|right]]<br />
<br />
<br />
Development will be through an open process starting in August 2019, with an estimated V1 release date in early 2020. <br />
<br />
'''We publish weekly updates on the development of the portal on [https://discourse.mozilla.org/c/community-portal discourse].'''<br />
<br />
'''Find the [https://discourse.mozilla.org/t/frequently-asked-questions-portal-edition-faq/43224/4 FAQ] here.'''</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=File:Screen_Shot_2019-11-21_at_9.51.20_AM.png&diff=1220526File:Screen Shot 2019-11-21 at 9.51.20 AM.png2019-11-21T14:52:39Z<p>Lucyeoh: </p>
<hr />
<div>Homepage of the community portal.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020&diff=1219968All Hands/Berlin20202019-11-07T21:03:15Z<p>Lucyeoh: /* Volunteer Contributors */</p>
<hr />
<div>'''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! <br />
<br />
'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor please inquire with your community manager/program manager about [[All_Hands/Contributor_nominations|contributor nominations]], interns please inquire to your coordinator. Volunteer contributors who have recieved an invitation can find relevant information [[All_Hands/Berlin2020/contributors|here]]. '''''<br />
<br />
=='''Dates and Location'''==<br />
Monday, January 27, 2020 - Friday, January 31, 2020 (travel days are Monday, Jan 27 & Saturday, Feb 1) in Berlin, Germany.<br />
<br />
We have guestrooms at three hotels: [https://www.ihg.com/intercontinental/hotels/us/en/berlin/berha/hoteldetail InterContinental Berlin], [https://www.pullman-berlin-schweizerhof.com/en/ Hotel Pullman Schweizerhof], and [https://www.hotel-berlin.de/en/ Hotel Berlin, Berlin]. [https://drive.google.com/open?id=1eu_rYMxuc_hgSNqCJxW7Vn32pYMNayPa&usp=sharing View on map].<br />
<br />
''*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.''<br />
<br />
=='''Registration'''==<br />
This is an invite-only event. All full time and Elance/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 and upon executive review and approval. <br />
<br />
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. This includes facilitators, and other related business guests. <br />
<br />
=====New Hires=====<br />
We have a process to identify qualified regular full time new hires and Brianna will invite all new hires to register and book travel directly on their start date. No action is necessary from hiring managers other than to let them know about the event (please do not forward any links). Please work closely with your recruiting manager as they are aware of all deadlines.<br />
<br />
All regular full time new hires must have a start date of January 6, 2020 or earlier and in workday by December 13, 2019. Final invites will be extended on December 16, 2019. Contractors/vendors will require executive approval and those who are hired after the approval will not be invited. If you have any questions, please email bmark@mozilla.com.<br />
<br />
=====Volunteer Contributors=====<br />
There are a number of policies that apply specifically to contributors that are different than for staff. Please look [[All_Hands/Berlin2020/contributors|here]] for all contributor specific instructions and policies.<br />
<br />
'''Local contributors:'''<br />
<br />
Please note that because of the extensive nomination and screening process we apply to all contributors who attend the event - we are unable to invite local contributors or temporary participants to the event outside of the regular nomination and screening process.<br />
<br />
=====Registration Changes=====<br />
Everyone who registered received a confirmation email titled "Registration Confirmation to Mozilla Berlin All Hands" which shows you how you answered each question. If you didn't get the email and/or need to make changes to your registration, please email mozilla@shworldwide.com.<br />
<br />
=='''Immigration'''==<br />
If you have any questions about immigration, please email immigration@mozilla.com. <br />
<br />
==== STEP ====<br />
'''What is STEP?''' <br />
The [https://step.state.gov/ Smart Traveler Enrollment Program (STEP)] is a free service to allow U.S. citizens and nationals traveling abroad to enroll their trip with the nearest U.S. Embassy or Consulate. <br />
Benefits of Enrolling in STEP <br />
* Receive important information from the Embassy about safety conditions in your destination country, helping you make informed decisions about your travel plans.<br />
* Help the U.S. Embassy contact you in an emergency, whether natural disaster, civil unrest, or family emergency.<br />
* Help family and friends get in touch with you in an emergency.<br />
<br />
==== Visas ====<br />
You do not need a visa if you hold a passport issued from the EU, USA, Australia, New Zealand, Taiwan, or Canada. <br />
Please see here to confirm the entry document requirements for the country you’re from: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node/staatenlistevisumpflicht-node <br />
<br />
If you are from a country that requires a visa to enter Germany, please plan to obtain one as early as possible as government processing times constantly change. You can find a broad overview of the process here: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node . For more detailed instructions regarding the visa process you will need to refer to the website of your nearest Mission/Consulate General. You will be able to learn more about the process by searching for “business visa” or “visitor visa” on the website for that German Mission.<br />
<br />
'''Please keep in mind that while you are traveling for work, you are not traveling for a German based job.''' All Hands is a business conference/event. As you book your travel please also keep in mind that you could require a transit visa if you have a layover in a country that requires it. <br />
<br />
If you have questions specific to your circumstances, please email immigration@mozilla.com. <br />
<br />
==== Entering Germany ====<br />
Your passport or identity card will be checked when you arrive at an EU port or airport to make sure you’re allowed to come into the country. The passport must be valid for the whole of your stay. You may also need a visa to come into or travel through Germany, depending on your nationality. <br />
* If you are from an EEA country or Switzerland, you can enter Germany with either a valid passport or a national identity card issued by a EEA country. <br />
* If you need a United States Passport, start here: https://travel.state.gov/content/passports/en/passports.html. Please note it can take 4-6 weeks to receive your passport. Please plan ahead. <br />
<br />
==== EU Visa Waiver Program Suspension - Update ====<br />
In March 2019 the EU announced that the visa free entry requirements for third country visitors to Europe would be changing. This change will not go into affect until 1 January 2021, note this is one year after our Berlin All Hands trip. After this date, citizens from certain countries, including the USA and Canada, will be required to obtain an ETIAS travel authorization before they can enter Europe.<br />
<br />
==== More details: ==== <br />
Mission websites in popular Mozillian locations:<br />
* United States: https://www.germany.info/us-en/service/05-VisaEinreise/business-visa/963542<br />
* Canada: https://canada.diplo.de/ca-en/consular-services/visa/shortstay<br />
* UK: https://uk.diplo.de/uk-en/02/visa<br />
* Paris: https://allemagneenfrance.diplo.de/fr-de/service/00-visa-seite<br />
* Taiwan: https://taipei.diplo.de/tw-en/service/visa<br />
* Beijing: https://china.diplo.de/cn-zh/service/visa-einreise/schengenvisum/1343246<br />
* India: https://india.diplo.de/in-en/service/-/1908794<br />
<br />
=='''Travel to Berlin'''==<br />
Bookings to Berlin have begun. The Egencia instructions have be emailed to '''anyone approved to attend'''. New hires will have individual deadlines based upon hire/start date. Approved contractors, vendors, seasonal, status employees will be notified with an email from bmark@mozilla.com with specific instructions. <br />
<br />
Specific instructions were emailed to you about how to book, as we have a new process for anyone based outside the US, Canada & Central/South America. APAC employees will '''NOT''' be booking your All Hands travel in country based site, and will be using Egencia Americas. European employees '''WILL''' be booking in your country based site to allow access to trains and low cost airlines. <br />
<br />
Should you need to reach someone at '''Egencia Americas''' for special circumstances or changes that can't be done online:<br />
*Call+1 (800) 361-1120 or +1(702)939-2533; Hours of operations are Monday – Friday (except holidays) 5:00 AM– 6:00 PM PT or 8:00 AM – 9:00 PM ET or 12:00 PM - 1:00 AM UTC. If you call outside these hours, you will get an after-hours agent (not a meeting agent, who may not be as helpful) . Please ensure the agent you speak with knows you are booking for a meeting.<br />
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday.<br />
<br />
Other Egencia contact details:<br />
*Egencia UK+EMEA - Email: customer_service@egencia.co.uk; UK Local #: +44 203 077 2536 (charged at local rate). For calls made outside the UK, please dial +00 44 161 233 5525. (From anywhere outside the EU, please dial +011 44...)<br />
*Egencia FR - Email: service_client@egencia.fr; France Local #: +33 8 11 65 66 53. For calls made outside France, please dial +33 4 86 06 15 18 (From anywhere outside the EU, please dial +011 33)<br />
<br />
'''Important Details:'''<br />
Everyone should plan to arrive in Berlin Tegel Airport (TXL) on Monday, January 27 and leave on Saturday, February 1. 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 Berlin Tegel (anything custom). A few notes:<br />
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, those approved will be sent separate email.<br />
*Volunteers will be handled separate from this process.<br />
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.<br />
*If you would like to invite someone who is a business partner, facilitator or some other category that isn't an employee or volunteer (not a personal guest/family), email bmark@mozilla.com.<br />
*Change fees will be covered by Mozilla for business reasons only. Please email bmark@mozilla.com ahead of calling Egencia to make the change. Any changes for personal reasons must be paid by the employee directly to Egencia over the phone. <br />
<br />
====Arriving Early/Departing Late Guidelines====<br />
<br />
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, January 27 and leave on Saturday, February 1. Here are some exceptions: <br />
<br />
# If you plan to spend some extra '''personal time in Berlin/Europe''' or nearby (choosing to arrive before Monday, Jan 27 or depart after Saturday, Feb 1), you'll need to create a itinerary in Egencia for standard dates/locations within the Egencia Portal and compare to the custom dates/locations you'd like. Pricing for the standard dates should be ''Round Trip only''. Pricing for custom dates/locations should be for ''Round trip or Multi city trips only''. Please share the difference via email to bmark@mozilla.com and receive approval ahead of submission in Egencia. 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 TXL w/ longer dates, and you personally book & cover the rest). Please note that one way trips are only approved on a case by case basis. Do not book one ways without prior approval. ''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 Berlin Tegel than your home airport (ex. a layover in London for a few days, or flying out of something other than TXL). <br />
# If you are attending the '''Sunday/Monday CI event''' (by invite), you can arrive on Sunday, January 26.<br />
# 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.<br />
# If you are celebrating the '''Lunar New Year''', [https://wiki.mozilla.org/All_Hands/Berlin2020#Lunar_New_Year see here].<br />
# If you live in a country where '''work travel is prohibited on weekends''', you may travel on Friday, Jan 24 and Monday, Feb 3, 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). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively. <br />
# If you live in a country where '''work travel is prohibited on Sunday''', you may travel on Saturday, Jam 24, 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). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively.<br />
<br />
====Booking Family Travel====<br />
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.<br />
<br />
'''Direct (recommended):''' <br />
<br />
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.<br />
<br />
'''Via Egencia:'''<br />
<br />
We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com<br />
<br />
'''Notes:''' <br />
<br />
* If your family is arriving on a different flights than you but would like to take advantage of the airport shuttles on Sunday/Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.<br />
* We are unable to accommodate volunteer contributor families/guests.<br />
<br />
====Not Flying====<br />
Mozilla will reimburse U-Bahn tickets for those based in the Berlin area for getting to/from hotels. For more information on the U-Bahn, please see the Berlin office guide on [https://mana.mozilla.org/wiki/display/WPR/Berlin+Office+Guide#BerlinOfficeGuide-MovingAroundBerlin mana]. <br />
<br />
For those outside of the Berlin area who are taking the train, please book by November 10. Instructions were emailed to everyone. <br />
<br />
Parking is not reimbursable.<br />
<br />
====Travel Insurance====<br />
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. <br />
<br />
Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members (unless required for visa application).<br />
<br />
====Air Travel Fine Print====<br />
*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-877-255-1090 (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.<br />
*Mozilla will '''not''' reimburse for Business/First class upgrades, tickets or seat reservations. <br />
*Mozilla will reimburse for one checked bag each way.<br />
*''Mozilla Frequent Flyer perks do not apply for All Hands''. <br />
*Flights booked outside of Egencia will not be an approved expense unless email approval by Brianna is obtained prior to booking.<br />
*Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.<br />
<br />
====Ground Transportation====<br />
Berlin Tegel airport is open from 4:00 - 0:00. <br />
Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels:<br />
*Sunday, Jan 26 from 9:00 - 22:00, for flights landing between 7:45 and 21:45.<br />
*Monday, Jan 27 from 8:00 - 23:00, for flights landing between 7:15 and 22:55.<br />
<br />
Shuttles from our 3 hotels to Berlin Tegel will be provided:<br />
*Saturday, Feb 1 from 4:00 - 20:00, for flights departing 7:15 and 22:15.<br />
*Sunday, Feb 2 from 4:00 - 12:00, for flights departing 6:00 - 14:00. ''If you are on a later flight, you can take the last shuttle at 12:00.'' <br />
<br />
Taxis and Addison Lee are not reimbursable. <br />
<br />
If you are arriving by train to Hauptbahnhof:<br />
To Hotel Berlin Berlin<br />
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S5, S9 or S75 to the station “Zoologischer Garten” (20 min.). From there, take the bus 100 to the stop Lützowplatz. <br />
* Via U-BAHN: Take the U-Bahn metro lines U2, U3 and U1 to the station “U-Nollendorfplatz”. Exit the station in the direction of “Karl-Heinrich-Ulrichs-Straße." The road leads directly to the hotel (approx 5 mins). <br />
* [https://www.hotel-berlin.de/d/berlinberlinpro/media/PDF/Anfahrt_A4_E_Karl-Heinrich-Ulrichs-Strae_5c2ab7.pdf Map]<br />
<br />
To InterCon Berlin and Pullman<br />
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S3, S5, S7, or S9 to the station “Zoologischer Garten”. From there, walk 10 mins to hotel.<br />
<br />
Berlin's integrated public transport is divided in 3 tariff zones (ABC). To travel within the city, including from Tegel airport to the hotels, you only need an AB ticket. Tickets can be bought at automated booths in most stations (accept credit cards), and on Metro (need coins). You can use the same ticket to travel on buses, metro, S-Bahn, U-Bahn. More information, including PDF maps, are available on [https://www.berlin.de/en/public-transportation/1772016-2913840-tickets-fares-and-route-maps.en.html this website]. A mobile app is available on stores ("BVG FahrInfo Plus") and allows to create routes between stations, or you can use directly the [https://www.bvg.de/en BVG] website.<br />
<br />
=='''Families/Guests'''==<br />
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. We are unable to accommodate volunteer contributor or intern families/guests at our All Hands. <br />
<br />
====Quick summary logistics====<br />
* Air Travel: Employees do need to book via Egencia regardless of how families are booked. <br />
* Hotel: Family/friends are welcome to stay with you. All room rates are based upon single occupancy and include breakfast. Guests must be added to reservations in advance and any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. Higher occupancy rooms will be assigned in the order that you register. We will have extra rooms available for families to book and pay for at our hotels. <br />
* Lunch & Dinner: Family will be on their own for lunch daily and dinner on Tuesday, Wednesday & Thursday. <br />
* Monday & Friday Night Events: Family members who are registered for the event and registered with the hotel, are invited to join us for our evening events.<br />
* Childcare Services: We will not provide centralized childcare services. We have found that every family has different needs and centralized childcare does not deliver on those needs. If you are in need of help finding options for your family, we are happy to connect you with staff whose families who are coming (#allhands-childcare and #parents are great places to start), as well we are happy to help support finding of resources (although you are likely better at it than us). Given every circumstance is unique, we defer to your manager to determine what Mozilla can support you with financially.<br />
<br />
On demand babysitting services in Berlin: <br />
* https://extra-arms.com/for-families-babysitting/<br />
* https://www.withourbaby.com/<br />
<br />
=='''Lunar New Year'''==<br />
We are aware of the overlap in the Lunar New Year celebrations with the Berlin All Hands. To help folks who decide to attend the Berlin All Hands and who also celebrate Chinese New Year, we will offer the following:<br />
* A higher airfare caps for air travel to allow for fewer layovers on Monday, January 27<br />
* Assurance that Berlin is optional but if employee wants to attend they can shift their holiday days to another time. <br />
* Live Airmo Feeds of Plenary (+ relevant team all hands meetings) + quick posting of recording to accommodate those who choose not to travel. <br />
* Potentially shifting any main plenary session date/time<br />
<br />
We are working with leadership and representatives of those most affected and will update wiki regularly with updates. Feel free to reach out to Brianna with questions.<br />
<br />
=='''Week at a Glance'''==<br />
View [https://docs.google.com/spreadsheets/d/1kIwKEmlYE9tMuWRvSNZnYDGWFwEumcHVp1s0LVPz-e8/edit#gid=0 Week at a glance]<br />
<br />
====Monday====<br />
*Monday is travel/arrival day<br />
*Registration<br />
*Welcome Reception from 6:00 pm - 9:00 pm<br />
<br />
====Tuesday====<br />
*Breakfast in hotel restaurants<br />
*Lunch in hotels of your team homeroom<br />
*Dinner on own<br />
<br />
====Wednesday====<br />
*Breakfast in hotel restaurants<br />
*Lunch in hotels of your team homeroom<br />
*Dinner on own<br />
<br />
====Thursday====<br />
*Breakfast in hotel restaurants<br />
*Lunch in hotels of your team homeroom<br />
*Dinner on own<br />
<br />
====Friday====<br />
*Breakfast in hotel restaurants<br />
*Lunch in hotels of your team homeroom<br />
*Closing event at Motorwerk<br />
<br />
====Saturday====<br />
*Breakfast in hotel restaurants<br />
*Departure day only. No scheduled activities.<br />
<br />
===Berlin All Hands Event Calendar===<br />
Coming soon!<br />
<br />
=='''Food, Drink & Events'''==<br />
Lunch & snacks will be provided and paid for centrally for attendees. Breakfast is provided Tuesday - Saturday as part of your guestroom reservation - you must eat breakfast in the hotel you sleep in. You will not be reimbursed if you go to another hotel and pay to eat there. <br />
<br />
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.<br />
<br />
===Hosted Evening Events===<br />
We have evening events on the Monday and Friday nights.<br />
<br />
====Monday Night Welcome Reception====<br />
6 pm - 9 pm, InterCon hotel<br />
<br />
====Friday Night at Motorwerk====<br />
6:00 pm - 11:00 pm<br />
<br />
======Getting to/from the event======<br />
Shuttles depart from the hotels starting at 5:30 pm. Shuttles will return shuttles starting at 8:00 pm. The last departure returning will leave at 11:05 pm. The only way to access the event is via our shuttles. <br />
<br />
=====Coat Check=====<br />
Coat check will be available for clothing only, no bags. <br />
<br />
====Tuesday, Wednesday & Thursday Night Dinners====<br />
You'll be on your own for Tuesday, Wednesday & Thursday and will have a similar expense policy from past all hands (50EUR/night - 150EUR total to include food, beverage, transportation, exchange fees, etc). <br />
<br />
Here is how this will work:<br />
<br />
For all 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 150EUR over the three days (or 50EUR/night).<br />
<br />
This amount includes:<br />
*Meal cost, including tax & gratuity<br />
*Any beverages<br />
*Transportation to/from the restaurant<br />
*Conversion fees (for credit cards) or cash withdrawal fees<br />
<br />
Anything over the 150EUR for the three evenings will be your own expense. The fine print:<br />
*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 100EUR for the other night.<br />
*You will be asked (later) to submit a Berlin All Hands only expense report. You can submit ONE report for Berlin only and must be submitted no later than February 28, 2020.<br />
*No expenses over $60 per night will be [https://docs.google.com/document/d/1XUD5KYotSr5SNi0q4ldgGG3bzBu-G3q4l5i-JiPE5ko/edit approved].<br />
<br />
Volunteer Contributors will have a separate process that will be communicated directly.<br />
<br />
=====Groups, Restaurants & Reservations=====<br />
*Group dinners - All large (eight or more people) reservations must go through Lisa Carlson (email lcarlson@mozilla.com) and dinners must stay within the per diem per night (50EURpp including, food, beverage, tax, gratuity and transportation), and employees attending must not also expense their per diem for that night.<br />
<br />
In no case should employees expense or use MoCo corporate cards to cover purchases of alcohol outside of team dinners or the 50EUR individual per diem.<br />
<br />
=='''Safety & Security'''==<br />
=====Alcohol at Events=====<br />
To better support and sustain an environment (and workplace culture) where people feel safe and included, we have made a set of changes regarding alcohol at our events. In all cases, our approach aligns with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).<br />
*All participants are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.<br />
*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.<br />
*Team dinners should be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.<br />
*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.<br />
<br />
=====Device Security=====<br />
If you are traveling to the 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)<br />
<br />
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.<br />
<br />
=====Physical Security=====<br />
Badges are required to access all meeting spaces and evening events.<br />
<br />
=='''Accessibility'''==<br />
====Evenings====<br />
Monday Night reception is at the InterContinental Berlin. No stairs or elevators required. <br />
<br />
====Meeting spaces====<br />
* InterCon: Most meeting space levels are accessible by elevators.<br />
* Pullman: All meeting space levels are accessible by guestroom elevators.<br />
* Hotel Berlin: All meeting space is on the ground level.<br />
<br />
====Listen Systems====<br />
We will have Listen Systems available for any meeting in the main plenary space. Visit the AV booth to pick one up.<br />
<br />
====Bathrooms====<br />
TBA <br />
<br />
====Breastfeeding/pumping stations====<br />
Milk Stork Services are reimbursable - please contact benefits@mozilla.com for more information.<br />
<br />
=='''Sustainability'''==<br />
'''Hotel Berlin, Berlin''' is certified partner of visitBerlin we stand for sustainable, green meetings and events. For more information, visit https://convention.visitberlin.de/en/sustain.<br />
<br />
'''InterContinental Hotel Berlin''' is Green Globe Certified. Green Globe Certification is the worldwide sustainability system based on internationally accepted criteria for sustainable operation and management of travel and tourism businesses. Operating under a worldwide license, Green Globe Certification is based in California, USA and is represented in over 83 countries. Green Globe Certification is a member of the Global Sustainable Tourism Council, supported by the United Nations World Tourism Organization. Additonally, as part of IHG’s Green Engage™ program the InterContinental Berlin has implemented best practices at all operational levels. The innovative Environmental Management System not only measures the day-to-day energy, water and waste consumption, but also provides recommended actions – ‘green solutions’ – to improve energy conservation and the property’s carbon footprint score.<br />
<br />
=='''All Hands Expense Policy'''==<br />
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Berlin All Hands Expense Report). Each expense must be tagged with "All Hands - Jan 2020"<br />
<br />
2. It must contain only those expenses relative to the All Hands Event in Berlin. <br />
<br />
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<br />
<br />
4. The deadline to submit the All Hands Expense Report is '''February 28, 2020'''.<br />
<br />
5. Expenses related to team events (except those coordinated through Lisa Carlson), parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved. <br />
<br />
<br />
'''The intention of our all hands are to centrally organize a structure that includes:'''<br />
*Meals (2 evening events + breakfast, lunch, drinks and snacks Tuesday - Friday)<br />
*Transportation<br />
*Accommodations<br />
<br />
Expenses submitted can not exceed the approved amounts. Any social events (except dinners/team building activities coordinated through Lisa Carlson) that are not part of our central plan will generally be self-organized and funded by participants. <br />
<br />
=====Travel expenses policy=====<br />
Reimbursement will be made for necessary and reasonable expenses. <br />
<br />
* Getting to/from home to your airport: We ask that you use the most economical option, while balancing your personal needs - whether that be mileage/parking, public transportation or ride shares. We will not reimburse for private towncar services or car rental. <br />
* Per standard Mozilla travel policy, Travel Meal Policy: Employees are eligible for travel meals when traveling. For Meals: There is a $75 USD per day meal policy while traveling. This covers breakfast (est. $15), lunch (est. $20), and dinner (est. $40). Receipts: Receipts are required. When submitting a meal for reimbursement, please include how many people attended the meal. There is no need to include names.<br />
* We will not reimburse for seat/class upgrades. Frequent flyer status does not apply for All Hands. <br />
* We will reimburse for bag checking fees for one bag. <br />
<br />
Any other expenses must be approved by your manager ahead of time. Any expenses for extending your stay for business reasons - such as additional hotel nights, meals, etc must be approved by your manager before booking and travel.<br />
<br />
=====Cell phone reimbursement policy=====<br />
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. <br />
<br />
=====Internet reimbursement policy=====<br />
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.<br />
<br />
=='''Activities'''==</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Support/Weekly_Meetings/Agenda_2019-11-06&diff=1219929Support/Weekly Meetings/Agenda 2019-11-062019-11-06T16:49:08Z<p>Lucyeoh: </p>
<hr />
<div>== Meeting Details (scroll down for the agenda) ==<br />
(meeting duration approx. 30 minutes) starting at:<br />
17:00 UTC<br />
[http://www.thetimezoneconverter.com/?t=17:00&tz=UTC&]<br />
<br />
==Call Details==<br />
*California: 1-650-903-0800, pin 2 then 8437 then #<br />
*Toll-free: +1 800 707 2533, pin 2 - then 8437 then #<br />
*Skype (free): +1 800 707 2533, pin 2 - then 8437 then #<br />
<br />
==Participate==<br />
* [https://mozilla.zoom.us/j/3241778647 Join the meeting on Zoom] (You'll have to download and install the [https://zoom.us/support/download Zoom Desktop client])<br />
* [https://www.youtube.com/watch?v=OVbt8Xzrz0Y Watch the meeting live via YouTube]<br />
* [https://mzl.la/sumo-2019-11-06 AirMozilla]<br />
<br />
===Read more===<br />
* [http://blog.mozilla.org/sumo Support blog]<br />
<br />
===Live chat===<br />
* [https://kiwiirc.com/client/irc.mozilla.org/sumo irc.mozilla.org #sumo - web-based IRC]<br />
* [https://t.me/mozsumo @mozsumo] - Telegram channel<br />
<br />
== Please note that the agenda should not be edited starting 2 hours prior to the event - thanks! ==<br />
-----------------------------------------------------------------------------------------------------------------------------<br />
<br />
== PARTICIPANTS ==<br />
Please add your name and profile link (if you have one, Mozillians or support.mozilla.org)<br />
* Kiki<br />
* Giulia<br />
* Luna<br />
<br />
== AGENDA ==<br />
<br />
===CONTRIBUTORS OF THE WEEK===<br />
(Please link to their profile and add a reason for nomination)<br />
# <br />
# <br />
#<br />
<br />
===NEW CONTRIBUTORS FOR THE WEEK===<br />
# <br />
<br />
=== COMMUNITY ROUNDTABLE ===<br />
Please add your agenda items here if you are a contributor or community member<br />
# Thank you for 100 enthusiastic participants during Firefox 70 SUMO Sprint.<br />
# <br />
# <br />
<br />
=== COOL COMMUNITY NEWS OF THE WEEK ===<br />
# [https://discourse.mozilla.org/t/sumo-community-meeting-planning/46298 SUMO Community Meeting content planning], remember to suggest the guests you would like to see on our Community calls!<br />
# [https://discourse.mozilla.org/t/how-firefox-accounts-support-mozilla-s-mission/47762 How Firefox Account support Mozilla's mission]<br />
## Did this help you understand why accounts are critical for our strategy?<br />
## Are there still outstanding questions? <br />
## How do you think your communities are feeling about accounts? <br />
## What additional materials/content etc. do you want/need? <br />
# Missed the Community Portal demo call? No worries! Check out the whole portal [https://www.figma.com/proto/7P5C9UtORoEfdi4SZjAMz5/Mozilla-v2.0?node-id=1253%3A101655&viewport=965%2C800%2C0.5&scaling=min-zoom here] share your feedback [https://pad.mozilla.org/p/Community_Portal_Call here].<br />
<br />
=== UPDATES AND ANNOUNCEMENTS ===<br />
==== PRODUCT UPDATES ====<br />
# [https://www.mozilla.org/en-US/firefox/70.0.1/releasenotes/ Firefox 70.0.1]<br />
# <br />
<br />
==== PLATFORM UPDATES ====<br />
# [https://discourse.mozilla.org/t/help-firefox-preview-users-in-your-language/47908 Help Firefox Preview users in your language!]<br />
<br />
==== KNOWLEDGE BASE AND LOCALIZATION====<br />
# <br />
# <br />
#<br />
<br />
==== SUPPORT FORUM ====<br />
# Please give some love for Fx for iOS, Firefox Focus, and Lockwise on the forum.<br />
#<br />
#<br />
<br />
==== SOCIAL SUPPORT ====<br />
# <br />
# <br />
# <br />
<br />
==== DECISIONS AND ACTION ITEMS ====<br />
# <br />
<br />
==== FUN ZONE - JOKES, ETC. ====</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219903All Hands/Berlin2020/contributors2019-11-05T17:30:38Z<p>Lucyeoh: /* Families/Guests */</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
<br />
===Registration:===<br />
This is an invite-only event. Details of the nomination process for contributors are [[All_Hands/Contributor_nominations|here]]. Please note the nomination process for the Berlin 2020 All Hands is now closed. <br />
Once you have booked flights, please register. The link to register is in your email. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Please note that we are unable to accommodate volunteer contributor or intern families/guests at our All Hands. While you can travel with your family all arrangements will need to be made independently and they will not be able to attend any events or meetings associated with the All Hands. <br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
* '''Flights''' - you'll need to book them separately (not through egencia) and you can call the airline once all the bookings are done to request moving your seats together. If your visa is rejected we will not be able to cover flight cancellation costs for your partner. <br />
* '''Hotel''' - All room rates are based upon single occupancy and includes breakfast. Guests must be added to reservations in advance by contacting the hotel after you receive a confirmation. Any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. You can contact the hotel directly to book and pay for an extra room at the hotel. <br />
* '''Exceptions''' may only be made for underage contributors who are required to have a legal guardian present.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Travel expenses policy===<br />
<br />
Reimbursement will only be made for the following expenses.<br />
<br />
Getting to/from home to your airport: We ask that you use the most economical option whether that be mileage/parking, public transportation or ride shares. <br />
<br />
We will not reimburse the following: <br />
We will not reimburse for private town-car services or car rentals.<br />
We will not reimburse the cost of insurance. <br />
We will not reimburse for seat/class upgrades.<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219902All Hands/Berlin2020/contributors2019-11-05T17:25:13Z<p>Lucyeoh: /* Visa information: */</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
<br />
===Registration:===<br />
This is an invite-only event. Details of the nomination process for contributors are [[All_Hands/Contributor_nominations|here]]. Please note the nomination process for the Berlin 2020 All Hands is now closed. <br />
Once you have booked flights, please register. The link to register is in your email. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Please note that we are unable to accommodate volunteer contributor or intern families/guests at our All Hands. <br />
While you can travel with your family and they are welcome to stay in your hotel room, all other arrangements will need to be independently and they will not be able to attend any events or meetings associated with the All Hands. <br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
* '''Flights''' - you'll need to book them separately (not through egencia) and you can call the airline once all the bookings are done to request moving your seats together. If your visa is rejected we will not be able to cover flight cancellation costs for your partner. <br />
* '''Hotel''' - All room rates are based upon single occupancy and includes breakfast. Guests must be added to reservations in advance by contacting the hotel after you receive a confirmation. Any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. You can contact the hotel directly to book and pay for an extra room at the hotel. <br />
* '''Exceptions''' may only be made for underage contributors who are required to have a legal guardian present.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Travel expenses policy===<br />
<br />
Reimbursement will only be made for the following expenses.<br />
<br />
Getting to/from home to your airport: We ask that you use the most economical option whether that be mileage/parking, public transportation or ride shares. <br />
<br />
We will not reimburse the following: <br />
We will not reimburse for private town-car services or car rentals.<br />
We will not reimburse the cost of insurance. <br />
We will not reimburse for seat/class upgrades.<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Contributor_nominations&diff=1219846All Hands/Contributor nominations2019-11-04T20:29:55Z<p>Lucyeoh: </p>
<hr />
<div>'''<span>Please note the nomination process for the Berlin 2020 All Hands is now closed.</span>'''<br />
<br />
== Introduction ==<br />
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.<br />
<br />
This page outlines the nomination and selection process that will be used for all Mozilla All Hands.<br />
<br />
== Goals ==<br />
The goals of the nomination process are:<br />
<br />
# 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<br />
# Have contributors and employees working in an integrated way -- during and immediately before and after the All Hands<br />
# Mozilla teams are thinking about contributors strategically<br />
# A process that has legitimacy with contributors and employees<br />
<br />
== Process outline ==<br />
{| class="wikitable"<br />
|-<br />
! Step !! Starts !! Duration<br />
|-<br />
| 1) Team nominations -- staff nominate contributors (different process by team ... run by Organization Designate) || 3.5 months in advance || 2 Weeks<br />
|-<br />
| 2) Review and final prioritization || 3 months in advance || 1 week<br />
|-<br />
| 3) Invitations go out || 3 months in advance || - <br />
|-<br />
| 4) Registration and flight booking → information about this will be on another page || || <br />
|-<br />
| 5) Working with contributors and teams on their plans for integration/communication → plan for this will be on another page || || <br />
|}<br />
<br />
''Important note''<br />
* We are emphasizing greater gender balance for nominated contributors -- based on the past, our hope is to have 30% non-male contributors attending<br />
<br />
== Open Nominations ==<br />
There will be '''no "open nominations" from non-employees'''. Nominations must come directly from employees.<br />
<br />
== Organization Designates ==<br />
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.<br />
<br />
{| class="wikitable"<br />
|-<br />
! Organization !! Name of Org Designate(s)<br />
|-<br />
| Firefox/Product || Mike Hoye (mhoye)<br />
|-<br />
| Emerging Technologies || Nancy Hang (nhang)<br />
|-<br />
| Operations (incl Open Innovation) || Lucy Harris (lharris)<br />
|}<br />
<br />
''Organization Designates will be accountable for:''<br />
* Creating/curating a contributor nomination process for their part of Mozilla<br />
* Communicating within their organization about this process<br />
* Making final prioritization decisions (if needed)<br />
* Ensuring a good process across their organization to be in contact with/prepare contributors who have been invited<br />
<br />
== Number of Contributors ==<br />
We have space for roughly 60 contributors.<br />
<br />
== Criteria for contributor nominees ==<br />
[[All_Hands/Berlin2020/Contributor_nominee_criteria|Guidance and criteria are here]].<br />
<br />
== Contact ==<br />
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.<br />
<br />
If you have questions about the process in general, please get in touch with [https://mozillians.org/en-US/u/geroter/ George Roter].</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219845All Hands/Berlin2020/contributors2019-11-04T20:29:23Z<p>Lucyeoh: </p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
<br />
===Registration:===<br />
This is an invite-only event. Details of the nomination process for contributors are [[All_Hands/Contributor_nominations|here]]. Please note the nomination process for the Berlin 2020 All Hands is now closed. <br />
Once you have booked flights, please register. The link to register is in your email. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Please note that we are unable to accommodate volunteer contributor or intern families/guests at our All Hands. <br />
While you can travel with your family and they are welcome to stay in your hotel room, all other arrangements will need to be independently and they will not be able to attend any events or meetings associated with the All Hands. <br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
* '''Flights''' - you'll need to book them separately (not through egencia) and you can call the airline once all the bookings are done to request moving your seats together. If your visa is rejected we will not be able to cover flight cancellation costs for your partner. <br />
* '''Hotel''' - All room rates are based upon single occupancy and includes breakfast. Guests must be added to reservations in advance by contacting the hotel after you receive a confirmation. Any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. You can contact the hotel directly to book and pay for an extra room at the hotel. <br />
* '''Exceptions''' may only be made for underage contributors who are required to have a legal guardian present.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219838All Hands/Berlin2020/contributors2019-11-04T19:46:47Z<p>Lucyeoh: /* Families/Guests */</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
===Registration:===<br />
Once you have booked flights, please register. The link to register is here. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Please note that we are unable to accommodate volunteer contributor or intern families/guests at our All Hands. <br />
While you can travel with your family and they are welcome to stay in your hotel room, all other arrangements will need to be independently and they will not be able to attend any events or meetings associated with the All Hands. <br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
* '''Flights''' - you'll need to book them separately (not through egencia) and you can call the airline once all the bookings are done to request moving your seats together. If your visa is rejected we will not be able to cover flight cancellation costs for your partner. <br />
* '''Hotel''' - All room rates are based upon single occupancy and includes breakfast. Guests must be added to reservations in advance by contacting the hotel after you receive a confirmation. Any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. You can contact the hotel directly to book and pay for an extra room at the hotel. <br />
* '''Exceptions''' may only be made for underage contributors who are required to have a legal guardian present.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219837All Hands/Berlin2020/contributors2019-11-04T19:45:45Z<p>Lucyeoh: /* Families/Guests */</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
===Registration:===<br />
Once you have booked flights, please register. The link to register is here. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Please note that we are unable to accommodate volunteer contributor or intern families/guests at our All Hands. <br />
While you can travel with your family and they are welcome to stay in your hotel room, all other arrangements will need to be independently and they will not be able to attend any events or meetings associated with the All Hands. <br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
*Exceptions may be made for underage contributors who are required to have a legal guardian present.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219830All Hands/Berlin2020/contributors2019-11-04T18:51:45Z<p>Lucyeoh: </p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
===Registration:===<br />
Once you have booked flights, please register. The link to register is here. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Unfortunately we are '''not able to cover any costs''' associated with bringing family members to the All Hands*. If contributors choose to bring their family members with them, you will be accountable for any costs associated with their inclusion i.e. visas, flights, double-occupancy rates and meals. <br />
<br />
Also note that family members who have not been invited to the All Hands through the nomination process will not be able to attend any of the events or meetings associated with the All Hands.<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
*Exceptions may be made for underage contributors who are required to have a legal guardian present.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219829All Hands/Berlin2020/contributors2019-11-04T18:51:27Z<p>Lucyeoh: /* Families/Guests */</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
===Registration:===<br />
Once you have booked flights, please register. The link to register is here. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Unfortunately we are '''not able to cover any costs''' associated with bringing family members to the All Hands*. If contributors choose to bring their family members with them, you will be accountable for any costs associated with their inclusion i.e. visas, flights, double-occupancy rates and meals. <br />
<br />
Also note that family members who have not been invited to the All Hands through the nomination process will not be able to attend any of the events or meetings associated with the All Hands.<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
*Exceptions may be made for underage contributors who are required to have a legal guardian presence.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219828All Hands/Berlin2020/contributors2019-11-04T18:50:27Z<p>Lucyeoh: /* Visa information: */</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
===Registration:===<br />
Once you have booked flights, please register. The link to register is here. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Unfortunately we are '''not able to cover any costs''' associated with bringing family members to the All Hands. If contributors choose to bring their family members with them, you will be accountable for any costs associated with their inclusion i.e. visas, flights, double-occupancy rates and meals. <br />
<br />
Also note that family members who have not been invited to the All Hands through the nomination process will not be able to attend any of the events or meetings associated with the All Hands.<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219827All Hands/Berlin2020/contributors2019-11-04T18:49:59Z<p>Lucyeoh: /* Families/Guests */</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
===Registration:===<br />
Once you have booked flights, please register. The link to register is here. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Unfortunately we are '''not able to cover any costs''' associated with bringing family members to the All Hands. If contributors choose to bring their family members with them, you will be accountable for any costs associated with their inclusion i.e. visas, flights, double-occupancy rates and meals. <br />
<br />
Also note that family members who have not been invited to the All Hands through the nomination process will not be able to attend any of the events or meetings associated with the All Hands.<br />
<br />
We will also not be able to provide "invitation letters" to anyone who has not been officially invited to the all hands through the [[All_Hands/Contributor_nominations|contributor nomination process]].<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219826All Hands/Berlin2020/contributors2019-11-04T18:47:00Z<p>Lucyeoh: </p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
===Registration:===<br />
Once you have booked flights, please register. The link to register is here. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Families/Guests===<br />
Unfortunately we are not able to cover costs associated with bringing family members to the All Hands. While contributors can choose to invite their family members you will be accountable for any costs associated with their inclusion i.e. visas, flights, double-occupancy rates and meals. Also note that family members who have not been invited to the All Hands through the nomination process will not be able to attend any of the events or meetings associated with the All Hands.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020&diff=1219823All Hands/Berlin20202019-11-04T18:29:43Z<p>Lucyeoh: </p>
<hr />
<div>'''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! <br />
<br />
'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor please inquire with your community manager/program manager about [[All_Hands/Contributor_nominations|contributor nominations]], interns please inquire to your coordinator. Volunteer contributors who have recieved an invitation can find relevant information [[All_Hands/Berlin2020/contributors|here]]. '''''<br />
<br />
=='''Dates and Location'''==<br />
Monday, January 27, 2020 - Friday, January 31, 2020 (travel days are Monday, Jan 27 & Saturday, Feb 1) in Berlin, Germany.<br />
<br />
We have guestrooms at three hotels: [https://www.ihg.com/intercontinental/hotels/us/en/berlin/berha/hoteldetail InterContinental Berlin], [https://www.pullman-berlin-schweizerhof.com/en/ Hotel Pullman Schweizerhof], and [https://www.hotel-berlin.de/en/ Hotel Berlin, Berlin]. [https://drive.google.com/open?id=1eu_rYMxuc_hgSNqCJxW7Vn32pYMNayPa&usp=sharing View on map].<br />
<br />
''*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.''<br />
<br />
=='''Registration'''==<br />
This is an invite-only event. All full time and Elance/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 and upon executive review and approval. <br />
<br />
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. This includes facilitators, and other related business guests. <br />
<br />
=====New Hires=====<br />
We have a process to identify qualified regular full time new hires and Brianna will invite all new hires to register and book travel directly on their start date. No action is necessary from hiring managers other than to let them know about the event (please do not forward any links). Please work closely with your recruiting manager as they are aware of all deadlines.<br />
<br />
All regular full time new hires must have a start date of January 6, 2020 or earlier and in workday by December 16, 2019. Final invites will be extended on December 17, 2019. Contractors/vendors will require executive approval and those who are hired after the approval will not be invited. If you have any questions, please email bmark@mozilla.com.<br />
<br />
=====Volunteer Contributors=====<br />
There are a number of policies that apply specifically to contributors that are different than for staff. Please look [[All_Hands/Berlin2020/contributors|here]] for all contributor specific instructions and policies. <br />
<br />
<br />
=====Registration Changes=====<br />
Everyone who registered received a confirmation email titled "Registration Confirmation to Mozilla Berlin All Hands" which shows you how you answered each question. If you didn't get the email and/or need to make changes to your registration, please email mozilla@shworldwide.com.<br />
<br />
=='''Immigration'''==<br />
If you have any questions about immigration, please email immigration@mozilla.com. <br />
<br />
==== STEP ====<br />
'''What is STEP?''' <br />
The [https://step.state.gov/ Smart Traveler Enrollment Program (STEP)] is a free service to allow U.S. citizens and nationals traveling abroad to enroll their trip with the nearest U.S. Embassy or Consulate. <br />
Benefits of Enrolling in STEP <br />
* Receive important information from the Embassy about safety conditions in your destination country, helping you make informed decisions about your travel plans.<br />
* Help the U.S. Embassy contact you in an emergency, whether natural disaster, civil unrest, or family emergency.<br />
* Help family and friends get in touch with you in an emergency.<br />
<br />
==== Visas ====<br />
You do not need a visa if you hold a passport issued from the EU, USA, Australia, New Zealand, Taiwan, or Canada. <br />
Please see here to confirm the entry document requirements for the country you’re from: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node/staatenlistevisumpflicht-node <br />
<br />
If you are from a country that requires a visa to enter Germany, please plan to obtain one as early as possible as government processing times constantly change. You can find a broad overview of the process here: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node . For more detailed instructions regarding the visa process you will need to refer to the website of your nearest Mission/Consulate General. You will be able to learn more about the process by searching for “business visa” or “visitor visa” on the website for that German Mission.<br />
<br />
'''Please keep in mind that while you are traveling for work, you are not traveling for a German based job.''' All Hands is a business conference/event. As you book your travel please also keep in mind that you could require a transit visa if you have a layover in a country that requires it. <br />
<br />
If you have questions specific to your circumstances, please email immigration@mozilla.com. <br />
<br />
==== Entering Germany ====<br />
Your passport or identity card will be checked when you arrive at an EU port or airport to make sure you’re allowed to come into the country. The passport must be valid for the whole of your stay. You may also need a visa to come into or travel through Germany, depending on your nationality. <br />
* If you are from an EEA country or Switzerland, you can enter Germany with either a valid passport or a national identity card issued by a EEA country. <br />
* If you need a United States Passport, start here: https://travel.state.gov/content/passports/en/passports.html. Please note it can take 4-6 weeks to receive your passport. Please plan ahead. <br />
<br />
==== EU Visa Waiver Program Suspension - Update ====<br />
In March 2019 the EU announced that the visa free entry requirements for third country visitors to Europe would be changing. This change will not go into affect until 1 January 2021, note this is one year after our Berlin All Hands trip. After this date, citizens from certain countries, including the USA and Canada, will be required to obtain an ETIAS travel authorization before they can enter Europe.<br />
<br />
==== More details: ==== <br />
Mission websites in popular Mozillian locations:<br />
* United States: https://www.germany.info/us-en/service/05-VisaEinreise/business-visa/963542<br />
* Canada: https://canada.diplo.de/ca-en/consular-services/visa/shortstay<br />
* UK: https://uk.diplo.de/uk-en/02/visa<br />
* Paris: https://allemagneenfrance.diplo.de/fr-de/service/00-visa-seite<br />
* Taiwan: https://taipei.diplo.de/tw-en/service/visa<br />
* Beijing: https://china.diplo.de/cn-zh/service/visa-einreise/schengenvisum/1343246<br />
* India: https://india.diplo.de/in-en/service/-/1908794<br />
<br />
=='''Travel to Berlin'''==<br />
Bookings to Berlin have begun. The Egencia instructions have be emailed to '''anyone approved to attend'''. New hires will have individual deadlines based upon hire/start date. Approved contractors, vendors, seasonal, status employees will be notified with an email from bmark@mozilla.com with specific instructions. <br />
<br />
Specific instructions were emailed to you about how to book, as we have a new process for anyone based outside the US, Canada & Central/South America. APAC employees will '''NOT''' be booking your All Hands travel in country based site, and will be using Egencia Americas. European employees '''WILL''' be booking in your country based site to allow access to trains and low cost airlines. <br />
<br />
Should you need to reach someone at '''Egencia Americas''' for special circumstances or changes that can't be done online:<br />
*Call+1 (800) 361-1120 or +1(702)939-2533; Hours of operations are Monday – Friday (except holidays) 5:00 AM– 6:00 PM PT or 8:00 AM – 9:00 PM ET or 12:00 PM - 1:00 AM UTC. If you call outside these hours, you will get an after-hours agent (not a meeting agent, who may not be as helpful) . Please ensure the agent you speak with knows you are booking for a meeting.<br />
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday.<br />
<br />
Other Egencia contact details:<br />
*Egencia UK+EMEA - Email: customer_service@egencia.co.uk; UK Local #: +44 203 077 2536 (charged at local rate). For calls made outside the UK, please dial +00 44 161 233 5525. (From anywhere outside the EU, please dial +011 44...)<br />
*Egencia FR - Email: service_client@egencia.fr; France Local #: +33 8 11 65 66 53. For calls made outside France, please dial +33 4 86 06 15 18 (From anywhere outside the EU, please dial +011 33)<br />
<br />
'''Important Details:'''<br />
Everyone should plan to arrive in Berlin Tegel Airport (TXL) on Monday, January 27 and leave on Saturday, February 1. 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 Berlin Tegel (anything custom). A few notes:<br />
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, those approved will be sent separate email.<br />
*Volunteers will be handled separate from this process.<br />
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.<br />
*If you would like to invite someone who is a business partner, facilitator or some other category that isn't an employee or volunteer (not a personal guest/family), email bmark@mozilla.com.<br />
*Change fees will be covered by Mozilla for business reasons only. Please email bmark@mozilla.com ahead of calling Egencia to make the change. Any changes for personal reasons must be paid by the employee directly to Egencia over the phone. <br />
<br />
====Arriving Early/Departing Late Guidelines====<br />
<br />
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, January 27 and leave on Saturday, February 1. Here are some exceptions: <br />
<br />
# If you plan to spend some extra '''personal time in Berlin/Europe''' or nearby (choosing to arrive before Monday, Jan 27 or depart after Saturday, Feb 1), you'll need to create a itinerary in Egencia for standard dates/locations within the Egencia Portal and compare to the custom dates/locations you'd like. Pricing for the standard dates should be ''Round Trip only''. Pricing for custom dates/locations should be for ''Round trip or Multi city trips only''. Please share the difference via email to bmark@mozilla.com and receive approval ahead of submission in Egencia. 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 TXL w/ longer dates, and you personally book & cover the rest). Please note that one way trips are only approved on a case by case basis. Do not book one ways without prior approval. ''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 Berlin Tegel than your home airport (ex. a layover in London for a few days, or flying out of something other than TXL). <br />
# If you are attending the '''Sunday/Monday CI event''' (by invite), you can arrive on Sunday, January 26.<br />
# 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.<br />
# If you are celebrating the '''Lunar New Year''', [https://wiki.mozilla.org/All_Hands/Berlin2020#Lunar_New_Year see here].<br />
# If you live in a country where '''work travel is prohibited on weekends''', you may travel on Friday, Jan 24 and Monday, Feb 3, 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). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively. <br />
# If you live in a country where '''work travel is prohibited on Sunday''', you may travel on Saturday, Jam 24, 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). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively.<br />
<br />
====Booking Family Travel====<br />
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.<br />
<br />
'''Direct (recommended):''' <br />
<br />
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.<br />
<br />
'''Via Egencia:'''<br />
<br />
We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com<br />
<br />
'''Notes:''' <br />
<br />
* If your family is arriving on a different flights than you but would like to take advantage of the airport shuttles on Sunday/Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.<br />
* We are unable to accommodate volunteer contributor families/guests.<br />
<br />
====Not Flying====<br />
Mozilla will reimburse U-Bahn tickets for those based in the Berlin area for getting to/from hotels. For more information on the U-Bahn, please see the Berlin office guide on [https://mana.mozilla.org/wiki/display/WPR/Berlin+Office+Guide#BerlinOfficeGuide-MovingAroundBerlin mana]. <br />
<br />
For those outside of the Berlin area who are taking the train, please add your name [https://docs.google.com/spreadsheets/d/1A8AKfpdaeD_gVoC6eZfxZoQ4zacgP8l_r9vM04RKyPI/edit#gid=0 here]. We will notify you when train bookings open (on or about Nov 1). You will book train via Egencia FR, UK, DE. <br />
<br />
Parking is not reimbursable.<br />
<br />
====Travel Insurance====<br />
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. <br />
<br />
Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members (unless required for visa application).<br />
<br />
====Air Travel Fine Print====<br />
*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-877-255-1090 (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.<br />
*Mozilla will '''not''' reimburse for Business/First class upgrades, tickets or seat reservations. <br />
*Mozilla will reimburse for one checked bag each way.<br />
*''Mozilla Frequent Flyer perks do not apply for All Hands''. <br />
*Flights booked outside of Egencia will not be an approved expense unless email approval by Brianna is obtained prior to booking.<br />
*Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.<br />
<br />
====Ground Transportation====<br />
Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00.<br />
<br />
Taxis and Addison Lee are not reimbursable. <br />
<br />
If you are arriving by train to Hauptbahnhof:<br />
To Hotel Berlin Berlin<br />
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S5, S9 or S75 to the station “Zoologischer Garten” (20 min.). From there, take the bus 100 to the stop Lützowplatz. <br />
* Via U-BAHN: Take the U-Bahn metro lines U2, U3 and U1 to the station “U-Nollendorfplatz”. Exit the station in the direction of “Karl-Heinrich-Ulrichs-Straße." The road leads directly to the hotel (approx 5 mins). <br />
* [https://www.hotel-berlin.de/d/berlinberlinpro/media/PDF/Anfahrt_A4_E_Karl-Heinrich-Ulrichs-Strae_5c2ab7.pdf Map]<br />
<br />
To InterCon Berlin and Pullman<br />
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S3, S5, S7, or S9 to the station “Zoologischer Garten”. From there, walk 10 mins to hotel.<br />
<br />
Berlin's integrated public transport is divided in 3 tariff zones (ABC). To travel within the city, including from Tegel airport to the hotels, you only need an AB ticket. Tickets can be bought at automated booths in most stations (accept credit cards), and on Metro (need coins). You can use the same ticket to travel on buses, metro, S-Bahn, U-Bahn. More information, including PDF maps, are available on [https://www.berlin.de/en/public-transportation/1772016-2913840-tickets-fares-and-route-maps.en.html this website]. A mobile app is available on stores ("BVG FahrInfo Plus") and allows to create routes between stations, or you can use directly the [https://www.bvg.de/en BVG] website.<br />
<br />
=='''Families/Guests'''==<br />
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. We are unable to accommodate volunteer contributor or intern families/guests at our All Hands. <br />
<br />
====Quick summary logistics====<br />
* Air Travel: Employees do need to book via Egencia regardless of how families are booked. <br />
* Hotel: Family/friends are welcome to stay with you. All room rates are based upon single occupancy and include breakfast. Guests must be added to reservations in advance and any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. Higher occupancy rooms will be assigned in the order that you register. We will have extra rooms available for families to book and pay for at our hotels. <br />
* Lunch & Dinner: Family will be on their own for lunch daily and dinner on Tuesday, Wednesday & Thursday. <br />
* Monday & Friday Night Events: Family members who are registered for the event and registered with the hotel, are invited to join us for our evening events.<br />
* Childcare Services: We will not provide centralized childcare services. We have found that every family has different needs and centralized childcare does not deliver on those needs. If you are in need of help finding options for your family, we are happy to connect you with staff whose families who are coming (#allhands-childcare and #parents are great places to start), as well we are happy to help support finding of resources (although you are likely better at it than us). Given every circumstance is unique, we defer to your manager to determine what Mozilla can support you with financially.<br />
<br />
On demand babysitting services in Berlin: <br />
* https://extra-arms.com/for-families-babysitting/<br />
* https://www.withourbaby.com/<br />
<br />
=='''Lunar New Year'''==<br />
We are aware of the overlap in the Lunar New Year celebrations with the Berlin All Hands. To help folks who decide to attend the Berlin All Hands and who also celebrate Chinese New Year, we will offer the following:<br />
* A higher airfare caps for air travel to allow for fewer layovers on Monday, January 27<br />
* Assurance that Berlin is optional but if employee wants to attend they can shift their holiday days to another time. <br />
* Live Airmo Feeds of Plenary (+ relevant team all hands meetings) + quick posting of recording to accommodate those who choose not to travel. <br />
* Potentially shifting any main plenary session date/time<br />
<br />
We are working with leadership and representatives of those most affected and will update wiki regularly with updates. Feel free to reach out to Brianna with questions.<br />
<br />
=='''Safety & Security'''==<br />
=====Alcohol at Events=====<br />
To better support and sustain an environment (and workplace culture) where people feel safe and included, we have made a set of changes regarding alcohol at our events. In all cases, our approach aligns with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).<br />
*All participants are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.<br />
*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.<br />
*Team dinners should be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.<br />
*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.<br />
<br />
=====Device Security=====<br />
If you are traveling to the 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)<br />
<br />
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.<br />
<br />
=====Physical Security=====<br />
Badges are required to access all meeting spaces and evening events.<br />
<br />
=='''Accessibility'''==<br />
====Evenings====<br />
Monday Night reception is at the InterContinental Berlin. No stairs or elevators required. <br />
<br />
====Meeting spaces====<br />
* InterCon: Most meeting space levels are accessible by elevators.<br />
* Pullman: All meeting space levels are accessible by guestroom elevators.<br />
* Hotel Berlin: All meeting space is on the ground level.<br />
<br />
====Listen Systems====<br />
We will have Listen Systems available for any meeting in the main plenary space. Visit the AV booth to pick one up.<br />
<br />
====Bathrooms====<br />
TBA <br />
<br />
====Breastfeeding/pumping stations====<br />
Milk Stork Services are reimbursable - please contact benefits@mozilla.com for more information.<br />
<br />
=='''Sustainability'''==<br />
'''Hotel Berlin, Berlin''' is certified partner of visitBerlin we stand for sustainable, green meetings and events. For more information, visit https://convention.visitberlin.de/en/sustain.<br />
<br />
'''InterContinental Hotel Berlin''' is Green Globe Certified. Green Globe Certification is the worldwide sustainability system based on internationally accepted criteria for sustainable operation and management of travel and tourism businesses. Operating under a worldwide license, Green Globe Certification is based in California, USA and is represented in over 83 countries. Green Globe Certification is a member of the Global Sustainable Tourism Council, supported by the United Nations World Tourism Organization. Additonally, as part of IHG’s Green Engage™ program the InterContinental Berlin has implemented best practices at all operational levels. The innovative Environmental Management System not only measures the day-to-day energy, water and waste consumption, but also provides recommended actions – ‘green solutions’ – to improve energy conservation and the property’s carbon footprint score.<br />
<br />
=='''All Hands Expense Policy'''==<br />
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Berlin All Hands Expense Report). Each expense must be tagged with "All Hands - Jan 2020"<br />
<br />
2. It must contain only those expenses relative to the All Hands Event in Berlin. <br />
<br />
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<br />
<br />
4. The deadline to submit the All Hands Expense Report is '''February 28, 2020'''.<br />
<br />
5. Expenses related to team events (except those coordinated through Lisa Carlson), parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved. <br />
<br />
<br />
'''The intention of our all hands are to centrally organize a structure that includes:'''<br />
*Meals (2 evening events + breakfast, lunch, drinks and snacks Tuesday - Friday)<br />
*Transportation<br />
*Accommodations<br />
<br />
Expenses submitted can not exceed the approved amounts. Any social events (except dinners/team building activities coordinated through Lisa Carlson) that are not part of our central plan will generally be self-organized and funded by participants. <br />
<br />
=====Travel expenses policy=====<br />
Reimbursement will be made for necessary and reasonable expenses. <br />
<br />
* Getting to/from home to your airport: We ask that you use the most economical option, while balancing your personal needs - whether that be mileage/parking, public transportation or ride shares. We will not reimburse for private towncar services or car rental. <br />
* Per standard Mozilla travel policy, Travel Meal Policy: Employees are eligible for travel meals when traveling. For Meals: There is a $75 USD per day meal policy while traveling. This covers breakfast (est. $15), lunch (est. $20), and dinner (est. $40). Receipts: Receipts are required. When submitting a meal for reimbursement, please include how many people attended the meal. There is no need to include names.<br />
* We will not reimburse for seat/class upgrades. Frequent flyer status does not apply for All Hands. <br />
* We will reimburse for bag checking fees for one bag. <br />
<br />
Any other expenses must be approved by your manager ahead of time. Any expenses for extending your stay for business reasons - such as additional hotel nights, meals, etc must be approved by your manager before booking and travel.<br />
<br />
=====Cell phone reimbursement policy=====<br />
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. <br />
<br />
=====Internet reimbursement policy=====<br />
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.<br />
<br />
=='''Activities'''==</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020&diff=1219822All Hands/Berlin20202019-11-04T18:28:09Z<p>Lucyeoh: /* Registration */</p>
<hr />
<div>'''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! <br />
<br />
'''''The information on this wiki primarily applies to Full time and contractor staff. If you are a volunteer contributor please inquire with your community manager/program manager about [[All_Hands/Contributor_nominations|contributor nominations]], interns please inquire to your coordinator. '''''<br />
<br />
=='''Dates and Location'''==<br />
Monday, January 27, 2020 - Friday, January 31, 2020 (travel days are Monday, Jan 27 & Saturday, Feb 1) in Berlin, Germany.<br />
<br />
We have guestrooms at three hotels: [https://www.ihg.com/intercontinental/hotels/us/en/berlin/berha/hoteldetail InterContinental Berlin], [https://www.pullman-berlin-schweizerhof.com/en/ Hotel Pullman Schweizerhof], and [https://www.hotel-berlin.de/en/ Hotel Berlin, Berlin]. [https://drive.google.com/open?id=1eu_rYMxuc_hgSNqCJxW7Vn32pYMNayPa&usp=sharing View on map].<br />
<br />
''*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.''<br />
<br />
=='''Registration'''==<br />
This is an invite-only event. All full time and Elance/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 and upon executive review and approval. <br />
<br />
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. This includes facilitators, and other related business guests. <br />
<br />
=====New Hires=====<br />
We have a process to identify qualified regular full time new hires and Brianna will invite all new hires to register and book travel directly on their start date. No action is necessary from hiring managers other than to let them know about the event (please do not forward any links). Please work closely with your recruiting manager as they are aware of all deadlines.<br />
<br />
All regular full time new hires must have a start date of January 6, 2020 or earlier and in workday by December 16, 2019. Final invites will be extended on December 17, 2019. Contractors/vendors will require executive approval and those who are hired after the approval will not be invited. If you have any questions, please email bmark@mozilla.com.<br />
<br />
=====Volunteer Contributors=====<br />
There are a number of policies that apply specifically to contributors that are different than for staff. Please look [[https://wiki.mozilla.org/All_Hands/Berlin2020/contributors|here]] for all contributor specific instructions and policies. <br />
<br />
<br />
=====Registration Changes=====<br />
Everyone who registered received a confirmation email titled "Registration Confirmation to Mozilla Berlin All Hands" which shows you how you answered each question. If you didn't get the email and/or need to make changes to your registration, please email mozilla@shworldwide.com.<br />
<br />
=='''Immigration'''==<br />
If you have any questions about immigration, please email immigration@mozilla.com. <br />
<br />
==== STEP ====<br />
'''What is STEP?''' <br />
The [https://step.state.gov/ Smart Traveler Enrollment Program (STEP)] is a free service to allow U.S. citizens and nationals traveling abroad to enroll their trip with the nearest U.S. Embassy or Consulate. <br />
Benefits of Enrolling in STEP <br />
* Receive important information from the Embassy about safety conditions in your destination country, helping you make informed decisions about your travel plans.<br />
* Help the U.S. Embassy contact you in an emergency, whether natural disaster, civil unrest, or family emergency.<br />
* Help family and friends get in touch with you in an emergency.<br />
<br />
==== Visas ====<br />
You do not need a visa if you hold a passport issued from the EU, USA, Australia, New Zealand, Taiwan, or Canada. <br />
Please see here to confirm the entry document requirements for the country you’re from: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node/staatenlistevisumpflicht-node <br />
<br />
If you are from a country that requires a visa to enter Germany, please plan to obtain one as early as possible as government processing times constantly change. You can find a broad overview of the process here: https://www.auswaertiges-amt.de/en/einreiseundaufenthalt/visabestimmungen-node . For more detailed instructions regarding the visa process you will need to refer to the website of your nearest Mission/Consulate General. You will be able to learn more about the process by searching for “business visa” or “visitor visa” on the website for that German Mission.<br />
<br />
'''Please keep in mind that while you are traveling for work, you are not traveling for a German based job.''' All Hands is a business conference/event. As you book your travel please also keep in mind that you could require a transit visa if you have a layover in a country that requires it. <br />
<br />
If you have questions specific to your circumstances, please email immigration@mozilla.com. <br />
<br />
==== Entering Germany ====<br />
Your passport or identity card will be checked when you arrive at an EU port or airport to make sure you’re allowed to come into the country. The passport must be valid for the whole of your stay. You may also need a visa to come into or travel through Germany, depending on your nationality. <br />
* If you are from an EEA country or Switzerland, you can enter Germany with either a valid passport or a national identity card issued by a EEA country. <br />
* If you need a United States Passport, start here: https://travel.state.gov/content/passports/en/passports.html. Please note it can take 4-6 weeks to receive your passport. Please plan ahead. <br />
<br />
==== EU Visa Waiver Program Suspension - Update ====<br />
In March 2019 the EU announced that the visa free entry requirements for third country visitors to Europe would be changing. This change will not go into affect until 1 January 2021, note this is one year after our Berlin All Hands trip. After this date, citizens from certain countries, including the USA and Canada, will be required to obtain an ETIAS travel authorization before they can enter Europe.<br />
<br />
==== More details: ==== <br />
Mission websites in popular Mozillian locations:<br />
* United States: https://www.germany.info/us-en/service/05-VisaEinreise/business-visa/963542<br />
* Canada: https://canada.diplo.de/ca-en/consular-services/visa/shortstay<br />
* UK: https://uk.diplo.de/uk-en/02/visa<br />
* Paris: https://allemagneenfrance.diplo.de/fr-de/service/00-visa-seite<br />
* Taiwan: https://taipei.diplo.de/tw-en/service/visa<br />
* Beijing: https://china.diplo.de/cn-zh/service/visa-einreise/schengenvisum/1343246<br />
* India: https://india.diplo.de/in-en/service/-/1908794<br />
<br />
=='''Travel to Berlin'''==<br />
Bookings to Berlin have begun. The Egencia instructions have be emailed to '''anyone approved to attend'''. New hires will have individual deadlines based upon hire/start date. Approved contractors, vendors, seasonal, status employees will be notified with an email from bmark@mozilla.com with specific instructions. <br />
<br />
Specific instructions were emailed to you about how to book, as we have a new process for anyone based outside the US, Canada & Central/South America. APAC employees will '''NOT''' be booking your All Hands travel in country based site, and will be using Egencia Americas. European employees '''WILL''' be booking in your country based site to allow access to trains and low cost airlines. <br />
<br />
Should you need to reach someone at '''Egencia Americas''' for special circumstances or changes that can't be done online:<br />
*Call+1 (800) 361-1120 or +1(702)939-2533; Hours of operations are Monday – Friday (except holidays) 5:00 AM– 6:00 PM PT or 8:00 AM – 9:00 PM ET or 12:00 PM - 1:00 AM UTC. If you call outside these hours, you will get an after-hours agent (not a meeting agent, who may not be as helpful) . Please ensure the agent you speak with knows you are booking for a meeting.<br />
*Email: groupagents@customercare.egencia.com. The email is monitored Monday - Friday.<br />
<br />
Other Egencia contact details:<br />
*Egencia UK+EMEA - Email: customer_service@egencia.co.uk; UK Local #: +44 203 077 2536 (charged at local rate). For calls made outside the UK, please dial +00 44 161 233 5525. (From anywhere outside the EU, please dial +011 44...)<br />
*Egencia FR - Email: service_client@egencia.fr; France Local #: +33 8 11 65 66 53. For calls made outside France, please dial +33 4 86 06 15 18 (From anywhere outside the EU, please dial +011 33)<br />
<br />
'''Important Details:'''<br />
Everyone should plan to arrive in Berlin Tegel Airport (TXL) on Monday, January 27 and leave on Saturday, February 1. 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 Berlin Tegel (anything custom). A few notes:<br />
*If you are a vendor (paid by a company other than Mozilla or Upwork), contractor, or seasonal staff, those approved will be sent separate email.<br />
*Volunteers will be handled separate from this process.<br />
*We work closely with Recruiting to ensure new hires are invited after their start date. No need to let us know about these.<br />
*If you would like to invite someone who is a business partner, facilitator or some other category that isn't an employee or volunteer (not a personal guest/family), email bmark@mozilla.com.<br />
*Change fees will be covered by Mozilla for business reasons only. Please email bmark@mozilla.com ahead of calling Egencia to make the change. Any changes for personal reasons must be paid by the employee directly to Egencia over the phone. <br />
<br />
====Arriving Early/Departing Late Guidelines====<br />
<br />
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, January 27 and leave on Saturday, February 1. Here are some exceptions: <br />
<br />
# If you plan to spend some extra '''personal time in Berlin/Europe''' or nearby (choosing to arrive before Monday, Jan 27 or depart after Saturday, Feb 1), you'll need to create a itinerary in Egencia for standard dates/locations within the Egencia Portal and compare to the custom dates/locations you'd like. Pricing for the standard dates should be ''Round Trip only''. Pricing for custom dates/locations should be for ''Round trip or Multi city trips only''. Please share the difference via email to bmark@mozilla.com and receive approval ahead of submission in Egencia. 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 TXL w/ longer dates, and you personally book & cover the rest). Please note that one way trips are only approved on a case by case basis. Do not book one ways without prior approval. ''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 Berlin Tegel than your home airport (ex. a layover in London for a few days, or flying out of something other than TXL). <br />
# If you are attending the '''Sunday/Monday CI event''' (by invite), you can arrive on Sunday, January 26.<br />
# 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.<br />
# If you are celebrating the '''Lunar New Year''', [https://wiki.mozilla.org/All_Hands/Berlin2020#Lunar_New_Year see here].<br />
# If you live in a country where '''work travel is prohibited on weekends''', you may travel on Friday, Jan 24 and Monday, Feb 3, 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). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively. <br />
# If you live in a country where '''work travel is prohibited on Sunday''', you may travel on Saturday, Jam 24, 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). You must have approval from our benefits team in writing (and send to bmark@mozilla.com) '''prior''' to booking any travel. Approvals and expenses will not be applied retroactively.<br />
<br />
====Booking Family Travel====<br />
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.<br />
<br />
'''Direct (recommended):''' <br />
<br />
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.<br />
<br />
'''Via Egencia:'''<br />
<br />
We do not recommend booking family through Egencia. If you'd like details about how to do it, please email bmark@mozilla.com<br />
<br />
'''Notes:''' <br />
<br />
* If your family is arriving on a different flights than you but would like to take advantage of the airport shuttles on Sunday/Monday and/or Saturday, please email their itinerary to mozilla@shworldwide.com.<br />
* We are unable to accommodate volunteer contributor families/guests.<br />
<br />
====Not Flying====<br />
Mozilla will reimburse U-Bahn tickets for those based in the Berlin area for getting to/from hotels. For more information on the U-Bahn, please see the Berlin office guide on [https://mana.mozilla.org/wiki/display/WPR/Berlin+Office+Guide#BerlinOfficeGuide-MovingAroundBerlin mana]. <br />
<br />
For those outside of the Berlin area who are taking the train, please add your name [https://docs.google.com/spreadsheets/d/1A8AKfpdaeD_gVoC6eZfxZoQ4zacgP8l_r9vM04RKyPI/edit#gid=0 here]. We will notify you when train bookings open (on or about Nov 1). You will book train via Egencia FR, UK, DE. <br />
<br />
Parking is not reimbursable.<br />
<br />
====Travel Insurance====<br />
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. <br />
<br />
Mozilla does not cover travel insurance for elancers, upworkers, contractors, vendors, or volunteers/community members (unless required for visa application).<br />
<br />
====Air Travel Fine Print====<br />
*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-877-255-1090 (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.<br />
*Mozilla will '''not''' reimburse for Business/First class upgrades, tickets or seat reservations. <br />
*Mozilla will reimburse for one checked bag each way.<br />
*''Mozilla Frequent Flyer perks do not apply for All Hands''. <br />
*Flights booked outside of Egencia will not be an approved expense unless email approval by Brianna is obtained prior to booking.<br />
*Any submitted expenses needs to have an itinerary attached to ensure it is employee expenses only and within policy.<br />
<br />
====Ground Transportation====<br />
Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00.<br />
<br />
Taxis and Addison Lee are not reimbursable. <br />
<br />
If you are arriving by train to Hauptbahnhof:<br />
To Hotel Berlin Berlin<br />
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S5, S9 or S75 to the station “Zoologischer Garten” (20 min.). From there, take the bus 100 to the stop Lützowplatz. <br />
* Via U-BAHN: Take the U-Bahn metro lines U2, U3 and U1 to the station “U-Nollendorfplatz”. Exit the station in the direction of “Karl-Heinrich-Ulrichs-Straße." The road leads directly to the hotel (approx 5 mins). <br />
* [https://www.hotel-berlin.de/d/berlinberlinpro/media/PDF/Anfahrt_A4_E_Karl-Heinrich-Ulrichs-Strae_5c2ab7.pdf Map]<br />
<br />
To InterCon Berlin and Pullman<br />
* FROM HAUPTBAHNHOF STATION: Take the S-Bahn metro lines S3, S5, S7, or S9 to the station “Zoologischer Garten”. From there, walk 10 mins to hotel.<br />
<br />
Berlin's integrated public transport is divided in 3 tariff zones (ABC). To travel within the city, including from Tegel airport to the hotels, you only need an AB ticket. Tickets can be bought at automated booths in most stations (accept credit cards), and on Metro (need coins). You can use the same ticket to travel on buses, metro, S-Bahn, U-Bahn. More information, including PDF maps, are available on [https://www.berlin.de/en/public-transportation/1772016-2913840-tickets-fares-and-route-maps.en.html this website]. A mobile app is available on stores ("BVG FahrInfo Plus") and allows to create routes between stations, or you can use directly the [https://www.bvg.de/en BVG] website.<br />
<br />
=='''Families/Guests'''==<br />
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. We are unable to accommodate volunteer contributor or intern families/guests at our All Hands. <br />
<br />
====Quick summary logistics====<br />
* Air Travel: Employees do need to book via Egencia regardless of how families are booked. <br />
* Hotel: Family/friends are welcome to stay with you. All room rates are based upon single occupancy and include breakfast. Guests must be added to reservations in advance and any additional room expenses will be yours to cover. Most of our hotel rooms have a maximum of double occupancy (2 adults), with very limited availability of rooms for higher occupancy. Higher occupancy rooms will be assigned in the order that you register. We will have extra rooms available for families to book and pay for at our hotels. <br />
* Lunch & Dinner: Family will be on their own for lunch daily and dinner on Tuesday, Wednesday & Thursday. <br />
* Monday & Friday Night Events: Family members who are registered for the event and registered with the hotel, are invited to join us for our evening events.<br />
* Childcare Services: We will not provide centralized childcare services. We have found that every family has different needs and centralized childcare does not deliver on those needs. If you are in need of help finding options for your family, we are happy to connect you with staff whose families who are coming (#allhands-childcare and #parents are great places to start), as well we are happy to help support finding of resources (although you are likely better at it than us). Given every circumstance is unique, we defer to your manager to determine what Mozilla can support you with financially.<br />
<br />
On demand babysitting services in Berlin: <br />
* https://extra-arms.com/for-families-babysitting/<br />
* https://www.withourbaby.com/<br />
<br />
=='''Lunar New Year'''==<br />
We are aware of the overlap in the Lunar New Year celebrations with the Berlin All Hands. To help folks who decide to attend the Berlin All Hands and who also celebrate Chinese New Year, we will offer the following:<br />
* A higher airfare caps for air travel to allow for fewer layovers on Monday, January 27<br />
* Assurance that Berlin is optional but if employee wants to attend they can shift their holiday days to another time. <br />
* Live Airmo Feeds of Plenary (+ relevant team all hands meetings) + quick posting of recording to accommodate those who choose not to travel. <br />
* Potentially shifting any main plenary session date/time<br />
<br />
We are working with leadership and representatives of those most affected and will update wiki regularly with updates. Feel free to reach out to Brianna with questions.<br />
<br />
=='''Safety & Security'''==<br />
=====Alcohol at Events=====<br />
To better support and sustain an environment (and workplace culture) where people feel safe and included, we have made a set of changes regarding alcohol at our events. In all cases, our approach aligns with our [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] (“CPG”).<br />
*All participants are '''required to read and acknowledge our new Community Participation Guidelines as a condition of participation'''.<br />
*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.<br />
*Team dinners should be '''thoughtful about the potential exclusionary nature of alcohol when planning'''.<br />
*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.<br />
<br />
=====Device Security=====<br />
If you are traveling to the 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)<br />
<br />
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.<br />
<br />
=====Physical Security=====<br />
Badges are required to access all meeting spaces and evening events.<br />
<br />
=='''Accessibility'''==<br />
====Evenings====<br />
Monday Night reception is at the InterContinental Berlin. No stairs or elevators required. <br />
<br />
====Meeting spaces====<br />
* InterCon: Most meeting space levels are accessible by elevators.<br />
* Pullman: All meeting space levels are accessible by guestroom elevators.<br />
* Hotel Berlin: All meeting space is on the ground level.<br />
<br />
====Listen Systems====<br />
We will have Listen Systems available for any meeting in the main plenary space. Visit the AV booth to pick one up.<br />
<br />
====Bathrooms====<br />
TBA <br />
<br />
====Breastfeeding/pumping stations====<br />
Milk Stork Services are reimbursable - please contact benefits@mozilla.com for more information.<br />
<br />
=='''Sustainability'''==<br />
'''Hotel Berlin, Berlin''' is certified partner of visitBerlin we stand for sustainable, green meetings and events. For more information, visit https://convention.visitberlin.de/en/sustain.<br />
<br />
'''InterContinental Hotel Berlin''' is Green Globe Certified. Green Globe Certification is the worldwide sustainability system based on internationally accepted criteria for sustainable operation and management of travel and tourism businesses. Operating under a worldwide license, Green Globe Certification is based in California, USA and is represented in over 83 countries. Green Globe Certification is a member of the Global Sustainable Tourism Council, supported by the United Nations World Tourism Organization. Additonally, as part of IHG’s Green Engage™ program the InterContinental Berlin has implemented best practices at all operational levels. The innovative Environmental Management System not only measures the day-to-day energy, water and waste consumption, but also provides recommended actions – ‘green solutions’ – to improve energy conservation and the property’s carbon footprint score.<br />
<br />
=='''All Hands Expense Policy'''==<br />
1. All "All Hands" Expenses must be submitted on 1 (and only 1) Expense report (e.g. Berlin All Hands Expense Report). Each expense must be tagged with "All Hands - Jan 2020"<br />
<br />
2. It must contain only those expenses relative to the All Hands Event in Berlin. <br />
<br />
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<br />
<br />
4. The deadline to submit the All Hands Expense Report is '''February 28, 2020'''.<br />
<br />
5. Expenses related to team events (except those coordinated through Lisa Carlson), parking, room service, mini-bar charges, and food/drink costs above the vouched amounts, will not be approved. <br />
<br />
<br />
'''The intention of our all hands are to centrally organize a structure that includes:'''<br />
*Meals (2 evening events + breakfast, lunch, drinks and snacks Tuesday - Friday)<br />
*Transportation<br />
*Accommodations<br />
<br />
Expenses submitted can not exceed the approved amounts. Any social events (except dinners/team building activities coordinated through Lisa Carlson) that are not part of our central plan will generally be self-organized and funded by participants. <br />
<br />
=====Travel expenses policy=====<br />
Reimbursement will be made for necessary and reasonable expenses. <br />
<br />
* Getting to/from home to your airport: We ask that you use the most economical option, while balancing your personal needs - whether that be mileage/parking, public transportation or ride shares. We will not reimburse for private towncar services or car rental. <br />
* Per standard Mozilla travel policy, Travel Meal Policy: Employees are eligible for travel meals when traveling. For Meals: There is a $75 USD per day meal policy while traveling. This covers breakfast (est. $15), lunch (est. $20), and dinner (est. $40). Receipts: Receipts are required. When submitting a meal for reimbursement, please include how many people attended the meal. There is no need to include names.<br />
* We will not reimburse for seat/class upgrades. Frequent flyer status does not apply for All Hands. <br />
* We will reimburse for bag checking fees for one bag. <br />
<br />
Any other expenses must be approved by your manager ahead of time. Any expenses for extending your stay for business reasons - such as additional hotel nights, meals, etc must be approved by your manager before booking and travel.<br />
<br />
=====Cell phone reimbursement policy=====<br />
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. <br />
<br />
=====Internet reimbursement policy=====<br />
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.<br />
<br />
=='''Activities'''==</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=All_Hands/Berlin2020/contributors&diff=1219821All Hands/Berlin2020/contributors2019-11-04T18:27:30Z<p>Lucyeoh: Created page with " '''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.''' === Booking Airfare or Trains === We book all business airfare through Egencia. You will create a temporary..."</p>
<hr />
<div><br />
<br />
'''PLEASE BOOK TRAVEL BY AND REGISTER BY FRIDAY, NOVEMBER 15.'''<br />
<br />
=== Booking Airfare or Trains ===<br />
We book all business airfare through Egencia. You will create a temporary travel account for Berlin only, using the instructions below. Trains will not be booked in Egencia. <br />
<br />
Before you book: If you already have an Egencia account, you will NOT be using it to book for All Hands. You will be creating a temporary account for Berlin booking only. Please make sure your login and password are different than any existing account.<br />
<br />
==== To help you choose your flights/travel:====<br />
Fly into and out of Berlin Tegel International Airport (TXL).<br />
You should plan to arrive in Berlin on Monday, January 27, and leave on Saturday, February 1. <br />
Shuttle times: (please keep these times in mind while booking) Berlin Tegel airport is open from 4:00 - 0:00. Shuttles will be provided from Berlin Tegel Airport (TXL) to our 3 hotels on Monday, Jan 27 from 8:00 - 23:00. Shuttles from our 3 hotels to Berlin Tegel will be provided on Saturday, Feb 1 from 4:00 - 20:00. <br />
Other than shuttles, the only thing that happens on Monday is registration and a welcome reception.<br />
You should research whether you need a transit visa if you have a layover or stop in a country that requires it. Common in but not limited to, the United States.<br />
Change fees will not be covered by Mozilla.<br />
All flights must be in Economy Class seats.<br />
You must choose in policy flights (no reg flags). If there are no in policy flights, choose a flight closest in cost the benchmark flight listed.<br />
If you have specific questions about flights or registration, please email Lucy Harris lharris@mozilla.com. <br />
<br />
====Steps to book flights:====<br />
Go here to book your flights. You’ll want to bookmark this to have access until June.<br />
Select “Create an Account for Berlin 2020 Contributors” (second option)<br />
Fill out the form.<br />
* Your name should match your name as it appears on your passport.<br />
* Your Egencia User Name needs to be in email format (but not an actual email - something like contributor@berlinallhands.com).<br />
* Choose Password sign-in.<br />
* Enter your email.<br />
* “Country”: indicate the country you are traveling from.<br />
You will receive an email to set up a password. Set up your password by opening the link in a private window. Check your spam if you don’t see an email. If you don’t see one in spam either (within a few minutes), let Lucy know.<br />
You should now be logged in and able to see the Meeting portal. Click “add a flight” and you can start searching for flights.<br />
<br />
====Booking Trains====<br />
Please book your train ticket direct with the appropriate provider and seek reimbursement (see “Costs” below). <br />
You should arrive in Berlin on Monday, January 27, and leave on Saturday, February 1<br />
Tickets must be booked into second class and upgrades are not reimbursable. <br />
We will not be providing transportation between hotels and train stations. <br />
<br />
===Register:===<br />
Once you have booked flights, please register. The link to register is here. <br />
<br />
Prior to our All Hands, we’d like everyone to read our Community Participation Guidelines. You’ll be asked in registration to check a box confirming you’ve done it and understand that these guidelines are in effect at all Mozilla events.<br />
<br />
===Hotel:===<br />
Hotel details are provided during registration. Once hotel assignments have been made, we’ll communicate the specifics for your hotel. Mozilla will pay for your hotel room with a check in date of Monday, January 27 and a check-out of Saturday, February 1. Please do not try to book hotel through Egencia.<br />
<br />
Note: Volunteers will be sharing a room with another assigned volunteer.<br />
<br />
===Transportation:===<br />
Shuttles will be provided on Monday, January 27 to the hotels from TXL and on Saturday, February 1 to TXL. You will choose transportation in registration. We will not provide transportation from any train stations in Berlin. <br />
<br />
===Costs:===<br />
Mozilla will be covering costs associated with your participation in the All Hands. This includes costs of obtaining a visa, if that’s applicable. We will reimburse for a maximum of one visa application per person.<br />
<br />
If you need this paid out as an advance, please email me to let me know. If you can wait until costs are incurred, please wait for reimbursement instructions in a future email.<br />
<br />
===Visa information:===<br />
If you need a visa for travelling to Germany, it is your responsibility to arrange one (though we will cover the costs). Please visit the wiki for more information: https://wiki.mozilla.org/All_Hands/Berlin2020#Immigration. <br />
<br />
You will be able to request an invitation letter through the registration form. If getting a visa requires an interview before your hotel confirmation arrives -- please ensure you are registered and then email us ASAP. Please email me once your appointment is booked (no need to email if no interview is required).<br />
<br />
===Finding answers:===<br />
The information you receive in email will live in a permanent state on the wiki here (although keep in mind, your information as a contributor is slightly different than most employees). It’s the primary source of all that you need to know about Berlin.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Contribute&diff=1219720Contribute2019-10-31T15:27:46Z<p>Lucyeoh: /* Specialist Programs & Funding Programs: */</p>
<hr />
<div>Thanks for your interest in contributing to Mozilla! The Mozilla Project welcomes contributions from everyone who shares our goals and wants to contribute in a healthy and constructive manner within our community. As such, we require all those who participate to agree to adhere to the [http://Community%20Participation%20Guidelineshttps://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines] in order to help us create a safe and positive community experience for all. <br />
<br />
== Quick Start: == <br />
<br />
'''To make a technical contribution''':<br />
<br />
* Contribute to the Mozilla code base -> [https://developer.mozilla.org/en-US/docs/Mozilla/Developer_guide/Introduction Introduction] <br />
* Find your first code contribution -> [http://codetribute.mozilla.org codetribute.mozilla.org]<br />
* Contribute documentation to the Mozilla Developer Network -> [https://developer.mozilla.org/en-US/ developer.mozilla.org]<br />
* Contribute your design to an open design community -> [https://github.com/mozilla/OpenDesign/ github.com/mozilla/OpenDesign/]<br />
<br />
'''To make a non-technical contribution''':<br />
* Localize Mozilla into your language -> [https://pontoon.mozilla.org/ pontoon.mozilla.org] <br />
* Help support users from the comfort of your couch by answering questions and/or writing and translating support articles -> [https://support.mozilla.org/en-US/get-involved support.mozilla.org]<br />
* Support Mozilla's mission - find impactful, fun ways to get involved right away on Activate Mozilla -> [https://activate.mozilla.community/ activate.mozilla.community]<br />
<br />
== Specialist Programs & Funding Programs: == <br />
''As a critical part of the mission, Mozilla invests in innovators and projects working to make the internet more open, inclusive, decentralized, and secure. These programs each have their own set of requirements and application process, please read carefully.''<br />
<br />
Available by application: <br />
* [https://events.mozilla.org/techspeakers/ Tech Speakers] - For volunteer technical advocates and educators who are interested in informing others about the open web and Mozilla products and technologies.<br />
* [https://reps.mozilla.org/ Reps program] - For contributors who are already regularly organizing community events and mobilizing in their communities.<br />
* [https://foundation.mozilla.org/fellowships/ Fellowships] - For web activists, open-source researchers and scientists, and technology policy experts who work on the front lines of the internet health movement.<br />
* [https://research.mozilla.org/ Research Grants & Sponsorships] - For universities, labs and research-focused registered non-profits working to make the internet a better place.<br />
* [https://foundation.mozilla.org/en/awards/ Mozilla Awards] - For open source projects that contribute to Mozilla’s work and to the health of the Internet.<br />
* [https://www.mozilla.org/en-US/moss/ Mozilla's Open Source Support Awards]- provide catalytic funding to open source technologists. <br />
* [https://careers.mozilla.org/university/ Student Internships] - For university/college students looking to intern with Mozilla. <br />
* [https://wiki.mozilla.org/Outreachy Outreachy] - For members of under-represented groups who want to intern in free and open source software. <br />
* [https://wiki.mozilla.org/SummerOfCode Summer of Code] - For student developers who want to work with an open source organization on a 3 month programming project during their break from school.<br />
* [http://ossn.club/ Open Source Student Network] - A Network of university and college Clubs and students who are passionate about Open Source and eager to learn about, contribute to and create Open Source projects.<br />
* [https://wiki.mozilla.org/Engagement/Developer_Engagement/Event_request_guidelines Developer Engagement Events] - for people seeking speakers or sponsorship for developer-oriented events. <br />
<br />
<br />
<br />
<br />
Still can’t find what you’re looking for? Check out the conversations on [https://discourse.mozilla.org/ the Mozilla Discourse].<br />
<br />
==Contribution areas==<br />
<br />
Here we’ve compiled a directory of ways you can get involved and contribute to Mozilla and some featured projects to get you started:<br />
<br />
Here is a list of projects in Mozilla organized by contribution area, note that Mozilla changes rapidly and some of this information may be out of date. Click the contribution topics to reveal the teams and projects below:<br />
<br />
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"<br />
!colspan="9"|Coding<br />
|-<br />
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address <br />
|-<br />
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources<br />
|-<br />
| General - Firefox || Firefox || #introduction || mhoye || [https://mozillians.org/en-US/u/mhoye/ Mike Hoye] || [https://developer.mozilla.org/en-US/docs/Introduction Introduction] || N/A || N/A <br />
|-<br />
| Add-Ons || Firefox Add-ons || #amo, #addons, #addon-reviewers, #webextensions || caitmuenster|| [https://mozillians.org/en-US/u/amyt/ Amy Tsay] || [https://addons.mozilla.org/en-US/firefox/ addons.mozilla.org] || [[Add-ons/Contribute]] || N/A <br />
|-<br />
| Web Compatibility || Diagnosing Web Compatibility Issues ||webcompat || miketaylr || [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [https://webcompat.com/ webcompat.com] || N/A || N/A <br />
|-<br />
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"<br />
!colspan="9"|Testing<br />
|-<br />
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address <br />
|-<br />
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources<br />
|-<br />
| Add-Ons ||Testing for Firefox Add-Ons || addons, amo || caitmuenster || [https://mozillians.org/en-US/u/amyt/ Amy Tsay] ||[https://addons.mozilla.org/en-US/firefox/ addons.mozilla.org] || [[https://wiki.mozilla.org/Add-ons/Contribute#Test_add-ons|Add-ons/Contribute]] || N/A <br />
|-<br />
| Web Compatibility ||Testing Web Compatibility Issues || webcompat || miketaylr || [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [https://webcompat.com/ webcompat] || N/A || N/A <br />
|-<br />
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"<br />
!colspan="9"|Localization<br />
|-<br />
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address <br />
|-<br />
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources<br />
|-<br />
| 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]] <br/> [[L10n:Localization_Process]]<br />
|-<br />
| Web Localization ||Web Localization || [[L10n:Contribute#Mozilla_web_sites]] <br/> [[L10n:Web_parts]]<br />
|-<br />
| Localization Tools Dev ||Localization Tools Dev || [[Contribute#Mozilla_l10n_development_projects]] || N/A <br />
|-<br />
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"<br />
!colspan="9"|Helping<br />
|-<br />
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address <br />
|-<br />
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources<br />
|-<br />
| User Support ||SUMO || sumo || madalina || [https://mozillians.org/en-US/u/mana/ Madalina Ana]|| [http://support.mozilla.org/ support.mozilla.org] || [[Support]] || [http://blog.mozilla.org/sumo/ blog.mozilla.org/sumo]<br />
|-<br />
| Web Compatibility ||Help Make Websites Firefox Compatible || webcompat || miketaylr || [https://mozillians.org/en-US/u/miketaylr/ Mike Taylor] || [http://webcompat.com/contributors webcompat.com/contributors] || [[Compatibility]] || N/A <br />
|-<br />
{|class="wikitable collapsible collapsed" style="width:100%;text-align: center;"<br />
!colspan="9"|Writing <br />
|-<br />
! rowspan="2"|Area!! rowspan="2"|Project Name!! IRC Room!! IRC Contact Person!! rowspan="2"|Steward!! colspan="3"|Relevant web address <br />
|-<br />
| colspan="2"|See [http://irc.mozilla.org irc.mozilla.org] on how to access it || Project's website || wiki page || Other Resources<br />
|-<br />
| Tech Documentation for Users ||Technical Documentation for Users || sumo || Madalina || [https://mozillians.org/en-US/u/mana/ Madalina Ana] || [https://support.mozilla.org/get-involved get involved] || [[Support]] || [http://blog.mozilla.org/sumo/ SUMO blog] <br />
|-<br />
| 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 <br />
|-<br />
| AddOns ||Technical Documentation for Add-Ons || amyt ||[https://mozillians.org/en-US/u/amyt/ Amy Tsay] || |N/A || [[Add-ons/Contribute#Help_add-on_developers|Add-ons/Contribute]] || N/A <br />
|-<br />
<br />
<br />
Still can’t find what you’re looking for? Check out the conversations on [https://discourse.mozilla.org/ the Mozilla Discourse].<br />
<br />
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. <br />
<br />
<br />
''Looking for content from the old page? You can find it in the archive [[Contributearchive|HERE]].''</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Mission-Driven_Mozillians_Strategy&diff=1219704Innovation/Projects/Mission-Driven Mozillians Strategy2019-10-30T21:17:37Z<p>Lucyeoh: /* MDM Projects */</p>
<hr />
<div>=== What is the Mission-Driven Mozillians strategy program?===<br />
<br />
This program, driven by the Community Development Team (part of the [[Open Innovation Team]]), aims at driving forward the creation of a modern unified contributor experience for Mission-Driven Mozillians.<br />
<br />
'''Mission-Driven Mozillians are a persona of contributors who:'''<br />
* Regularly contribute to a number of activities in support of Mozilla’s mission<br />
* Are highly invested in Mozilla as an organization and a mission<br />
* Contribute in multiple areas (either sequentially or simultaneously)<br />
* Have Mozilla at the core of their community identities<br />
<br />
While there are Mission Driven Mozillians in many areas of the project, the major areas of activity for this persona are: evangelizing, teaching, advocating, localizing, documenting, community building and doing testing.<br />
<br />
''If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.''<br />
<br />
=== Goal ===<br />
The goal of this project is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
<br />
This proposal is different to anything we have done in the past, we want to address the issues identified in the research, and create a revised approach that is a shared across the organization.<br />
<br />
(This is also communicated through the video [https://www.youtube.com/watch?v=E_vAIPkVTHE Intro to Mission Driven Mozillians]).<br />
<br />
=== Our Vision ===<br />
<br />
By 2020, a healthy global community of Mozillians is bringing benefits for our mission that none of our “competitors” can match and is a formidable foundation serving the movement for an open internet.<br />
<br />
Mission Driven Mozillians will have impact on Mozilla projects by adding capacity beyond our means, sharing global perspective and ideas, and extending our reach into valuable networks. Furthermore by growing and empowering a community of people who truly put Mozilla’s mission first, we’ll discover new and wonderful value that we cannot currently predict.<br />
<br />
Participating as a Mozillian will be deeply rewarding and fun. It will be easy to find and make valuable contributions to important projects.<br />
<br />
Communities will be healthy and inclusive environments that support individual growth and bring out the best in all Mozillians. Staff teams will find it clear, effective and rewarding to engage with Mozillians.<br />
<br />
=== Background ===<br />
<br />
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&amp;I community research, which produced the [https://docs.google.com/document/d/1ZK7l4e9-UVTMacxmmCzA8pDqVfsZOahkBC6eIOsRQyc/edit State of Diversity & Inclusion] report. Community as well as additional interviews &amp; research with key staff members and volunteers.<br />
<br />
This produced the most extensive understanding of Mozilla’s contributor communities ever and two key insights that created this work: <br />
<br />
* There are a large number of contributors who regularly contribute to a number of activities in support of Mozilla’s mission, are highly invested in Mozilla as an organization and a mission, contribute in multiple areas (either sequentially or simultaneously). We called this profile of contributor “Mission Driven Mozillians” to reflect their reported motivating force, which was advancing Mozilla’s Mission. <br />
* The way Mozilla’s teams and projects are structured does NOT making it easy for Mission Driven Mozillians to be successful.<br />
<br />
[https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Additional background]<br />
<br />
''This project was formerly known as "Non-coding Enthusiast communities and contributors".''<br />
<br />
=== Who’s Involved ===<br />
<br />
'''The project is being driven by''' - Lucy Harris (with support from George Roter)<br />
<br />
'''The decision-maker is''' - Lucy Harris<br />
<br />
'''Agreement is to be sought from''' - Ruben Martin, Katharina Borchert, Chris Beard, Mitchell Baker and the Reps Module Owner<br />
<br />
'''Input &amp; Consultation'''- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, D&amp;I Staff, Mozilla Foundation Staff.<br />
<br />
=== Approach ===<br />
<br />
The approach is to work with staff and contributors to gradually address each of the project themes. In each project we will follow the [https://toolkit.mozilla.org/ open design] approach of: <br />
<br />
# Gathering insights <br />
# Ideating Solutions<br />
# Testing & Implementing <br />
<br />
At each step we will gather insights and hold discussions with members of Mozilla communities.<br />
<br />
=== Project Themes ===<br />
<br />
Both proposal &amp; strategy will be based around the following 7 project themes(*):<br />
<br />
# '''Group Identities:''' How do we create a process for recognizing groups, that emphasises inclusivity while allowing volunteers the freedom to create and manage structures that reflect their interests and identities?<br />
# '''Metrics''': How can we increase our understanding of the impact and health of Mozillian communities?<br />
# '''Diversity & Inclusion''': How do we create a set of processes, standards, and workflows that make Mozilla’s communities more inclusive?<br />
# '''Volunteer Leadership''': How can shared agreements and approaches to volunteer leadership create healthier, more impactful communities?<br />
# '''Recognition''': How can cohesive approaches to recognition create a more rewarding contribution experience for more people? <br />
# '''Resource Distribution''': How do we create standards and systems that make resource distribution fair and consistent across the project? <br />
# '''Contributor Journey & Opportunity Matching''': How do we connect more people to higher impact contribution opportunities? How can we make it easy to join the community? <br />
<br />
(*)The project themes were updated from 10 to 7 in January 2018. To see how they evolved click [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 here]. <br />
=== MDM Projects ===<br />
A number of major projects have been created as a direct result of this strategy. Here are some relevant links: <br />
<br />
* [[Volunteer_leadership_principles|Volunteer Leadership Principles]] #leadership #D&I <br />
* [https://events.mozilla.org/pilot Group Pilot] #groupidentities<br />
* [[Diversity_and_Inclusion_for_Communities_and_Contributors|D&I resources, reports, calls & trainings]] #D&I<br />
* [https://activate.mozilla.community/ Activate activities & campaigns] #contribjourney&matching<br />
* [https://activate.mozilla.community/newsletter Campaigns mailing list] #contribjourney&matching<br />
* [https://blog.mozilla.org/mozillareps/2018/10/10/community-coordinator-role/ Reps Evolution] #leadership<br />
* [[Innovation/Projects/Community_Portal|Community Portal]] #groupidentities #contribjourney&matching<br />
<br />
=== Stay Connected ===<br />
If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.<br />
<br />
Helpful Posts: <br />
* [https://discourse.mozilla.org/c/community-portal Mozilla Community Portal] <br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2019-update/35430 Mission Driven Mozillians 2019 Update]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 Mission Driven Mozillians 2018 Update]<br />
* [https://blog.mozilla.org/sumo/2017/11/23/non-coding-volunteers-mission-driven-mozillians-community-coordinators-sumo/ Non-coding Volunteers, Mission-driven Mozillians, Community Coordinators & SUMO]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Mission Driven Mozillians Communities Proposal]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-volunteer-leadership-principles-practices/22386 Mission Driven Mozillians - volunteer leadership proposal]<br />
* [https://www.youtube.com/watch?v=E_vAIPkVTHE Watch the video Intro to Mission Driven Mozillians]</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Community_Portal&diff=1219703Innovation/Projects/Community Portal2019-10-30T21:14:24Z<p>Lucyeoh: /* Goal */</p>
<hr />
<div><br />
== What is the Community Portal ==<br />
'''The Mozillian Community Portal''' is an initiative led by the Community Development Team in Open Innovation. It is part of the [[Innovation/Projects/Mission-Driven_Mozillians_Strategy|Mission Driven Mozillians project]] the goal of which is to work with teams and communities to create modern structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
[[File:Communityportal2.jpg|500px|right]]<br />
<br />
== Goal ==<br />
<br />
The goal of the community portal is to create a central place for Mozillians to be able to find, discover opportunities and collaborate across community members & groups.<br />
<br />
The portal will be a place to discover community events, groups, contribution opportunities and individual profiles. <br />
<br />
[[File:Wireframe Events Page.png|500px|right]]<br />
<br />
<br />
Development will be through an open process starting in August 2019, with an estimated V1 release date in early 2020. <br />
<br />
'''We publish weekly updates on the development of the portal on [https://discourse.mozilla.org/c/community-portal discourse].'''<br />
<br />
'''Find the [https://discourse.mozilla.org/t/frequently-asked-questions-portal-edition-faq/43224/4 FAQ] here.'''</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Community_Portal&diff=1219702Innovation/Projects/Community Portal2019-10-30T21:13:58Z<p>Lucyeoh: /* What is the Community Portal */</p>
<hr />
<div><br />
== What is the Community Portal ==<br />
'''The Mozillian Community Portal''' is an initiative led by the Community Development Team in Open Innovation. It is part of the [[Innovation/Projects/Mission-Driven_Mozillians_Strategy|Mission Driven Mozillians project]] the goal of which is to work with teams and communities to create modern structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
[[File:Communityportal2.jpg|500px|right]]<br />
<br />
== Goal ==<br />
<br />
The goal of the community portal is to create a central place for Mozillians to be able to find, discover opportunities and collaborate across community members & groups.<br />
<br />
The portal will be a centralized place to discover community events, groups, contribution opportunities and individual profiles. <br />
<br />
[[File:Wireframe Events Page.png|500px|right]]<br />
<br />
<br />
Development will be through an open process starting in August 2019, with an estimated V1 release date in early 2020. <br />
<br />
'''We publish weekly updates on the development of the portal on [https://discourse.mozilla.org/c/community-portal discourse].'''<br />
<br />
'''Find the [https://discourse.mozilla.org/t/frequently-asked-questions-portal-edition-faq/43224/4 FAQ] here.'''</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Mission-Driven_Mozillians_Strategy&diff=1219701Innovation/Projects/Mission-Driven Mozillians Strategy2019-10-30T21:04:06Z<p>Lucyeoh: </p>
<hr />
<div>=== What is the Mission-Driven Mozillians strategy program?===<br />
<br />
This program, driven by the Community Development Team (part of the [[Open Innovation Team]]), aims at driving forward the creation of a modern unified contributor experience for Mission-Driven Mozillians.<br />
<br />
'''Mission-Driven Mozillians are a persona of contributors who:'''<br />
* Regularly contribute to a number of activities in support of Mozilla’s mission<br />
* Are highly invested in Mozilla as an organization and a mission<br />
* Contribute in multiple areas (either sequentially or simultaneously)<br />
* Have Mozilla at the core of their community identities<br />
<br />
While there are Mission Driven Mozillians in many areas of the project, the major areas of activity for this persona are: evangelizing, teaching, advocating, localizing, documenting, community building and doing testing.<br />
<br />
''If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.''<br />
<br />
=== Goal ===<br />
The goal of this project is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
<br />
This proposal is different to anything we have done in the past, we want to address the issues identified in the research, and create a revised approach that is a shared across the organization.<br />
<br />
(This is also communicated through the video [https://www.youtube.com/watch?v=E_vAIPkVTHE Intro to Mission Driven Mozillians]).<br />
<br />
=== Our Vision ===<br />
<br />
By 2020, a healthy global community of Mozillians is bringing benefits for our mission that none of our “competitors” can match and is a formidable foundation serving the movement for an open internet.<br />
<br />
Mission Driven Mozillians will have impact on Mozilla projects by adding capacity beyond our means, sharing global perspective and ideas, and extending our reach into valuable networks. Furthermore by growing and empowering a community of people who truly put Mozilla’s mission first, we’ll discover new and wonderful value that we cannot currently predict.<br />
<br />
Participating as a Mozillian will be deeply rewarding and fun. It will be easy to find and make valuable contributions to important projects.<br />
<br />
Communities will be healthy and inclusive environments that support individual growth and bring out the best in all Mozillians. Staff teams will find it clear, effective and rewarding to engage with Mozillians.<br />
<br />
=== Background ===<br />
<br />
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&amp;I community research, which produced the [https://docs.google.com/document/d/1ZK7l4e9-UVTMacxmmCzA8pDqVfsZOahkBC6eIOsRQyc/edit State of Diversity & Inclusion] report. Community as well as additional interviews &amp; research with key staff members and volunteers.<br />
<br />
This produced the most extensive understanding of Mozilla’s contributor communities ever and two key insights that created this work: <br />
<br />
* There are a large number of contributors who regularly contribute to a number of activities in support of Mozilla’s mission, are highly invested in Mozilla as an organization and a mission, contribute in multiple areas (either sequentially or simultaneously). We called this profile of contributor “Mission Driven Mozillians” to reflect their reported motivating force, which was advancing Mozilla’s Mission. <br />
* The way Mozilla’s teams and projects are structured does NOT making it easy for Mission Driven Mozillians to be successful.<br />
<br />
[https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Additional background]<br />
<br />
''This project was formerly known as "Non-coding Enthusiast communities and contributors".''<br />
<br />
=== Who’s Involved ===<br />
<br />
'''The project is being driven by''' - Lucy Harris (with support from George Roter)<br />
<br />
'''The decision-maker is''' - Lucy Harris<br />
<br />
'''Agreement is to be sought from''' - Ruben Martin, Katharina Borchert, Chris Beard, Mitchell Baker and the Reps Module Owner<br />
<br />
'''Input &amp; Consultation'''- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, D&amp;I Staff, Mozilla Foundation Staff.<br />
<br />
=== Approach ===<br />
<br />
The approach is to work with staff and contributors to gradually address each of the project themes. In each project we will follow the [https://toolkit.mozilla.org/ open design] approach of: <br />
<br />
# Gathering insights <br />
# Ideating Solutions<br />
# Testing & Implementing <br />
<br />
At each step we will gather insights and hold discussions with members of Mozilla communities.<br />
<br />
=== Project Themes ===<br />
<br />
Both proposal &amp; strategy will be based around the following 7 project themes(*):<br />
<br />
# '''Group Identities:''' How do we create a process for recognizing groups, that emphasises inclusivity while allowing volunteers the freedom to create and manage structures that reflect their interests and identities?<br />
# '''Metrics''': How can we increase our understanding of the impact and health of Mozillian communities?<br />
# '''Diversity & Inclusion''': How do we create a set of processes, standards, and workflows that make Mozilla’s communities more inclusive?<br />
# '''Volunteer Leadership''': How can shared agreements and approaches to volunteer leadership create healthier, more impactful communities?<br />
# '''Recognition''': How can cohesive approaches to recognition create a more rewarding contribution experience for more people? <br />
# '''Resource Distribution''': How do we create standards and systems that make resource distribution fair and consistent across the project? <br />
# '''Contributor Journey & Opportunity Matching''': How do we connect more people to higher impact contribution opportunities? How can we make it easy to join the community? <br />
<br />
(*)The project themes were updated from 10 to 7 in January 2018. To see how they evolved click [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 here]. <br />
=== MDM Projects ===<br />
A number of major projects have been created as a direct result of this strategy. Here are some relevant links: <br />
<br />
* [[Volunteer_leadership_principles|Volunteer Leadership Principles]] #leadership #D&I <br />
* [https://events.mozilla.org/pilot Group Pilot] #groupidentities<br />
* [[Diversity_and_Inclusion_for_Communities_and_Contributors|D&I resources, reports, calls & trainings]] #D&I<br />
* [https://activate.mozilla.community/ Activate activities & campaigns] #contribjourney&matching<br />
* [https://activate.mozilla.community/newsletter Campaigns mailing list] #contribjourney&matching<br />
* [[Innovation/Projects/Community_Portal|Community Portal]] #groupidentities #contribjourney&matching<br />
<br />
=== Stay Connected ===<br />
If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.<br />
<br />
Helpful Posts: <br />
* [https://discourse.mozilla.org/c/community-portal Mozilla Community Portal] <br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2019-update/35430 Mission Driven Mozillians 2019 Update]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 Mission Driven Mozillians 2018 Update]<br />
* [https://blog.mozilla.org/sumo/2017/11/23/non-coding-volunteers-mission-driven-mozillians-community-coordinators-sumo/ Non-coding Volunteers, Mission-driven Mozillians, Community Coordinators & SUMO]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Mission Driven Mozillians Communities Proposal]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-volunteer-leadership-principles-practices/22386 Mission Driven Mozillians - volunteer leadership proposal]<br />
* [https://www.youtube.com/watch?v=E_vAIPkVTHE Watch the video Intro to Mission Driven Mozillians]</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Mission-Driven_Mozillians_Strategy&diff=1219700Innovation/Projects/Mission-Driven Mozillians Strategy2019-10-30T20:46:03Z<p>Lucyeoh: /* MDM Projects */</p>
<hr />
<div>=== What is the Mission-Driven Mozillians strategy program?===<br />
<br />
This program, driven by the Community Development Team (part of the [[Open Innovation Team]]), aims at driving forward the creation of a modern unified contributor experience for Mission-Driven Mozillians.<br />
<br />
'''Mission-Driven Mozillians are a persona of contributors who:'''<br />
* Regularly contribute to a number of activities in support of Mozilla’s mission<br />
* Are highly invested in Mozilla as an organization and a mission<br />
* Contribute in multiple areas (either sequentially or simultaneously)<br />
* Have Mozilla at the core of their community identities<br />
<br />
While there are Mission Driven Mozillians in many areas of the project, the major areas of activity for this persona are: evangelizing, teaching, advocating, localizing, documenting, community building and doing testing.<br />
<br />
''If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.''<br />
<br />
=== Goal ===<br />
The goal of this project is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
<br />
This proposal is different to anything we have done in the past, we want to address the issues identified in the research, and create a revised approach that is a shared across the organization.<br />
<br />
(This is also communicated through the video [https://www.youtube.com/watch?v=E_vAIPkVTHE Intro to Mission Driven Mozillians]).<br />
<br />
=== Our Vision ===<br />
<br />
By 2020, a healthy global community of Mozillians is bringing benefits for our mission that none of our “competitors” can match and is a formidable foundation serving the movement for an open internet.<br />
<br />
Mission Driven Mozillians will have impact on Mozilla projects by adding capacity beyond our means, sharing global perspective and ideas, and extending our reach into valuable networks. Furthermore by growing and empowering a community of people who truly put Mozilla’s mission first, we’ll discover new and wonderful value that we cannot currently predict.<br />
<br />
Participating as a Mozillian will be deeply rewarding and fun. It will be easy to find and make valuable contributions to important projects.<br />
<br />
Communities will be healthy and inclusive environments that support individual growth and bring out the best in all Mozillians. Staff teams will find it clear, effective and rewarding to engage with Mozillians.<br />
<br />
=== Background ===<br />
<br />
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&amp;I community research, which produced the [https://docs.google.com/document/d/1ZK7l4e9-UVTMacxmmCzA8pDqVfsZOahkBC6eIOsRQyc/edit State of Diversity & Inclusion] report. Community as well as additional interviews &amp; research with key staff members and volunteers.<br />
<br />
This produced the most extensive understanding of Mozilla’s contributor communities ever and two key insights that created this work: <br />
<br />
* There are a large number of contributors who regularly contribute to a number of activities in support of Mozilla’s mission, are highly invested in Mozilla as an organization and a mission, contribute in multiple areas (either sequentially or simultaneously). We called this profile of contributor “Mission Driven Mozillians” to reflect their reported motivating force, which was advancing Mozilla’s Mission. <br />
* The way Mozilla’s teams and projects are structured does NOT making it easy for Mission Driven Mozillians to be successful.<br />
<br />
[https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Additional background]<br />
<br />
''This project was formerly known as "Non-coding Enthusiast communities and contributors".''<br />
<br />
=== Who’s Involved ===<br />
<br />
'''The project is being driven by''' - Lucy Harris (with support from George Roter)<br />
<br />
'''The decision-maker is''' - Lucy Harris<br />
<br />
'''Agreement is to be sought from''' - Ruben Martin, Katharina Borchert, Chris Beard, Mitchell Baker and the Reps Module Owner<br />
<br />
'''Input &amp; Consultation'''- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, D&amp;I Staff, Mozilla Foundation Staff.<br />
<br />
=== Approach ===<br />
<br />
The approach is to work with staff and contributors to gradually address each of the project themes. In each project we will follow the [https://toolkit.mozilla.org/ open design] approach of: <br />
<br />
# Gathering insights <br />
# Ideating Solutions<br />
# Testing & Implementing <br />
<br />
At each step we will gather insights and hold discussions with members of Mozilla communities.<br />
<br />
=== Project Themes ===<br />
<br />
Both proposal &amp; strategy will be based around the following 7 project themes(*):<br />
<br />
# '''Group Identities:''' How do we create a process for recognizing groups, that emphasises inclusivity while allowing volunteers the freedom to create and manage structures that reflect their interests and identities?<br />
# '''Metrics''': How can we increase our understanding of the impact and health of Mozillian communities?<br />
# '''Diversity & Inclusion''': How do we create a set of processes, standards, and workflows that make Mozilla’s communities more inclusive?<br />
# '''Volunteer Leadership''': How can shared agreements and approaches to volunteer leadership create healthier, more impactful communities?<br />
# '''Recognition''': How can cohesive approaches to recognition create a more rewarding contribution experience for more people? <br />
# '''Resource Distribution''': How do we create standards and systems that make resource distribution fair and consistent across the project? <br />
# '''Contributor Journey & Opportunity Matching''': How do we connect more people to higher impact contribution opportunities? How can we make it easy to join the community? <br />
<br />
(*)The project themes were updated from 10 to 7 in January 2018. To see how they evolved click [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 here]. <br />
=== MDM Projects ===<br />
A number of major projects have been created as a direct result of this strategy. Here are some relevant links: <br />
* [[Innovation/Projects/Community_Portal|Community Portal]] #groupidentities #contribjourney&matching<br />
* [[Volunteer_leadership_principles|Volunteer Leadership Principles]] #leadership #D&I <br />
* [https://events.mozilla.org/pilot Group Pilot] #groupidentities<br />
* [[Diversity_and_Inclusion_for_Communities_and_Contributors|D&I resources, reports, calls & trainings]] #D&I<br />
* [https://activate.mozilla.community/ Activate activities & campaigns] #contribjourney&matching<br />
* [https://activate.mozilla.community/newsletter Campaigns mailing list] #contribjourney&matching<br />
<br />
=== Stay Connected ===<br />
If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.<br />
<br />
Helpful Posts: <br />
* [https://discourse.mozilla.org/c/community-portal Mozilla Community Portal] <br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2019-update/35430 Mission Driven Mozillians 2019 Update]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 Mission Driven Mozillians 2018 Update]<br />
* [https://blog.mozilla.org/sumo/2017/11/23/non-coding-volunteers-mission-driven-mozillians-community-coordinators-sumo/ Non-coding Volunteers, Mission-driven Mozillians, Community Coordinators & SUMO]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Mission Driven Mozillians Communities Proposal]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-volunteer-leadership-principles-practices/22386 Mission Driven Mozillians - volunteer leadership proposal]<br />
* [https://www.youtube.com/watch?v=E_vAIPkVTHE Watch the video Intro to Mission Driven Mozillians]</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Mission-Driven_Mozillians_Strategy&diff=1219680Innovation/Projects/Mission-Driven Mozillians Strategy2019-10-30T14:22:02Z<p>Lucyeoh: /* Who’s Involved */</p>
<hr />
<div>=== What is the Mission-Driven Mozillians strategy program?===<br />
<br />
This program, driven by the Community Development Team (part of the [[Open Innovation Team]]), aims at driving forward the creation of a modern unified contributor experience for Mission-Driven Mozillians.<br />
<br />
'''Mission-Driven Mozillians are a persona of contributors who:'''<br />
* Regularly contribute to a number of activities in support of Mozilla’s mission<br />
* Are highly invested in Mozilla as an organization and a mission<br />
* Contribute in multiple areas (either sequentially or simultaneously)<br />
* Have Mozilla at the core of their community identities<br />
<br />
While there are Mission Driven Mozillians in many areas of the project, the major areas of activity for this persona are: evangelizing, teaching, advocating, localizing, documenting, community building and doing testing.<br />
<br />
''If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.''<br />
<br />
=== Goal ===<br />
The goal of this project is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
<br />
This proposal is different to anything we have done in the past, we want to address the issues identified in the research, and create a revised approach that is a shared across the organization.<br />
<br />
(This is also communicated through the video [https://www.youtube.com/watch?v=E_vAIPkVTHE Intro to Mission Driven Mozillians]).<br />
<br />
=== Our Vision ===<br />
<br />
By 2020, a healthy global community of Mozillians is bringing benefits for our mission that none of our “competitors” can match and is a formidable foundation serving the movement for an open internet.<br />
<br />
Mission Driven Mozillians will have impact on Mozilla projects by adding capacity beyond our means, sharing global perspective and ideas, and extending our reach into valuable networks. Furthermore by growing and empowering a community of people who truly put Mozilla’s mission first, we’ll discover new and wonderful value that we cannot currently predict.<br />
<br />
Participating as a Mozillian will be deeply rewarding and fun. It will be easy to find and make valuable contributions to important projects.<br />
<br />
Communities will be healthy and inclusive environments that support individual growth and bring out the best in all Mozillians. Staff teams will find it clear, effective and rewarding to engage with Mozillians.<br />
<br />
=== Background ===<br />
<br />
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&amp;I community research, which produced the [https://docs.google.com/document/d/1ZK7l4e9-UVTMacxmmCzA8pDqVfsZOahkBC6eIOsRQyc/edit State of Diversity & Inclusion] report. Community as well as additional interviews &amp; research with key staff members and volunteers.<br />
<br />
This produced the most extensive understanding of Mozilla’s contributor communities ever and two key insights that created this work: <br />
<br />
* There are a large number of contributors who regularly contribute to a number of activities in support of Mozilla’s mission, are highly invested in Mozilla as an organization and a mission, contribute in multiple areas (either sequentially or simultaneously). We called this profile of contributor “Mission Driven Mozillians” to reflect their reported motivating force, which was advancing Mozilla’s Mission. <br />
* The way Mozilla’s teams and projects are structured does NOT making it easy for Mission Driven Mozillians to be successful.<br />
<br />
[https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Additional background]<br />
<br />
''This project was formerly known as "Non-coding Enthusiast communities and contributors".''<br />
<br />
=== Who’s Involved ===<br />
<br />
'''The project is being driven by''' - Lucy Harris (with support from George Roter)<br />
<br />
'''The decision-maker is''' - Lucy Harris<br />
<br />
'''Agreement is to be sought from''' - Ruben Martin, Katharina Borchert, Chris Beard, Mitchell Baker and the Reps Module Owner<br />
<br />
'''Input &amp; Consultation'''- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, D&amp;I Staff, Mozilla Foundation Staff.<br />
<br />
=== Approach ===<br />
<br />
The approach is to work with staff and contributors to gradually address each of the project themes. In each project we will follow the [https://toolkit.mozilla.org/ open design] approach of: <br />
<br />
# Gathering insights <br />
# Ideating Solutions<br />
# Testing & Implementing <br />
<br />
At each step we will gather insights and hold discussions with members of Mozilla communities.<br />
<br />
=== Project Themes ===<br />
<br />
Both proposal &amp; strategy will be based around the following 7 project themes(*):<br />
<br />
# '''Group Identities:''' How do we create a process for recognizing groups, that emphasises inclusivity while allowing volunteers the freedom to create and manage structures that reflect their interests and identities?<br />
# '''Metrics''': How can we increase our understanding of the impact and health of Mozillian communities?<br />
# '''Diversity & Inclusion''': How do we create a set of processes, standards, and workflows that make Mozilla’s communities more inclusive?<br />
# '''Volunteer Leadership''': How can shared agreements and approaches to volunteer leadership create healthier, more impactful communities?<br />
# '''Recognition''': How can cohesive approaches to recognition create a more rewarding contribution experience for more people? <br />
# '''Resource Distribution''': How do we create standards and systems that make resource distribution fair and consistent across the project? <br />
# '''Contributor Journey & Opportunity Matching''': How do we connect more people to higher impact contribution opportunities? How can we make it easy to join the community? <br />
<br />
(*)The project themes were updated from 10 to 7 in January 2018. To see how they evolved click [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 here]. <br />
=== MDM Projects ===<br />
A number of major projects have been created as a direct result of this strategy. Here are some relevant links: <br />
* [[Innovation/Projects/Community_Portal|Community Portal]]<br />
* [[Volunteer_leadership_principles|Volunteer Leadership Principles]]<br />
<br />
=== Stay Connected ===<br />
If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.<br />
<br />
Helpful Posts: <br />
* [https://discourse.mozilla.org/c/community-portal Mozilla Community Portal] <br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2019-update/35430 Mission Driven Mozillians 2019 Update]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 Mission Driven Mozillians 2018 Update]<br />
* [https://blog.mozilla.org/sumo/2017/11/23/non-coding-volunteers-mission-driven-mozillians-community-coordinators-sumo/ Non-coding Volunteers, Mission-driven Mozillians, Community Coordinators & SUMO]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Mission Driven Mozillians Communities Proposal]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-volunteer-leadership-principles-practices/22386 Mission Driven Mozillians - volunteer leadership proposal]<br />
* [https://www.youtube.com/watch?v=E_vAIPkVTHE Watch the video Intro to Mission Driven Mozillians]</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Mission-Driven_Mozillians_Strategy&diff=1219679Innovation/Projects/Mission-Driven Mozillians Strategy2019-10-30T14:20:51Z<p>Lucyeoh: /* Our Vision */</p>
<hr />
<div>=== What is the Mission-Driven Mozillians strategy program?===<br />
<br />
This program, driven by the Community Development Team (part of the [[Open Innovation Team]]), aims at driving forward the creation of a modern unified contributor experience for Mission-Driven Mozillians.<br />
<br />
'''Mission-Driven Mozillians are a persona of contributors who:'''<br />
* Regularly contribute to a number of activities in support of Mozilla’s mission<br />
* Are highly invested in Mozilla as an organization and a mission<br />
* Contribute in multiple areas (either sequentially or simultaneously)<br />
* Have Mozilla at the core of their community identities<br />
<br />
While there are Mission Driven Mozillians in many areas of the project, the major areas of activity for this persona are: evangelizing, teaching, advocating, localizing, documenting, community building and doing testing.<br />
<br />
''If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.''<br />
<br />
=== Goal ===<br />
The goal of this project is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
<br />
This proposal is different to anything we have done in the past, we want to address the issues identified in the research, and create a revised approach that is a shared across the organization.<br />
<br />
(This is also communicated through the video [https://www.youtube.com/watch?v=E_vAIPkVTHE Intro to Mission Driven Mozillians]).<br />
<br />
=== Our Vision ===<br />
<br />
By 2020, a healthy global community of Mozillians is bringing benefits for our mission that none of our “competitors” can match and is a formidable foundation serving the movement for an open internet.<br />
<br />
Mission Driven Mozillians will have impact on Mozilla projects by adding capacity beyond our means, sharing global perspective and ideas, and extending our reach into valuable networks. Furthermore by growing and empowering a community of people who truly put Mozilla’s mission first, we’ll discover new and wonderful value that we cannot currently predict.<br />
<br />
Participating as a Mozillian will be deeply rewarding and fun. It will be easy to find and make valuable contributions to important projects.<br />
<br />
Communities will be healthy and inclusive environments that support individual growth and bring out the best in all Mozillians. Staff teams will find it clear, effective and rewarding to engage with Mozillians.<br />
<br />
=== Background ===<br />
<br />
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&amp;I community research, which produced the [https://docs.google.com/document/d/1ZK7l4e9-UVTMacxmmCzA8pDqVfsZOahkBC6eIOsRQyc/edit State of Diversity & Inclusion] report. Community as well as additional interviews &amp; research with key staff members and volunteers.<br />
<br />
This produced the most extensive understanding of Mozilla’s contributor communities ever and two key insights that created this work: <br />
<br />
* There are a large number of contributors who regularly contribute to a number of activities in support of Mozilla’s mission, are highly invested in Mozilla as an organization and a mission, contribute in multiple areas (either sequentially or simultaneously). We called this profile of contributor “Mission Driven Mozillians” to reflect their reported motivating force, which was advancing Mozilla’s Mission. <br />
* The way Mozilla’s teams and projects are structured does NOT making it easy for Mission Driven Mozillians to be successful.<br />
<br />
[https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Additional background]<br />
<br />
''This project was formerly known as "Non-coding Enthusiast communities and contributors".''<br />
<br />
=== Who’s Involved ===<br />
<br />
'''The project is being driven by''' - Lucy Harris &amp; Ruben Martin (with support from George Roter)<br />
<br />
'''The decision-maker is''' - Lucy Harris<br />
<br />
'''Agreement is to be sought from''' - George Roter, Katharina Borchert, Chris Beard, Mitchell Baker and the Reps Module Owner<br />
<br />
'''Input &amp; Consultation'''- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, D&amp;I Staff, Mozilla Foundation Staff.<br />
<br />
=== Approach ===<br />
<br />
The approach is to work with staff and contributors to gradually address each of the project themes. In each project we will follow the [https://toolkit.mozilla.org/ open design] approach of: <br />
<br />
# Gathering insights <br />
# Ideating Solutions<br />
# Testing & Implementing <br />
<br />
At each step we will gather insights and hold discussions with members of Mozilla communities.<br />
<br />
=== Project Themes ===<br />
<br />
Both proposal &amp; strategy will be based around the following 7 project themes(*):<br />
<br />
# '''Group Identities:''' How do we create a process for recognizing groups, that emphasises inclusivity while allowing volunteers the freedom to create and manage structures that reflect their interests and identities?<br />
# '''Metrics''': How can we increase our understanding of the impact and health of Mozillian communities?<br />
# '''Diversity & Inclusion''': How do we create a set of processes, standards, and workflows that make Mozilla’s communities more inclusive?<br />
# '''Volunteer Leadership''': How can shared agreements and approaches to volunteer leadership create healthier, more impactful communities?<br />
# '''Recognition''': How can cohesive approaches to recognition create a more rewarding contribution experience for more people? <br />
# '''Resource Distribution''': How do we create standards and systems that make resource distribution fair and consistent across the project? <br />
# '''Contributor Journey & Opportunity Matching''': How do we connect more people to higher impact contribution opportunities? How can we make it easy to join the community? <br />
<br />
(*)The project themes were updated from 10 to 7 in January 2018. To see how they evolved click [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 here]. <br />
=== MDM Projects ===<br />
A number of major projects have been created as a direct result of this strategy. Here are some relevant links: <br />
* [[Innovation/Projects/Community_Portal|Community Portal]]<br />
* [[Volunteer_leadership_principles|Volunteer Leadership Principles]]<br />
<br />
=== Stay Connected ===<br />
If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.<br />
<br />
Helpful Posts: <br />
* [https://discourse.mozilla.org/c/community-portal Mozilla Community Portal] <br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2019-update/35430 Mission Driven Mozillians 2019 Update]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 Mission Driven Mozillians 2018 Update]<br />
* [https://blog.mozilla.org/sumo/2017/11/23/non-coding-volunteers-mission-driven-mozillians-community-coordinators-sumo/ Non-coding Volunteers, Mission-driven Mozillians, Community Coordinators & SUMO]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Mission Driven Mozillians Communities Proposal]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-volunteer-leadership-principles-practices/22386 Mission Driven Mozillians - volunteer leadership proposal]<br />
* [https://www.youtube.com/watch?v=E_vAIPkVTHE Watch the video Intro to Mission Driven Mozillians]</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Mission-Driven_Mozillians_Strategy&diff=1219678Innovation/Projects/Mission-Driven Mozillians Strategy2019-10-30T14:19:52Z<p>Lucyeoh: /* MDM Projects */</p>
<hr />
<div>=== What is the Mission-Driven Mozillians strategy program?===<br />
<br />
This program, driven by the Community Development Team (part of the [[Open Innovation Team]]), aims at driving forward the creation of a modern unified contributor experience for Mission-Driven Mozillians.<br />
<br />
'''Mission-Driven Mozillians are a persona of contributors who:'''<br />
* Regularly contribute to a number of activities in support of Mozilla’s mission<br />
* Are highly invested in Mozilla as an organization and a mission<br />
* Contribute in multiple areas (either sequentially or simultaneously)<br />
* Have Mozilla at the core of their community identities<br />
<br />
While there are Mission Driven Mozillians in many areas of the project, the major areas of activity for this persona are: evangelizing, teaching, advocating, localizing, documenting, community building and doing testing.<br />
<br />
''If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.''<br />
<br />
=== Goal ===<br />
The goal of this project is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
<br />
This proposal is different to anything we have done in the past, we want to address the issues identified in the research, and create a revised approach that is a shared across the organization.<br />
<br />
(This is also communicated through the video [https://www.youtube.com/watch?v=E_vAIPkVTHE Intro to Mission Driven Mozillians]).<br />
<br />
=== Our Vision ===<br />
<br />
By 2020, a healthy global community of Mission Driven Mozillians is bringing benefits for our mission that none of our “competitors” can match and is a formidable foundation serving the movement for an open internet.<br />
<br />
Mission Driven Mozillians will have impact on Mozilla projects by adding capacity beyond our means, sharing global perspective and ideas, and extending our reach into valuable networks. Furthermore by growing and empowering a community of people who truly put Mozilla’s mission first, we’ll discover new and wonderful value that we cannot currently predict.<br />
<br />
Participating as a Mission Driven Mozillian will be deeply rewarding and fun. It will be easy to find and make valuable contributions to important projects.<br />
<br />
Communities will be healthy and inclusive environments that support individual growth and bring out the best in all Mozillians. Staff teams will find it clear, effective and rewarding to engage with Mission Driven Mozillians.<br />
<br />
=== Background ===<br />
<br />
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&amp;I community research, which produced the [https://docs.google.com/document/d/1ZK7l4e9-UVTMacxmmCzA8pDqVfsZOahkBC6eIOsRQyc/edit State of Diversity & Inclusion] report. Community as well as additional interviews &amp; research with key staff members and volunteers.<br />
<br />
This produced the most extensive understanding of Mozilla’s contributor communities ever and two key insights that created this work: <br />
<br />
* There are a large number of contributors who regularly contribute to a number of activities in support of Mozilla’s mission, are highly invested in Mozilla as an organization and a mission, contribute in multiple areas (either sequentially or simultaneously). We called this profile of contributor “Mission Driven Mozillians” to reflect their reported motivating force, which was advancing Mozilla’s Mission. <br />
* The way Mozilla’s teams and projects are structured does NOT making it easy for Mission Driven Mozillians to be successful.<br />
<br />
[https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Additional background]<br />
<br />
''This project was formerly known as "Non-coding Enthusiast communities and contributors".''<br />
<br />
=== Who’s Involved ===<br />
<br />
'''The project is being driven by''' - Lucy Harris &amp; Ruben Martin (with support from George Roter)<br />
<br />
'''The decision-maker is''' - Lucy Harris<br />
<br />
'''Agreement is to be sought from''' - George Roter, Katharina Borchert, Chris Beard, Mitchell Baker and the Reps Module Owner<br />
<br />
'''Input &amp; Consultation'''- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, D&amp;I Staff, Mozilla Foundation Staff.<br />
<br />
=== Approach ===<br />
<br />
The approach is to work with staff and contributors to gradually address each of the project themes. In each project we will follow the [https://toolkit.mozilla.org/ open design] approach of: <br />
<br />
# Gathering insights <br />
# Ideating Solutions<br />
# Testing & Implementing <br />
<br />
At each step we will gather insights and hold discussions with members of Mozilla communities.<br />
<br />
=== Project Themes ===<br />
<br />
Both proposal &amp; strategy will be based around the following 7 project themes(*):<br />
<br />
# '''Group Identities:''' How do we create a process for recognizing groups, that emphasises inclusivity while allowing volunteers the freedom to create and manage structures that reflect their interests and identities?<br />
# '''Metrics''': How can we increase our understanding of the impact and health of Mozillian communities?<br />
# '''Diversity & Inclusion''': How do we create a set of processes, standards, and workflows that make Mozilla’s communities more inclusive?<br />
# '''Volunteer Leadership''': How can shared agreements and approaches to volunteer leadership create healthier, more impactful communities?<br />
# '''Recognition''': How can cohesive approaches to recognition create a more rewarding contribution experience for more people? <br />
# '''Resource Distribution''': How do we create standards and systems that make resource distribution fair and consistent across the project? <br />
# '''Contributor Journey & Opportunity Matching''': How do we connect more people to higher impact contribution opportunities? How can we make it easy to join the community? <br />
<br />
(*)The project themes were updated from 10 to 7 in January 2018. To see how they evolved click [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 here]. <br />
=== MDM Projects ===<br />
A number of major projects have been created as a direct result of this strategy. Here are some relevant links: <br />
* [[Innovation/Projects/Community_Portal|Community Portal]]<br />
* [[Volunteer_leadership_principles|Volunteer Leadership Principles]]<br />
<br />
=== Stay Connected ===<br />
If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.<br />
<br />
Helpful Posts: <br />
* [https://discourse.mozilla.org/c/community-portal Mozilla Community Portal] <br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2019-update/35430 Mission Driven Mozillians 2019 Update]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 Mission Driven Mozillians 2018 Update]<br />
* [https://blog.mozilla.org/sumo/2017/11/23/non-coding-volunteers-mission-driven-mozillians-community-coordinators-sumo/ Non-coding Volunteers, Mission-driven Mozillians, Community Coordinators & SUMO]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Mission Driven Mozillians Communities Proposal]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-volunteer-leadership-principles-practices/22386 Mission Driven Mozillians - volunteer leadership proposal]<br />
* [https://www.youtube.com/watch?v=E_vAIPkVTHE Watch the video Intro to Mission Driven Mozillians]</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Community_Portal&diff=1219616Innovation/Projects/Community Portal2019-10-29T14:30:47Z<p>Lucyeoh: /* Goal */</p>
<hr />
<div><br />
== What is the Community Portal ==<br />
'''The Mozillian Community Portal''' is an initiative led by the Community Development Team in Open Innovation. It is part of the [[Innovation/Projects/Mission-Driven_Mozillians_Strategy|Mission Driven Mozillians project]] the goal of which is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
[[File:Communityportal2.jpg|500px|right]]<br />
<br />
== Goal ==<br />
<br />
The goal of the community portal is to create a central place for Mozillians to be able to find, discover opportunities and collaborate across community members & groups.<br />
<br />
The portal will be a centralized place to discover community events, groups, contribution opportunities and individual profiles. <br />
<br />
[[File:Wireframe Events Page.png|500px|right]]<br />
<br />
<br />
Development will be through an open process starting in August 2019, with an estimated V1 release date in early 2020. <br />
<br />
'''We publish weekly updates on the development of the portal on [https://discourse.mozilla.org/c/community-portal discourse].'''<br />
<br />
'''Find the [https://discourse.mozilla.org/t/frequently-asked-questions-portal-edition-faq/43224/4 FAQ] here.'''</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Mission-Driven_Mozillians_Strategy&diff=1219427Innovation/Projects/Mission-Driven Mozillians Strategy2019-10-23T17:59:59Z<p>Lucyeoh: </p>
<hr />
<div>=== What is the Mission-Driven Mozillians strategy program?===<br />
<br />
This program, driven by the Community Development Team (part of the [[Open Innovation Team]]), aims at driving forward the creation of a modern unified contributor experience for Mission-Driven Mozillians.<br />
<br />
'''Mission-Driven Mozillians are a persona of contributors who:'''<br />
* Regularly contribute to a number of activities in support of Mozilla’s mission<br />
* Are highly invested in Mozilla as an organization and a mission<br />
* Contribute in multiple areas (either sequentially or simultaneously)<br />
* Have Mozilla at the core of their community identities<br />
<br />
While there are Mission Driven Mozillians in many areas of the project, the major areas of activity for this persona are: evangelizing, teaching, advocating, localizing, documenting, community building and doing testing.<br />
<br />
''If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.''<br />
<br />
=== Goal ===<br />
The goal of this project is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
<br />
This proposal is different to anything we have done in the past, we want to address the issues identified in the research, and create a revised approach that is a shared across the organization.<br />
<br />
(This is also communicated through the video [https://www.youtube.com/watch?v=E_vAIPkVTHE Intro to Mission Driven Mozillians]).<br />
<br />
=== Our Vision ===<br />
<br />
By 2020, a healthy global community of Mission Driven Mozillians is bringing benefits for our mission that none of our “competitors” can match and is a formidable foundation serving the movement for an open internet.<br />
<br />
Mission Driven Mozillians will have impact on Mozilla projects by adding capacity beyond our means, sharing global perspective and ideas, and extending our reach into valuable networks. Furthermore by growing and empowering a community of people who truly put Mozilla’s mission first, we’ll discover new and wonderful value that we cannot currently predict.<br />
<br />
Participating as a Mission Driven Mozillian will be deeply rewarding and fun. It will be easy to find and make valuable contributions to important projects.<br />
<br />
Communities will be healthy and inclusive environments that support individual growth and bring out the best in all Mozillians. Staff teams will find it clear, effective and rewarding to engage with Mission Driven Mozillians.<br />
<br />
=== Background ===<br />
<br />
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&amp;I community research, which produced the [https://docs.google.com/document/d/1ZK7l4e9-UVTMacxmmCzA8pDqVfsZOahkBC6eIOsRQyc/edit State of Diversity & Inclusion] report. Community as well as additional interviews &amp; research with key staff members and volunteers.<br />
<br />
This produced the most extensive understanding of Mozilla’s contributor communities ever and two key insights that created this work: <br />
<br />
* There are a large number of contributors who regularly contribute to a number of activities in support of Mozilla’s mission, are highly invested in Mozilla as an organization and a mission, contribute in multiple areas (either sequentially or simultaneously). We called this profile of contributor “Mission Driven Mozillians” to reflect their reported motivating force, which was advancing Mozilla’s Mission. <br />
* The way Mozilla’s teams and projects are structured does NOT making it easy for Mission Driven Mozillians to be successful.<br />
<br />
[https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Additional background]<br />
<br />
''This project was formerly known as "Non-coding Enthusiast communities and contributors".''<br />
<br />
=== Who’s Involved ===<br />
<br />
'''The project is being driven by''' - Lucy Harris &amp; Ruben Martin (with support from George Roter)<br />
<br />
'''The decision-maker is''' - Lucy Harris<br />
<br />
'''Agreement is to be sought from''' - George Roter, Katharina Borchert, Chris Beard, Mitchell Baker and the Reps Module Owner<br />
<br />
'''Input &amp; Consultation'''- Reps Council + Peers , Reps Community Managers, SUMO Community Managers + key volunteers, L10N Community Managers + key volunteers, D&amp;I Staff, Mozilla Foundation Staff.<br />
<br />
=== Approach ===<br />
<br />
The approach is to work with staff and contributors to gradually address each of the project themes. In each project we will follow the [https://toolkit.mozilla.org/ open design] approach of: <br />
<br />
# Gathering insights <br />
# Ideating Solutions<br />
# Testing & Implementing <br />
<br />
At each step we will gather insights and hold discussions with members of Mozilla communities.<br />
<br />
=== Project Themes ===<br />
<br />
Both proposal &amp; strategy will be based around the following 7 project themes(*):<br />
<br />
# '''Group Identities:''' How do we create a process for recognizing groups, that emphasises inclusivity while allowing volunteers the freedom to create and manage structures that reflect their interests and identities?<br />
# '''Metrics''': How can we increase our understanding of the impact and health of Mozillian communities?<br />
# '''Diversity & Inclusion''': How do we create a set of processes, standards, and workflows that make Mozilla’s communities more inclusive?<br />
# '''Volunteer Leadership''': How can shared agreements and approaches to volunteer leadership create healthier, more impactful communities?<br />
# '''Recognition''': How can cohesive approaches to recognition create a more rewarding contribution experience for more people? <br />
# '''Resource Distribution''': How do we create standards and systems that make resource distribution fair and consistent across the project? <br />
# '''Contributor Journey & Opportunity Matching''': How do we connect more people to higher impact contribution opportunities? How can we make it easy to join the community? <br />
<br />
(*)The project themes were updated from 10 to 7 in January 2018. To see how they evolved click [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 here]. <br />
=== MDM Projects ===<br />
A number of projects have been created as a direct result of this strategy. Here are some relevant links: <br />
* https://wiki.mozilla.org/Innovation/Projects/Community_Portal<br />
* https://wiki.mozilla.org/Volunteer_leadership_principles<br />
=== Stay Connected ===<br />
If you are interested in getting updates about this project, please subscribe to the [https://discourse.mozilla.org/tags/mission-mozillians mission-mozillians] tag on discourse.<br />
<br />
Helpful Posts: <br />
* [https://discourse.mozilla.org/c/community-portal Mozilla Community Portal] <br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2019-update/35430 Mission Driven Mozillians 2019 Update]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-2018-update/25068 Mission Driven Mozillians 2018 Update]<br />
* [https://blog.mozilla.org/sumo/2017/11/23/non-coding-volunteers-mission-driven-mozillians-community-coordinators-sumo/ Non-coding Volunteers, Mission-driven Mozillians, Community Coordinators & SUMO]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-communities-proposal/21728 Mission Driven Mozillians Communities Proposal]<br />
* [https://discourse.mozilla.org/t/mission-driven-mozillians-volunteer-leadership-principles-practices/22386 Mission Driven Mozillians - volunteer leadership proposal]<br />
* [https://www.youtube.com/watch?v=E_vAIPkVTHE Watch the video Intro to Mission Driven Mozillians]</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Volunteer_leadership_principles&diff=1219426Volunteer leadership principles2019-10-23T17:57:44Z<p>Lucyeoh: Created page with "=Principles & Practices for Volunteer Leadership at Mozilla= The principles and practices below were created and agreed upon by the input group, a diverse group of staff and..."</p>
<hr />
<div>=Principles & Practices for Volunteer Leadership at Mozilla=<br />
<br />
The principles and practices below were created and agreed upon by the input group, a diverse group of staff and volunteers who are most closely connected to the primary contribution areas (listed above). We believe that these principles and practices should be part of all structures and processes around volunteer leadership across Mozilla.<br />
<br />
This is part of the [[Innovation/Projects/Mission-Driven_Mozillians_Strategy|Mission Driven Mozillians strategy project]]. <br />
<br />
The original post with discussion links is available [https://discourse.mozilla.org/t/mission-driven-mozillians-volunteer-leadership-principles-practices/22386 here].<br />
<br />
Principle = the foundational belief<br />
Practice = how it should be applied<br />
<br />
==Principle 1. Leadership should require renewal==<br />
<br />
Practices:<br />
* There should be set terms for all leadership roles<br />
* There should be regular renewal checkpoints (by community &/or staff)<br />
<br />
<br />
==Principle 2. Leadership should be distributed==<br />
<br />
Practices:<br />
* The number of leadership roles someone can hold at a single time should be limited<br />
* New leadership opportunities and pathways should be decided and consulted on by the community involved in that area<br />
* Criteria for the role requirements should be validated by the impacted group<br />
* We should create clear definitions for roles and avoid the generic term “leader”<br />
* Leadership responsibility should be held by groups where possible<br />
<br />
<br />
==Principle 3. Leadership should be accountable==<br />
<br />
Practices:<br />
<br />
* All leaders should have clarity in their roles<br />
* All leaders should agree to a standard by which they can be held<br />
* Staff & community should have a way to hold leaders accountable<br />
* Mozilla should enforce the Community Participation Guidelines consistently and strictly<br />
* All leaders should be validated by the community members who are directly working in the same area<br />
* All leaders should be aware that they represent the organization<br />
* All leaders should follow a shared framework for decision making<br />
* All leaders should be active and stay active for the duration of their term<br />
<br />
==Principles 4. Leadership should be diverse & inclusive==<br />
<br />
Practices:<br />
<br />
* Leaders should strive to include diverse voices and groups<br />
* Mozilla should enforce the Community Participation Guidelines consistently and strictly<br />
* Roles should be transparent and visible so that people know what opportunities are available to them and the expectations of them<br />
* Leadership pathways should explicitly consider inclusion dimensions (i.e. time, language, bandwidth, cultural norms)<br />
<br />
==Principle 5. Leadership should be consistent==<br />
<br />
Practices:<br />
<br />
* Leadership roles are valued the same across the org/areas (recognition, access to resources, opportunities etc. )<br />
* All leaders should have clarity in their roles and expectations<br />
* All leaders should have a shared foundational knowledge base & skills (i.e. Community Participation Guidelines)<br />
* Follow a shared framework for decision making<br />
* We should create clear definitions for roles and avoid the generic term “leader”<br />
* Tools should be consistent and coherent where possible<br />
<br />
==Principle 6. Leadership should include Community Experts and Technical Experts==<br />
''Where community experts have expertise around community building and organizing, and technical experts have expertise in a specific functional area.'' <br />
<br />
Practices:<br />
<br />
* Mozilla should value and recognize them equally<br />
* Both should be considered “leaders”<br />
* Both should have a minimum capability in the other skill set (community management skills & technical skill)<br />
* All community expert leaders should be aligned across all Mission-Driven Mozillians Functional Areas<br />
* Technical Experts and Community Experts should balance each other and work together</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=NDA-Slack&diff=1218903NDA-Slack2019-10-10T17:24:56Z<p>Lucyeoh: </p>
<hr />
<div>== <big>NDA and Slack Access</big> == <br />
<br />
Mozilla’s Slack is a great tool for working collaboratively with staff on Mozilla projects. As of February 2018 volunteers who have signed [[NDA|Mozilla's Non-Disclosure Agreement (NDA)]] '''can be''' invited by their [https://mozillians.org/en-US/group/nda/ NDA Administrator] to sign up to [http://mozilla.slack.com/ Mozilla Slack] (via SSO) if they need to regularly, synchronously communicate with staff. You can see if a Slacker is a staff member or a volunteer by clicking on their Slack profile.<br />
<br />
'''To invite contractors, vendors''' or anyone else we have a business arrangement with, but who does not have an LDAP to Slack, staff should file a ticket on [https://mozilla.service-now.com/sp?id=sc_cat_item&sys_id=a0601f6213148f407b5450782244b0a1 Service Now].<br />
<br />
==== What do you commit to when you join Slack? ==== <br />
<br />
Mozilla’s Slack is primarily a professional environment where people collaborate to get work done in a safe and positive environment. <br />
<br />
'''Community Participation Guideline:'''Staff and volunteers are required to follow the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guideline] in all of their interactions on Slack, failure to abide by the CPG may result in temporary or permanent loss of access. <br />
<br />
'''Slack Etiquette Guide:''' Slack is a microcosm of Mozilla's professional environment has norms and etiquette expectations beyond the CPG, to keep Slack a productive environment for everyone you must also read and comply with the [[NDA-Slack/Etiquette-Guide|Etiquette Guide here]].<br />
<br />
==== How long does Slack access last: ====<br />
<br />
Having a valid [[NDA]] is a prerequisite for Slack access and your access will only last as long as you are a member of the NDA group. <br />
<br />
NDA’s expire after one year, in order to make sure that those on the list are regularly active. One year from the acceptance date, inviters will have the opportunity to re-invite volunteers to the NDA group. <br />
<br />
==== What happens once I get my invitation: ==== <br />
<br />
Once you receive your invitation, you will be directed to read and agree to the [https://www.mozilla.org/en-US/about/governance/policies/participation/ Community Participation Guidelines], and the [[NDA-Slack/Etiquette-Guide|etiquette guide]]. Make sure you read them both carefully before you agree to their terms. If you have any questions please do not hesitate to reach out to your inviter!<br />
<br />
Once you have accepted the terms of the Guidelines you will: <br />
* Be able to sign up to slack via SSO using your Github identity<br />
* You will have access to all public channels.<br />
<br />
If at any point you have any questions jump into the #slack-onboarding channel or reach out to your Inviter.<br />
<br />
== Who Can Join Slack? == <br />
<br />
Slack access is available by invitation to contributors who are have signed an [[NDA]] and who have '''also''' been invited to join the [https://mozillians.org/en-US/group/slack-access/ Slack-Access] group by administrators of a Mozilla Community. Signing an NDA does not automatically grant access to Slack but is a necessary prerequisite. <br />
<br />
Staff who are not administrators can vouch for contributors to join Slack access group if they believe that their ability to contribute effectively would be benefited by the capacity to synchronously communicate through Slack. Staff can place a request using this form - using [http://goo.gl/forms/RoR5kv9ouJ this form].<br />
<br />
Mozilla Staff can see who has vouched for a contributor by visiting their Mozillians.org profile and looking under "Access Groups".<br />
<br />
Groups like Reps, L10N, Security and SUMO may also have additional procedures for determining who should receive Slack access. Here is the information for each of these groups. <br />
<br />
'''To invite contractors, vendors or anyone else we have a business arrangement with, but who does not have an LDAP to Slack, staff should file a ticket on [https://mozilla.service-now.com/sp?id=sc_cat_item&sys_id=a0601f6213148f407b5450782244b0a1 Service Now].'''<br />
<br />
===== Reps =====<br />
In order to get access to Mozilla Slack, Reps will have to fill [https://docs.google.com/forms/d/e/1FAIpQLSdWL96GO39UfAub68qP9OtZKT6j9iR_X4phR95ct81Q5uQtCA/viewform?usp=sf_link this form] explaining why Slack is needed to their Reps contributions.<br />
<br />
The requests will be reviewed weekly by the Reps team.<br />
<br />
If you have any questions, reach out to [https://reps.mozilla.org/u/couci/ Konstantina Papadea].<br />
<br />
===== SUMO =====<br />
The Mozilla Support Community requires an NDA for product updates and support related communications and participation in the Social Support program that answers brand questions. Check out how to get involved at https://support.mozilla.com and [[Support]]. If you are a member of the Mozilla Support Community who has participated for a while and would benefit from synchronous communication with staff on Slack please send a request here https://forms.gle/W68PK5svZqzhzfD3A. Please note that an NDA is required for participation in the Social Support program. If you do not currently have an NDA, please read more about the NDA and how to request one here: [[NDA|https://wiki.mozilla.org/NDA]].<br />
<br />
===== L10N =====<br />
The l10n-drivers prefer the #l10n IRC channel (irc.mozilla.org) or the Mozilla L10n Community Telegram group for real-time chat with l10n staff.<br />
That being said, we know that some contributors may need Slack access. Please reach out to a member of the l10n-drivers team on IRC or Telegram to make your case for Slack access.<br />
<br />
===== Tech Speakers =====<br />
[Looks like this team hasn't shared details about Slack-Access yet - reach out to the staff team for more details!]<br />
<br />
===== Security Contributors =====<br />
[Looks like this team hasn't shared details about Slack-Access yet - reach out to the staff team for more details!]<br />
<br />
===== Research Contributors =====<br />
Please email [https://mozillians.org/en-US/u/larsberg/ Lars Bergstrom] at larsberg@mozilla.com if you require NDA slack access. Most Research work is done on IRC or public forums, but contractors and frequent speakers may require access to additional internal information that is easier to share over Slack.<br />
<br />
===== Add-ons Contributors =====<br />
Synchronous chat with members of the add-ons team almost always occurs in irc.mozilla.org in the following public channels: #addon-reviewers, #addons, #amo, #themedev, or #webextensions. <br />
<br />
While the add-ons team prefers communications to happen IRC, we understand that some contributors may need to have access to slack. Please email [https://mozillians.org/en-US/u/caitmuenster/ Caitlin Neiman] at cneiman [at] mozilla [dot] com to discuss.<br />
<br />
===== Mozilla Community Web Services ===== <br />
The [https://discourse.mozilla.org/c/mcws MCWS Team] is using their own Telegram group for most synchronous/chat-like communications. MCWS volunteers provision resources to Mozilla communities. It is therefore helpful to be able to reach Staff members who might be program/product/service/capability owners on Slack. MCWS members also provide invaluable insight about managing resources for distributed, self-governed Mozilla communities to our conversations.<br />
<br />
Please reach out to [https://mozillians.org/u/hmitsch/ Henrik Mitsch] to be vouched as a MCWS volunteer for Slack.<br />
<br />
-- <br />
<br />
===== Staff Requests for Contributor Access ===== <br />
In order to receive access to Slack, if you are not in any of these groups, you must be invited by a staff member. Staff members can vouch for contributors using [http://goo.gl/forms/RoR5kv9ouJ this form].<br />
<br />
Staff should consider whether this contributors ability to contribute would be improved by the ability to communicate freely and synchronously with Mozilla staff on Slack. Please think about whether this person is active and trusted in your community and whether you believe that being added to Mozilla-Slack will improve their ability to contribute.<br />
<br />
<br />
Please note that contributors must have a Mozillians.org account and must also meet the criteria to be added to the [[NDA|NDA Group]]. <br />
<br />
Staff: Please note that you will accountable for your invitee while they are on Slack. In order to accommodate for changes in position or employment you must also list a “back-up” inviter who will assume responsibility for your contributors should you leave the organization.</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Community_Portal&diff=1218517Innovation/Projects/Community Portal2019-10-01T16:36:01Z<p>Lucyeoh: </p>
<hr />
<div><br />
== What is the Community Portal ==<br />
'''The Mozillian Community Portal''' is an initiative led by the Community Development Team in Open Innovation. It is part of the [[Innovation/Projects/Mission-Driven_Mozillians_Strategy|Mission Driven Mozillians project]] the goal of which is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
[[File:Communityportal2.jpg|500px|right]]<br />
<br />
== Goal ==<br />
<br />
The goal of the community portal is to create a central place for Mozillians to be able to find, discover opportunities and collaborate across community members & groups.<br />
<br />
The portal will be a centralized place to discover community events, groups, contribution opportunities and individual profiles. <br />
<br />
[[File:Wireframe Events Page.png|500px|right]]<br />
<br />
<br />
Development will be through an open process starting in August 2019, with an estimated V1 release date in early 2020. <br />
<br />
'''We publish weekly updates on the development of the portal on [https://discourse.mozilla.org/t/about-the-community-portal-category/43218 discourse].'''<br />
<br />
'''Find the [https://discourse.mozilla.org/t/frequently-asked-questions-portal-edition-faq/43224/4 FAQ] here.'''</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Community_Portal&diff=1218516Innovation/Projects/Community Portal2019-10-01T16:35:23Z<p>Lucyeoh: /* What is the Community Portal */</p>
<hr />
<div><br />
== What is the Community Portal ==<br />
'''The Mozillian Community Portal''' is an initiative led by the Community Development Team in Open Innovation. It is part of the [https://wiki.mozilla.org/Innovation/Projects/Mission-Driven_Mozillians_Strategy| Mission Driven Mozillians project] the goal of which is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
[[File:Communityportal2.jpg|500px|right]]<br />
<br />
== Goal ==<br />
<br />
The goal of the community portal is to create a central place for Mozillians to be able to find, discover opportunities and collaborate across community members & groups.<br />
<br />
The portal will be a centralized place to discover community events, groups, contribution opportunities and individual profiles. <br />
<br />
[[File:Wireframe Events Page.png|500px|right]]<br />
<br />
<br />
Development will be through an open process starting in August 2019, with an estimated V1 release date in early 2020. <br />
<br />
'''We publish weekly updates on the development of the portal on [https://discourse.mozilla.org/t/about-the-community-portal-category/43218 discourse].'''<br />
<br />
'''Find the [https://discourse.mozilla.org/t/frequently-asked-questions-portal-edition-faq/43224/4 FAQ] here.'''</div>Lucyeohhttps://wiki.mozilla.org/index.php?title=Innovation/Projects/Community_Portal&diff=1218515Innovation/Projects/Community Portal2019-10-01T16:34:49Z<p>Lucyeoh: </p>
<hr />
<div><br />
== What is the Community Portal ==<br />
'''The Mozillian Community Portal''' is an initiative led by the Community Development Team in Open Innovation. It is part of the [https://wiki.mozilla.org/Innovation/Projects/Mission-Driven_Mozillians_Strategy|Mission Driven Mozillians project] the goal of which is to work with teams and communities to implement modern unified structures and processes to optimize the health and impact of Mission-Driven Mozillians communities.<br />
[[File:Communityportal2.jpg|500px|right]]<br />
<br />
== Goal ==<br />
<br />
The goal of the community portal is to create a central place for Mozillians to be able to find, discover opportunities and collaborate across community members & groups.<br />
<br />
The portal will be a centralized place to discover community events, groups, contribution opportunities and individual profiles. <br />
<br />
[[File:Wireframe Events Page.png|500px|right]]<br />
<br />
<br />
Development will be through an open process starting in August 2019, with an estimated V1 release date in early 2020. <br />
<br />
'''We publish weekly updates on the development of the portal on [https://discourse.mozilla.org/t/about-the-community-portal-category/43218 discourse].'''<br />
<br />
'''Find the [https://discourse.mozilla.org/t/frequently-asked-questions-portal-edition-faq/43224/4 FAQ] here.'''</div>Lucyeoh