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

Add the constraints file referenced in readme.

Install a newer pysaml2 than django-saml2 pins to.

Move secrets values to the top

Probably not the best way to do it, but it'll do.

We should add some logic to bail if certain values are unset.
Logic in settings, *gross*, I know.

Update the README

Attempting to reflect the current state.

Pycon seems to be using fixtures to setup the data that
populate_inventory does. Need to look into that.

Cleanup templates

Unused tags
Unused templates
Leftovers pinax-pages templates

Support Django 1.10

Few minor changes to support Django 1.10

Remove sponsorship for now

Simplify for CFP.

Sponsorship needs some thought.

Ask file provider for URL

Don't reason the URL from implmentation specific magic.

Cleanup pages for readability

This removes images, and giant headers, and makes the text - not white.
The next layer down in CSS is blue, so that's it for now.

This helps understand what's on the page visually, so this, at the
least, make testing easier for now.

Store user files in GCS - Ephemeral Disks

Issue #2

Bind in djangosaml2

Our authn is provided via shibboleth

Remove wagtail

This should eradicate wagtail from the project.

While wagtail may be nice, our goals are to keep all things public, and
having things locked behidn a DB is congruent to that plan.

All in all, the django project only leveraged a single wagtail feature,
"richtext" which has been hacikly removed and will result in bad display
of however it comes up. But this is on homepage.html, which will be
removed and covered up with a static website, which means we should be
able remove homepage entirely from this project.

This reduction hopefully makes the monolith easier to understand,
maintain, and wield.

Remove 500 patch. 1.7.0 upgrade.

While 1.7.0 exhibits a similar issue, we would need to re-verify and
re-patch this library with a new 1.7.0 monkeypatch.

This is ultimately only an annoyance. It only occours when we've
already 500'd, and this just means we get a second 500. As such it's
not critical.

Remove dj-user-accounts

That's a nice macro, but we don't need it.
dj-user-accounts stands in the way of using more generic AUTN_METHODS

Remove boxes

Boxes takes content directly from the DB and drops it into the django
templates. This is rather ugly and goes against keeping as much as we
can in static locations. As such, this is being dropped.

This seems to make it work. NFI

Works in prod mode, dies in dev with a warning/error

Doco seems to suggest that mixing these directories together is an
error as it means user uploads mingle with site files.

Use outbound mail provider for admin BCC

We can use our outbound provider to BCC any required administive
retention that is required.

Mass style-check update

Seems okay.

Kludge tox to run flake8

This hasn't been run in a loong time...

Config file cleanup

- remove a whole bunch of comments, they're useless

- Update TimeZone to Sydney

- Don't colocate MEDIA (user uploads), with STATIC in fact,
how is this set, Django has a safety check for this and bails.

- Do not store a default SECRET_KEY in git.
We'll set a random one by default, so things "just work"
It would also be acceptable to not set it and let DJ bail

- We dont want to log to a file. Our disks are ephemeral.

- We likely will not overlay a production settings.py over this one.
We need to implement something that is more container friendly in the
future. This will be env-vars or a config file.

Drop the wiki

Whatever wiki is used, will be run as a standalone application that is
not part of the primary application.

Closes #4

Revert "Switched to using posgresql for db."

Add MySQL deps

Support Django 1.10 with timezone upgrade

Needed as SubfieldBase is depricated

Use django's login_required decorator

This only seems to be here to have some custom login_url used bypassing
django's model. Well as we want to use django's model, this just won't
do. So lets move to using django's model.

django-sitetree >= 1.7.0 and not use version pin

In the future, when we want to lock a package to a specific version, we
will do that via a constraints file in the master project.

Making it difficult to update deps is not okay.

News pages working.

Sponsorship ... getting there.

Default content page and sponsor list is working, mostly.
TODO: get sponsor logos to show up instead of the names (text).