Changes

Jump to: navigation, search

NDA-Slack

1,006 bytes removed, 20:01, 8 February 2018
no edit summary
== <big>NDA and Slack Access</big> ==
As of February 2018 volunteers who have signed [[NDA|Mozilla'd Volunteers who are s Non-Disclosure Agreement (NDA)]] can be invited by an NDA Admin can to 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.  Here is a quick guide to slack etiquette.  • 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.
However Slack is a microcosm of Mozilla's professional environment has norms and etiquette expectations beyond the CPG, you can find the full guide here.
==== 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 you are a member of the NDAgroup. To find out more about 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 expiry click [[NDA group|here]].
==== What happens once I get my invitation: ====
Once you receive your invitation, please read the Community Participation Guidelines , and the etiquette guide 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:
== Who Can Join Slack? ==
Slack access is available by invitation to individuals who are deeply involved with Mozilla and are known and trusted by the administrators of a Mozilla Community, and whose ability to contribute would be improved by the ability to communicate synchronously with staff. Groups like Reps, L10N, Security and SUMO each have their own procedure for determining who should receive slack Slack access. Staff can also nominate contributors to join slack if they believe that a volunteer would benefit from accesshaving the capacity to synchronously communicate through Slack. Here is the information for each of these groups.
===== Reps =====
===== Staff Requests for Contributor Access =====
In order to receive access to slackSlack, 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 and must also meet the criteria to be added to the [[NDA|NDA Group]].
Staff: Please note that you will accountable for your invitee while they are on slackSlack. 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.
Confirm
465
edits

Navigation menu