Changeset - f4d0eda48514
fixtures/sitetree.json
Show inline comments
 
[
 
{
 
    "model": "sitetree.tree",
 
    "pk": 1,
 
    "fields": {
 
        "title": "main",
 
        "alias": "main"
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 1,
 
    "fields": {
 
        "title": "About",
 
        "hint": "",
 
        "url": "/about/north-bay-python",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": null,
 
        "sort_order": 2,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 3,
 
    "fields": {
 
        "title": "Become a Sponsor",
 
        "title": "Sponsors",
 
        "hint": "",
 
        "url": "/sponsors/become-a-sponsor",
 
        "url": "/sponsors",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": null,
 
        "sort_order": 7,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 7,
 
    "fields": {
 
        "title": "Call for Proposals",
 
        "hint": "",
 
        "url": "/program/call-for-proposals",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": null,
 
        "sort_order": 4,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 8,
 
    "fields": {
 
        "title": "Safety",
 
        "hint": "",
 
        "url": "/code-of-conduct",
...
 
@@ -110,97 +110,97 @@
 
        "title": "News",
 
        "hint": "",
 
        "url": "/news",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": null,
 
        "sort_order": 9,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 11,
 
    "fields": {
 
        "title": "North Bay Python",
 
        "hint": "",
 
        "url": "/about/north-bay-python",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": 1,
 
        "sort_order": 11,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 12,
 
    "fields": {
 
        "title": "The Team",
 
        "title": "Our Team",
 
        "hint": "",
 
        "url": "/about/team",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": 1,
 
        "sort_order": 12,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 13,
 
    "fields": {
 
        "title": "Colophon",
 
        "hint": "",
 
        "url": "/about/colophon",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": 1,
 
        "sort_order": 13,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 14,
 
    "fields": {
 
        "title": "Reporting an Incident",
...
 
@@ -225,50 +225,98 @@
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 15,
 
    "fields": {
 
        "title": "Staff Procedures",
 
        "hint": "",
 
        "url": "/code-of-conduct/harassment-staff-procedures",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": 8,
 
        "sort_order": 17,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 17,
 
    "fields": {
 
        "title": "Code of Conduct",
 
        "hint": "",
 
        "url": "/code-of-conduct",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": 8,
 
        "sort_order": 14,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 21,
 
    "fields": {
 
        "title": "Our Sponsors",
 
        "hint": "",
 
        "url": "/sponsors",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": 3,
 
        "sort_order": 21,
 
        "access_permissions": []
 
    }
 
},
 
{
 
    "model": "sitetree.treeitem",
 
    "pk": 23,
 
    "fields": {
 
        "title": "Become a Sponsor",
 
        "hint": "",
 
        "url": "/sponsors/become-a-sponsor",
 
        "urlaspattern": false,
 
        "tree": 1,
 
        "hidden": false,
 
        "alias": null,
 
        "description": "",
 
        "inmenu": true,
 
        "inbreadcrumbs": true,
 
        "insitetree": true,
 
        "access_loggedin": false,
 
        "access_guest": false,
 
        "access_restricted": false,
 
        "access_perm_type": 1,
 
        "parent": 3,
 
        "sort_order": 22,
 
        "access_permissions": []
 
    }
 
}
 
]
pinaxcon/templates/_account_bar.html
Show inline comments
 
{% load i18n %}
 
{% load account_tags %}
 

	
 

	
 
<ul class="nav navbar-nav pull-right">
 
    {% if request.user.is_authenticated %}
 
        <span class="navbar-text">
 
            <i class="fa fa-user"></i> {% user_display request.user %}
 
        </span>
 
        <li>
 
            <a href="{% url "dashboard" %}"><i class="fa fa-tasks"></i> {% trans "Dashboard" %}</a>
 
        </li>
 
        <li>
 
            <a id="account_logout" href="{% url 'account_logout' %}"><i class="fa fa-power-off"></i> {% trans "Log out" %}</a>
 
        </li>
 
    {% else %}
 
        <li><a href="{% url 'account_login' %}">{% trans "Log in" %}</a></li>
 
        {% if ACCOUNT_OPEN_SIGNUP %}
 
            <li><a href="{% url 'account_signup' %}">{% trans "Sign up" %}</a></li>
 
        {% endif %}
 
    {% endif %}
 
</ul>
 

	
 
<form id="accountLogOutForm" action="{% url 'account_logout' %}" method="POST">
 
    {% csrf_token %}
 
</form>
pinaxcon/templates/_default_sidebar.html
Show inline comments
 
{% load sponsorship_tags %}
 
{% load thumbnail %}
 
{% load pinax_boxes_tags %}
 

	
 
{% sponsor_levels as levels %}
 

	
 
<h4>Sponsors</h4>
 

	
 
<div class="sponsor-list">
 
    {% for level in levels %}
 
        {% if level.sponsors %}
 
            <h3>{{ level.name }}</h3>
 

	
 
            {% for sponsor in level.sponsors %}
 
                <div>
 
                    {% if sponsor.website_logo %}
 
                        <a href="{{ sponsor.external_url }}">
 
                        <a href="{{ sponsor.external_url }}" title="{{ sponsor.name }}">
 
                            <img src="{% thumbnail sponsor.website_logo '150x90' %}" alt="{{ sponsor.name }}" />
 
                        </a>
 
                    {% else %}
 
                        <a href="{{ sponsor.external_url }}">{{ sponsor.name }}</a>
 
                        <a href="{{ sponsor.external_url }}" title="{{ sponsor.name }}">{{ sponsor.name }}</a>
 
                    {% endif %}
 
                </div>
 
            {% endfor %}
 
        {% endif %}
 
    {% endfor %}
 
</div>
 

	
 

	
pinaxcon/templates/_footer.html
Show inline comments
 
<div class="pull-left">
 
    North Bay Python is a member project of the <a href="https://sfconservancy.org">Software Freedom Conservancy</a>, a 501(c)(3) charity.<br/>
 
    North Bay Python is a member project of the <a href="https://sfconservancy.org" title="Software Freedom Conservancy">Software Freedom Conservancy</a>, a 501(c)(3) charity.<br/>
 

	
 
    <a href="https://facebook.com/northbaypython">Facebook</a> | <a href="https://twitter.com/northbaypython">Twitter</a> | <a href="https://lanyrd.com/2017/nbpy">Lanyrd</a> | <a href="/code-of-conduct">Code of Conduct</a> | <a href="/terms-and-conditions">Terms and Conditions</a> | <a href="/about/colophon">Colophon</a>
 
    <a href="https://facebook.com/northbaypython" title="North Bay Python on Facebook">Facebook</a> | <a href="https://twitter.com/northbaypython" title="North Bay Python on Twitter">Twitter</a> | <a href="https://lanyrd.com/2017/nbpy" title="North Bay Python on Lanyrd">Lanyrd</a> | <a href="/code-of-conduct" title="North Bay Python Code of Conduct">Code of Conduct</a> | <a href="/terms-and-conditions" title="North Bay Python Terms and Conditions">Terms and Conditions</a> | <a href="/about/colophon" title="North Bay Python Colophon">Colophon</a>
 
</div>
 

	
 
<div class="pull-right">
 
    Site powered by <a href="https://github.com/chrisjrn/symposion/"><b>Symposion</b></a>
 
    and <a href="https://github.com/chrisjrn/registrasion/"><b>Registrasion</b></a>.
 
    Site powered by <a href="https://github.com/chrisjrn/symposion/" title="Symposion Git Repository"><b>Symposion</b></a>
 
    and <a href="https://github.com/chrisjrn/registrasion/" title="Registrasion Git Repository"><b>Registrasion</b></a>.
 
</div>
pinaxcon/templates/dashboard.html
Show inline comments
 
{% extends "site_base.html" %}
 

	
 
{% load i18n %}
 
{% load proposal_tags %}
 
{% load review_tags %}
 
{% load teams_tags %}
 
{% load registrasion_tags %}
 
{% load account_tags %}
 

	
 
{% block head_title %}Dashboard{% endblock %}
 

	
 
{% block body_class %}auth{% endblock %}
 

	
 
{% block body %}
 

	
 
    <div class="panel panel-default">
 
      <div class="panel-heading">
 
          <h3 class="panel-title">
 
              <i class="fa fa-user-o"></i>
 
              Account
 
              <span class="pull-right">
 
                <i class="fa fa-user"></i> {% user_display request.user %}
 
              </span>
 
          </h3>
 
      </div>
 
      <div class="panel-body">
 
        <li>
 
            <a href="{% url 'account_password' %}">{% trans "Change password" %}</a>
 
        </li>
 
      </div>
 
    </div>
 

	
 
    <div class="panel panel-default">
 
        <div class="panel-heading">
 
            <div class="pull-right">
 
                {% if not user.speaker_profile %}
 
                    <a href="{% url "speaker_create" %}" class="btn btn-xs btn-default">
 
                        <i class="fa fa-plus-sign"></i> Create a speaker profile
 
                    </a>
 
                {% else %}
 
                    <a href="{% url "speaker_edit" %}" class="btn btn-xs btn-default">
 
                        <i class="fa fa-pencil"></i> Edit your speaker profile
 
                    </a>
 
                    <a href="{% url "proposal_submit" %}" class="btn btn-xs btn-default">
 
                    <a href="/proposals/submit/talk" class="btn btn-xs btn-default">
 
                        <i class="fa fa-plus-sign"></i> Submit a new proposal
 
                    </a>
 
                {% endif %}
 
            </div>
 
            <h3 class="panel-title">
 
                <i class="fa fa-bullhorn"></i>
 
                {% trans "Speaking" %}
 
            </h3>
 
        </div>
 

	
 
        <div class="panel-body">
 
            {% if not user.speaker_profile %}
 
                <p>To submit a proposal, you must first <a href="{% url "speaker_create" %}">create a speaker profile</a>.</p>
 
            {% else %}
 
                <h4>Your Proposals</h4>
 
                {% if not user.speaker_profile.proposals.exists %}
 
                    <p>No proposals submitted yet.</p>
 
                {% endif %}
 
            {% endif %}
 
        </div>
 
        {% if user.speaker_profile.proposals.exists %}
 
            <table class="table">
 
                <tr>
 
                    <th>Title</th>
 
                    <th>Session type</th>
 
                    <th>Status</th>
 
                    <th>Actions</th>
 
                </tr>
 
                {% for proposal in user.speaker_profile.proposals.all %}
 
                    {% include "symposion/proposals/_proposal_row.html" %}
 
                {% endfor %}
 
            </table>
 
        {% endif %}
 

	
 
        {% if user.speaker_profile %}
 
            {% associated_proposals as associated_proposals %}
 
            {% if associated_proposals %}
 
                <div class="panel-body">
 
                    <h4>Proposals you have joined as an additional speaker</h4>
 
                </div>
 
                <table class="table">
 
                    <tr>
 
                        <th>Title</th>
 
                        <th>Session type</th>
 
                        <th>Status</th>
 
                        <th>Actions</th>
 
                    </tr>
 
                    {% for proposal in associated_proposals %}
pinaxcon/templates/static_pages/about/colophon.html
Show inline comments
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}Colophon{% endblock %}
 

	
 
{% block heading %}Colophon{% endblock %}
 

	
 
{% block body_class %}about{% endblock %}
 

	
 
{% block content %}
 

	
 
<h2>Call for Proposals</h2>
 

	
 
<p>Portions of our <a href="/program/call-for-proposals">Call for Proposals</a> page were drawn from ideas seen on <a href="https://djangocon.eu">DjangoCon EU</a>, <a href="https://seagl.org">SeaGL</a>, <a href="http://www.fogcityruby.com/speak/">Fog City Ruby</a>, and others. Thanks to all for their inspiration and permission to borrow!</p>
 
<p>Portions of our <a href="/program/call-for-proposals" title="North Bay Python Call for Proposals">Call for Proposals</a> page were drawn from ideas seen on <a href="https://djangocon.eu" title="DjangoCon Europe">DjangoCon EU</a>, <a href="https://seagl.org" title="Seattle GNU Linux">SeaGL</a>, <a href="http://www.fogcityruby.com/speak/" title="Fog City Ruby">Fog City Ruby</a>, and others. Thanks to all for their inspiration and permission to borrow!</p>
 

	
 
<h2>Code of Conduct</h2>
 

	
 
<p>Our <a href="/code-of-conduct">Code of Conduct</a> was forked from the <a href="https://github.com/python/pycon-code-of-conduct">PyCon US Code of Conduct</a>, including the staff and attendee guides, under a <a href="http://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution 3.0 Unported License</a>, itself originally forked from the example policy from the <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy">Geek Feminism wiki</a>, created by the <a href="https://adainitiative.org/">Ada Initiative</a> and other volunteers, which is under a <a href="https://creativecommons.org/publicdomain/zero/1.0/">Creative Commons Zero license</a>.</p>
 
<p>Our <a href="/code-of-conduct" title="North Bay Python Code of Conduct">Code of Conduct</a> was forked from the <a href="https://github.com/python/pycon-code-of-conduct" title="PyCon United States Code of Conduct">PyCon US Code of Conduct</a>, including the staff and attendee guides, under a <a href="http://creativecommons.org/licenses/by/3.0/" title="Creative Commons Attribution 3.0 Unported License">Creative Commons Attribution 3.0 Unported</a> license, itself originally forked from the example policy from the <a href="http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy" title="Geek Feminism Wiki Conference Anti-harassment Policy">Geek Feminism wiki</a>, created by the <a href="https://adainitiative.org/" title="Ada Initiative">Ada Initiative</a> and other volunteers, which is under a <a href="https://creativecommons.org/publicdomain/zero/1.0/" title="Creative Commons Zero License">Creative Commons Zero</a> license.</p>
 

	
 
<h2>Fiscal Sponsor</h2>
 

	
 
<p>Our fiscal sponsor is <a href="https://sfconservancy.org">Software Freedom Conservancy</a>, a 501(c)(3) charity dedicated to the promotion and development of free and open source software. Conservancy allows us to work without managing our own corporate structure and administrative services. Our relationship with Conservancy goes beyond logistics, though, as we are also philosophically aligned as we work to advance software freedom and expand the Python developer community.</p>
 
<p>Our fiscal sponsor is <a href="https://sfconservancy.org" title="Software Freedom Conservancy">Software Freedom Conservancy</a>, a 501(c)(3) charity dedicated to the promotion and development of free and open source software. Conservancy allows us to work without managing our own corporate structure and administrative services. Our relationship with Conservancy goes beyond logistics, though, as we are also philosophically aligned as we work to advance software freedom and expand the Python developer community.</p>
 

	
 
<h2>Photography</h2>
 

	
 
<!-- TODO -->
 
<p>describe/credit photos used on the home page and other pages, perhaps list event photographer information ...maybe Next Day Video?</p>
 

	
 
<h2>Python</h2>
 

	
 
<p>"Python" and the Python logos are trademarks or registered trademarks of the <a href="https://python.org">Python Software Foundation</a>, used by North Bay Python with permission from the Foundation.</p>
 
<p>"Python" and the Python logos are trademarks or registered trademarks of the <a href="https://python.org" title="Python Software Foundation">Python Software Foundation</a>, used by North Bay Python with permission from the Foundation.</p>
 

	
 
<h2>Terms and Conditions</h2>
 

	
 
<p>Our <a href="/terms-and-conditions">Terms and Conditions</a> were forked from the <a href="https://github.com/linuxaustralia/constitution_and_policies/blob/master/terms_and_conditions.md">Linux Australia Event Terms and Conditions</a> under the <a href="https://github.com/linuxaustralia/constitution_and_policies/blob/master/LICENCE.md">GNU General Public License v3.0</a>. Our Photography and Audio Video Recording policy is adapted from the <a href="https://evergreen-ils.org/conference/photography-policy/">Evergreen policy</a>, itself adapted from the <a href="https://adacamp.org/adacamp-toolkit/policies/#photo">AdaCamp policy</a> under a <a href="http://creativecommons.org/licenses/by-sa/4.0/">Creative Commons Attribution Share Alike 4.0 International</a> license.</p>
 
<p>Our <a href="/terms-and-conditions" title="North Bay Python Terms and Conditions">Terms and Conditions</a> were forked from the <a href="https://github.com/linuxaustralia/constitution_and_policies/blob/master/terms_and_conditions.md" title="Linux Australia Terms and Conditions">Linux Australia Event Terms and Conditions</a> under the <a href="https://github.com/linuxaustralia/constitution_and_policies/blob/master/LICENCE.md" title="GNU General Public License 3.0">GNU General Public License 3.0</a>. Our Photography and Audio Video Recording policy is adapted from the <a href="https://evergreen-ils.org/conference/photography-policy/" title="Evergreen Event Photography Policy">Evergreen policy</a>, itself adapted from the <a href="https://adacamp.org/adacamp-toolkit/policies/#photo" title="AdaCamp Event Photography Policy">AdaCamp policy</a> under a <a href="http://creativecommons.org/licenses/by-sa/4.0/" title="Creative Commons Attribution Share Alike 4.0 International License">Creative Commons Attribution Share Alike 4.0 International</a> license.</p>
 

	
 
<h2>Web Application</h2>
 

	
 
<p>Our website is powered by a heap of free and open source software, most notably:</p>
 

	
 
<ul>
 
  <li><a href="https://www.djangoproject.com/">Django</a> is the web framework that underpins everything else.</li>
 
  <li><a href="https://github.com/chrisjrn/symposion/">Symposion</a> is used for the call for proposals and session scheduling.</li>
 
  <li><a href="http://github.com/chrisjrn/registrasion/">Registrasion</a> is used for ticket sales.</li>
 
  <li><a href="https://www.djangoproject.com/" title="Django Web Framework">Django</a> is the web framework that underpins everything else.</li>
 
  <li><a href="https://github.com/chrisjrn/symposion/" title="Symposion">Symposion</a> is used for the call for proposals and session scheduling.</li>
 
  <li><a href="http://github.com/chrisjrn/registrasion/" title="Registrasion">Registrasion</a> is used for ticket sales.</li>
 
  <li><a href="https://inkscape.org/" title="Inkscape">Inkscape</a> is used to create most of our graphics.</li>
 
</ul>
 

	
 
{% endblock %}
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/about/team.html
Show inline comments
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}About the Team{% endblock %}
 

	
 
{% block heading %}About the Team{% endblock %}
 

	
 
{% block body_class %}about{% endblock %}
 

	
 
{% block lede %}
 

	
 
Our five-person team has years of experience building communities, running events, and, of course, programming. We're also all-in on cultivating a more inclusive culture.
 

	
 
{% endblock %}
 

	
 
{% block content %}
 

	
 
<h2>Meet the Team</h2>
 

	
 
<p>Need to contact someone in a hurry? You can reach us all at <a href="mailto:spam@northbaypython.org">spam@northbaypython.org</a>. Read on to learn about the organizing team.</p>
 
<p>Need to contact someone in a hurry? You can reach us all at <a href="mailto:spam@northbaypython.org" title="spam@northbaypython.org">spam@northbaypython.org</a>. Read on to learn about the organizing team.</p>
 

	
 
<h4>Christopher Neugebauer, Conference Chair</h4>
 

	
 
<p><a href="https://twitter.com/chrisjrn">Christopher</a> is a Python developer who lives in glorious Petaluma, California, though he's originally from the the city of Hobart in Tasmania, Australia. A serial conference organizer, he has been a core organiser of PyCon Australia for a number of years, was director of linux.conf.au 2017, and a good number of his open source contributions help power the website this conference runs on. He was made a fellow of the Python Software Foundation in 2013 in recognition for his contributions to building the Australian Python community.</p>
 
<p><a href="https://twitter.com/chrisjrn" title="Christopher Neugebauer on Twitter">Christopher</a> is a Python developer who lives in glorious Petaluma, California, though he's originally from the the city of Hobart in Tasmania, Australia. A serial conference organizer, he has been a core organiser of PyCon Australia for a number of years, was director of linux.conf.au 2017, and a good number of his open source contributions help power the website this conference runs on. He was made a fellow of the Python Software Foundation in 2013 in recognition for his contributions to building the Australian Python community.</p>
 

	
 
<h4>Sam Kitajima-Kimbrel, Program Chair</h4>
 

	
 
<p><a href="https://twitter.com/skimbrel">Sam</a> is a Python developer and distributed-systems “enthusiast” hailing from Seattle by birth, New York by nurture, and the Bay Area by choice. About five years ago he attended PyCon US for the first time and hasnt been able to break the habit since; after making the jump from audience to stage in 2014 and speaking regularly at PyCons and other events around the world, he was thrilled to sign on with the North Bay Python team when invited by Chris and Josh. Sam currently works at Nuna building healthcare data infrastructure for the U.S. Medicaid and Medicare programs and resides in Oakland with his husband Kameron.</p>
 
<p><a href="https://twitter.com/skimbrel" title="Sam Kitajima-Kimbrel on Twitter">Sam</a> is a Python developer and distributed-systems “enthusiast” hailing from Seattle by birth, New York by nurture, and the Bay Area by choice. About five years ago he attended PyCon US for the first time and hasn't been able to break the habit since; after making the jump from audience to stage in 2014 and speaking regularly at PyCons and other events around the world, he was thrilled to sign on with the North Bay Python team when invited by Chris and Josh. Sam currently works at Nuna building healthcare data infrastructure for the U.S. Medicaid and Medicare programs and resides in Oakland with his husband Kameron.</p>
 

	
 
<h4>Andrew Godwin</h4>
 

	
 
<p><a href="https://twitter.com/andrewgodwin">Andrew</a> is a Django and Python developer who originally hails from London but moved to the Bay Area four years ago. Hes been writing open source software for over a decade as well as working in various different parts of the technology industry, and currently works at Eventbrite. He regularly speaks at Python (and other) events around the world, and has a keen interest in building communities and inclusivity.</p>
 
<p><a href="https://twitter.com/andrewgodwin" title="Andrew Godwin on Twitter">Andrew</a> is a Django and Python developer who originally hails from London but moved to the Bay Area four years ago. He's been writing open source software for over a decade as well as working in various different parts of the technology industry, and currently works at Eventbrite. He regularly speaks at Python (and other) events around the world, and has a keen interest in building communities and inclusivity.</p>
 

	
 
<h4>Sarah Kuchinsky</h4>
 

	
 
<p>Bio and a pic</p>
 

	
 
<h4>Josh Simmons</h4>
 

	
 
<p><a href="https://twitter.com/joshsimmons">Josh</a> is a community organizer and web developer who was born and raised in the North Bay. He spent 4.5 years building Web &amp; Interactive Media Professionals (WIMP), a local community with over 600 members, before moving on to do community management for OReilly Media. These days Josh works on the Google Open Source outreach team and serves as a board member and volunteer CFO for Open Source Initiative.</p>
 
<p><a href="https://twitter.com/joshsimmons" title="Josh Simmons on Twitter">Josh</a> is a community organizer and web developer who was born and raised in the North Bay. He spent 4.5 years building Web &amp; Interactive Media Professionals (WIMP), a local community with over 600 members, before moving on to do community management for O'Reilly Media. These days Josh works on the Google Open Source outreach team and serves as a board member and volunteer CFO for Open Source Initiative.</p>
 

	
 
<h2>Software Freedom Conservancy</h2>
 

	
 
<p><a href="https://twitter.com/conservancy">Conservancy</a> is a public charity dedicated to the promotion and development of free and open source software, and is the fiscal sponsor of North Bay Python. Without Conservancy and the people behind it -- namely <a href="https://twitter.com/o0karen0o">Karen Sandler</a>, <a href="https://twitter.com/bkuhn_ebb_org">Bradley Kuhn</a>, <a href="https://twitter.com/keynote2k">Tony Sebro</a>, and <a href="https://twitter.com/Brett20XX">Brett Smith</a> -- none of this would be possible!</p>
 
<p><a href="https://twitter.com/conservancy" title="Software Freedom Conservancy on Twitter">Conservancy</a> is a public charity dedicated to the promotion and development of free and open source software, and is the fiscal sponsor of North Bay Python. Without Conservancy and the people behind it&mdash;namely <a href="https://twitter.com/o0karen0o" title="Karen Sandler on Twitter">Karen Sandler</a>, <a href="https://twitter.com/bkuhn_ebb_org" title="Bradley Kuhn on Twitter">Bradley Kuhn</a>, <a href="https://twitter.com/keynote2k" title="Tony Sebro on Twitter">Tony Sebro</a>, and <a href="https://twitter.com/Brett20XX" title="Brett Smith on Twitter">Brett Smith</a>&mdash;none of this would be possible!</p>
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/code_of_conduct/code_of_conduct.md
Show inline comments
 
North Bay Python is a community conference intended for networking and collaboration in the developer community.
 

	
 
We value the participation of each member of the Python community and want all attendees to have an enjoyable and fulfilling experience. Accordingly, all attendees are expected to show respect and courtesy to other attendees throughout the conference and at all conference events, whether officially sponsored by North Bay Python or not.
 

	
 
To make clear what is expected, all delegates/attendees, speakers, exhibitors, organizers and volunteers at any North Bay Python event are required to conform to the following Code of Conduct. Organizers will enforce this code throughout the event.
 

	
 
The Short Version
 
-----------------
 

	
 
North Bay Python is dedicated to providing a harassment-free conference experience for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion. We do not tolerate harassment of conference participants in any form.
 

	
 
All communication should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery is not appropriate for any conference venue, including talks.
 

	
 
Be kind to others. Do not insult or put down other attendees. Behave professionally. Remember that harassment and sexist, racist, or exclusionary jokes are not appropriate for North Bay Python.
 

	
 
Attendees violating these rules may be asked to leave the conference without a refund at the sole discretion of the conference organizers.
 

	
 
Thank you for helping make this a welcoming, friendly event for all.
 

	
 
The Longer Version
 
------------------
 

	
 
Harassment includes offensive verbal comments related to gender, sexual orientation, disability, physical appearance, body size, race, religion, sexual images in public spaces, deliberate intimidation, stalking, following, harassing photography or recording, sustained disruption of talks or other events, inappropriate physical contact, and unwelcome sexual attention.
 

	
 
Participants asked to stop any harassing behavior are expected to comply immediately.
 

	
 
Exhibitors in the expo hall, sponsor or vendor booths, or similar activities are also subject to the anti-harassment policy. In particular, exhibitors should not use sexualized images, activities, or other material. Booth staff (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
 

	
 
Be careful in the words that you choose. Remember that sexist, racist, and other exclusionary jokes can be offensive to those around you. Excessive swearing and offensive jokes are not appropriate for PyCon.
 

	
 
If a participant engages in behavior that violates this code of conduct, the conference organizers may take any action they deem appropriate, including warning the offender or expulsion from the conference with no refund.
 

	
 
Contact Information
 
-------------------
 

	
 
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff. Conference staff will be wearing t-shirts and/or badges that clearly identify them as staff. You may also contact venue staff and ask to be put in touch with the conference chair &mdash; Christopher Neugebauer.
 
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of conference staff. Conference staff will be wearing t-shirts and/or badges that clearly identify them as staff. You may also contact venue staff and ask to be put in touch with the conference chair&mdash;Christopher Neugebauer.
 

	
 
<!-- TODO add phone number -->
 
If the matter is especially urgent, please call our Code of Conduct and safety incident hotline at XXX-YYY-ZZZZ. This number will automatically route to a member of the conference staff who can render assistance.
 

	
 
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. We value your attendance.
 

	
 
Procedure for Handling Harassment
 
------------------------------------------
 
- [Attendee procedure for incident handling](/code-of-conduct/harassment-incidents)
 
- [Staff procedure for incident handling](/code-of-conduct/harassment-staff-procedures)
 
- [Attendee procedure for incident handling](/code-of-conduct/harassment-incidents "North Bay Python attendee procedure for incident handling")
 
- [Staff procedure for incident handling](/code-of-conduct/harassment-staff-procedures "North Bay Python staff procedure for incident handling")
 

	
 
License
 
-------
 

	
 
This Code of Conduct was forked from the [PyCon US Code of Conduct](https://github.com/python/pycon-code-of-conduct) under a <a href="http://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution 3.0 Unported License</a>, itself originally forked from the example policy from the [Geek Feminism wiki, created by the Ada Initiative and other volunteers.](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy) which is under a Creative Commons Zero license.
...
 
\ No newline at end of file
 
This Code of Conduct was forked from the [PyCon US Code of Conduct](https://github.com/python/pycon-code-of-conduct "PyCon United States Code of Conduct") under a [Creative Commons Attribution 3.0 Unported](http://creativecommons.org/licenses/by/3.0/ "Creative Commons Attribution 3.0 Unported License") license, itself originally forked from the example policy in [Geek Feminism wiki](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy "Geek Feminism Wiki Example Anti-harassment Policy"), created by the Ada Initiative and other volunteers. which is under a [Creative Commons Zero](https://creativecommons.org/publicdomain/zero/1.0/ "Creative Commons Zero License") license.
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/code_of_conduct/harassment_procedure_attendee.md
Show inline comments
 
*This procedure has been adopted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports).*
 
*This procedure has been adopted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports "Ada Initive Anti-harassment Guide on Responding to Reports")".*
 

	
 
1\. Keep in mind that all conference staff will be wearing a conference t-shirt/button with the word STAFF on it (or otherwise clearly marked as staff). The staff will also be prepared to handle the incident. All of our staff are informed of the [code of conduct policy](/code-of-conduct) and guide for handling harassment at the conference. *There will be a mandatory staff meeting onsite at the conference when this will be reiterated.*
 
1\. Keep in mind that all conference staff will be wearing a conference t-shirt/button with the word "STAFF" on it (or otherwise clearly marked as staff). The staff will also be prepared to handle the incident. All of our staff are informed of the [code of conduct policy](/code-of-conduct "North Bay Python Code of Conduct") and guide for handling harassment at the conference. *There will be a mandatory staff meeting onsite at the conference when this will be reiterated.*
 

	
 
2\. Report the harassment incident (preferably in writing) to a conference staff member. All reports are confidential. Please do not disclose public information about the incident until the staff have had sufficient time in which to address the situation. This is as much for your safety and protection as it is the other attendees.
 

	
 
When reporting the event to staff, try to gather as much information as available but do not interview people about the incident. Staff will assist you in writing the report/collecting information.
 

	
 
The important information consists of:
 

	
 
- Identifying information (name/badge number) of the participant doing the harassing
 
- The behavior that was in violation
 
- The approximate time of the behavior (if different than the time the report was made)
 
- The circumstances surrounding the incident
 
- Other people involved in the incident
 

	
 
The staff is well informed on how to deal with the incident and how to further proceed with the situation.
 

	
 
3\. If everyone is presently physically safe, involve law enforcement or security only at a victim's request. If you do feel your safety in jeopardy please do not hesitate to contact local law enforcement by dialing 911. If you do not have a cell phone, you can use any hotel phone or simply ask a staff member.
 

	
 
**Note**: Incidents that violate the Code of Conduct are extremely damaging to the community, and they will not be tolerated. The silver lining is that, in many cases, these incidents present a chance for the offenders, and the community at large, to grow, learn, and become better. North Bay Python staff requests that they be your first resource when reporting a North Bay Python-related incident, so that they may enforce the Code of Conduct and take quick action toward a resolution.
 

	
 
A listing of [North Bay Python staff is located here](/about/team), including contact phone numbers. If at all possible, all reports should be made directly to Bleep and Bloop.
...
 
\ No newline at end of file
 
A listing of [North Bay Python staff is located here](/about/team "About the North Bay Python team"), including contact phone numbers. If at all possible, all reports should be made directly to Bleep and Bloop.
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/code_of_conduct/harassment_procedure_staff.md
Show inline comments
 
*This procedure has been adopted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports).*
 
*This procedure has been adopted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports "Ada Initive Anti-harassment Guide on Responding to Reports")".*
 

	
 
Be sure to have a good understanding of our Code of Conduct policy, which can be found here: [https://northbaypython.org/code-of-conduct](/code-of-conduct)
 
Be sure to have a good understanding of our Code of Conduct policy, which can be found here: [https://northbaypython.org/code-of-conduct](/code-of-conduct "North Bay Python Code of Conduct")
 

	
 
Also have a good understanding of what is expected from an attendee that wants to report a harassment incident. These guidelines can be found here: [https://northbaypython.org/code-of-conduct/harassment-incidents](/code-of-conduct/harassment-incidents)
 
Also have a good understanding of what is expected from an attendee that wants to report a harassment incident. These guidelines can be found here: [https://northbaypython.org/code-of-conduct/harassment-incidents](/code-of-conduct/harassment-incidents "North Bay Python attendee procedure for incident handling")
 

	
 
Try to get as much of the incident in written form by the reporter. If you cannot, transcribe it yourself as it was told to you. The important information to gather include the following:
 

	
 
 - Identifying information (name/badge number) of the participant doing the harassing
 
 - The behavior that was in violation
 
 - The approximate time of the behavior (if different than the time the report was made)
 
 - The circumstances surrounding the incident
 
 - Other people involved in the incident
 

	
 
Prepare an initial response to the incident. This initial response is very important and will set the tone for North Bay Python. Depending on the severity/details of the incident, please follow these guidelines:
 

	
 
 - If there is any general threat to attendees or the safety of anyone including conference staff is in doubt, summon security or police
 
 - Offer the victim a private place to sit
 
 - Ask "is there a friend or trusted person who you would like to be with you?" (if so, arrange for someone to fetch this person)
 
 - Ask them "how can I help?"
 
 - Provide them with your list of emergency contacts if they need help later
 
 - If everyone is presently physically safe, involve law enforcement or security only at a victim's request
 

	
 
There are also some guidelines as to what not to do as an initial response:
 

	
 
 - Do not overtly invite them to withdraw the complaint or mention that withdrawal is OK. This suggests that you want them to do so, and is therefore coercive. "If you're OK with it [pursuing the complaint]" suggests that you are by default pursuing it and is not coercive.
 
 - Do not ask for their advice on how to deal with the complaint. This is a staff responsibility.
 
 - Do not offer them input into penalties. This is the staff's responsibility.
 

	
 
Once something is reported to a staff member, immediately meet with the conference chair and/or event coordinator. The main objectives of this meeting is to find out the following:
 

	
 
 - What happened?
 
 - Are we doing anything about it?
 
 - Who is doing those things?
 
 - When are they doing them?
 

	
 
After the staff meeting and discussion, have a staff member (preferably the conference chair or event coordinator if available) communicate with the alleged harasser. Make sure to inform them of what has been reported about them.
 

	
 
Allow the alleged harasser to give their side of the story to the staff. After this point, if the report stands, let the alleged harasser know what actions will be taken against them.
 

	
 
Some things for the staff to consider when dealing with Code of Conduct offenders:
 

	
 
- Warning the harasser to cease their behavior and that any further reports will result in sanctions
 
- Requiring that the harasser avoid any interaction with, and physical proximity to, their victim for the remainder of the event
 
- Ending a talk that violates the policy early
 
- Not publishing the video or slides of a talk that violated the policy
 
- Not allowing a speaker who violated the policy to give (further) talks at the event now or in the future
 
- Immediately ending any event volunteer responsibilities and privileges the harasser holds
 
- Requiring that the harasser not volunteer for future events your organization runs (either indefinitely or for a certain time period)
 
- Requiring that the harasser refund any travel grants and similar they received (this would need to be a condition of the grant at the time of being awarded)
 
- Requiring that the harasser immediately leave the event and not return
 
- Banning the harasser from future events (either indefinitely or for a certain time period)
 
- Removing a harasser from membership of relevant organizations
 
- Publishing an account of the harassment and calling for the resignation of the harasser from their responsibilities (usually pursued by people without formal authority: may be called for if the harasser is the event leader, or refuses to stand aside from the conflict of interest, or similar, typically event staff have sufficient governing rights over their space that this isn't as useful)
 

	
 
Give accused attendees a place to appeal to if there is one, but in the meantime the report stands. Keep in mind that it is not a good idea to encourage an apology from the harasser.
 

	
 
It is very important how we deal with the incident publicly. Our policy is to make sure that everyone aware of the initial incident is also made aware that it is not according to policy and that official action has been taken - while still respecting the privacy of individual attendees.  When speaking to individuals (those who are aware of the incident, but were not involved with the incident) about the incident it is a good idea to keep the details out.
 

	
 
Depending on the incident, the conference chair, or designate, may decide to make one or more public announcements. If necessary, this will be done with a short announcement either during the plenary and/or through other channels. No one other than the conference chair or someone delegated authority from the conference chair should make any announcements. No personal information about either party will be disclosed as part of this process.
 

	
 
If some attendees were angered by the incident, it is best to apologize to them that the incident occurred to begin with.  If there are residual hard feelings, suggest to them to write an email to the conference chair or to the event coordinator. It will be dealt with accordingly.
 

	
 
A listing of [North Bay Python staff is located here](/about/team), including contact phone numbers. If at all possible, all reports should be made directly to Bleep and Bloop.
...
 
\ No newline at end of file
 
A listing of [North Bay Python staff is located here](/about/team "About the North Bay Python team"), including contact phone numbers. If at all possible, all reports should be made directly to Bleep and Bloop.
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/news.html
Show inline comments
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}News{% endblock %}
 

	
 
{% block heading %}News{% endblock %}
 

	
 
{% block body_class %}news{% endblock %}
 

	
 
{% block content %}
 

	
 
<h2>Now accepting talk proposals for North Bay Python 2017</h2>
 

	
 
<p><span class="date">Monday, August 21, 2017</span> -- The North Bay Python team is excited to announce that the <a href="/program/call-for-proposals">call for proposals</a> (CFP) is now open! We are seeking speakers of all experience levels to contribute to our inaugural conference. The CFP will close on September 29, 2017.</p>
 
<p><span class="date">Monday, August 21, 2017</span>&mdash;The North Bay Python team is excited to announce that the <a href="/program/call-for-proposals" title="North Bay Python Call for Proposals">call for proposals</a> (CFP) is now open! We are seeking speakers of all experience levels to contribute to our inaugural conference. The CFP will close on September 29, 2017.</p>
 

	
 
<p>North Bay Python is a single-track event featuring two days of presentations by members of the community. The vast majority of the conference program will come from people who propose talks in our CFP process. Whether you use Python professionally, as a hobbyist, or are just excited about Python or programming or open source, we'd love to hear from you.</p>
 

	
 
<p>Our program committee, which is responsible for reviewing proposals, is interested in building a program that reflects the diversity of people who are using Python. Never given a presentation before but excited to share? We're here to help you craft a proposal and can refer you to quality resources for making your first conference talk. Not sure what to talk about, but interested in trying? We've got ideas for presentations we'd love to see and we're happy to share them with you!</p>
 

	
 
<p>In order to ensure a balanced program, we are proactively doing outreach to new and experienced speakers alike. We are also including a blind review phase in our <a href="/program/selection-process">selection process</a> in order to combat bias. Our goal is to have no less than 33% of our speakers be not-men, ideally 50%, and to reflect the racial diversity of United States and Bay Area demographics.</p>
 
<p>In order to ensure a balanced program, we are proactively doing outreach to new and experienced speakers alike. We are also including a blind review phase in our <a href="/program/selection-process" title="North Bay Python proposal selection process">selection process</a> in order to combat bias. Our goal is to have no less than 33% of our speakers be not-men, ideally 50%, and to reflect the racial diversity of United States and Bay Area demographics.</p>
 

	
 
<p>Feel free to reach out with any questions, comments, or ideas you have. You can find us on <a href="https://twitter.com/northbaypython">Twitter</a>, <a href="https://facebook.com/northbaypython">Facebook</a>, and <a href="http://webchat.freenode.net/?channels=%23nbpy">IRC</a>, or you can <a href="mailto:program@northbaypython.org">email us</a>. And, please, get started today! The <a href="/program/call-for-proposals">call for proposals</a> closes on September 29, 2017.</p>
 
<p>Feel free to reach out with any questions, comments, or ideas you have. You can find us on <a href="https://twitter.com/northbaypython" title="North Bay Python on Twitter">Twitter</a>, <a href="https://facebook.com/northbaypython" title="North Bay Python on Facebook">Facebook</a>, and <a href="http://webchat.freenode.net/?channels=%23nbpy" title="IRC Web Client for #nbpy Channel on Freenode">IRC</a>, or you can <a href="mailto:program@northbaypython.org" title="program@northbaypython.org">email us</a>. Please, get started today! The <a href="/program/call-for-proposals" title="North Bay Python Call for Proposals">call for proposals</a> closes on September 29, 2017.</p>
 

	
 
<h2>North Bay Python joins Software Freedom Conservancy</h2>
 

	
 
<p><span class="date">Bloop, August Bleep, 2017</span> -- We are proud to announce that North Bay Python is now a member project of <a href="https://sfconservancy.org">Software Freedom Conservancy</a>, a 501(c)(3) charity dedicated to ethical technology and the development and promotion free and open source software. Conservancy will act as our fiscal sponsor, allowing our team to operate without managing our own corporate structure and administrative services.</p>
 
<p><span class="date">Bloop, August Bleep, 2017</span>&mdash;We are proud to announce that North Bay Python is now a member project of <a href="https://sfconservancy.org" title="Software Freedom Conservancy">Software Freedom Conservancy</a>, a 501(c)(3) charity dedicated to ethical technology and the development and promotion free and open source software. Conservancy will act as our fiscal sponsor, allowing our team to operate without managing our own corporate structure and administrative services.</p>
 

	
 
<p>Conservancy is home to many popular <a href="https://sfconservancy.org/projects/current/">free and open source software projects</a>, like <a href="http://www.seleniumhq.org/">Selenium</a>, <a href="https://www.phpmyadmin.net/">phpMyAdmin</a>, <a href="https://twistedmatrix.com/trac/">Twisted</a>, and <a href="https://www.gnome.org/outreachy/">Outreachy</a>, some of which run their own events. North Bay Python has the distinct honor of being the first member project that is exclusively focused on organizing community events.</p>
 
<p>Conservancy is home to many popular <a href="https://sfconservancy.org/projects/current/" title="Current Member Projects of the Software Freedom Conservancy">free and open source software projects</a>, like <a href="http://www.seleniumhq.org/" title="Selenium">Selenium</a>, <a href="https://www.phpmyadmin.net/" title="phpMyAdmin">phpMyAdmin</a>, <a href="https://twistedmatrix.com/trac/" title="Twisted">Twisted</a>, and <a href="https://www.gnome.org/outreachy/" title="Outreachy">Outreachy</a>, some of which run their own events. North Bay Python has the distinct honor of being the first member project that is exclusively focused on organizing community events.</p>
 

	
 
<p>We couldn't be more excited. We're celebrating by donating five free tickets to Outreachy interns and will be promoting member projects relevant to the Python community at the conference. Interested Outreachy interns should <a href="mailto:outreach@northbaypython.org">contact us</a>. We'll also have discounted tickets available for active financial supporters of Software Freedom Conservancy.</p>
 
<p>We couldn't be more excited. We're celebrating by donating five free tickets to Outreachy interns and will be promoting member projects relevant to the Python community at the conference. Interested Outreachy interns should <a href="mailto:outreach@northbaypython.org" title="outreach@northbaypython.org">contact us</a>. We'll also have discounted tickets available for active financial supporters of Software Freedom Conservancy.</p>
 

	
 
<p>We look forward to working with Conservancy to advance software freedom and expand the community of Python developers. If this is the first time you've heard of Conservancy, we encourage you to check out <a href="https://sfconservancy.org">their website</a> and give them your support.</p>
 
<p>We look forward to working with Conservancy to advance software freedom and expand the community of Python developers. If this is the first time you've heard of Conservancy, we encourage you to check out <a href="https://sfconservancy.org" title="Software Freedom Conservancy">their website</a> and give them your support.</p>
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/program/call_for_proposals.md
Show inline comments
 
### The North Bay Python 2017 CFP is open!
 

	
 
If you've never presented at a conference before and think you might like to try it, we want to hear from you! The program committee is *very* much interested in encouraging and supporting new speakers, and we will be able to provide detailed feedback and work with you to develop your proposal and talk content so you can give the best talk possible.
 

	
 
In the interest of transparency, we have documented our [Selection Process](/program/selection-process). Portions of this page were drawn from ideas seen on [DjangoCon EU](https://djangocon.eu), [SeaGL](https://seagl.org), [Fog City Ruby](http://www.fogcityruby.com/speak/), and others. Thanks to all for their inspiration and permission to borrow!
 
In the interest of transparency, we have documented our [selection process](/program/selection-process "North Bay Python proposal selection process"). Portions of this page were drawn from ideas seen on [DjangoCon EU](https://djangocon.eu "DjangoCon Europe"), [SeaGL](https://seagl.org "Seattle GNU Linux"), [Fog City Ruby](http://www.fogcityruby.com/speak/ "Fog City Ruby"), and others. Thanks to all for their inspiration and permission to borrow!
 

	
 
## Dates
 

	
 
+ **August 21, 2017**: CFP opens
 
+ **September 29, 2017**: CFP closes
 
+ **Week of October 9**: Acceptance notifications sent
 
+ **Week of October 16**: Speaker confirmations due; program finalized and announced
 
+ **December 2–3, 2017**: Conference happens!
 

	
 
## Speakers
 

	
 
North Bay Python is dedicated to featuring a diverse and inclusive speaker lineup.
 

	
 
**All speakers will be expected to have read and adhere to the conference [Code of Conduct](/code-of-conduct). In particular for speakers: slide contents and spoken material should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery is not appropriate, and neither are language or imagery that denigrate or demean people based on race, gender, religion, sexual orientation, physical appearance, disability, or body size.**
 
**All speakers will be expected to have read and adhere to the conference [Code of Conduct](/code-of-conduct "North Bay Python Code of Conduct"). In particular for speakers: slide contents and spoken material should be appropriate for a professional audience including people of many different backgrounds. Sexual language and imagery is not appropriate, and neither are language or imagery that denigrate or demean people based on race, gender, religion, sexual orientation, physical appearance, disability, or body size.**
 

	
 
We will make every effort to provide accommodations for speakers and attendees of all abilities all we ask is that you let us know so we can prepare accordingly.
 
We will make every effort to provide accommodations for speakers and attendees of all abilities&mdash;all we ask is that you let us know so we can prepare accordingly.
 

	
 
North Bay Python is a conference in support of the local programmer community outside of the core San Francisco Bay Area tech scene. We aim to feature a mix of local and non-local speakers to offer a program with broad appeal. **All speakers will receive complimentary registration to the conference, and requests for further financial compensation to assist with travel will be considered on a case-by-case basis independent of the proposal's merits.**
 

	
 
## Talk formats
 

	
 
**Most of the talk slots will be short** approximately 25 to 30 minutes, including Q&A. If your ideas would benefit from a longer slot, please explain in your submission how you would use the additional time.
 
**Most of the talk slots will be short**&mdash;approximately 25 to 30 minutes, including Q&A. If your ideas would benefit from a longer slot, please explain in your submission how you would use the additional time.
 

	
 
## Topics
 

	
 
**We are a single track conference. This means that your talk needs to hold the attention of beginners to experienced developers alike.**
 

	
 
This doesnt mean that every talk needs to be a beginners talk: if youre talking about advanced concepts, people who are new to Python – or new to your library – should come away excited about the possibilities, and know how to learn the concepts that they need to get there.
 
This doesn't mean that every talk needs to be a beginner's talk: if you're talking about advanced concepts, people who are new to Python – or new to your library – should come away excited about the possibilities, and know how to learn the concepts that they need to get there.
 

	
 
This is a list of topics we think might go well in the North Bay Python program, but it is by no means exhaustive. If you have a talk idea on a subject not listed here and you think it fits well with our community and mission, we would love to hear about it!
 

	
 
+ The Python community
 
+ Python fundamentals
 
+ Useful libraries and tools
 
+ Testing in Python
 
+ Deploying, operating, or scaling Python
 
+ Organization and communication skills for software development
 
+ What Python can learn from other communities
 
+ Unexpected places Python gets used (Embedded systems! Health science!)
 
+ ... and anything else we might not have thought of!
 

	
 
## Resources
 

	
 
The [Public Speaking](https://github.com/vmbrasseur/Public_Speaking) repository has collected many useful resources to help you polish your proposals and talks.
 
This [public speaking](https://github.com/vmbrasseur/Public_Speaking "Public Speaking Resource Repository by VM Brasseur") repository, maintained by [VM Brasseur](https://twitter.com/vmbrasseur "VM Brasseur on Twitter"), has many useful resources to help you polish your proposals and talks.
 

	
 
### Office Hours and Mentorship
 

	
 
The Program Committee will be holding regularly-scheduled office hours during the CFP period to help you organize proposals.
 
The program committee will be holding regularly-scheduled office hours during the CFP period to help you organize proposals.
 

	
 
We're happy to help with any of the following:
 

	
 
+ Exploring and brainstorming your interests to help you identify hidden things that would make great talks
 
+ Connecting you with experienced speakers to help build your proposal and talk
 
+ Reviewing your outline, slide deck, or presenter notes
 
+ Connecting you with rehearsal audiences or even just watching you present over a video conference as practice
 
+ Anything else that'd help you be at ease and excited about bringing your ideas to our audience!
 

	
 
<!-- TODO schedule and contact info go here -->
 

	
 
## Submitting
 

	
 
To help us evaluate proposals and build our program, we would like as much detail as you can provide on your talk. At a minimum this should include: **a brief abstract (~500 characters) suitable for inclusion in a schedule page; a detailed prose summary (intended as the content for a talk detail page on the program site); and at least a rough outline of the structure including estimated timings for each section of your talk.**
 

	
 
If you've given your talk before, links to video or slides would be excellent, or if you've blogged about this topic links to your blog posts would be of use as well.
 

	
 
Your speaker profile includes a space for you to describe your prior experience giving talks this is your chance to talk yourself up and explain why you're the best person in the world to bring us your amazing ideas, so take advantage of it!
 
Your speaker profile includes a space for you to describe your prior experience giving talks&mdash;this is your chance to talk yourself up and explain why you're the best person in the world to bring us your amazing ideas, so take advantage of it!
 

	
 
Please click the invitingly large button below to submit a proposal.
 

	
 
<!-- TODO invitingly large button plz -->
 

	
 
## Feedback and mentorship
 

	
 
**First time speakers are welcomed and encouraged; if you've never done this before but have an idea please contact the program committee to be connected with a mentor and receive guidance structuring your proposal and talk. Above all we want you to be successful and have a good time telling other attendees about your amazing ideas!**
 

	
 
If you have an idea (or don't!) and want to speak, here's a very rough process of what you should do next:
 

	
 
+ Brainstorm or [mind map](https://en.wikipedia.org/wiki/Mind_map) to expand upon your ideas or knowledge in search of a general topic
 
+ Brainstorm or [mind map](https://en.wikipedia.org/wiki/Mind_map "Wikipedia Entry on Mind Mapping") to expand upon your ideas or knowledge in search of a general topic
 
+ Write a paragraph or two, or some bullet points, to outline the core concepts you want to communicate and what people might learn from your talk
 
+ Get someone you trust to read your notes and tell you what they think they'd learn
 
+ Attend our office hours to get help building up your submission
 
+ Practice!
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/program/selection_process.md
Show inline comments
 
## Phase one: ranking of anonymized proposal contents
 

	
 
During this phase, the program committee will score each proposal solely on the merits of its contents, without any identifying information or other knowledge about the speaker(s) proposing the talk.
 

	
 

	
 
## Phase two: identify-aware ranking and curation
 

	
 
The program committee will use the scored proposals in conjunction with speaker profiles to rank and organize a program meeting our goals for diversity of speakers and topics.
 

	
 
## North Bay Python's diversity goals
 

	
 
+ At least one-third (33%) of speakers should be not-men, and ideally at least half (50%).
 
+ As North Bay Python aims to serve the "tech-adjacent" and client services industries, at least one-fifth (20%) of speakers should be from professional backgrounds that are not the Silicon Valley or San Francisco startup/software industry.
 
+ Racial demographics of the speaker lineup should ideally reflect US and Bay Area demographics within some margin of error.
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/terms_and_conditions.md
Show inline comments
...
 
@@ -10,97 +10,97 @@ Security and Credit Cards
 

	
 
All transactions are performed through a payment gateway facility and use SSL encryption. The facility accepts MasterCard, Visa, and may accept other cards as well. All transactions are performed by the event organizers on behalf of Software Freedom Conservancy.
 

	
 
Cancellation Policy
 
-------------------
 

	
 
**Cancellations made prior to November 2, 2017**: Incur a cancellation fee of $25 or 15% of the ticket cost, whichever is greater, which will be deducted from any registration fee paid. The balance will be refunded.
 

	
 
**Cancellations made after November 2, 2017**: No refund.
 

	
 
Substitutions
 
-------------
 

	
 
You may substitute another person, however you must contact us with this person's details. If you wish to substitute after November 2, 2017 please note that we will not be able to provide any personalized items.
 

	
 
Privacy Notice
 
--------------
 

	
 
In the course of registering for the event and related events, personal information will be collected about attendees such as their name, contact details, etc. This information is required to facilitate registration to the event, for catering requirements, and for organizers or their agents to contact particular attendees as and when required in respect of the event. Attendees who do not disclose this personal information will be unable to complete registration at the event and will therefore not be able to attend.
 

	
 
Personal information will only be disclosed to North Bay Python, Software Freedom Conservancy, and to Government agencies where organizers believe disclosure is appropriate for legal compliance and law enforcement; to facilitate court proceedings; to enforce our terms and conditions; or to protect the rights, property, or safety of the event, our attendees, or others. North Bay Python and Software Freedom Conservancy will not sell your personal information to third parties and will not use your personal information to send promotional material from any of our affiliated partners and/or sponsors.
 

	
 
As part of the registration process attendees will be asked if they would like to subscribe to the event mailing lists and/or the event announcement mailing list. Attendees who subscribe to one or more of these lists will be sent emails from the event organizers and other subscribers to the mailing lists. If at any time, attendees wish to unsubscribe from any of these mailing lists, please follow the 'how to unsubscribe' directions on the bottom of any message you receive from these mailing lists.
 

	
 
From time to time event organizers update their information and website practices. Please regularly review this page for the most recent information about the event privacy practices.
 

	
 
All personal information will be kept private and used only for event registration purposes, statistics for future events, and convenience for future event registration.
 

	
 
Network
 
-------
 

	
 
The event may provide attendees with access to a wired and/or wireless network. Access to this network is a privilege and not an entitlement, and must be used appropriately. Inappropriate use includes, but is not limited to: unlawful activities, interfering with the equipment or network access of others and not respecting the reasonable expectations of privacy that attendees have for traffic flowing through the network.
 

	
 
If any attendees use the network inappropriately, then the event organisers will take any enforcement action they consider appropriate. Enforcement action includes but is not limited to:
 

	
 
* suspending access to the network
 
* disconnecting the network permanently
 
* the alleged offender may be asked to immediately leave the venue and/or will be prohibited from continuing to attend the event (without reimbursement)
 
* the incident may be reported to the police
 
* any other measure the event organizers see fit
 

	
 
Be aware that for security and operational reasons the event organizers may both monitor and log network traffic.
 

	
 
Discrimination and Anti-Social Behaviour
 
----------------------------------------
 

	
 
North Bay Python is proud to support people from all walks of life, especially underrepresented groups like women and people of color, and will not tolerate in any fashion any intimidation, harassment, and/or any abusive, discriminatory or derogatory behaviour by any attendees of the event and/or related events.
 

	
 
Examples of these behaviors and measures the event organizers may take are set out in the [Code of Conduct](/code-of-conduct). By registering for and attending North Bay Python, you agree to this Code of Conduct.
 
Examples of these behaviors and measures the event organizers may take are set out in the [Code of Conduct](/code-of-conduct "North Bay Python Code of Conduct"). By registering for and attending North Bay Python, you agree to this Code of Conduct.
 

	
 
Talk Recordings
 
---------------
 

	
 
Event organizers may provide recordings of talks (audio and/or video) given at the event. This service is provided on a best-effort basis only. Any recordings will be released as and when they are ready, which may be some time after the conclusion of the event, and the recordings may be of varying quality.
 

	
 
Photography and Audio Video Recording
 
-------------------------------------
 

	
 
This applies to all attendees of North Bay Python and related events, including staff who are designated as official photographers and audio and video recorders.
 

	
 
Do not photograph, video or audio record anyone without their express permission.
 

	
 
Attendees will have a way to visibly signal their preference for photography at the conference. You agree to consider and act according to these preferences:
 

	
 
* Opt-in: Photography always okay
 
* Permission required: Ask before photographing
 
* Opt-out: Photographs are never okay, don't ask
 

	
 
There is no prior opt-in for audio or video recordings. You must always ask before recording. 
 

	
 
The event may have one or more staff taking photographs and/or audio or video recordings during the 
 
event. These staff will respect attendees' preferences regarding photography and recordings.
 

	
 
The only exception is for recordings of talks given at the event where attendees who ask questions of the presenter may be included in the talk recording.
 

	
 
If Software Freedom Conservancy or North Bay Python organizers chooses to publish photographs and recordings taken by event staff, we will publish them under a Creative Commons license. Conservancy and North Bay Python further reserve the right to use those photographs and recordings in promotional materials to promote North Bay Python and/or the use of free and open source software.
 

	
 
If there is a violation of this policy, event organizers will request that the photograph be removed from any sites where it was posted and deleted from the devices. In the event that this request is ignored or further violations occur, the participants violating this policy may be sanctioned or expelled from the conference without a refund or banned from future North Bay Python events.
 

	
 
Media
 
-----
 

	
 
There are a limited number of Media Passes available to media personnel. Media Passes are free of charge, and entitle media personnel to attend the event with all the entitlements of a Corporate registration. Please note, due to the limited numbers of Media Passes available, all Media Passes will need to be approved by the event organizers.
 

	
 
Any media attending the event are required to identify themselves as "media" to attendees prior to speaking on the record with any attendees of the event. It is the responsibility of the media to introduce themselves to the persons they wish to interview and to arrange any interviews with those persons. The event organizers will not make introductions or arrange interviews on behalf of media.
 

	
 
Students
 
--------
 

	
 
Students who register for a student ticket (if available) to attend the event may be required to provide event organizers with proof that they are eligible for registration as a student, such as providing a valid student ID card.
 

	
 
Smoke-free
 
----------
 

	
 
All event venues including the social event venues are smoke-free. If attendees wish to smoke during the event and/or related events, they must do so in signed areas. Please consider others and refrain from smoking directly outside the venues' entrances.
 

	
 
Health and Safety
static/js/site.js
Show inline comments
 
/* global window ace */
 

	
 
const loadEditors = () => {
 
    const $editors = $('.modal-body textarea, #id_body, #id_comment, #id_message, #id_text, #id_abstract, #id_additional_notes, #id_content_override, #id_description, #id_biography');
 
    $editors.each((i, el) => {
 
      const editorId = `markdown-editor-${i}`;
 
      const reportDiv = $('<div>').attr('id', editorId);
 
      const setupEditor = (editor, textarea) => {
 
          const session = editor.getSession();
 
          editor.setTheme('ace/theme/tomorrow');
 
          editor.$blockScrolling = Infinity;
 
          editor.setOption('scrollPastEnd', true);
 
          session.setMode('ace/mode/markdown');
 
          session.setValue(textarea.val());
 
          session.setUseWrapMode(true);
 
          session.on('change', () => {
 
              textarea.val(session.getValue());
 
          });
 
          editor.renderer.setShowGutter(false);
 
          session.setTabSize(4);
 
          session.setUseSoftTabs(true);
 
      };
 
      const $formGroup = $(el).closest('.form-group');
 
      const $textarea = $formGroup.find('textarea');
 
      $formGroup.append(reportDiv);
 
      setupEditor(ace.edit(editorId), $textarea);
 
    });
 
};
 

	
 
$(() => {
 
    loadEditors();
 
});
static/scss/custom.scss
Show inline comments
...
 
@@ -20,51 +20,54 @@ p.login-signup {
 

	
 
    > div {
 
        i.fa {
 
            margin-bottom: 0.2em;
 
        }
 
        @include make-sm-column(4);
 
        /*.text-center;
 
        margin: 2em 0;*/
 
    }
 
}
 

	
 
body.reviews.review-list .review-list,
 
body.reviews.voting-status .voting-status,
 
body.reviews.review-results .review-results {
 
    z-index: 2; // Place active items above their siblings for proper border styling
 
    color: $list-group-active-color;
 
    background-color: $list-group-active-bg;
 
    border-color: $list-group-active-border;
 
}
 

	
 
body.reviews.voting-status {
 
    &.positive a.positive,
 
    &.negative a.negative,
 
    &.indifferent a.indifferent,
 
    &.controversial a.controversial,
 
    &.too_few a.too_few {
 
        z-index: 2;
 
        color: #333;
 
        background-color: #e6e6e6;
 
        border-color: #adadad;
 
        outline: 0;
 
        background-image: none;
 
        box-shadow: inset 0 3px 5px rgba(0, 0, 0, 0.125);
 
    }
 
}
 

	
 
#accountLogOutForm {
 
    display: none;
 
}
 

	
 
.sponsor-list h3 {
 
    margin-top: 3em;
 
}
 

	
 
.sponsor-list > div {
 
    margin: 10px 0;
 
}
 

	
 
body.auth .panel-heading .panel-title span.pull-right {
 
    margin: 0 auto;
 
}
 

	
 

	
 

	
static/scss/editor.scss
Show inline comments
 
form {
 
   #id_body,
 
   #id_comment,
 
   #id_message,
 
   #id_text,
 
   #id_abstract,
 
   #id_additional_notes,
 
   #id_content_override,
 
   #id_description,
 
   #id_biography,
 
   .modal-body textarea {
 
       display: none
 
   }
 
   .ace_editor {
 
       min-height: 200px;
 
       width: 100%;
 
       border: 1px dotted #CCC;
 
   }
 
   .ace_content {
 
       padding: 5px;
 
   }
 
   textarea.ace_text-input {
 
       display: block;
 
   }
 
}
0 comments (0 inline, 0 general)