<commit_before>{% extends "conduct/base.html" %}

{% block title %}Django Code of Conduct - FAQ{% endblock %}

{% block content %}
<h1>Django Code of Conduct - FAQ</h1>

<h2 class="deck">
This FAQ attempts to address common questions and concerns around the Django
communnity's <a href="/conduct/">Code of Conduct</a>. If you still have
questions after reading it, please feel free to
<a href="mailto:<EMAIL>">contact us</a>.
</h2>

<h3 id="why-adopt">Why have you adopted a Code of Conduct? <a class="plink" href="#why-adopt">¶</a></h3>

    <p>We think the Django community is awesome. If you're familiar with the Django
    community, you'll probably notice that the Code basically matches what
    we already do. Think of this as documentation: we're taking implicit
    expectations about behavior and making them explicit.</p>

    <p>We're doing this because the Django community is growing faster than any of
    us could have anticipated. This is on balance a very positive thing, but
    as we've grown past the point where it's possible to know the whole community
    we think it's very important to be clear about our values.</p>

    <p>We know that the Django community is open, friendly, and welcoming. We want to
    make sure everyone else knows it too.</p>

<h3 id="what-does-it-mean">What does it mean to "adopt" a Code of Conduct? <a class="plink" href="#what-does-it-mean">¶</a></h3>

    <p>For the most part, we don't think it means large changes. We think that the text
    does a really good job describing the way the Django community already conducts
    itself. We expect that most people will simple continue to behave in the
    awesome way they have for years.</p>

    <p>However, we do expect that people will abide by the spirit and words of the CoC
    when in "official" Django spaces. We're proposing that this code — or rather,
    the final draft of it — be adopted simultaneously by the Django core team and by
    the Django Software Foundation. So that means that it'll apply both in community
    spaces <em>and</em> at DSF events.</p>

    <p>In practice, this means mailing lists (django-users, django-developers, etc.),
    the various Django IRC channels (<tt>#django</tt>, <tt>#django-dev</tt>, etc.), bug
    tracking and code review tools, and "official" Django events such as sprints.</p>

<h3 id="dsf-events">What about events funded by the Django Software Foundation? <a class="plink" href="#dsf-events">¶</a></h3>

    <p>This Code of Conduct also covers any events that the DSF funds. However, events
    funded by the DSF already
    <a class="plink" href="https://www.djangoproject.com/foundation/code-of-conduct">require a code of conduct</a>.
    Isn't this redundant?</p><commit_msg>Fixed another tense issue in the FAQ.<commit_after>{% extends "conduct/base.html" %}

{% block title %}Django Code of Conduct - FAQ{% endblock %}

{% block content %}
<h1>Django Code of Conduct - FAQ</h1>

<h2 class="deck">
This FAQ attempts to address common questions and concerns around the Django
communnity's <a href="/conduct/">Code of Conduct</a>. If you still have
questions after reading it, please feel free to
<a href="mailto:<EMAIL>">contact us</a>.
</h2>

<h3 id="why-adopt">Why have you adopted a Code of Conduct? <a class="plink" href="#why-adopt">¶</a></h3>

    <p>We think the Django community is awesome. If you're familiar with the Django
    community, you'll probably notice that the Code basically matches what
    we already do. Think of this as documentation: we're taking implicit
    expectations about behavior and making them explicit.</p>

    <p>We're doing this because the Django community is growing faster than any of
    us could have anticipated. This is on balance a very positive thing, but
    as we've grown past the point where it's possible to know the whole community
    we think it's very important to be clear about our values.</p>

    <p>We know that the Django community is open, friendly, and welcoming. We want to
    make sure everyone else knows it too.</p>

<h3 id="what-does-it-mean">What does it mean to "adopt" a Code of Conduct? <a class="plink" href="#what-does-it-mean">¶</a></h3>

    <p>For the most part, we don't think it means large changes. We think that the text
    does a really good job describing the way the Django community already conducts
    itself. We expect that most people will simple continue to behave in the
    awesome way they have for years.</p>

    <p>However, we do expect that people will abide by the spirit and words of the CoC
    when in "official" Django spaces. This code has been adopted by both the Django core
    team and by the Django Software Foundation. That means that it'll apply both in community
    spaces <em>and</em> at DSF events.</p>

    <p>In practice, this means mailing lists (django-users, django-developers, etc.),
    the various Django IRC channels (<tt>#django</tt>, <tt>#django-dev</tt>, etc.), bug
    tracking and code review tools, and "official" Django events such as sprints.</p>

<h3 id="dsf-events">What about events funded by the Django Software Foundation? <a class="plink" href="#dsf-events">¶</a></h3>

    <p>This Code of Conduct also covers any events that the DSF funds. However, events
    funded by the DSF already
    <a class="plink" href="https://www.djangoproject.com/foundation/code-of-conduct">require a code of conduct</a>.
    Isn't this redundant?</p>
{'fraction_non_alphanumeric': 0.09976116112437994, 'fraction_numerical': 0.0036744442403086534, 'mean_word_length': 3.8434163701067616, 'pattern_counts': {'":': 0, '<': 89, '<?xml version=': 0, '>': 89, 'https://': 2, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1331143', 'n_tokens_mistral': 1615, 'n_tokens_neox': 1499, 'n_words': 743}