Merge pull request #11 from northbaypython/josh/copy

add colophon and code of conduct

fixtures/sitetree.json

@@ -150,5 +150,29 @@
         "sort_order": 9,
         "access_permissions": []
     }
+},
+{
+    "model": "sitetree.treeitem",
+    "pk": 10,
+    "fields": {
+        "title": "Colophon",
+        "hint": "",
+        "url": "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": 10,
+        "access_permissions": []
+    }
 }
 ]

pinaxcon/templates/_footer.html

@@ -1,5 +1,6 @@
 <div class="pull-left">
-    &copy; 2017
+    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>
 </div>
 
 <div class="pull-right">

pinaxcon/templates/static_pages/code-of-conduct.html

@@ -1,6 +1,7 @@
 {% extends "page_with_title_and_lede.html" %}
 
 {% load i18n %}
+{% load markdown_deux_tags %}
 
 {% block head_title %}Code of Conduct{% endblock %}
 
@@ -9,5 +10,9 @@
 {% block body_class %}code-of-conduct{% endblock %}
 
 {% block content %}
+  {% markdown %}
 
+{% include "static_pages/code-of-conduct.md" %}
+
+  {% endmarkdown %}
 {% endblock %}

pinaxcon/templates/static_pages/code-of-conduct.md

@@ -0,0 +1,50 @@
+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 — Chris 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
+------------------------------------------
+- [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) 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.

pinaxcon/templates/static_pages/colophon.html

@@ -0,0 +1,18 @@
+{% extends "page_with_title_and_lede.html" %}
+
+{% load i18n %}
+
+{% block head_title %}Colophon{% endblock %}
+
+{% block heading %}Colophon{% endblock %}
+
+{% block body_class %}colophon{% endblock %}
+
+{% block content %}
+
+  * Python logo attribution and copyright notice
+  * SFC copyright notices
+  * information about codebase inc. Django, Symposion, Registrasion
+  * COC attribution
+
+{% endblock %}

pinaxcon/templates/static_pages/harassment-procedure-attendee.html

@@ -0,0 +1,18 @@
+{% extends "page_with_title_and_lede.html" %}
+
+{% 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 %}
+
+{% include "static_pages/harassment-procedure-attendee.md" %}
+
+  {% endmarkdown %}
+{% endblock %}

pinaxcon/templates/static_pages/harassment-procedure-attendee.md

@@ -0,0 +1,23 @@
+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) 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/staff), including contact phone numbers. If at all possible, all reports should be made directly to Bleep and Bloop.

pinaxcon/templates/static_pages/harassment-procedure-staff.html

@@ -0,0 +1,18 @@
+{% extends "page_with_title_and_lede.html" %}
+
+{% 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 %}
+
+{% include "static_pages/harassment-procedure-staff.md" %}
+
+  {% endmarkdown %}
+{% endblock %}

pinaxcon/templates/static_pages/harassment-procedure-staff.md

@@ -0,0 +1,65 @@
+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)
+
+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)
+ - 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/staff), including contact phone numbers. If at all possible, all reports should be made directly to Bleep and Bloop.

pinaxcon/urls.py

@@ -10,9 +10,17 @@ import symposion.views
 
 urlpatterns = [
     url(r"^$", TemplateView.as_view(template_name="static_pages/homepage.html"), name="home"),
-    url(r"^code-of-conduct$", TemplateView.as_view(template_name="static_pages/code-of-conduct.html"), name="code-of-conduct"),
     url(r"^about$", TemplateView.as_view(template_name="static_pages/about.html"), name="about"),
     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"),
+
+    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")),
@@ -21,10 +29,7 @@ urlpatterns = [
 
     url(r"^speaker/", include("symposion.speakers.urls")),
     url(r"^proposals/", include("symposion.proposals.urls")),
-    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"),
     url(r"^sponsors/", include("symposion.sponsorship.urls")),
-    url(r"^sponsors$", TemplateView.as_view(template_name="static_pages/sponsors.html"), name="sponsors"),
     url(r"^reviews/", include("symposion.reviews.urls")),
     url(r"^schedule/", include("symposion.schedule.urls")),