GitLab

- Allows you to send whatever text you want to clients
- Responsibility on admins once again

Closes #63

- It's a URLField
- Depends on trusting the admins not to insert dirty images to be sent to clients
- pls

Closes #37

- specify as abbreviation

Closes #62

- by default, remove all schedules
- but of you click this button then this behavior will not happen

Closes #68

- by default, remove all schedules
- but of you click this button then this behavior will not happen

- in some silly scenarios, a schedule may come into effect on a date at a certain time
- this allows that to happen

Closes #70

- It's a boolean that if set True, will always return that the Facility is open.

- ?all_alerts to request all alerts
- is_active function checks if the current Alert is active

- each Location must lie within a campus_region, or, an area that is within
the nearest vicinity to a GMU campus

Closes #55

- define FILTER_FIELDS that lists all model fields that are available to
filter on

- plus field rename
- plus docs!
- plus another package

- there's no scenario where anyone wants to deal with schedules
that have expired

- (x,y) point where the Facility is located
- Pretty map added to admin interface

- named product_tags so that it can scale to non food related places
- ie. whatever the facility produces to the consumer can be tagged as
such

Closes #40

- using some great libs
- it just works
- needs docs

- oops forgot to remove this one

Closes #36

- optional, enforced with RegexValidator

- get the list of alerts
	- todo: remove alerts that have expired or
		are no longer in effect

- plus a correction in Alert model doc

- An alert is a message we display to clients in case of some event
- start/stop date and time
- message
- urgency tag for colorization purposes

- did not seperate third part from Django

- require a category for every facility

- also settings/ added
- also renamed whats_open to whats-open to be consistant with repo name
- updated docker and CI accordingly

- starting the commenting process
- cleanup = removing stuff that doesn't actually do anything

- some things that were bugging me that I think can be agreed
upon as overall good

- fields moved over to the new model
- ForeignKey connection from Facility to Location
- also commenting all the things, slowly
Signed-off-by: David Haynes <dhaynes3@gmu.edu>

- each Facility _may_ have a building it is located in
which _may_ have an address
- allow someone to query for that Facility address
- allow someone on the admin page to input a Facility address

Closes #38

Signed-off-by: David Haynes <dhaynes3@gmu.edu>

- deprecation fix
Signed-off-by: David Haynes <dhaynes3@gmu.edu>

- If the file is run in py2, it should still function if using certain
py3 functionality (unicode, division, imports, etc)
Signed-off-by: David Haynes <dhaynes3@gmu.edu>

added help text to the special schedules attribute-- "This schedule will come into effect only for its specified duration."

- Update requirements packages
- Fix colliding field names
    - You cannot have a foreign key field name be the same as the
      model's name that it is referencing