Confirm
465
edits
Changes
Created page with "== <big>NDA and Slack Access</big> == ==== What is Slack: ==== As of February 2018 NDA'd Volunteers who are invited by an NDA Admin can sign up to slack via SSO using their..."
== <big>NDA and Slack Access</big> ==
==== What is Slack: ====
As of February 2018 NDA'd Volunteers who are invited by an NDA Admin can sign up to slack via SSO using their Github identity and have the same level of access as staff. You can see if a Slacker is a staff member or a volunteer by clicking on their Slack profile
==== What do I commit to when I join Slack? ====
As a Mozilla space staff and volunteers are required to follow the 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.
However Slack is a microcosm of Mozilla's professional environment has norms and etiquette expectations beyond the CPG that we will continue to document and update here:
• Please edit your Slack profile, adding your *full name* and *contribution area* (in section _What I do_).
• Remember our Mozilla *Community Participation Guidelines* (CPG): https://www.mozilla.org/about/governance/policies/participation/
* Remember that all information on Mozilla Slack is classified as *Mozilla Confidential - Staff and NDA'd Mozillians Only*.
Mozilla Slack Etiquette:
• Avoid posting to #announcements unless the message is really an announcement that is relevant to most of us.
• Read the _Channel Details_ as they might tell you about a channel's purpose and etiquette.
• On high-traffic channels it's good practice to *read a long for a little while to get a feeling for channel culture*.
• Be mindful when mentioning other users or the entire channel in your messages. Most of the time writing in the channel or replying to a thread works great.
==== How long does Slack access last: ====
Having a valid NDA is a prerequisite for slack access and your access will only last as long as your NDA. 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.
==== What happens once I get my invitation: ====
Once you receive your invitation, please read the Community Participation Guidelines and think about how you will contribute in a healthy and constructive manner before you agree to its terms. If you have any questions please do not hesitate to reach out to your inviter!
Once you have accepted the terms of the Guidelines you will:
* Be able to sign up to slack via SSO using your Github identity
* You will have access to all public channels.
If at any point you have any questions jump into the #slack-onboarding channel or reach out to your inviter.
== Who Can Join Slack ==
Slack access is available by invitation to individuals who are deeply involved with Mozilla are trusted by the administrators of a Mozilla Community, and whose ability to contribute would be improved by the ability to communicate synchronously with staff. Reps, L10N, Security and SUMO each have their own procedure for determining who should receive slack access. Staff can also nominate contributors to join slack if they believe that a volunteer would benefit from access. Here is the information for each of these groups.
===== Reps =====
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].
===== SUMO =====
[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].
===== L10N =====
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].
===== Tech Speakers =====
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].
===== Security Contributors =====
Non-Staff working as part of the Bugzilla Security Group will be invited to join the NDA group.
===== Research Contributors =====
Non-Staff contributing to Research organization projects such as Rust, Servo, WebVR/WebAR, Daala, and Deep Speech may contact larsberg.
===== Add-ons Contributors =====
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].
===== Mozilla Community Web Services =====
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.
===== All Hands Contributors =====
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).
--
===== Staff Vouching =====
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].
Please note that contributors must have a Mozillians.org account to be added to the NDA Group.
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.
==== What is Slack: ====
As of February 2018 NDA'd Volunteers who are invited by an NDA Admin can sign up to slack via SSO using their Github identity and have the same level of access as staff. You can see if a Slacker is a staff member or a volunteer by clicking on their Slack profile
==== What do I commit to when I join Slack? ====
As a Mozilla space staff and volunteers are required to follow the 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.
However Slack is a microcosm of Mozilla's professional environment has norms and etiquette expectations beyond the CPG that we will continue to document and update here:
• Please edit your Slack profile, adding your *full name* and *contribution area* (in section _What I do_).
• Remember our Mozilla *Community Participation Guidelines* (CPG): https://www.mozilla.org/about/governance/policies/participation/
* Remember that all information on Mozilla Slack is classified as *Mozilla Confidential - Staff and NDA'd Mozillians Only*.
Mozilla Slack Etiquette:
• Avoid posting to #announcements unless the message is really an announcement that is relevant to most of us.
• Read the _Channel Details_ as they might tell you about a channel's purpose and etiquette.
• On high-traffic channels it's good practice to *read a long for a little while to get a feeling for channel culture*.
• Be mindful when mentioning other users or the entire channel in your messages. Most of the time writing in the channel or replying to a thread works great.
==== How long does Slack access last: ====
Having a valid NDA is a prerequisite for slack access and your access will only last as long as your NDA. 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.
==== What happens once I get my invitation: ====
Once you receive your invitation, please read the Community Participation Guidelines and think about how you will contribute in a healthy and constructive manner before you agree to its terms. If you have any questions please do not hesitate to reach out to your inviter!
Once you have accepted the terms of the Guidelines you will:
* Be able to sign up to slack via SSO using your Github identity
* You will have access to all public channels.
If at any point you have any questions jump into the #slack-onboarding channel or reach out to your inviter.
== Who Can Join Slack ==
Slack access is available by invitation to individuals who are deeply involved with Mozilla are trusted by the administrators of a Mozilla Community, and whose ability to contribute would be improved by the ability to communicate synchronously with staff. Reps, L10N, Security and SUMO each have their own procedure for determining who should receive slack access. Staff can also nominate contributors to join slack if they believe that a volunteer would benefit from access. Here is the information for each of these groups.
===== Reps =====
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].
===== SUMO =====
[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].
===== L10N =====
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].
===== Tech Speakers =====
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].
===== Security Contributors =====
Non-Staff working as part of the Bugzilla Security Group will be invited to join the NDA group.
===== Research Contributors =====
Non-Staff contributing to Research organization projects such as Rust, Servo, WebVR/WebAR, Daala, and Deep Speech may contact larsberg.
===== Add-ons Contributors =====
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].
===== Mozilla Community Web Services =====
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.
===== All Hands Contributors =====
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).
--
===== Staff Vouching =====
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].
Please note that contributors must have a Mozillians.org account to be added to the NDA Group.
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.
