Changeset - 5f01790f40fc
pinaxcon/middleware.py
Show inline comments
...
 
@@ -2,12 +2,35 @@ import re
 
import warnings
 

	
 
from django import http
 
from django.conf import settings
 
from django.utils.deprecation import MiddlewareMixin
 

	
 
class CanonicalHostMiddleware(MiddlewareMixin):
 
    """ Redirects to a canonical host if the current host is not the canonical
 
    host. """
 

	
 
    response_redirect_class = http.HttpResponsePermanentRedirect
 

	
 
    def process_request(self, request):
 

	
 
        canonical_host = getattr(settings, "CANONICAL_HOST", None)
 

	
 
        if not canonical_host:
 
            return
 

	
 
        host = request.get_host()
 

	
 
        if host == canonical_host:
 
            return
 

	
 
        path = request.get_full_path()
 
        redirect_url = ('%s://%s%s' % (request.scheme, canonical_host, path))
 
        return self.response_redirect_class(redirect_url)
 

	
 

	
 
class UnprependWWWMiddleware(MiddlewareMixin):
 
    """ Unprepends www if necessary. """
 

	
 
    response_redirect_class = http.HttpResponsePermanentRedirect
 

	
 
    def process_request(self, request):
pinaxcon/settings.py
Show inline comments
...
 
@@ -20,12 +20,13 @@ UNPREPEND_WWW = bool(os.environ.get("DJANGO_UNPREPEND_WWW", False))
 
# HEROKU: Update database configuration with $DATABASE_URL.
 
import dj_database_url
 
db_from_env = dj_database_url.config()
 
DATABASES['default'].update(db_from_env)
 

	
 
ALLOWED_HOSTS = [".localhost", ".herokuapp.com", ".northbaypython.org"]
 
CANONICAL_HOST = os.environ.get("DJANGO_CANONICAL_HOST", None)
 

	
 
# If DEFAULT_FROM_EMAIL is not set, email will most likely break in prod.
 
from_email = os.environ.get("DJANGO_DEFAULT_FROM_EMAIL", None)
 
if from_email is not None:
 
    DEFAULT_FROM_EMAIL = from_email
 

	
...
 
@@ -142,14 +143,14 @@ MIDDLEWARE_CLASSES = [
 
    "django.contrib.auth.middleware.AuthenticationMiddleware",
 
    "django.contrib.auth.middleware.SessionAuthenticationMiddleware",
 
    "django.contrib.messages.middleware.MessageMiddleware",
 
    "reversion.middleware.RevisionMiddleware",
 
    "django.middleware.clickjacking.XFrameOptionsMiddleware",
 
    "ssl_redirect.middleware.SSLRedirectMiddleware",
 
    "pinaxcon.middleware.CanonicalHostMiddleware",
 
    "pinaxcon.middleware.UnprependWWWMiddleware",
 

	
 
]
 

	
 
ROOT_URLCONF = "pinaxcon.urls"
 

	
 
# Python dotted path to the WSGI application used by Django's runserver.
 
WSGI_APPLICATION = "pinaxcon.wsgi.application"
pinaxcon/templates/_default_sidebar.html
Show inline comments
...
 
@@ -12,17 +12,17 @@
 

	
 
          <h4>{{ level.name }}</h4>
 

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

	
 
          {% endfor %}
 

	
 
        {% endif %}
pinaxcon/templates/_footer.html
Show inline comments
...
 
@@ -5,17 +5,17 @@
 
    <div class="circle">
 
      <div class="fill" style="background-image: url('{% static "images/logo.svg" %}');"></div>
 
    </div>
 
  </div>
 

	
 
  <div class="footer-copy">
 
    <p>&copy; 2017 North Bay Python, member project of <a href="https://sfconservancy.org" title="Software Freedom Conservancy">Software Freedom Conservancy</a>, a 501(c)(3) charity.</p>
 
    <p>&copy; 2017 North Bay Python, member project of <a href="https://sfconservancy.org" >Software Freedom Conservancy</a>, a 501(c)(3) charity.</p>
 

	
 
    <p>
 
      <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="/code-of-conduct" title="North Bay Python Code of Conduct">Code of Conduct</a>
 
      | <a href="/about/colophon" title="North Bay Python Colophon">Colophon</a></p>
 
      <a href="https://facebook.com/northbaypython">Facebook</a>
 
      | <a href="https://twitter.com/northbaypython">Twitter</a>
 
      | <a href="/code-of-conduct">Code of Conduct</a>
 
      | <a href="/about/colophon">Colophon</a></p>
 

	
 
    <p>This site is <a href="https://github.com/northbaypython/website" title="North Bay Python Website Git Repository">free and open source software</a>, powered by <a href="https://github.com/chrisjrn/symposion/" title="Symposion Git Repository">Symposion</a> and <a href="https://github.com/chrisjrn/registrasion/" title="Registrasion Git Repository">Registrasion</a>.</p>
 
    <p>This site is <a href="https://github.com/northbaypython/website">free and open source software</a>, powered by <a href="https://github.com/chrisjrn/symposion/">Symposion</a> and <a href="https://github.com/chrisjrn/registrasion/">Registrasion</a>.</p>
 
  </div>
 
</div>
pinaxcon/templates/override_bootstrap_theme_base.html
Show inline comments
 
new file 100644
 
{% extends "theme_bootstrap/base.html" %}
 
{% comment %}
 
    Derived from pinax_theme_bootstrap's "theme_bootstrap/base.html".
 

	
 
    Pinax Bootstrap Theme
 
    Copyright (c) 2015 James Tauber and contributors.
 

	
 
    Permission is hereby granted, free of charge, to any person
 
    obtaining a copy of this software and associated documentation
 
    files (the "Software"), to deal in the Software without
 
    restriction, including without limitation the rights to use,
 
    copy, modify, merge, publish, distribute, sublicense, and/or sell
 
    copies of the Software, and to permit persons to whom the
 
    Software is furnished to do so, subject to the following
 
    conditions:
 

	
 
    The above copyright notice and this permission notice shall be
 
    included in all copies or substantial portions of the Software.
 

	
 
    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
 
    EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES
 
    OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
 
    NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
 
    HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
 
    WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
 
    FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
 
    OTHER DEALINGS IN THE SOFTWARE.
 

	
 
{% endcomment %}
 

	
 

	
 
{% block topbar_base %}
 
  <header>
 
    <div class="navbar navbar-default {% block navbar_class %}navbar-fixed-top{% endblock %}">
 
      <div class="container">
 
        {% block topbar %}
 
          <div class="navbar-header">
 
            <button class="navbar-toggle" data-toggle="collapse" data-target=".navbar-collapse">
 
              <span class="fa fa-bars">
 
                <span class="hidden-accessible">Pages Menu</span>
 
              </span>
 
            </button>
 
            {% block site_brand %}<a class="navbar-brand" href="{% url "home" %}">{{ SITE_NAME }}</a>{% endblock %}
 
          </div>
 
          <div class="collapse navbar-collapse navbar-responsive-collapse">
 
            {% block nav %}
 
              {% comment %}
 
                <ul class="nav navbar-nav">
 
                  <li><a href="#tab_one">One</a></li>
 
                  <li><a href="#tab_two">Two</a></li>
 
                </ul>
 
              {% endcomment %}
 
            {% endblock %}
 
            {% block account_bar %}{% include "_account_bar.html" %}{% endblock %}
 
          </div>
 
        {% endblock %}
 
      </div>
 
    </div>
 
  </header>
 
{% endblock %}
pinaxcon/templates/site_base.html
Show inline comments
 
{% extends "theme_bootstrap/base.html" %}
 
{% extends "override_bootstrap_theme_base.html" %}
 

	
 
{% load staticfiles %}
 
{% load metron_tags %}
 
{% load i18n %}
 
{% load sitetree %}
 

	
pinaxcon/templates/static_pages/about/colophon.html
Show inline comments
...
 
@@ -9,44 +9,44 @@
 
{% block body_class %}about{% endblock %}
 

	
 
{% block content %}
 

	
 
<h2>Call for Proposals</h2>
 

	
 
<p>Portions of our Call for Proposals 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>
 
<p>Portions of our Call for Proposals 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>
 

	
 
<h2>Code of Conduct</h2>
 

	
 
<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>
 
<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</a> license, 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</a> license.</p>
 

	
 
<h2>Fiscal Sponsor</h2>
 

	
 
<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>
 
<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>
 

	
 
<h2>Photography</h2>
 

	
 
<ul>
 
  <li>Photo of <a href="https://www.instagram.com/p/BU-G5dGAkHt" title="Photo of Mystic Theatre">Mystic Theatre</a> used on the home page by Christopher Neugebauer under the <a href="https://creativecommons.org/licenses/by-sa/2.0/" title="Creative Commons Attribution Share Alike 2.0 Generic License">Creative Commons Attribute Share Alike 2.0 Generic</a> license.</li>
 
  <li>Photo of <a href="https://www.flickr.com/photos/richard_jones/14638274749" title="Photo of DjangoGirls Brisbane 2014">DjangoGirls Brisbane 2014</a> used on the home page by Richard Jones under the <a href="https://creativecommons.org/licenses/by/2.0/" title="Creative Commons Attribution 2.0 Generic">Creative Commons Attribution 2.0 Generic</a> license.</li>
 
  <li>Photo of <a href="https://www.instagram.com/p/BU-G5dGAkHt">Mystic Theatre</a> used on the home page by Christopher Neugebauer under the <a href="https://creativecommons.org/licenses/by-sa/2.0/" >Creative Commons Attribute Share Alike 2.0 Generic</a> license.</li>
 
  <li>Photo of <a href="https://www.flickr.com/photos/richard_jones/14638274749">DjangoGirls Brisbane 2014</a> used on the home page by Richard Jones under the <a href="https://creativecommons.org/licenses/by/2.0/">Creative Commons Attribution 2.0 Generic</a> license.</li>
 
</ul>
 

	
 
<h2>Python</h2>
 

	
 
<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>
 
<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>
 

	
 
<h2>Terms and Conditions</h2>
 

	
 
<p>
 
  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>
 
  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>
 

	
 
<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/" 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>
 
  <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://inkscape.org/">Inkscape</a> is used to create most of our graphics.</li>
 
</ul>
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/about/team.html
Show inline comments
...
 
@@ -17,51 +17,51 @@ Our team of North Bay and Bay Area locals has years of experience building commu
 
{% endblock %}
 

	
 
{% block content %}
 

	
 
<h2>Contact the Team</h2>
 

	
 
<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>
 
<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>You can also find us all over the internet, including:</p>
 

	
 
<ul>
 
  <li><a href="https://facebook.com/northbaypython" title="North Bay Python on Facebook">Facebook</a></li>
 
  <li><a href="https://twitter.com/northbaypython" title="North Bay Python on Twitter">Twitter</a></li>
 
  <li><a href="https://webchat.freenode.net/?channels=%23nbpy" title="IRC Web Client for North Bay Python's #nbpy Channel on Freenode">IRC (#nbpy on Freenode)</a></li>
 
  <li><a href="https://facebook.com/northbaypython">Facebook</a></li>
 
  <li><a href="https://twitter.com/northbaypython">Twitter</a></li>
 
  <li><a href="https://webchat.freenode.net/?channels=%23nbpy">IRC (#nbpy on Freenode)</a></li>
 
</ul>
 

	
 

	
 
<h2>Meet the Team</h2>
 

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

	
 
<p><img src="{% static "images/team/chris.jpg" %}" alt="Christopher Neugebauer" class="team-headshot">Christopher 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. (<a href="https://twitter.com/chrisjrn" title="Christopher Neugebauer on Twitter">@chrisjrn on Twitter</a>)</p>
 
<p><img src="{% static "images/team/chris.jpg" %}" alt="Christopher Neugebauer" class="team-headshot">Christopher 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. (<a href="https://twitter.com/chrisjrn">@chrisjrn on Twitter</a>)</p>
 

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

	
 
<p><img src="{% static "images/team/sam.jpg" %}" alt="Sam Kitajima-Kimbrel" class="team-headshot">Sam is a Python developer and distributed-systems "enthusiast" hailing from Seattle by birth, New York by nurture, and the Bay Area by choice. Five years ago he attended his first PyCon US and hasn't been able to break the habit; after making the jump from audience to stage in 2014 and speaking regularly at events around the world, he was thrilled to join 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. (<a href="https://twitter.com/skimbrel" title="Sam Kitajima-Kimbrel on Twitter">@skimbrel on Twitter</a>)</p>
 
<p><img src="{% static "images/team/sam.jpg" %}" alt="Sam Kitajima-Kimbrel" class="team-headshot">Sam is a Python developer and distributed-systems "enthusiast" hailing from Seattle by birth, New York by nurture, and the Bay Area by choice. Five years ago he attended his first PyCon US and hasn't been able to break the habit; after making the jump from audience to stage in 2014 and speaking regularly at events around the world, he was thrilled to join 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. (<a href="https://twitter.com/skimbrel">@skimbrel on Twitter</a>)</p>
 

	
 
<h4>Andrew Godwin</h4>
 
<h3>Andrew Godwin</h3>
 

	
 
<p><img src="{% static "images/team/andrew.jpg" %}" alt="Andrew Godwin" class="team-headshot">Andrew 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. (<a href="https://twitter.com/andrewgodwin" title="Andrew Godwin on Twitter">@andrewgodwin on Twitter</a>)</p>
 
<p><img src="{% static "images/team/andrew.jpg" %}" alt="Andrew Godwin" class="team-headshot">Andrew 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. (<a href="https://twitter.com/andrewgodwin">@andrewgodwin on Twitter</a>)</p>
 

	
 
<h4>Josh Simmons</h4>
 
<p><img src="{% static "images/team/josh.jpg" %}" alt="Josh Simmons" class="team-headshot">Josh is a community organizer and web developer with a penchant for armchair philosophy 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. (<a href="https://twitter.com/joshsimmons" title="Josh Simmons on Twitter">@joshsimmons on Twitter</a>)</p>
 
<h3>Josh Simmons</h3>
 
<p><img src="{% static "images/team/josh.jpg" %}" alt="Josh Simmons" class="team-headshot">Josh is a community organizer and web developer with a penchant for armchair philosophy 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. (<a href="https://twitter.com/joshsimmons">@joshsimmons on Twitter</a>)</p>
 

	
 

	
 
<h2>Advisors</h2>
 

	
 
<p>We acknowledge that our small team has limited perspective, and that to build a truly inclusive event, we need to seek the perspectives of a diverse range of people. We thank the following people and organizations for providing us with advice along the way.</p>
 

	
 
<ul>
 
  <li><a href="https://twitter.com/vavroom" title="Nicolas Steenhout on Twitter">Nicolas Steenhout</a> is helping us with accessibility and inclusion of people with disabilities.</li>
 
  <li><a href="https://twitter.com/vmbrasseur" title="VM Brasseur on Twitter">VM (Vicky) Brasseur</a> is helping us run an excellent call for proposals, design our office hours program, and support new speakers with speaker training.</li>
 
  <li><a href="https://twitter.com/vavroom">Nicolas Steenhout</a> is helping us with accessibility and inclusion of people with disabilities.</li>
 
  <li><a href="https://twitter.com/vmbrasseur">VM (Vicky) Brasseur</a> is helping us run an excellent call for proposals, design our office hours program, and support new speakers with speaker training.</li>
 
</ul>
 

	
 

	
 
<h2>Supporting Organizations</h2>
 
<h4>Software Freedom Conservancy</h4>
 
<h3>Software Freedom Conservancy</h3>
 

	
 
<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>
 
<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&mdash;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>&mdash;none of this would be possible!</p>
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/code_of_conduct/code_of_conduct.md
Show inline comments
...
 
@@ -30,21 +30,21 @@ Be careful in the words that you choose. Remember that sexist, racist, and other
 

	
 
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 conference chair [Christopher Neugebauer](mailto:chrisjrn@northbaypython.org "chrisjrn@northbaypython.org").
 
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 conference chair [Christopher Neugebauer](mailto:chrisjrn@northbaypython.org).
 

	
 
If the matter is especially urgent, please call our Code of Conduct and safety incident hotline. **The phone number for this hotline will be released shortly before the conference begins.** 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 "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")
 
- [Attendee procedure for incident handling](/code-of-conduct/harassment-incidents)
 
- [Staff procedure for incident handling](/code-of-conduct/harassment-staff-procedures)
 

	
 
License
 
-------
 

	
 
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
 
This Code of Conduct was forked from the [PyCon US Code of Conduct](https://github.com/python/pycon-code-of-conduct) under a [Creative Commons Attribution 3.0 Unported](http://creativecommons.org/licenses/by/3.0/) license, itself originally forked from the example policy in [Geek Feminism wiki](http://geekfeminism.wikia.com/wiki/Conference_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/) license.
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 "Ada Initive Anti-harassment Guide on 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)".*
 

	
 
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.*
 
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.*
 

	
 
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:
...
 
@@ -17,7 +17,7 @@ The important information consists of:
 
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 "About the North Bay Python team"), including contact phone numbers. If at all possible, all reports should be made directly to conference chair [Christopher Neugebauer](mailto:chrisjrn@northbaypython.org "chrisjrn@northbaypython.org").
...
 
\ No newline at end of file
 
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 conference chair [Christopher Neugebauer](mailto:chrisjrn@northbaypython.org).
...
 
\ 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 "Ada Initive Anti-harassment Guide on 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)".*
 

	
 
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")
 
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)
 

	
 
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")
 
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)
 

	
 
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)
...
 
@@ -58,7 +58,7 @@ Give accused attendees a place to appeal to if there is one, but in the meantime
 
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 "About the North Bay Python team"), including contact phone numbers. If at all possible, all reports should be made directly to conference chair [Christopher Neugebauer](mailto:chrisjrn@northbaypython.org "chrisjrn@northbaypython.org").
...
 
\ No newline at end of file
 
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 conference chair [Christopher Neugebauer](mailto:chrisjrn@northbaypython.org).
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/homepage.html
Show inline comments
...
 
@@ -13,13 +13,13 @@
 
  <div class="jumbotron homepage-block light">
 
    <div class="homepage-block-bg website-background"></div>
 
    <div class="hills main"></div>
 
    <div class="container homepage-block-content">
 
      <div class="tight-headings">
 
        <h1>North Bay Python</h1>
 
        <h3>A Python conference north of the Golden Gate</h3>
 
        <h2 class="homepage-subtitle">A Python conference north of the Golden Gate</h2>
 
      </div>
 

	
 
      <div class="row">
 
        <div class="col-md-6">
 
          <h3>
 
            The Mystic Theatre</br>
...
 
@@ -39,13 +39,13 @@
 
            <div class="panel-body">
 
              <form
 
                class="form-inline"
 
                action="https://tinyletter.com/northbaypython" method="post" target="popupwindow" onsubmit="window.open('https://tinyletter.com/northbaypython', 'popupwindow', 'scrollbars=yes,width=800,height=600');return true">
 
                <div class="form-group">
 
                  <span>
 
                    <label style="display: none;" for="tlemail">Email address:</label>
 
                    <label class="hidden-accessible" for="tlemail">Email address:</label>
 
                  </span>
 
                  <span>
 
                    <input class="form-control" type="email" name="email" id="tlemail" placeholder="E-mail address"/>
 
                  </span>
 
                </div>
 
                <span>
...
 
@@ -61,14 +61,14 @@
 
      </div>
 

	
 
    </div>
 

	
 
    <div class="container homepage-block-footer">
 
      <div>
 
        <a class="btn btn-default btn-lg " href="https://twitter.com/northbaypython" title="North Bay Python on Twitter">Twitter</a>
 
        <a class="btn btn-default btn-lg" href="https://facebook.com/northbaypython" title="North Bay Python on Facebook">Facebook</a>
 
        <a class="btn btn-default btn-lg " href="https://twitter.com/northbaypython">Twitter</a>
 
        <a class="btn btn-default btn-lg" href="https://facebook.com/northbaypython">Facebook</a>
 
      </div>
 
    </div>
 
  </div>
 

	
 
  <div class="jumbotron homepage-block dark">
 
    <div class="homepage-block-bg mystic-background"></div>
...
 
@@ -87,17 +87,17 @@
 
    </div>
 

	
 
    <div class="homepage-block-footer full-width">
 
      <div class="container">
 
        <div class="row">
 
          <div class="btn-group col-md-4">
 
            <a class="btn btn-lg btn-primary btn-shadow" href="/about/north-bay-python" title="About North Bay Python">Learn More</a>
 
            <a class="btn btn-lg btn-primary btn-shadow" href="/about/north-bay-python">Learn More</a>
 
          </div>
 

	
 
          <div class="col-md-8 text-right photo-attribution">
 
            Image credit: <a href="https://www.instagram.com/p/BU-G5dGAkHt" title="Photo of the Mystic Theatre">Mystic Theatre</a>, &copy; 2017 Christopher Neugebauer (<a href="https://creativecommons.org/licenses/by-sa/2.0/" title="Creative Commons Attribute Share Alike 2.0 Generic License">CC BY-SA 2.0</a>)
 
            Image credit: <a href="https://www.instagram.com/p/BU-G5dGAkHt">Mystic Theatre</a>, &copy; 2017 Christopher Neugebauer (<a href="https://creativecommons.org/licenses/by-sa/2.0/">CC BY-SA 2.0</a>)
 
          </div>
 
        </div>
 
      </div>
 
    </div>
 
  </div>
 

	
...
 
@@ -113,28 +113,28 @@
 
      <div class="row sponsor-list">
 
      {% for level in levels %}
 
          {% if level.sponsors %}
 
              {% for sponsor in level.sponsors %}
 
                  <div class="sponsor">
 
                      {% if sponsor.website_logo %}
 
                          <a href="{{ sponsor.external_url }}" title="{{ sponsor.name }}">
 
                          <a href="{{ sponsor.external_url }}">
 
                              <img src="{% thumbnail sponsor.website_logo '600x360' %}" alt="{{ sponsor.name }}">
 
                          </a>
 
                      {% else %}
 
                          <a href="{{ sponsor.external_url }}" title="{{ sponsor.name }}">{{ sponsor.name }}</a>
 
                          <a href="{{ sponsor.external_url }}">{{ sponsor.name }}</a>
 
                      {% endif %}
 
                  </div>
 
              {% endfor %}
 
          {% endif %}
 
      {% endfor %}
 
      </div>
 
    </div>
 

	
 
    <div class="container homepage-block-footer">
 
      <div class="btn-group">
 
        <a class="btn btn-lg btn-primary btn-shadow" href="/sponsors/become-a-sponsor" title="Become a Sponsor">Become a Sponsor</a>
 
        <a class="btn btn-lg btn-primary btn-shadow" href="/sponsors/become-a-sponsor">Become a Sponsor</a>
 
      </div>
 
    </div>
 
  </div>
 

	
 
  <div class="jumbotron homepage-block dark">
 
    <div class="homepage-block-bg djangogirls-background"></div>
...
 
@@ -156,13 +156,13 @@
 
        <div class="row">
 
          <div class="btn-group col-md-4">
 
            <a class="btn btn-lg btn-primary btn-shadow" href="/code-of-conduct" title"North Bay Python Code of Conduct">Read the Code of Conduct</a>
 
          </div>
 

	
 
          <div class="col-md-8 text-right photo-attribution">
 
            Image credit: <a href="https://www.flickr.com/photos/richard_jones/14638274749" title="Photo from DjangoGirls Brisbane 2014">DjangoGirls Brisbane</a>, &copy; 2014 Richard Jones (<a href="https://creativecommons.org/licenses/by/2.0/" title="Creative Commons Attribute 2.0 Generic License">CC BY 2.0</a>)
 
            Image credit: <a href="https://www.flickr.com/photos/richard_jones/14638274749">DjangoGirls Brisbane</a>, &copy; 2014 Richard Jones (<a href="https://creativecommons.org/licenses/by/2.0/">CC BY 2.0</a>)
 
          </div>
 
        </div>
 
      </div>
 
    </div>
 
  </div>
 

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

	
 
We've got lots of good information and resources below that you should read, but in case you've already read it and want to dive in now:
 

	
 
<div class="btn-group">
 
  <a class="btn btn-lg btn-primary" href="/dashboard" title="Submit a Proposal to North Bay Python">Submit a Proposal</a>
 
  <a class="btn btn-lg btn-primary" href="/dashboard">Submit a Proposal</a>
 
</div>
 

	
 
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 "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!
 
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!
 

	
 
## Dates
 

	
 
+ **August 21, 2017**: CFP opens
 
+ **September 29, 2017**: CFP closes
 
+ **Week of October 9**: Acceptance notifications sent
...
 
@@ -19,13 +19,13 @@ In the interest of transparency, we have documented our [selection process](/pro
 
+ **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 "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.**
 
**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.**
 

	
 
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
...
 
@@ -35,13 +35,13 @@ North Bay Python is a conference in support of the local programmer community ou
 
## Topics
 

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

	
 
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 your library should come away excited about the possibilities, and know what concepts they need to learn 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 <a href="mailto:program@northbaypython.org" title="program@northbaypython.org">hear about it</a>!
 
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 <a href="mailto:program@northbaypython.org">hear about it</a>!
 

	
 
+ The Python community
 
+ Python fundamentals
 
+ Useful libraries and tools
 
+ Testing in Python
 
+ Deploying, operating, or scaling Python
...
 
@@ -50,27 +50,27 @@ This is a list of topics we think might go well in the North Bay Python program,
 
+ Accessibility in Python (and other) software
 
+ Unexpected places Python gets used (Embedded systems! Health science!)
 
+ ... and anything else we might not have thought of!
 

	
 
## Resources
 

	
 
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.
 
This [public speaking](https://github.com/vmbrasseur/Public_Speaking) repository, maintained by [VM Brasseur](https://twitter.com/vmbrasseur), 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. You are also welcome to <a href="mailto:program@northbaypython.org" title="program@northbaypython.org">email us</a> or drop by <a href="https://webchat.freenode.net/?channels=%23nbpy" title="IRC Web Client for #nbpy Channel on Freenode">#nbpy on the Freenode IRC network</a> anytime to ask questions.
 
The program committee will be holding regularly-scheduled office hours during the CFP period to help you organize proposals. You are also welcome to <a href="mailto:program@northbaypython.org">email us</a> or drop by <a href="https://webchat.freenode.net/?channels=%23nbpy">#nbpy on the Freenode IRC network</a> anytime to ask questions.
 

	
 
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!
 

	
 
Our office hours are scheduled for every <strong>Wednesday at 7pm</strong> and <strong>Friday at 3pm</strong> Pacific Time. They will take place in <a href="https://webchat.freenode.net/?channels=%23nbpy" title="IRC Web Client for #nbpy Channel on Freenode">#nbpy on the Freenode IRC network</a>. IRC is a web chat protocol and you can use <a href="https://webchat.freenode.net/?channels=%23nbpy" title="IRC Web Client for #nbpy Channel on Freenode">this IRC web client</a> to connect.
 
Our office hours are scheduled for every <strong>Wednesday at 7pm</strong> and <strong>Friday at 3pm</strong> Pacific Time. They will take place in <a href="https://webchat.freenode.net/?channels=%23nbpy">#nbpy on the Freenode IRC network</a>. IRC is a web chat protocol and you can use <a href="https://webchat.freenode.net/?channels=%23nbpy">this IRC web client</a> to connect.
 

	
 
+ Wednesday, August 23 at 7pm
 
+ Friday, August 25 at 3pm
 
+ Wednesday, August 30 at 7pm
 
+ Friday, September 1 at 3pm
 
+ Wednesday, September 6 at 7pm
...
 
@@ -88,20 +88,20 @@ To help us evaluate proposals and build our program, we would like as much detai
 

	
 
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&mdash;this is your chance to talk yourself up and explain how you're qualified to share your ideas, so take advantage of it!
 

	
 
<div class="btn-group">
 
  <a class="btn btn-lg btn-primary" href="/dashboard" title="Submit a Proposal to North Bay Python">Submit a Proposal</a>
 
  <a class="btn btn-lg btn-primary" href="/dashboard">Submit a Proposal</a>
 
</div>
 

	
 
## Feedback and mentorship
 

	
 
**First time speakers are welcomed and encouraged; if you've never done this before but have an idea please <a href="mailto:program@northbaypython.org" title="program@northbaypython.org">contact the program committee</a> 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!**
 
**First time speakers are welcomed and encouraged; if you've never done this before but have an idea please <a href="mailto:program@northbaypython.org">contact the program committee</a> 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 "Wikipedia Entry on Mind Mapping") to expand upon your ideas or knowledge in search of a general topic
 
+ Brainstorm or [mind map](https://en.wikipedia.org/wiki/Mind_map) 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!
static/scss/custom.scss
Show inline comments
...
 
@@ -100,12 +100,25 @@ body.auth .panel-heading .panel-title span.pull-right {
 

	
 
#content_body {
 
  background-color: $background-filter-transparent;
 
  box-shadow: 0px 0px 2em $background-filter; //, inset 0px -5px 1em rgba(0, 0, 0, 0.8);
 
}
 

	
 

	
 
.hidden-accessible {
 
  border:0 none;
 
  clip:rect(0px,0px,0px,0px);
 
  height:1px;
 
  margin:-1px;
 
  overflow:hidden;
 
  padding:0;
 
  position:absolute;
 
  width:1px
 
}
 

	
 

	
 
$homepage-block-min-height: 480px;
 

	
 
.homepage-block {
 
  margin-top: 0;
 
  margin-bottom: 0;
 
  min-height: $homepage-block-min-height;
...
 
@@ -359,6 +372,14 @@ footer .footer-copy {
 

	
 
@media (min-width: 992px) {
 
  .email-signup-panel {
 
    margin-top: 22px;
 
  }
 
}
 

	
 
.homepage-subtitle {
 
  font-size: $font-size-h3;
 
}
 

	
 
.navbar-toggle {
 
  background-color: $gray-lighter;
 
}
0 comments (0 inline, 0 general)