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

</div>

<div class="pull-right">

    Site powered by <a href="http://eldarion.com/symposion/"><b>Symposion</b></a>

    and <a href="http://github.com/chrisjrn/registrasion/"><b>Registrasion</b></a>.

</div>

{% extends "page_with_title_and_lede.html" %}

{% load i18n %}

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

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

{% block content %}

  * Python logo attribution and copyright notice

  * SFC copyright notices

  * information about codebase inc. Django, Symposion, Registrasion

  * COC attribution

{% endblock %}

{% load i18n %}

{% load markdown_deux_tags %}

{% block head_title %}Code of Conduct{% endblock %}

{% block heading %}Code of Conduct{% endblock %}

{% block body_class %}code-of-conduct{% endblock %}

{% block content %}

  {% markdown %}

  {% endmarkdown %}

{% endblock %}

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

License

-------

{% load i18n %}

{% load markdown_deux_tags %}

{% block head_title %}Attendee procedure for incident handling{% endblock %}

{% block heading %}Attendee procedure for incident handling{% endblock %}

{% block body_class %}code-of-conduct{% endblock %}

{% block content %}

  {% markdown %}

  {% endmarkdown %}

{% endblock %}

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

{% load i18n %}

{% load markdown_deux_tags %}

{% block head_title %}Staff procedure for incident handling{% endblock %}

{% block heading %}Staff procedure for incident handling{% endblock %}

{% block body_class %}code-of-conduct{% endblock %}

{% block content %}

  {% markdown %}

  {% endmarkdown %}

{% endblock %}

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

{% extends "page_with_title_and_lede.html" %}

{% load i18n %}

{% load markdown_deux_tags %}

{% block head_title %}Call for Proposals{% endblock %}

{% block heading %}Call for Proposals{% endblock %}

{% block content %}

  {% markdown %}

  {% endmarkdown %}

{% endblock %}

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

### The North Bay Python 2017 CFP is open!

North Bay Python is seeking speakers of all experience levels, especially first-timers, to contribute to our first-ever conference program! If you use Python professionally or as a hobbyist, or are even just excited about Python or programming and open source in general, we'd love to hear from you.

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.

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

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.

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.

## Topics

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

{% extends "page_with_title_and_lede.html" %}

{% load i18n %}

{% load markdown_deux_tags %}

{% block head_title %}Selection Process{% endblock %}

{% block heading %}Selection Process{% endblock %}

{% block content %}

  {% markdown %}

  {% endmarkdown %}

{% endblock %}

{% extends "page_with_title_and_lede.html" %}

{% load i18n %}

{% block body_class %}sponsors{% endblock %}

{% block content %}

{% endblock %}

from django.conf import settings

from django.conf.urls import include, url

from django.conf.urls.static import static

from django.views.generic import TemplateView

from django.contrib import admin

import symposion.views

urlpatterns = [

    url(r"^$", TemplateView.as_view(template_name="static_pages/homepage.html"), name="home"),

    url(r"^news$", TemplateView.as_view(template_name="static_pages/news.html"), name="news"),

    url(r"^admin/", include(admin.site.urls)),

    url(r"^account/", include("account.urls")),

    url(r"^dashboard/", symposion.views.dashboard, name="dashboard"),

    url(r"^speaker/", include("symposion.speakers.urls")),

    url(r"^proposals/", include("symposion.proposals.urls")),

    url(r"^sponsors/", include("symposion.sponsorship.urls")),

    url(r"^reviews/", include("symposion.reviews.urls")),

    url(r"^schedule/", include("symposion.schedule.urls")),