Fix static content serving

What? Why did this stop working?

Specify how to create a superuser account in dev

To do development you will need a local super user account. This is
a standard Django practice but should be documented here as well.

Add fixture data to the README

The site requires you to have some basic data installed in your database
before running. This is located in the fixtures file and so the README
should tell people to install this data.

Remove sponsor fixtures

The sponsor fixtures don't work with our current site. Remove them to
make loading easier.

Add a dev-env.sh script you can source in dev

In dev we need some environment variables set to allow us to at least
test the site. Add a file we can source to get past this step.

Display failure messages when environment variables missing

Running migrate initially as specified from README leads to a cryptic
"CONFIG ERROR" failure message. Print out what variables are actually
missing.

Add our vendor path to our path

I guess this is as good a method as any to get or vendored packages in.

Taking one out of PyCon's (US) book

We're lock-step with symposion, and upstream is dead.
Vendor it.

Use a standard login handler

Is there any reason to not use the standard login decorator?

Link to GCP storage for files

WARNING: We need to reflect in the webpage that these won't be behind a
login.

GitLab Issue #2

require django-bootstrap-forms

While pinax-theme-bootstrap pulls this in, we use this directly too, so
we need to put this into our top level reqs too.

Support monospace TextFields instead of Markdown

Drop markdown for monospace

With markdown, we're only allowing about 1/10 of what is possible.
This creates a false reality and expectation. Lets not suggest this.
Nor do we have in-editor preview. So the user has to save, look at it,
then go back and edit. And seeing a bunch of sanitized HTML or just
missing sections isn't firendly.

Monospace, what you type, is what you're going to get. It gives the
presenter enough power to build a readable abstract, but not so much
that they can break the page and it's CSS, nor the ability to confuse
onselve through not getting what you expect.

We keep bleach sanitation and we should probably run linkify on this in
the long term. (Turn links into clickable links)

Use monospace font, hack, and not markdown.

Font should be made local and not remote loaded.

Use app.css not inlined css

Simpler for us.

Remove unused "hooks"

This isn't used, drop it.

settings - DEBUG hardening

DEBUG is something that should never be turned in on prod. As such,
lets be extremely specific on what we expect to process.

As we'll be taking this in from the environment, it's ensured we will
get a string. So we'll always get and only handle this in string
form. If it's anything else, it's an operational error and we bail.

(Note: bool('0') is truthy, so we make sure we leverge our string -> int
-> bool every time, so corectness can be noticed if it is not)

settings saml2_contact type is wrong.

We had List[Dict[str, str]], but this was passed without question from
djangosaml2 to pysaml2 no questions asked, which expects Dict[str, str].

Lets try to automate this build a bit

This doesn't rebuild on subproject changes... this is something that
will need fixed.

Add initial Dockerfile

This builds a working docker image for the application.
This is only an initial revision. It needs testing. MySQL, PIL, etc.

Was going to use Alpine, however, python3.6 segfaulted on docker
starting up, and I couldn't find the core files...

Add a CSS class on required fields labels

This makes it possible to add a ' *' required notifier to labels without
needing a bunch of custom form code in templates.

Py2 compatability has been broke elsewhere drop it

This is all noop in Py3, and Py2 is broke now in various places.
Dropping Py2 code as it will not be a thing going forward.

Django 2 is the next release, Py2 support will be dropped, as such,
dropping this is forward looking.

Sanitize user input on markdown fields

This is an XSS vulnribilitiy.

This also blocks a number of MD attributes that a user might attempt to
use.

The following are the allowed attributes.

['a', 'abbr', 'acronym', 'b', 'blockquote', 'code', 'em', 'i', 'li',
'ol', 'p', 'pre', 'strong', 'ul']

I belive this to be acceptable, as honeslty, a speaker using H1 is going
to stomp all over the page and make it harder for the reviewer to parse.

UX wise, it's less than great. A user can do # title and be left with
<h1> in the sanitized output.

Use full imports not .

And tox to py3.6

Remove excess CSS and fonts

print wont work for us now. Will need to be recreated.

Fonts, I don't even know where they came from, so I can't keep them

_styles.html is not loaded anywhere

Not in use, remove it.

Hym, might be able to remove this CSS now too.

Convert to bootstrap tab configuration

This was broken due to being something not bootstrap for tabs.

Convert to tab layout, just like reviewers page already is.

This script isn't loaded - remove it

This isn't loaded, doesn't seem to be for 2017 or PyCon, so I'll chuck
it.

We don't run modernizer.js

Remove the "no-js" class, that could be expected to change to "js" if
one doesn't know we don't have javascript that does that running.

We don't maintain this manifest, drop it

We don't use this currently. Removal.

While we'll likely put gulp or like back in, drop it

This was put in place a long while ago and lacks the usage documentaiton
for use with this repo. For now, I will remove it from the repo.

We obviously need to bring this or something similar back. But there's
no reason to keep this when it is not being used.

Remove metron

Not used - old/depricated name

Asset cleanup

Remove in-app stale resources and their branching of different cons.
Remove dist and move everyting into static/src.
Remove unused stale resouces such as less and hbs, etc.

Remove AceEditor

I cannot find the benifit to this over the base editor.

Tabs work, but that's pretty minimal. And tabs don't work on GitLab or
GitHub, so I don't feel not having that is substantual to functionality.

Add ' *' required markers back

The bootstrap renderer did not do anything to signify required rows. We
can do this by adding a class for CSS to work on, and add this field in
a more simplified manner.

label-required == append ' *'

Simplify django form rendering

Remove my hack to get bootstrap forms.

Remove the insane render-row-at-a-time forms that then only render
default django forms.

Disable SAML debug

We don't need this and it prints a lot of information.

Environtment the settings

And finally, dev settings converge with commited settings.

Signal rejections and standby talks.

Go green for Accepted

Go Red for Rejected

Go yellow for Standby

Add a CSS class on required fields labels

This makes it possible to add a ' *' required notifier to labels without
needing a bunch of custom form code in templates.

Add a CSS class on required fields labels

This makes it possible to add a ' *' required notifier to labels without
needing a bunch of custom form code in templates.

Remove unicode(), we're all unicode

Py3

Remove state select box

I'm not against putting this back, however, it doesn't work quite as one
would expect, so I'm removing it as its functionality is more confusing
that working.

Is this really the best way to address this?

If you unselect AU, then it never comes back. It leaves its value in
the textbox pre-filled if it ever got a value, leaving the field
pre-filled with an Aus state even if the person is New Zealand.

Most of our attendees are from but a few countries, we should make these
equal effort to fill in.

Use a selectbox for of_legal_age

To me, this registeres to a user as a required field better than a
radio-button.

As well, we now signal it as "required = True"

NotImplmented refund

We don't actually do it. Ban it for now.

Test fixes

There are a number of attempts to use Deci in ints, which won't work in
2.7 or 3.x, we fix that.

Description doesn't exist in symposion. So that fails our tests pretty
hard. Switch that to Private Abstract. It's clear these tests have not
been run in a very long time. So both failures and especially passes
need to be taken with salt.

ve is scoped to the except block.

We probably want to see a whole bunch of errors collected in errors
anyways. That should get converted to a string uppon being raised, so
pass errors directly.

Flake8 Fixes

Mostly whitespace fixes
Some unicode fixes
Fixed up CSV writer. str is not bytes and all.

Remove print statements.

I was originally going to switch to print function, but frankly I can't
see any reason to keep these. I don't know what data it's leaking into
the logs, but it certainly doesn't seem useful

StringIO is not in Py3. And it's not used at all, so removing that
import. Seems to work with Py3 now. More testing is required.

Bootstrapification

Boot custom CSS, and put some base, standard css in its place.
Shame I did not start with fresh Bootstrap4, but oh well.

Some more templates could be made to make this less messy, which would
be good.

DJ 1.11 support has improved upstream

We can now force to released versions with 1.11 support.

Cleanout conf-specific proposals.

We don't have these mini-confs (yet).
We don't want these files.
We're not going to rename the release in 0010 and drop all the extra
tables in 0011, we're going to toss them on the cutting room floor and
call it good.

They're in git, we can look at this commit and past ones on how to
recreate these for new proposal additions going forward.

move templates out of vendor specific locations

Lets not kid ourselves. The whole apps templates are client specific.
Lets just remove that and not think it isn't.

Bootstrapification: SiteTree Nav Bar

Make sitetree a bootstrap navbar.

Remove mobile menu, bootstrap provides this.

Update bootstrap blobs

Todo: Install these via npm, these should not be checked in.

Remove DJDT template view

This causes template rendering to blow out of proportion on certain
views. I don't care enough about this feature to spend time fixing it.
It has not provided me any value to this point.

One such view is ^/tickets/profile$ however there are others where I saw
this, yet do not remember which ones they were.

Switch to LCA2017 templates

This fixes proposal details.

Update requirements for Django 1.11

This has long enough support to reach post conf + a fair bit.

Price is not a relation and cannot select_related

This field is ignored in 1.9, however in 1.10+ it is an error.
As this is a no-op in 1.9, removal keeps functionality while
extending compatability going forward.

For full details please see Django Ticket 10414 at:
https://code.djangoproject.com/ticket/10414

If user does not exist, catch exception

User = None