Changeset - 1bdb037f4740
[Not reviewed]
18 6 1
Brett Smith - 5 years ago 2018-10-05 16:15:11
Remove URLs and pages we know we don't need.

This includes some pages that need to be completely revised.
23 files changed:
0 comments (0 inline, 0 general)
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
North Bay Python is a community conference intended for networking and collaboration in the developer community.

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

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

The Short Version

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

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

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

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

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

The Longer Version

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

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

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

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

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 can email the incident response team at []( You may also contact venue staff and ask to be put in touch with conference chair [Christopher Neugebauer](

If the matter is especially urgent, please dial our Code of Conduct and safety incident hotline (we'll publish the phone number closer to the date of the event). 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)


This Code of Conduct was forked from the [PyCon US Code of Conduct]( under a [Creative Commons Attribution 3.0 Unported]( license, itself originally forked from the example policy in [Geek Feminism wiki](, created by the Ada Initiative and other volunteers. which is under a [Creative Commons Zero]( license.
Show inline comments
*This procedure has been adopted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](".*

1\. Keep in mind that all conference staff, volunteers, and incident responders will be clearly marked. The staff and incident responders 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.
\ No newline at end of file
Show inline comments
*This procedure has been adopted from the Ada Initiative's guide titled "[Conference anti-harassment/Responding to Reports](".*

Be sure to have a good understanding of our Code of Conduct policy, which can be found here: [](/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: [](/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.
\ No newline at end of file
Show inline comments
<a name="1"></a>
## Now accepting talk proposals for North Bay Python 2018

**Thursday, July 5, 2018**&mdash;The North Bay Python team is excited to announce that the [call for proposals]( (CFP) is now open! We are seeking speakers of all experience levels to contribute to our second annual conference. The CFP will close on August 10, 2018.

North Bay Python, taking place the weekend of November 3 &amp; 4, 2018, is a single-track event featuring two days of presentations by members of the community. The vast majority of the conference program will come from people who propose talks in our CFP process. Whether you use Python professionally, as a hobbyist, or are just excited about Python or programming and open source, we'd love to hear from you.

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

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

Feel free to reach out with any questions, comments, or ideas you have. You can find us on [Twitter](, [Facebook](, and [IRC](, or you can [email us]( Please, get started today! The [call for proposals]( closes on August 10, 2018.

<a name="0"></a>
## North Bay Python joins Software Freedom Conservancy

**Wednesday, August 16, 2017**&mdash;We are proud to announce that North Bay Python is now a member project of [Software Freedom Conservancy](, a 501(c)(3) charity dedicated to ethical technology and the development and promotion free and open source software. Conservancy will act as our fiscal sponsor, allowing our team to operate without managing our own corporate structure and administrative services.

Conservancy is home to many popular [free and open source software projects](, like [Selenium](, [PyPy](, [phpMyAdmin](, [Twisted](, and [Outreachy](, some of which run their own events. North Bay Python has the distinct honor of being the first member project that is exclusively focused on organizing community events.

We couldn't be more excited. We're celebrating by donating five free tickets to Outreachy participants and will be promoting member projects relevant to the Python community at the conference. Interested Outreachy alums (past or present) should [contact us]( We'll also have discounted tickets available for active financial supporters of Software Freedom Conservancy.

We look forward to working with Conservancy to advance software freedom and expand the community of Python developers. If this is the first time you've heard of Conservancy, we encourage you to check out [their website]( and give them your support.
\ No newline at end of file
Show inline comments
## Phase one: ranking of anonymized proposal contents

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

## Phase two: identity-aware ranking and curation

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

## North Bay Python's diversity goals

+ At least one-third (33%) of speakers should be not-men, and ideally at least half (50%).
+ As North Bay Python aims to serve the "tech-adjacent" and client services industries, at least one-fifth (20%) of speakers should be from professional backgrounds that are not the Silicon Valley or San Francisco startup/software industry.
+ People with disabilities should be represented in the North Bay Python speaker lineup.
+ Racial demographics of the speaker lineup should ideally reflect US and Bay Area demographics within some margin of error.
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
deleted file
Show inline comments
from django.conf import settings
from django.conf.urls import include, url
from django.conf.urls.static import static
from django.contrib.staticfiles.templatetags.staticfiles import static as _static
from django.views.generic import TemplateView
from django.views.generic import RedirectView

from django.contrib import admin

from pinaxcon import views

import symposion.views


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

    # about
    url(r"^about/north-bay-python$", TemplateView.as_view(template_name="static_pages/about/north_bay_python.html"), name="about/north-bay-python"),
    url(r"^about/petaluma$", TemplateView.as_view(template_name="static_pages/about/petaluma.html"), name="about/petaluma"),
    url(r"^about/team$", TemplateView.as_view(template_name="static_pages/about/team.html"), name="about/team"),
    url(r"^about/transparency$", TemplateView.as_view(template_name="static_pages/about/transparency/transparency.html"), name="about/transparency"),
    url(r"^about/program-transparency$", TemplateView.as_view(template_name="static_pages/about/transparency/program.html"), name="about/program-transparency"),
    url(r"^about/colophon$", TemplateView.as_view(template_name="static_pages/about/colophon.html"), name="about/colophon"),
    url(r"^about$", TemplateView.as_view(template_name="static_pages/about.html"), name="about"),

    # program
    url(r"^program/events$", TemplateView.as_view(template_name="static_pages/program/events.html"), name="program/events"),
    url(r"^events$", RedirectView.as_view(url="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"),
    # url(r"^program/selection-process$", TemplateView.as_view(template_name="static_pages/program/selection_process.html"), name="program/selection-process"),
    url(r"^proposals$", RedirectView.as_view(url="program/call-for-proposals")),
    url(r"^cfp$", RedirectView.as_view(url="program/call-for-proposals")),

    # attend
    url(r"^attend$", TemplateView.as_view(template_name="static_pages/attend/attend.html"), name="attend/attend"),
    url(r"^tickets$", RedirectView.as_view(url="attend")),
    url(r"^tickets/buy$", views.buy_ticket, name="buy_ticket"),
    url(r"^attend/business-case$", TemplateView.as_view(template_name="static_pages/attend/business-case.html"), name="attend/business-case"),
    url(r"^attend/finaid$", TemplateView.as_view(template_name="static_pages/attend/finaid.html"), name="attend/finaid"),
    url(r"^attend/travel$", TemplateView.as_view(template_name="static_pages/attend/travel.html"), name="attend/travel"),
    url(r"^attend/hotels$", TemplateView.as_view(template_name="static_pages/attend/hotels.html"), name="attend/hotels"),
    url(r"^attend/tshirt$", TemplateView.as_view(template_name="static_pages/attend/tshirt.html"), name="attend/tshirt"),
    url(r"^attend/accessibility-and-accommodations$",TemplateView.as_view(template_name="static_pages/attend/accommodations.html"), name="attend/accessibility-and-accommodations"),
    url(r"^accessibility$", RedirectView.as_view(url="attend/accessibility-and-accommodations")),
    url(r"^guides$",TemplateView.as_view(template_name="static_pages/attend/guides.html"), name="attend/guides"),
    url(r"^guide$", RedirectView.as_view(url="guides")),

    url(r"^safety$", TemplateView.as_view(template_name="static_pages/safety.html"), name="safety"),
    url(r"^emergencies$", RedirectView.as_view(url="safety")),
    url(r"^emergency$", RedirectView.as_view(url="safety")),

    url(r"^attend/food$", TemplateView.as_view(template_name="static_pages/attend/food.html"), name="attend/food"),
    url(r"^food$", RedirectView.as_view(url="attend/food")),
    url(r"^attend/transit$", TemplateView.as_view(template_name="static_pages/attend/transit.html"), name="attend/transit"),
    url(r"^transit$", RedirectView.as_view(url="attend/transit")),
    # url(r"^attend/accessibility-and-accommodations$",TemplateView.as_view(template_name="static_pages/attend/accommodations.html"), name="attend/accessibility-and-accommodations"),
    # url(r"^accessibility$", RedirectView.as_view(url="attend/accessibility-and-accommodations")),

    # url(r"^safety$", TemplateView.as_view(template_name="static_pages/safety.html"), name="safety"),
    # url(r"^emergencies$", RedirectView.as_view(url="safety")),
    # url(r"^emergency$", RedirectView.as_view(url="safety")),

    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"^coc$", RedirectView.as_view(url="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"),
    url(r"^terms$", RedirectView.as_view(url="terms-and-conditions")),
    # 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"),

    # sponsor
    url(r"^sponsors/prospectus$", RedirectView.as_view(url=_static("assets/northbaypython_prospectus.pdf")), name="sponsors/prospectus"),
    url(r"^northbaypython_prospectus.pdf$", RedirectView.as_view(url=_static("assets/northbaypython_prospectus.pdf")), name="northbaypython_prospectus.pdf"),
    url(r"^sponsors/become-a-sponsor$", TemplateView.as_view(template_name="static_pages/sponsors/become_a_sponsor.html"), name="sponsors/become-a-sponsor"),
    url(r"^sponsors/prospectus$", RedirectView.as_view(url=_static("assets/2019_CopyleftConf_prospectus.pdf")), name="sponsors/prospectus"),
    # url(r"^sponsors/become-a-sponsor$", TemplateView.as_view(template_name="static_pages/sponsors/become_a_sponsor.html"), name="sponsors/become-a-sponsor"),
    url(r"^sponsors/donate$", TemplateView.as_view(template_name="static_pages/sponsors/donate.html"), name="sponsors/donate"),
    url(r"^donate$", RedirectView.as_view(url="sponsors/donate")),
    url(r"^about/donate$", RedirectView.as_view(url="sponsors/donate")),

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

    # Django, Symposion, and Registrasion URLs

    url(r"^admin/", include(,

    url(r"^login$", views.account_login, name="nbpy_login"),
    # Override the default account_login view with one that takes email addys
    url(r"^account/login/$", views.EmailLoginView.as_view(), name="account_login"),
    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("")),
    url(r"^schedule/", include("symposion.schedule.urls")),

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

    # Demo payment gateway and related features
    url(r"^tickets/payments/", include("registripe.urls")),

    # Required by registrasion
    url(r'^tickets/', include('registrasion.urls')),
    url(r'^nested_admin/', include('nested_admin.urls')),

    # Catch-all MUST go last.
    #url(r"^", include("pinax.pages.urls")),


urlpatterns += static(settings.MEDIA_URL, document_root=settings.MEDIA_ROOT)

handler500 = views.server_error

Changeset was too big and was cut off... Show full diff anyway

0 comments (0 inline, 0 general)