Skip to content

Latest commit

 

History

History
103 lines (72 loc) · 6.01 KB

README.md

File metadata and controls

103 lines (72 loc) · 6.01 KB

This policy is a "living" document, and subject to refinement and expansion in the future.

Code of Conduct

The Android Study Group Slack should be a safe place for everybody regardless of

  • gender, gender identity or gender expression
  • sexual orientation
  • disability
  • physical appearance (including but not limited to body size)
  • race
  • age
  • religion

As someone who is part of this Slack, you agree that:

  • We are collectively and individually committed to safety and inclusivity.
  • We have zero tolerance for abuse, harassment, or discrimination.
  • We respect people’s boundaries and identities.
  • We refrain from using language that can be considered oppressive (systemically or otherwise), eg. sexist, racist, homophobic, transphobic, ableist, classist, etc. - this includes (but is not limited to) various slurs.
  • We avoid using offensive topics as a form of humor.

We actively work towards:

  • Being a safe community
  • Cultivating a network of support & encouragement for each other
  • Encouraging responsible and varied forms of expression

We condemn:

  • Stalking, doxxing, or publishing private information
  • Threats of harm, harassment
  • Anything that compromises people’s safety
  • Personal attacks

These things are NOT OK.

If you say something that is found offensive, and you are called out on it, let’s:

  • Listen without interruption.
  • Believe what the person is saying & do not attempt to disqualify what they have to say.
  • Ask for tips / help with avoiding making the offense in the future.
  • Apologize and ask forgiveness.

Failing to follow the community guidelines as described in this document carries consequences. For minor infractions, you may be temporarily suspended from the Slack. Upon repeat offenses, or if the community believes you are not acting in good faith, you may be asked to leave permanently.

Privacy

  • All conversations are private unless otherwise specified.
  • If you wish to share a conversation, or part of one, you must get permission from each person involved.

Best Practices

  • Stay on topic. The goal of the ASG Slack is to facilitate discussion of things relating to Android development. This could be about marketing, business, server-side programming, or other things that may be important to an Android developer. For off-topic topics go to #random
  • If you have a technical question, please try and figure it out before posting here. If you're having trouble, all questions are welcome.
  • Before asking any questions, please check if there's a channel for it before asking in #android-general
  • Job posting can be posted in #hiring only. Do not reach out to individuals for hiring purposes.

If you experience abuse, harassment, discrimination, or feel unsafe, let a moderator know. Here is a list of the current admins and their Slack IDs:

  • Adrienne Park - @adrienne
  • Chiu-Ki Chan - @chiuki
  • Corey Latislaw - @colabug
  • Danny Roa - @dannyroa
  • Erik Hellman - @hellman
  • Garima Jain - @ragdroid
  • Grantland Chew - @grantland
  • Jake Ouellette - @jakeout
  • Mike Evans - @michael.evans
  • Mike Nakhimovich - @FriendlyMike
  • Olga Dominguez - @Olga
  • Sam Wolfand - @Sam

The role of the admins is to be an unbiased mediator, they will not moderate or edit anything written in the Slack unless it is required as a result of a discussed dispute.

Member Nomination

To invite a new member to ASG, use the built-in invite tool in the Slack menu. Enter email, full name and the necessary details in the Reason field. What we want to see is the following:

  • Years of Android experience. At the minimum 1 year of active Android development work.
  • What kind of Android experience do they bring to ASG?
  • Do you think the person would actively participate in ASG? .
  • Where is the nominee working and how do you know the person?
  • At least one external reference like GitHub, Twitter or LinkedIn. Due to limits in Slack for including URLs, use a format like this: github:username, twitter:username, linkedin:username, etc.

We highly discourage mass invites (don't invite all your coworkers at once) and invites missing information will also be denied. We might reach out for additional information or clarifications if needed. Since the Reason field doesn’t allow URLs and has a limited length (560 characters), send additional info in a DM to an admin and they will add it as a comment in the review channel.

This study group is for people actively involved in creating Android applications professionally. This includes people like software engineers and designers, and excludes people like journalists or recruiters. The admins will take into consideration the amount of time the nominee has spent working on Android (at least 1 year is ideal). Other helpful data points include the company where they work (if applicable), apps they have built, and their contributions to the Android community (via open source software, meetups, blog posts, etc). Membership is determined by a vote from the admins, who will then send out an invitation to the nominee.

If there is any person you would like to keep out of the study group for any reason, message one of the admins.

Because this Slack group is representative of the community, admins reserve the right to deny admission or revoke membership based on CoC violating behavior outside of the Slack chat environment (e.g. in person, GitHub, social media), if necessary.

Slack Etiquette

Slack Commands

Many members of ASG have this Slack open during the work day, or installed on their phones. Additionally, there are members in many different time zones. Please be cautious about using @channel or @everyone and avoid it if possible.

For tips and tricks or questions about Slack usage, check out #meta.

Q & A

Value your fellow members' time, and be considerate when asking questions. Before asking a question, please Google for it, and consult the Android documentation. If it is still unclear, please reference the sources you consulted in your question.

When answering questions, avoid condescending language or impatience. We are all trying our hardest!