Ansible Community
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Write
        • Owners
        • Signed-in users
        • Everyone
        Owners Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights
    • Engagement control
    • Transfer ownership
    • Delete this note
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Versions and GitHub Sync Note Insights Sharing URL Help
Menu
Options
Engagement control Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Write
Owners
  • Owners
  • Signed-in users
  • Everyone
Owners Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       owned this note    owned this note      
    Published Linked with GitHub
    Subscribed
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    Subscribe
    # Ansible Meetup Code of Conduct / D&I Survey ###### tags: `D&I` The Ansible community Diversity and Inclusion working group would like to survey our existing meetup organizers to check in and make sure they're familiar with the Ansible Code of Conduct, if they feel comfortable/confident with how to enforce the CoC or address violations, if there have been any incidents, and if there's anything we can do to better support them in this area. ([Meeting notes](https://meetbot.fedoraproject.org/ansible-diversity/2021-02-18/ansible_d&i_wg_agenda:_https:github.comansiblecommunityissues577.2021-02-18-19.02.log.html)) ## Potential Questions: 1. Are you familiar with the Ansible Code of Conduct (CoC)? 2. As a meetup organizer, you are an enforcer of the Ansible Code of Conduct at your events. How comfortable are you with this role? 3. Have you ever had to enforce the Code of Conduct at an Ansible event? 4. Could we help you in this area # Design * Landing page * Why are you being asked this? * Goal seems specified, questions are direct. Do we need other things? * Mention the D&I working group and how to connect with the group * How long it will take * Who gets access to the data * Current Questions * One * Add link to CoC. Spell out "Code of Conduct", don't use the acronym * Does this need to be a scale of familiarity? * Yes *action* define responses * ~~Do they think their *attendees* are familiar? A CoC isn't much use if the people who need it aren't aware of it.~~ * Nope, do this later * Two * Is this clear enough / can it be misinterpreted? Do we need to give scenarios? * Are people going to feel comfortable answering this? Do we need to edge around it? * Three * Can we word this away from hypotheticals (what should Ansible do to help)? We'll likely get unworkable replies - better to use experience eg "what problems have you met when applying the CoC, or think you might meet?" * Do we think help might take different forms in different scenarios? i.e do we need to ask this more than once for different scenarios? * Thanks & when to expect results * Notes * No question on incidents - the goals state "if there have been any incidents" but we haven't asked about it * Do we need demographics? I can see differences of opinion, say, across different coutries ... * Maybe we can ask them to indicate which meetup group(s) they organize, we need to be able to contact them anyway to follow up if they need assistance * Do we have anyone we can test the survey on? * How about Red Hatters who organize some of the meetups? (e.g. gundalow) ## ~~Draft~~ Survey The Ansible community Diversity and Inclusion (D&I) [working group](https://github.com/ansible/community/wiki/Diversity) would like to survey our existing meetup organizers to check in and make sure they're familiar with the Ansible [Code of Conduct](https://docs.ansible.com/ansible/devel/community/code_of_conduct.html#code-of-conduct) (CoC), if they feel confident with how to enforce the CoC or address violations, if there have been any incidents, and if there's anything we can do to better support you in this area. Our goal is to **support you better**, not to blame people. This survey should take no more than 5 minutes of your time. The raw data will be available to the D&I Working Group, and the Ansible Community Team. The aggregate results (for example, the percentage of respondants who answered "Yes" to a specific question) will be made public. No individual responses or personally identifiable information (PII) will be made public. If you need to speak to someone regarding your response, please contact TODO:MAIL https://docs.ansible.com/ansible/devel/community/code_of_conduct.html#code-of-conduct * How familiar are you with the Ansible [Code of Conduct](https://docs.ansible.com/ansible/devel/community/code_of_conduct.html#code-of-conduct) (CoC)? Please answer on a scale of 1-5, where 1 is "I do not know what a CoC is / I have never heard of Ansible's CoC" and 5 is "I have read Ansible's CoC in full / I understand how it applies to my meetup" * As a meetup organizer, you are responsible for enforcing the Ansible Code of Conduct at your events. Do you feel confident in your ability to perform this role? Please answer on a scale of 1-5, where 1 is not at all confident and 5 is "I have already handled these types of incidents or I have had training in responding to these types of incidents". * Have you ever had to enforce the Code of Conduct at an Ansible event? Examples of Code of Conduct enforcement might include: - Asking an attendee to refrain from repeatedly interrupting a speaker - Asking an attendee to refrain from touching another attendee - Prohibiting someone from attending an event due to behaviour they had previously been warned about Yes / No (if YES) * Did you report this incident to the Ansible Community Team (for example; by emailing codeofconduct@ansible.com, emailing a specific member of the community team, or contacting the team on IRC)? * (Optional) Which meetup do you organize (this information will only be shared with the Community Team)? * (Optional) Would you like us to follow up with you to discuss the Ansible Code of Conduct? Yes / No (if YES) * Please provide your email address (this information will only be shared with the Community Team).

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully