Changeset - febf21c8480b
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/>
 
    <a href="/code-of-conduct">Code of Conduct</a> | <a href="/colophon">Colophon</a> | <a href="/terms-conditions">Terms and Conditions</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>
 
</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>
pinaxcon/templates/static_pages/about/colophon.html
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/colophon.html to pinaxcon/templates/static_pages/about/colophon.html
...
 
@@ -3,13 +3,13 @@
 
{% load i18n %}
 

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

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

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

	
 
{% block content %}
 

	
 
  * Python logo attribution and copyright notice
 
  * SFC copyright notices
 
  * information about codebase inc. Django, Symposion, Registrasion
pinaxcon/templates/static_pages/about/north-bay-python.html
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/about.html to pinaxcon/templates/static_pages/about/north-bay-python.html
pinaxcon/templates/static_pages/about/team.html
Show inline comments
 
new file 100644
 
{% 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 content %}
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/code-of-conduct/code-of-conduct.html
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/code-of-conduct.html to pinaxcon/templates/static_pages/code-of-conduct/code-of-conduct.html
...
 
@@ -9,10 +9,10 @@
 

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

	
 
{% block content %}
 
  {% markdown %}
 

	
 
{% include "static_pages/code-of-conduct.md" %}
 
{% include "static_pages/code-of-conduct/code-of-conduct.md" %}
 

	
 
  {% endmarkdown %}
 
{% endblock %}
pinaxcon/templates/static_pages/code-of-conduct/code-of-conduct.md
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/code-of-conduct.md to pinaxcon/templates/static_pages/code-of-conduct/code-of-conduct.md
...
 
@@ -30,13 +30,13 @@ 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 the conference chair &mdash; Chris 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.
 

	
 
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
pinaxcon/templates/static_pages/code-of-conduct/harassment-procedure-attendee.html
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/harassment-procedure-attendee.html to pinaxcon/templates/static_pages/code-of-conduct/harassment-procedure-attendee.html
...
 
@@ -9,10 +9,10 @@
 

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

	
 
{% block content %}
 
  {% markdown %}
 

	
 
{% include "static_pages/harassment-procedure-attendee.md" %}
 
{% include "static_pages/code-of-conduct/harassment-procedure-attendee.md" %}
 

	
 
  {% endmarkdown %}
 
{% endblock %}
pinaxcon/templates/static_pages/code-of-conduct/harassment-procedure-attendee.md
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/harassment-procedure-attendee.md to pinaxcon/templates/static_pages/code-of-conduct/harassment-procedure-attendee.md
...
 
@@ -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/staff), 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), 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.html
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/harassment-procedure-staff.html to pinaxcon/templates/static_pages/code-of-conduct/harassment-procedure-staff.html
...
 
@@ -9,10 +9,10 @@
 

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

	
 
{% block content %}
 
  {% markdown %}
 

	
 
{% include "static_pages/harassment-procedure-staff.md" %}
 
{% include "static_pages/code-of-conduct/harassment-procedure-staff.md" %}
 

	
 
  {% endmarkdown %}
 
{% endblock %}
pinaxcon/templates/static_pages/code-of-conduct/harassment-procedure-staff.md
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/harassment-procedure-staff.md to pinaxcon/templates/static_pages/code-of-conduct/harassment-procedure-staff.md
...
 
@@ -59,7 +59,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/staff), 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), 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/program/call-for-proposals.html
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/proposals.html to pinaxcon/templates/static_pages/program/call-for-proposals.html
...
 
@@ -4,15 +4,15 @@
 
{% load markdown_deux_tags %}
 

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

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

	
 
{% block body_class %}proposals{% endblock %}
 
{% block body_class %}program{% endblock %}
 

	
 
{% block content %}
 
  {% markdown %}
 

	
 
{% include "static_pages/proposals.md" %}
 
{% include "static_pages/program/call-for-proposals.md" %}
 

	
 
  {% endmarkdown %}
 
{% endblock %}
pinaxcon/templates/static_pages/program/call-for-proposals.md
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/proposals.md to pinaxcon/templates/static_pages/program/call-for-proposals.md
...
 
@@ -3,13 +3,13 @@
 
### 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.
 

	
 
In the interest of transparency, we have documented our [Selection Process](./selection-process).
 
In the interest of transparency, we have documented our [Selection Process](/program/selection-process).
 

	
 
## Dates
 

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

	
 
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
pinaxcon/templates/static_pages/program/selection-process.html
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/selection-process.html to pinaxcon/templates/static_pages/program/selection-process.html
...
 
@@ -4,15 +4,15 @@
 
{% load markdown_deux_tags %}
 

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

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

	
 
{% block body_class %}selection-process{% endblock %}
 
{% block body_class %}program{% endblock %}
 

	
 
{% block content %}
 
  {% markdown %}
 

	
 
{% include "static_pages/selection-process.md" %}
 
{% include "static_pages/program/selection-process.md" %}
 

	
 
  {% endmarkdown %}
 
{% endblock %}
pinaxcon/templates/static_pages/program/selection-process.md
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/selection-process.md to pinaxcon/templates/static_pages/program/selection-process.md
pinaxcon/templates/static_pages/sponsors/become-a-sponsor.html
Show inline comments
 
file renamed from pinaxcon/templates/static_pages/sponsors.html to pinaxcon/templates/static_pages/sponsors/become-a-sponsor.html
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}Call for Sponsors{% endblock %}
 
{% block head_title %}Become a Sponsors{% endblock %}
 

	
 
{% block heading %}Call for Sponsors{% endblock %}
 
{% block heading %}Become a Sponsors{% endblock %}
 

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

	
 
{% block content %}
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/terms-and-conditions.html
Show inline comments
 
new file 100644
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}Terms and Conditions{% endblock %}
 

	
 
{% block heading %}Terms and Conditions{% endblock %}
 

	
 
{% block body_class %}terms-and-conditions{% endblock %}
 

	
 
{% block content %}
 

	
 
{% endblock %}
pinaxcon/urls.py
Show inline comments
...
 
@@ -7,23 +7,50 @@ from django.contrib import admin
 

	
 
import symposion.views
 

	
 

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

	
 
    # about
 
    # TODO add /about
 
    url(r"^about/north-bay-python$", TemplateView.as_view(template_name="static_pages/about/north-bay-python.html"), name="about/north-bay-python"),
 
    # TODO add /about/the-mystic
 
    # TODO add /about/petaluma
 
    url(r"^about/team$", TemplateView.as_view(template_name="static_pages/about/team.html"), name="about/team"),
 
    url(r"^about/colophon$", TemplateView.as_view(template_name="static_pages/about/colophon.html"), name="about/colophon"),
 

	
 
    # program
 
    # TODO add /program
 
    # TODO add /program/sessions
 
    # TODO add /program/events
 
    url(r"^program/call-for-proposals$", TemplateView.as_view(template_name="static_pages/program/call-for-proposals.html"), name="program/call-for-proposals"),
 
    url(r"^program/selection-process$", TemplateView.as_view(template_name="static_pages/program/selection-process.html"), name="program/selection-process"),
 

	
 
    # attend
 
    # TODO add /attend
 
    # TODO add /attend/buy-a-ticket
 
    # TODO add /attend/volunteer
 
    # TODO add /attend/financial-assistance
 
    # TODO add /attend/how-to-pitch-your-manager
 
    # TODO add /attend/how-to-get-here
 
    # TODO add /attend/where-to-stay
 
    url(r"^code-of-conduct$", TemplateView.as_view(template_name="static_pages/code-of-conduct/code-of-conduct.html"), name="code-of-conduct"),
 
    url(r"^code-of-conduct/harassment-incidents$", TemplateView.as_view(template_name="static_pages/code-of-conduct/harassment-procedure-attendee.html"), name="code-of-conduct/harassment-incidents"),
 
    url(r"^code-of-conduct/harassment-staff-procedures$", TemplateView.as_view(template_name="static_pages/code-of-conduct/harassment-procedure-staff.html"), name="code-of-conduct/harassment-staff-procedures"),
 
    url(r"^terms-and-conditions$", TemplateView.as_view(template_name="static_pages/terms-and-conditions.html"), name="terms-and-conditions"),
 

	
 
    # sponsor
 
    # TODO add /sponsors
 
    url(r"^sponsors/become-a-sponsor$", TemplateView.as_view(template_name="static_pages/sponsors/become-a-sponsor.html"), name="sponsors/become-a-sponsor"),
 

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

	
 
    url(r"^proposals$", TemplateView.as_view(template_name="static_pages/proposals.html"), name="proposals"),
 
    url(r"^selection-process$", TemplateView.as_view(template_name="static_pages/selection-process.html"), name="selection-process"),
 
    # Django, Symposion, and Registrasion URLs
 

	
 
    url(r"^code-of-conduct$", TemplateView.as_view(template_name="static_pages/code-of-conduct.html"), name="code-of-conduct"),
 
    url(r"^code-of-conduct/harassment-incidents$", TemplateView.as_view(template_name="static_pages/harassment-procedure-attendee.html"), name="harassment-procedure-attendee"),
 
    url(r"^code-of-conduct/harassment-staff-procedures$", TemplateView.as_view(template_name="static_pages/harassment-procedure-staff.html"), name="harassment-procedure-staff"),
 
    url(r"^admin/", include(admin.site.urls)),
 

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

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

	
0 comments (0 inline, 0 general)