Fix miniconf fixture dates

Some proposalsections were still set to open immediately. Change that
to 1 Nov.

Finish adding models/forms/admin for new miniconfs

NB: all the proposal sections for the miniconfs here are set to open
on 2017-11-01. To make them available sooner, visit
/admin/symposion_proposals/proposalsection and change the start date.

(re)create miniconf proposals

This is a partial revert of 6d864e8ce56b8cbb53c90c620729238181c6c8ae
- plucking out the bits we want to re-use

Restore docs

These were removed in d95d66d but still seem slightly userful.

Re-format sitetree fixture in preparation for update

This is just a reformat with "python -m json.tool"

Python3 compatibility in timetable listing

itertools changed a little between py2 and py3

Enable multi-level site-tree

* Remove the outdated compiled javascript once again
* Update the sitetree_header template to use more detail.

The extra detail here is taken from the menu_bootstrap3.html template
distributed with django-sitetree

More transparent support for symposion-fixtures dir

symposion-fixtures being a really crappy name for a folder that has
some utility stuff for helping populate a site with dummy data

Set review-table class to get goodness on notification page

Flagging this as a review table means we get sorting, pagination, and
search. Much awesome, esp when we want to do this like "show me all
the ones that haven't been notified yet"

Merge speaker migrations

Two different changes have updated the speaker model; this creates a
migration that merges the changes.

Allow flags for migrations

Switch Dockerfile from CMD to ENTRYPOINT so that flags can be passed
to the makemigrations command

This is required in cases where we need to use django's makemigrations
--merge to merge two migrations.

Expand bulk_accept to generic bulk_update

Allows for bulk rejection/undecided/standby in addition to bulk accept.

Remove jquery.history.js reference

* This reference was added in the very distant past
* But jquery.history.js itself has never been in the repo
* pyconau-2017 team resolved the dilemma but dropping
jquery.history.js into the repo
* But as near as I can tell, this does nothing except in obsolete
older browsers. The fact that it's been broken ever since it was
"added" is highly suggestive of it never having ever been used or
needed
* So, trim the fat. It's possible that this might break an older
browser that needs the functionality jquery.history.js provides -
except that such a browser would *already* be broken because
jquery.history.js has never actually been around to be used.
* If we ever do need this functionality, we can revert this
change.. and then we'd have to drop in jquery.history.js. In that
circumstance,
https://github.com/pyconau2017/symposion/commit/34bc7c0 may be of interest.

Fix review buttons by removing stale compiled JS; also some styling

Essentially cognate with 0673e35 from the pyconau-2017 fork.

dj-gapc-storage fix for num_retries went upstream

Fix for an attribute error in this module has been merged upstream and
been released as 0.4.1

https://github.com/eldarion/django-gapc-storage/pull/17

restore extra_script

This fell out of the template at some point, but is needed for some
javascripty things to work.

Revert "Don't populate inventory"

This reverts commit 0d06fc08ebcb029f9003d7d3da4e400dc647d907.

Add devmode_settings.py for local dev

* Adds an env variable to .env to turn on dev mode
* Uses the inbuilt django auth rather than saml when in dev mode
* For laziness, re-uses the admin login form for the non-admin login

make_dev_container now comes up ready to be logged into by any
user. No non-admin users are preconfigured; but you can add one at
http://localhost:28000/admin/auth/user/add/, log out, and then hit
http://localhost:28000/ to log in as the new user.

make_dev_container

Expand on support for devs by scripting the process of creating,
starting, and initialising a dev container.

Take container name as an optional parameter

Create a dev docker container for makemigrations

* Adds a laptop-mode-env file which docker can read env variables from
* Adds a Dockerfile.makemigrations; mostly identical to the main
Dockerfile. Important difference: instead of the source being copied
into the docker image at build time, it's mounted from the local
machine at run time.
* Adds a makemigrations shell script which builds an imagine using the
Dockefile.makemigrations and then uses it to run makemigrations
* Because the source is mounted from the local machine, any new
migrations created are dumped in the developer's git checkout ready
for adding to git.

Rename .env -> docker/laptop-mode-env

Update testing fixtures to add admin users

This allows testing deployments to have accounts that can log in as
admin.

Make review changes atomic

This follows from investigations in
https://rt.lca2018.org/Ticket/Display.html?id=283&results=eac0bd3c49f782d054f87d6b160ca36b;
in short, it seems that because this very long and complex method
creates several different objects at differnt times, the DB has been
getting out of sync; there are more votes recorded then there are
reviews, becuase the table that stores the vote count is updated
before the table that stores the vote and review information

This change is intended to make this operation (and the other
operations that the revew_detail handler performs) atomic, to prevent
things getting further out of step. It does *not* fix the existing
incosistency.

review_delete has been atomicified as well as it likely needs the same
treatment, but this has not been examined in detail.

Return an integer for the slice index.

Resolves:

File "/app/symposion_app/vendor/symposion/reviews/views.py", line 230, in review_random_proposal
proposals = proposals[:(len(proposals) + 1) / 2]
TypeError: slice indices must be integers or None or have an __index__ method

Fix container name reference for deploy command

In the pod, the container is not called frontend

Correct some spelling in README

README had some typos, correct them.

Switch score calculation to pure Python

Rip out the score expression madness, and calculate the score in Python,
since I hear that Python is better at math than SQL is.

Fix score calculation hack

I have no idea why we do this in the database as some magic after we
call save(). I also have no idea why MySQL is seeming to think we want
type BIGINT UNSIGNED at the end of the
((2 * '+2' + '+1') - ( '-1' + 2 * '-2')) but it does.

Setting it to 2.0 or float(2) doesn't get the ORM to get this right, but
we are going to Decimal and making the 2 multiplier be of type Decimal
manages to make the ORM pull it's shit together and use something that
seems like we're okay with.

+1, -2 = 1 / 2 = -0.5 Score == True
Looks like it works.

UPDATE `symposion_reviews_proposalresult` SET `score` = CASE WHEN `symposion_reviews_proposalresult`.`vote_count` = 0 THEN '0' ELSE ((((2 * `symposion_reviews_proposalresult`.`plus_two`) + `symposion_reviews_proposalresult`.`plus_one`) - (`symposion_reviews_proposalresult`.`minus_one` + (2 * `symposion_reviews_proposalresult`.`minus_two`))) / (`symposion_reviews_proposalresult`.`vote_count` * 1)) END WHERE `symposion_reviews_proposalresult`.`id` = 1

Cleanup more user exploitable input with bleach

My eyes hurt. More user exploitable XSS on inputs.

Build an ephemeral dev container for rego testing

Create a ephemeral dev container to facilitate testing of
populate_inventory. It can be created, tweeked in the admin interface,
files updated in admin's populate_inventory, then redeployed to deal
with those changes.

A branch based one will need to be created to so we can do this work
without polluting the master branch.

Improve image update workflow

This improves the administrative workflow of deploying updated images to
the k8s cluster. Still tag latest however, as that's important to
old-workflow.

Would be good to block this and have it fail on a db migration so it
doesn't happen accidently, and make the deployer deal with it.

Fix miniconf editing - No attribute issue

Editing a miniconf, on save, the code looks in settings for
ADMIN_USERNAMES, and as it does not exist, we stack-trace and 502 to the
user.

Add the attribute to settings.py

Travel assistance to sydney please

* Tweaks help_text to indicate that travel assistance is to Sydney
* Includes the required migration

This migration doesn't change the DB so it's safe to apply with the system live.

Revert "Removes speaker assistance options from the profile form."

This reverts commit 2aa0074bdce1674696c9c28d23a3ff0a449a0454.

Order by ID rather than at last update time

The current ordering is based on what appears to be a random ordering
that happens to correlate to the last time the paper was submitted or
updated. Oldest to most recent.

This changes it to submission order so ordering doesn't change and ID is
a static, making it easier to move through a list of papers. "I last
looked at 24, so 25 is assured to be the next one I want to look at.

There's the thought of updated papers being looked at and voted on, but
it does not seem to me that this is supported or possible. In general
one would look at their un-reviewed list, and go off it, which puts
updates out the window.

We can certainly order on other fields if desired, but this one makes
the most since to me.

Add a note to get the permission required for papers review

So not obvious...

Remove default name from create_review_permssions

This was removed somewhere in 1.8, which means this results in a
failure. If I understand correctly, this "name" is now derived from the
model name's __str__ or something like that.

Change favicon to an LCA-appropriate favicon.

This isn't the same one we're using for the static site - but honestly I think this one is probably better.

Don't tab stop on Hack links in proposal creation

It's really annoying when you are adding a proposal and you hit tab and
end up on the link to the Hack website. There's no need for this and at
least on newer browsers we can pretty easily skip the links for tab.

Unfortunately because this is model text it generates migrations. As we
know these migrations don't actually do anything, so they are annoying
but not actually harmful.

Other suggested django migrations

So django keeps strict synchronization between its code and migrations
so that it can help generating new migrations. These are the additional
suggested migrations. A lot of these are a null effect, some are things
like transforming an unsigned integer to a signed integer. So not super
urgent on a small scale, but worth doing to keep django happy.

Add release materials check boxes to miniconf proposal

We need to have people who are submitting a miniconf proposal agree to
releasing the material. The easiest way to do this is to just make it a
proposal like the other two types. We don't have audience type for
miniconf, instead of deleting it just have a default - it's easier.

WARNING: This requires a real migration to be performed before use.

Use Linux Australia for release and not pycon

Update the recording and materials release to say Linux Australia, not
Pycon Australia. This generates a migration because the model text has
change - but also because in the 0001_initial migration it appears that
this help text is stored as a byte string.

This is a bit weird, but realistically running this migration is not
going to cause us any problems so just add it so we don't end up
fighting django along the way.

Add the T&C and COC to the accept box

Link to the T&C and Code of conducts so people know what they are
accepting. Create this as a static link because i don't know how django
would accept this being something dynamic on the model.

This annoyingly creates a migration, but it's not a real change and
easier to accept it now than fight django forever.

Specify python3 when creating a virtualenv in README

This app is now python3 only so we must specify python3 when creating a
virtualenv. Yes this assumes that most people are using python2 as
default, most distros still ship this way.

Collect Static so admin works

Thanks tchaypo and jammielennox

Closes #11

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.