CINXE.COM

<!DOCTYPE html> <html lang="en"> <head> <meta charset="utf-8" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /><meta name="generator" content="Docutils 0.17.1: http://docutils.sourceforge.net/" /> <meta property="og:title" content="Code of Conduct" /> <meta property="og:type" content="website" /> <meta property="og:url" content="/code-of-conduct/" /> <meta property="og:site_name" content="Write the Docs" /> <meta property="og:description" content="Why do we have a Code of Conduct?, The principles, Where does the Code of Conduct apply?, Sponsors, affiliates, and exhibitors, What can happen if the CoC is violated?, What to do in case of violat..." /> <meta property="og:image" content="https://www.writethedocs.org/_static/logo-opengraph.png" /> <meta property="og:image:alt" content="Write the Docs" /> <meta name="description" content="Why do we have a Code of Conduct?, The principles, Where does the Code of Conduct apply?, Sponsors, affiliates, and exhibitors, What can happen if the CoC is violated?, What to do in case of violat..." /> <meta name="twitter:card" content="summary_large_image" /> <title>Code of Conduct — Write the Docs</title> <link rel="stylesheet" type="text/css" href="../_static/pygments.css" /> <link rel="stylesheet" type="text/css" href="../_static/alabaster.css" /> <link rel="stylesheet" type="text/css" href="../_static/css/global-customizations.css" /> <link rel="stylesheet" type="text/css" href="../_static/css/survey.css" /> <script data-url_root="../" id="documentation_options" src="../_static/documentation_options.js"></script> <script src="../_static/jquery.js"></script> <script src="../_static/underscore.js"></script> <script src="../_static/_sphinx_javascript_frameworks_compat.js"></script> <script src="../_static/doctools.js"></script> <script src="../_static/sphinx_highlight.js"></script> <link rel="canonical" href="https://www.writethedocs.org/code-of-conduct.html" /> <link rel="shortcut icon" href="../_static/favicon-96x96.png"/> <link rel="index" title="Index" href="../genindex/" /> <link rel="search" title="Search" href="../search/" /> <link rel="next" title="Contact Us" href="../contact/" /> <link rel="prev" title="Documentarians" href="../documentarians/" /> <link rel="stylesheet" href="../_static/custom.css" type="text/css" /> <link rel="alternate" type="application/atom+xml" href="../blog/archive/atom.xml" title="Blog" /> <link href="https://netdna.bootstrapcdn.com/font-awesome/4.0.3/css/font-awesome.min.css" rel="stylesheet" /> <style type="text/css"> ul.ablog-archive { list-style: none; overflow: auto; margin-left: 0px; } ul.ablog-archive li { float: left; margin-right: 5px; font-size: 80%; } ul.postlist a { font-style: italic; } ul.postlist-style-disc { list-style-type: disc; } ul.postlist-style-none { list-style-type: none; } ul.postlist-style-circle { list-style-type: circle; } </style> <script async type="text/javascript" src="/_/static/javascript/readthedocs-addons.js"></script><meta name="readthedocs-project-slug" content="writethedocs-www" /><meta name="readthedocs-version-slug" content="latest" /><meta name="readthedocs-resolver-filename" content="/code-of-conduct/" /><meta name="readthedocs-http-status" content="200" /></head><body> <div class="document"> <div class="announcement-banner-wrapper"> <div class="announcement-banner"> <p>Portland 2025 speakers announced. <a href='/conf/portland/2025/'>Buy your ticket now</a></p> </div> </div> <div class="documentwrapper"> <div class="bodywrapper"> <div class="body" role="main"> <div class="breadcrumbs"> <a href="../">Home</a> » <a href="../about/about-the-org/">About Our Organization</a> » </div> <section id="code-of-conduct"> <h1>Code of Conduct<a class="headerlink" href="#code-of-conduct" title="Permalink to this heading">¶</a></h1> <div class="contents local topic" id="contents"> <ul class="simple"> <li><p><a class="reference internal" href="#why-do-we-have-a-code-of-conduct" id="id1">Why do we have a Code of Conduct?</a></p></li> <li><p><a class="reference internal" href="#the-principles" id="id2">The principles</a></p></li> <li><p><a class="reference internal" href="#where-does-the-code-of-conduct-apply" id="id3">Where does the Code of Conduct apply?</a></p></li> <li><p><a class="reference internal" href="#sponsors-affiliates-and-exhibitors" id="id4">Sponsors, affiliates, and exhibitors</a></p></li> <li><p><a class="reference internal" href="#what-can-happen-if-the-coc-is-violated" id="id5">What can happen if the CoC is violated?</a></p></li> <li><p><a class="reference internal" href="#what-to-do-in-case-of-violations" id="id6">What to do in case of violations</a></p></li> <li><p><a class="reference internal" href="#guidelines-for-reporting-incidents" id="id7">Guidelines for reporting incidents</a></p></li> <li><p><a class="reference internal" href="#other-assistance" id="id8">Other assistance</a></p></li> <li><p><a class="reference internal" href="#reporting-and-contact-information" id="id9">Reporting and contact information</a></p></li> <li><p><a class="reference internal" href="#reports-about-a-code-of-conduct-response-team-member" id="id10">Reports about a Code of Conduct response team member</a></p></li> <li><p><a class="reference internal" href="#thanks" id="id11">Thanks</a></p></li> </ul> </div> <p>Write the Docs is a global community of documentarians who share information, discuss ideas, and work together to improve the art and science of documentation. Everybody who participates in our community in one way or another is required to conform to this Code of Conduct (CoC). This includes online communications, meetup and conference attendees, speakers, sponsors, founders, moderators, organisers and volunteers.</p> <section id="why-do-we-have-a-code-of-conduct"> <h2>Why do we have a Code of Conduct?<a class="headerlink" href="#why-do-we-have-a-code-of-conduct" title="Permalink to this heading">¶</a></h2> <p>Our goals with having this Code of Conduct are:</p> <ul class="simple"> <li><p>Helping everyone feel safe and included. Many documentarians are new to our community, and some may have had poor experiences in other communities. We want to set the expectation that harassment and other unpleasant behaviour are not acceptable. If people do have an unpleasant experience, they’ll know that’s neither the norm nor acceptable to us as a community.</p></li> <li><p>Helping to build trust that if an incident is reported, we will do a thorough investigation, and not blame the reporter. Even, for example, if the incident concerns someone in a position of power.</p></li> <li><p>Informing everyone of the expected behaviour. We are a diverse community, and having a Code of Conduct makes the expectations of everybody’s behaviour explicit and transparent.</p></li> <li><p>Having a framework for report handling. The Code of Conduct is the basis for dealing with a report, assessing whether the CoC was violated, and what action should be taken.</p></li> </ul> <p>The Code of Conduct isn’t an exhaustive list of things that you must do, or can’t do. Rather, take it in the spirit in which it’s intended. It’s a guide to make it easier to enrich all of us and the communities in which we participate, and which we represent.</p> <p>If you believe someone is violating the Code of Conduct, please report it. Contact details for each space are listed at the end of this page. When handling a report, we follow our <a class="reference internal" href="../code-of-conduct-response/"><span class="doc">Code of Conduct Response Guide</span></a>.</p> </section> <section id="the-principles"> <h2>The principles<a class="headerlink" href="#the-principles" title="Permalink to this heading">¶</a></h2> <ul class="simple"> <li><p><strong>Be friendly and patient.</strong></p></li> <li><p><strong>Be welcoming.</strong> We strive to be a community that welcomes and supports people of all backgrounds and identities. This includes, but is not limited to members of any race, ethnicity, culture, national origin, color, immigration status, social and economic class, educational level, sex, sexual orientation, gender identity and expression, age, size, family status, religion, and mental and physical ability.</p></li> <li><p><strong>Be considerate.</strong> Your work will be used by other people, and you in turn will depend on the work of others. Any decision you take will affect users and colleagues, and you should take those consequences into account when making decisions. Remember that we’re a world-wide community, so you might not be communicating in someone else’s primary language.</p></li> <li><p><strong>Be respectful.</strong> Not all of us will agree all the time, but disagreement is no excuse for poor behavior and poor manners. We might all experience some frustration now and then, but we cannot allow that frustration to turn into a personal attack. It’s important to remember that a community where people feel uncomfortable or threatened is not a productive one. Members of the Write the Docs community should be respectful when dealing with other members as well as with people outside the community.</p></li> <li><p><strong>Be careful in the words that you choose.</strong> We are a community of professionals, and we conduct ourselves professionally. Be kind to others. Do not insult or put down other participants, individually or as a group. Harassment and other exclusionary behavior aren’t acceptable. This includes, but is not limited to:</p> <ul> <li><p>Violent threats or language directed against another person.</p></li> <li><p>Discriminatory jokes and language.</p></li> <li><p>Posting sexually explicit or violent material.</p></li> <li><p>Personal insults, especially those using discriminatory terms.</p></li> <li><p>Inappropriate physical contact or unwelcome sexual attention.</p></li> <li><p>Harassing photography or recording, including taking photos of someone who is wearing a no photo-lanyard.</p></li> <li><p>Sustained disruption of talks or other events.</p></li> <li><p>Deliberate misgendering.</p></li> <li><p>Deliberate “outing” of any private aspect of a person’s identity without their consent except as necessary to protect vulnerable people from intentional abuse. This includes sharing personally identifying information (“doxing”).</p></li> <li><p>Knowingly making harmful false claims about a person.</p></li> <li><p>Pushing a person to drink alcohol when they don’t want to drink, or deceiving someone into drinking alcohol.</p></li> <li><p>Harassment of others in any form. In general, if someone asks you to stop, then stop.</p></li> <li><p>Advocating for, threatening to, or encouraging, any of the above behavior.</p></li> </ul> </li> </ul> <p>Some events may provide alcoholic drinks. However, participants are expected to drink responsibly. Alcohol use or other intoxication are never accepted as an excuse for CoC violations.</p> </section> <section id="where-does-the-code-of-conduct-apply"> <h2>Where does the Code of Conduct apply?<a class="headerlink" href="#where-does-the-code-of-conduct-apply" title="Permalink to this heading">¶</a></h2> <p>This Code of Conduct applies to all spaces managed by Write the Docs. This includes:</p> <ul class="simple"> <li><p>Conferences (including social events and peripheral activities)</p></li> <li><p>Unconferences and sprints</p></li> <li><p>Meetups, including their discussion boards</p></li> <li><p>Workshops</p></li> <li><p>Presentation materials used in talks or sessions</p></li> <li><p>Slack</p></li> <li><p>Mailing lists</p></li> <li><p>GitHub</p></li> <li><p>Twitter hashtag and mentions</p></li> <li><p>forum.writethedocs.org</p></li> <li><p>Any other forums created by the which the community uses for communication.</p></li> </ul> <p>The Code of Conduct does not exclusively apply to events on an official agenda. For example, if after a scheduled social event you go to a bar with a group of fellow participts, and someone harasses you there, we would still treat that as a CoC violation. Similarly, harassment in Twitter direct messages related to Write the Docs can still be covered under this Code of Conduct.</p> <p>In addition, violations of this code outside our spaces may affect a person’s ability to participate in them.</p> </section> <section id="sponsors-affiliates-and-exhibitors"> <h2>Sponsors, affiliates, and exhibitors<a class="headerlink" href="#sponsors-affiliates-and-exhibitors" title="Permalink to this heading">¶</a></h2> <p>When you sponsor a Write the Docs event, we welcome you as a member of our community, and we expect you to be respectful to the community you operate within.</p> <p>All exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the Code of Conduct. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) must not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.</p> <p>In addition, sponsors and affiliates of conference, meetups, and online activities should not employ aggressive recruiting techniques, invasive marketing behavior, or similar actions towards community members. In case of violations, sponsors might be sanctioned and expelled from the event or activity with no return of the sponsorship contribution.</p> </section> <section id="what-can-happen-if-the-coc-is-violated"> <h2>What can happen if the CoC is violated?<a class="headerlink" href="#what-can-happen-if-the-coc-is-violated" title="Permalink to this heading">¶</a></h2> <p>In case of a Code of Conduct violation, some of the most common actions organisers may take are:</p> <ul class="simple"> <li><p>No action (if the team determines no violation occurred).</p></li> <li><p>A private or public reprimand.</p></li> <li><p>Requiring that a public apology is made.</p></li> <li><p>Requiring that a participant stops their behaviour.</p></li> <li><p>Requiring that a participant prevents further contact with certain other participants.</p></li> <li><p>Not publishing the video of a conference talk.</p></li> <li><p>Cancelling a conference talk.</p></li> <li><p>Removing a participant from the conference, meetup or online space, without refund.</p></li> </ul> <p>The action taken is at the discretion of the Code of Conduct team. Participants are expected to comply immediately, and further action may be taken in case a participant does not comply. A record will be kept of all incidents.</p> </section> <section id="what-to-do-in-case-of-violations"> <h2>What to do in case of violations<a class="headerlink" href="#what-to-do-in-case-of-violations" title="Permalink to this heading">¶</a></h2> <p>If a Code of Conduct incident happens that affects you, or witness it affecting someone else, please contact the appropriate CoC team immediately. See the contact details below for the different teams for different spaces. In all cases, you may email <a class="reference external" href="mailto:conduct%40writethedocs.org">conduct<span>@</span>writethedocs<span>.</span>org</a>, but contacting local organisers may be faster. Email to the <a class="reference external" href="mailto:conduct%40writethedocs.org">conduct<span>@</span>writethedocs<span>.</span>org</a> is received by all members of the <a class="reference internal" href="../team/#core-team"><span class="std std-ref">Core Operations (CoreOps)</span></a>.</p> </section> <section id="guidelines-for-reporting-incidents"> <h2>Guidelines for reporting incidents<a class="headerlink" href="#guidelines-for-reporting-incidents" title="Permalink to this heading">¶</a></h2> <p>Please do not feel like you may be a burden to us by reporting incidents. Even if you happen to report multiple incidents. We rather consider reports an opportunity for us to act: by knowing about an incident, we can act on it, and often prevent it from continuing or repeating. But if we don’t know, we can’t take action.</p> <p>If you are not sure whether the situation was a Code of Conduct violation, or whether the CoC applied to that particular space, we encourage you to still report it. We would much rather have a additional reports where we decide to take no action, rather than miss a report of an actual violation. We do not look negatively on you if we find the incident is not a violation. And knowing about incidents that are not violations, or happen outside our spaces, can also help us to improve the Code of Conduct or the processes surrounding it.</p> <p>In your report please include, when possible:</p> <ul class="simple"> <li><p>Your contact info (so we can get in touch with you)</p></li> <li><p>Names or descriptions of anyone who was involved or who witnessed the incident.</p></li> <li><p>When and where the incident occurred. Please be as specific as possible.</p></li> <li><p>Your account of what occurred. If there is a written record (e.g. tweets or Slack messages) please include screenshots, or otherwise a link.</p></li> <li><p>Any extra context you believe existed for the incident.</p></li> <li><p>If you believe this incident is ongoing.</p></li> <li><p>Any other information you believe we should have.</p></li> </ul> <p>If you don’t communicate all of this information at the time, please still make the report and include as much information as you have.</p> <p>If you feel unsafe reporting in person, you may choose someone to represent you. In this case, we’d need their contact information, but we’d ask you to make clear that this person represents you.</p> <p>When handling a report, we follow our <a class="reference internal" href="../code-of-conduct-response/"><span class="doc">Code of Conduct Response Guide</span></a>.</p> <p>All reports will be kept confidential. In some cases a public statement might be required (for example in a CoC transparency report following conferences), but these reports are anonymized and do not include any personally identifying information.</p> </section> <section id="other-assistance"> <h2>Other assistance<a class="headerlink" href="#other-assistance" title="Permalink to this heading">¶</a></h2> <p>Conference staff will be happy to help participants contact hotel/venue security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the conference. However, we will not contact security or law enforcement without your consent, except if the safety risk is so significant that there is no other reasonable option.</p> </section> <section id="reporting-and-contact-information"> <h2>Reporting and contact information<a class="headerlink" href="#reporting-and-contact-information" title="Permalink to this heading">¶</a></h2> <ul class="simple"> <li><p>Each Write the Docs conference has a Code of Conduct team. For each conference, their names and contact details are listed below. They will be introduced at the start of the conference. You can also approach any other staff member, who can be identified by t-shirts or special badges.</p></li> <li><p>For online platforms, we ask that you make any reports by emailing <a class="reference external" href="mailto:conduct%40writethedocs.org">conduct<span>@</span>writethedocs<span>.</span>org</a>. This is received by all members of the <a class="reference internal" href="../team/#core-team"><span class="std std-ref">Core Operations (CoreOps)</span></a>. For reports on incidents on Slack, the core team may involve the <a class="reference internal" href="../team/#moderation-team"><span class="std std-ref">moderation team</span></a>.</p></li> <li><p>For meetups, please report the incident to the local meetup organisers. If you feel uncomfortable with this, if you feel the incident was not well handled by the local organisers, or if you are a meetup organiser and would like to ask for input, you can email <a class="reference external" href="mailto:conduct%40writethedocs.org">conduct<span>@</span>writethedocs<span>.</span>org</a>.</p></li> </ul> <p>If you believe anyone is in physical danger, please notify appropriate law enforcement first when possible. If you are unsure which law enforcement agency is appropriate, please include this in your report and we will attempt to notify them.</p> </section> <section id="reports-about-a-code-of-conduct-response-team-member"> <h2>Reports about a Code of Conduct response team member<a class="headerlink" href="#reports-about-a-code-of-conduct-response-team-member" title="Permalink to this heading">¶</a></h2> <p>If your report concerns a member of the Code of Conduct team of a conference, you can report the issue to any other response team member or any other organiser. For reports regarding meetup organisers, you can make the report to another meetup organiser, if there is one. If this is not possible, or for any reason you feel uncomfortable with this, you can also email <a class="reference external" href="mailto:conduct%40writethedocs.org">conduct<span>@</span>writethedocs<span>.</span>org</a>.</p> <p>If your report concerns a member of the <a class="reference internal" href="../team/#core-team"><span class="std std-ref">Core Operations (CoreOps)</span></a>, which receives emails to <a class="reference external" href="mailto:conduct%40writethedocs.org">conduct<span>@</span>writethedocs<span>.</span>org</a>, you can report the issue individually to any of the other core team members.</p> <section id="portland-conference-code-of-conduct-team"> <h3>Portland conference Code of Conduct Team<a class="headerlink" href="#portland-conference-code-of-conduct-team" title="Permalink to this heading">¶</a></h3> <p><strong>Eric Holscher</strong></p> <ul class="simple"> <li><p><a class="reference external" href="mailto:eric%40writethedocs.org">eric<span>@</span>writethedocs<span>.</span>org</a></p></li> <li><p>Phone: 757-705-0532</p></li> <li><p>Slack: ericholscher</p></li> </ul> <p><strong>Samuel Wright</strong></p> <ul class="simple"> <li><p><a class="reference external" href="mailto:sam%40writethedocs.org">sam<span>@</span>writethedocs<span>.</span>org</a></p></li> <li><p>Slack: plaindocs</p></li> </ul> </section> <section id="atlantic-conference-code-of-conduct-team"> <h3>Atlantic conference Code of Conduct Team<a class="headerlink" href="#atlantic-conference-code-of-conduct-team" title="Permalink to this heading">¶</a></h3> <p><strong>Sasha Romijn</strong></p> <ul class="simple"> <li><p><a class="reference external" href="mailto:sasha%40writethedocs.org">sasha<span>@</span>writethedocs<span>.</span>org</a></p></li> <li><p>Slack: sasha</p></li> </ul> <p><strong>Samuel Wright</strong></p> <ul class="simple"> <li><p><a class="reference external" href="mailto:sam%40writethedocs.org">sam<span>@</span>writethedocs<span>.</span>org</a></p></li> <li><p>Slack: plaindocs</p></li> </ul> <p><strong>Mikey Ariel</strong></p> <ul class="simple"> <li><p><a class="reference external" href="mailto:mikey%40writethedocs.org">mikey<span>@</span>writethedocs<span>.</span>org</a></p></li> <li><p>Slack: thatdocslady</p></li> </ul> </section> <section id="australia-code-of-conduct-team"> <h3>Australia Code-of-Conduct Team<a class="headerlink" href="#australia-code-of-conduct-team" title="Permalink to this heading">¶</a></h3> <p><strong>Swapnil Ogale</strong></p> <ul class="simple"> <li><p><a class="reference external" href="mailto:swapnilogale%40gmail.com">swapnilogale<span>@</span>gmail<span>.</span>com</a></p></li> <li><p>Slack: swapnil_ogale</p></li> </ul> <p><strong>Sam Wright</strong></p> <ul class="simple"> <li><p><a class="reference external" href="mailto:sam%40writethedocs.org">sam<span>@</span>writethedocs<span>.</span>org</a></p></li> <li><p>Slack: plaindocs</p></li> </ul> </section> </section> <section id="thanks"> <h2>Thanks<a class="headerlink" href="#thanks" title="Permalink to this heading">¶</a></h2> <p>This Code of Conduct was originally based on the <a class="reference external" href="https://2018.djangocon.eu/conduct/">DjangoCon Europe 2018 Code of Conduct</a> and the <a class="reference external" href="https://www.djangoproject.com/conduct/">Django Project Code of Conduct</a>, which in turn credits the original text of the Speak Up! project, inspired in its turn by the Fedora Project, as well as the Python Mentorship Project and many others. Some inspiration was also taken from the <a class="reference external" href="https://www.freebsd.org/internal/code-of-conduct.html">FreeBSD Code of Conduct</a></p> </section> </section> <div class="section"> </div> </div> </div> </div> <div class="sphinxsidebar" role="navigation" aria-label="main navigation"> <div class="sphinxsidebarwrapper"> <p class="logo"> <a href="../"> <img class="logo" src="../_static/sticker-wtd-colors.png" alt="Logo" /> </a> </p> <br> <p> Write the Docs is a global community of people who care about documentation. We have a Slack community, conferences on 3 continents, and local meetups! </p> <div id="searchbox" style="display: none" role="search"> <h3 id="searchlabel">Quick search</h3> <div class="searchformwrapper"> <form class="search" action="../search/" method="get"> <input type="text" name="q" aria-labelledby="searchlabel" autocomplete="off" autocorrect="off" autocapitalize="off" spellcheck="false"/> <input type="submit" value="Go" /> </form> </div> </div> <script>document.getElementById('searchbox').style.display = "block"</script><style> .ethical-alabaster::before {margin-top: 1em;} </style> <div id="ethical-ad-placement"></div> <div id="toc"> <h3>Site Content</h3> <ul class="current"> <li class="toctree-l1"><a class="reference internal" href="../surveys/">Salary Surveys</a></li> <li class="toctree-l1"><a class="reference internal" href="../guide/">Software documentation guide</a></li> <li class="toctree-l1"><a class="reference internal" href="../book-club/">Book Club</a></li> <li class="toctree-l1"><a class="reference internal" href="../hiring-guide/">Hiring guide</a></li> <li class="toctree-l1"><a class="reference internal" href="../about/stay-connected/">Stay Connected</a></li> <li class="toctree-l1 current"><a class="reference internal" href="../about/about-the-org/">About Our Organization</a></li> <li class="toctree-l1"><a class="reference internal" href="../about/events-activities/">Events and Activities</a></li> <li class="toctree-l1"><a class="reference internal" href="../about/learning-resources/">Learning Resources</a></li> </ul> </div> <br> <h3>Join our mailing list</h3>  <link href="//cdn-images.mailchimp.com/embedcode/classic-071822.css" rel="stylesheet" type="text/css"> <style type="text/css"> #mc_embed_signup{background:#fff; clear:left; font:14px Helvetica,Arial,sans-serif;} /* Add your own Mailchimp form style overrides in your site stylesheet or in this style block. We recommend moving this block and the preceding CSS link to the HEAD of your HTML file. */ </style> <div id="mc_embed_signup"> <form action="https://writethedocs.us6.list-manage.com/subscribe/post?u=94377ea46d8b176a11a325d03&id=dcf0ed349b&f_id=00d2c2e1f0" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate> <div id="mc_embed_signup_scroll"> <div class="mc-field-group"> <label for="mce-EMAIL">Email Address <span class="asterisk">*</span> </label> <input type="email" value="" name="EMAIL" class="required email" id="mce-EMAIL" required> <span id="mce-EMAIL-HELPERTEXT" class="helper_text"></span> </div> <div class="mc-field-group input-group"> <strong>What types of updates would you like? </strong> <ul><li> <input type="checkbox" value="1" name="group[14633][1]" id="mce-group[14633]-14633-0" checked> <label for="mce-group[14633]-14633-0">Monthly Community Newsletter</label> </li> <li> <input type="checkbox" value="2" name="group[14633][2]" id="mce-group[14633]-14633-1"> <label for="mce-group[14633]-14633-1">North American Conference Announcements</label> </li> <li> <input type="checkbox" value="4" name="group[14633][4]" id="mce-group[14633]-14633-2"> <label for="mce-group[14633]-14633-2">European Conference Announcements</label> </li> <li> <input type="checkbox" value="8" name="group[14633][8]" id="mce-group[14633]-14633-3"> <label for="mce-group[14633]-14633-3">Australian Conference Announcements</label> </li> <li> <input type="checkbox" value="16" name="group[14633][16]" id="mce-group[14633]-14633-4"> <label for="mce-group[14633]-14633-4">Atlantic Conference Announcements</label> </li> </ul> <span id="mce-group[14633]-HELPERTEXT" class="helper_text"></span> </div> <div id="mce-responses" class="clear"> <div class="response" id="mce-error-response" style="display:none"></div> <div class="response" id="mce-success-response" style="display:none"></div> </div>  <div style="position: absolute; left: -5000px;" aria-hidden="true"><input type="text" name="b_94377ea46d8b176a11a325d03_dcf0ed349b" tabindex="-1" value=""></div> <div class="clear"><input type="submit" value="Subscribe" name="subscribe" id="mc-embedded-subscribe" class="button"></div> </div> </form> </div>  </div> </div> <div class="clearer"></div> </div> <style> /* Sponsors */ .sponsors { float: left; margin-top: 12px; text-align: center; } .sponsors .sponsor { display: inline-block; text-align: center; text-decoration: none; padding: 10px; } .sponsors .sponsor img { width: 90px; height: auto; } .sponsors .sponsor-name { font-size: 12px; } .sponsors .sponsor-description { font-size: 10px; color: #BCC1C3; } .sponsors .sponsor-name, .sponsors .sponsor-description { text-align: center; line-height: 1.4; } /* Links in footer */ .footer-links { display: flex; justify-content: space-between; gap: 1rem; } #social-footer { line-height: 1.5rem; } div.footer,div.footer a { color: #757575; } </style> <div class="footer"> <div class="container footer-links"> <div style="flex-basis: 20rem; text-align: left;"> <span>© Write the Docs</span> <span>  <a rel="license" href="http://creativecommons.org/licenses/by-nc-sa/4.0/"><img alt="Creative Commons License" style="border-width:0; vertical-align: middle;" src="https://i.creativecommons.org/l/by-nc-sa/4.0/80x15.png" /></a> </span> </div> <div id="social-footer"> <span><a href="/contact/"><i class="iconf-email"></i>Contact Us</a></span> | <span><a href="/site-map"><i class="iconf-github-circled-alt2"></i>Site map</a></span> | <span><a href="https://github.com/writethedocs"><i class="iconf-github-circled-alt2"></i>GitHub</a></span> | <span><a href="https://twitter.com/writethedocs"><i class="iconf-twitter-circled"></i>Twitter</a></span> | <span> <a href="https://www.linkedin.com/company/write-the-docs"> LinkedIn </a> </span> | <span><a href="#">Code of Conduct</a></span> | </div> </div> <div class="sponsors" id="community-sponsors" style="width: 100%;"> <hr> <a class="sponsor" href="https://readthedocs.org" rel="noopener" target="_blank"> <img src="https://read-the-docs-guidelines.readthedocs-hosted.com/_images/logo-wordmark-dark.png" alt="Read the Docs" class="sponsor-image"> <div class="sponsor-name">Read the Docs</div> <div class="sponsor-description">Website Hosting</div> </a> <a class="sponsor" href="https://www.gitbook.com/?utm_campaign=launch&utm_medium=display&utm_source=write_the_docs&utm_content=ad" rel="noopener" target="_blank"> <img src="/_static/img/sponsors/gitbook.png" alt="GitBook" class="sponsor-image"> <div class="sponsor-name">GitBook</div> <div class="sponsor-description">Community sponsor</div> </a> <a class="sponsor" href="../sponsorship/" rel="noopener" target="_blank"> <div class="sponsor-name">Sponsorship Info</div> </a> </div> </div>  <script async defer src="https://scripts.simpleanalyticscdn.com/latest.js"></script> <noscript><img src="https://queue.simpleanalyticscdn.com/noscript.gif" alt="" referrerpolicy="no-referrer-when-downgrade" /></noscript> </body> </html>