Hackathon Five: Prep for the Gov!

The Hacks

• This will be a great run for the big hackathon that we are working on for next November time frame!

Why this would be useful

• Learn about parts of the codebase that we rarely touch
• Work with people we don't get to normally
• Want to get something done outside of the sprint
• Brainstorming and prototyping new features

The Schedule

1. Oct 10, 2013: hack
2. Oct 11, 2013: demo (3:30-5pm) (Google Hangout)

The Proposed Hacks

Advocate	Description	Interested Parties
Will	pip wheel: let's speed up virtualenv creation and stop the scipy recompilation madness!	DB
DHM	Restful CRUD for courses, xblocks, and definitions
DHM	Enable use by configuration of pymongo v Google DataStore
DHM	Prototype governance by domain for org, dept, course ids
Dave O	Alternative student courseware state storage, configurable on a per-course basis
Feanil	Break apart configuration cloudformation template by service and combine them programmatically
Marco	Google Hangout prototype feedback and discussion sessions, to be scheduled during hackathon twice for each of the following topics - discussion forums, lms redesign (content/navigation), visual analytics for instructors, learner profiles, SPOC experience, synchronous online group activities, (list can be adjusted)
Will	In-memory ModuleStore ==> fast tests
Adam	Add an app enabling students to take notes on what they're learning as they learn
Feanil	Replace the edx-platform vagrant environment with one that more closely matches production.	Will
James	Rewrite scripts for pull request aging and contributor list / AUTHORS file checking, and partially automate checking of whether contributor agreements signed
Cale	Per-hunk drag-and-drop interactive rebase (aka Patch Juggler)	Cale
Cale	Use Docker (or some other container solution) to run more tests per aws instance (while maintaining isolation)
JZ	Remove all Pearson code from the codebase
JZ	Architect and implement thorough tests of the import/export feature of Studio