Geotagged Meeting Planner Iteration 1 Marking Guide

[10] Welcome Screen & Login
	[8] Welcome screen has at least 2 animations.
	[2] The welcome screen can be intuitively skipped.

[15] Display Live Events
	- Scrolling list of events
	- Each event shows the title, planned date, and duration
	- Clicking event advances to event details screen
	- Android back button exits application
	- An indicator on screen shows the location of the user.
	    This *should not* be a map.
	- From this screen, the user must also be able to create a new event.
	- The event list persists across executions.
	- The list is sorted by starting time (soonest first)

[20] Display Event Details
	- Aesthetically pleasing display of event information
	- All event details are available
	- Map shows the location of the event
	- Time remaining until the event is shown
	- Android back button returns to the display of live events

[20] Create New Local Event
	- Allow the user to create a new event with at least:
	    title, date, time, duration, location
	- User should be able to customize the location through a map
	- The default location should be user's current location.
	- Android back button returns to the diplay of live events

[5] Administrative
	- docs/tasks1.txt states who is the scrum master for this iteration.
	- docs/tasks1.txt lists development tasks required to implement use cases
	    and states who was assigned each task.
	- docs/git1.png (or .jpg) shows Git commit history.

General Requriements
[10] Well built UI
	- Well laid out screens.
	- Use of icons/images where possible
	- Looks good and scales well to different screen sizes
	- Runs well under Android 4.2 (API 17)
[10] Clean Code
	- Good class, method, variable names.
	- Perfectly formatted code.
	- Comments on all classes (not needed *inside* classes, just on the class level)
	- All strings that the end user may see on UI (not LogCat) are in strings.xml
[10] Git use
	- Working project pushed to GitLab
	- Good commit comments on most or (almost) all commits.