Changeset - d84d9de1593b
[Not reviewed]
Merge
0 9 3
Christopher Neugebauer - 4 years ago 2017-08-09 04:03:21
_@chrisjrn.com
Merge pull request #7 from northbaypython/josh/copy

updates to site copy, fixes, and addition of markdown support
12 files changed with 177 insertions and 28 deletions:
0 comments (0 inline, 0 general)
pinaxcon/settings.py
Show inline comments
...
 
@@ -255,12 +255,18 @@ TICKET_PRODUCT_CATEGORY = 1
 

	
 
INVOICE_CURRENCY = "AUD"
 

	
 
# Use nose to run all tests
 
TEST_RUNNER = 'django_nose.NoseTestSuiteRunner'
 

	
 

	
 
# Tell nose to measure coverage on the 'foo' and 'bar' apps
 
NOSE_ARGS = [
 
    '--with-coverage',
 
    '--cover-package=registrasion.controllers,registrasion.models',
 
]
 

	
 
MARKDOWN_DEUX_STYLES = {
 
    "default": {
 
        "safe_mode": False,
 
    },
 
}
pinaxcon/templates/_default_sidebar.html
Show inline comments
...
 
@@ -4,20 +4,24 @@
 

	
 
{% sponsor_levels as levels %}
 

	
 
<h4>Sponsors</h4>
 

	
 
<div class="sponsor-list">
 
    {% for level in levels %}
 
        {% if level.sponsors %}
 
            <h3 style="margin-top: 3em;">{{ level.name }}</h3>
 

	
 
            {% for sponsor in level.sponsors %}
 
                <div style="margin: 10px 0;">
 
                    <a href="{{ sponsor.external_url }}">
 
                        <img src="{% thumbnail sponsor.website_logo '100x60' %}" alt="{{ sponsor.name }}" />
 
                    </a>
 
                    {% if sponsor.website_logo %}
 
                        <a href="{{ sponsor.external_url }}">
 
                            <img src="{% thumbnail sponsor.website_logo '100x60' %}" alt="{{ sponsor.name }}" />
 
                        </a>
 
                    {% else %}
 
                        <a href="{{ sponsor.external_url }}">{{ sponsor.name }}</a>
 
                    {% endif %}
 
                </div>
 
            {% endfor %}
 
        {% endif %}
 
    {% endfor %}
 
</div>
pinaxcon/templates/static_pages/about.html
Show inline comments
 
{% extends "site_base.html" %}
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}{% trans "Welcome" %}{% endblock %}
 
{% block head_title %}About North Bay Python{% endblock %}
 

	
 
{% block body_class %}home{% endblock %}
 
{% block heading %}About North Bay Python{% endblock %}
 

	
 
{% block body %}
 
{% block body_class %}about{% endblock %}
 

	
 
{% block content %}
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/code-of-conduct.html
Show inline comments
 
{% extends "site_base.html" %}
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}{% trans "Welcome" %}{% endblock %}
 
{% block head_title %}Code of Conduct{% endblock %}
 

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

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

	
 
{% block content %}
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/homepage.html
Show inline comments
 
{% extends "site_base.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}{% trans "Welcome" %}{% endblock %}
 
{% block head_title %}Welcome{% endblock %}
 

	
 
{% block body_class %}home{% endblock %}
 

	
 
{% block body %}
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/news.html
Show inline comments
 
{% extends "site_base.html" %}
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}{% trans "Welcome" %}{% endblock %}
 
{% block head_title %}News{% endblock %}
 

	
 
{% block body_class %}home{% endblock %}
 
{% block heading %}News{% endblock %}
 

	
 
{% block body %}
 
{% block body_class %}news{% endblock %}
 

	
 
{% block content %}
 

	
 
{% endblock %}
pinaxcon/templates/static_pages/proposals.html
Show inline comments
 
{% extends "site_base.html" %}
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 
{% load markdown_deux_tags %}
 

	
 
{% block head_title %}{% trans "Welcome" %}{% endblock %}
 
{% block head_title %}Call for Proposals{% endblock %}
 

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

	
 
{% block body %}
 
{% block body_class %}proposals{% endblock %}
 

	
 
{% block content %}
 
  {% markdown %}
 

	
 
{% include "static_pages/proposals.md" %}
 

	
 
  {% endmarkdown %}
 
{% endblock %}
pinaxcon/templates/static_pages/proposals.md
Show inline comments
 
new file 100644
 
*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.
 

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

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

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

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

	
 
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 new to your library – should come away excited about the possibilities, and know how to learn the concepts that they need 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 hear about it!
 

	
 
+ The Python community
 
+ Python fundamentals
 
+ Useful libraries and tools
 
+ Testing in Python
 
+ Deploying, operating, or scaling Python
 
+ Organization and communication skills for software development
 
+ What Python can learn from other communities
 
+ Unexpected places Python gets used (Embedded systems! Health science!)
 
+ ... and anything else we might not have thought of!
 

	
 
## Resources
 

	
 
The [Public Speaking](https://github.com/vmbrasseur/Public_Speaking) repository has collected 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.
 

	
 
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!
 

	
 
<!-- TODO schedule and contact info go here -->
 

	
 
## Submitting
 

	
 
To help us evaluate proposals and build our program, we would like as much detail as you can provide on your talk. At a minimum this should include: **a brief abstract (~500 characters) suitable for inclusion in a schedule page; a detailed prose summary (intended as the content for a talk detail page on the program site); and at least a rough outline of the structure including estimated timings for each section of your talk.**
 

	
 
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 — this is your chance to talk yourself up and explain why you're the best person in the world to bring us your amazing ideas, so take advantage of it!
 

	
 
Please click the invitingly large button below to submit a proposal.
 

	
 
<!-- TODO invitingly large button plz -->
 

	
 
## Feedback and mentorship
 

	
 
**First time speakers are welcomed and encouraged; if you've never done this before but have an idea please contact the program committee 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) 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!
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/selection-process.html
Show inline comments
 
new file 100644
 
{% 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 body_class %}selection-process{% endblock %}
 

	
 
{% block content %}
 
  {% markdown %}
 

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

	
 
  {% endmarkdown %}
 
{% endblock %}
pinaxcon/templates/static_pages/selection-process.md
Show inline comments
 
new file 100644
 
## 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: identify-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.
 
+ Racial demographics of the speaker lineup should ideally reflect US and Bay Area demographics within some margin of error.
...
 
\ No newline at end of file
pinaxcon/templates/static_pages/sponsors.html
Show inline comments
 
{% extends "site_base.html" %}
 
{% extends "page_with_title_and_lede.html" %}
 

	
 
{% load i18n %}
 

	
 
{% block head_title %}{% trans "Welcome" %}{% endblock %}
 
{% block head_title %}Call for Sponsors{% endblock %}
 

	
 
{% block body_class %}home{% endblock %}
 
{% block heading %}Call for Sponsors{% endblock %}
 

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

	
 
{% block content %}
 

	
 
{% endblock %}
pinaxcon/urls.py
Show inline comments
 
from django.conf import settings
 
from django.conf.urls import patterns, 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"^code-of-conduct$", TemplateView.as_view(template_name="static_pages/proposals.html"), name="code-of-conduct"),
 
    url(r"^about$", TemplateView.as_view(template_name="static_pages/proposals.html"), name="about"),
 
    url(r"^news$", TemplateView.as_view(template_name="static_pages/proposals.html"), name="news"),
 
    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"^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"^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/proposals.html"), name="sponsors"),
 
    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")),
 

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

	
 
    # Demo payment gateway and related features
 
    url(r"^register/pinaxcon/", include("pinaxcon.registrasion.urls")),
 

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

	
 
    # Required by registrasion
0 comments (0 inline, 0 general)