Documentation Design Jam June 27 2015

Media Lab Saturday design session.

Talked through a basic chronological and functional overview of the "OnlineHackathon" system concept.

• Whiteboard Image Here
• Video Overview

Decided to have pretty full documentation going forward. (hence this page)

• Whiteboard from June 27, 2015 https://github.com/FirstToDisclose/OnlineHackathon/blob/gh-pages/documentation/images/june27.JPG

6/27

Recap:

• wefilm inspired underestandable example of community video production as datadriven large scale hackathon project sharktank inspired evaluation of idea, engagement (panel experts)

pitch: discovery mechanism

Meeting outline:

•development of hackerthon (life cycle of online hackathon) judging criteria: novelty, functionality, usability, value for intended users, sustainabilty •code from a shanghai coder (github to cards)

Hackathon Event Chronology

Individual Identity: start with a Github Account

Individual Online Hackathon Event Cycle: Hackathon -> Start (Q&A plenary session, e.g examples)-> proposed projects (youtube) (input and feedback)-> team formation -> Project Building -> Project Demo (input) -> Project Evaluation (feedback)-> End

Hackathon theme: (e.g.invent for the homeless) project: app Round 1: *PROPOSAL: Input: title -> captions (format to card) -> youtube or hangout live Feedback: questions & ideas -> Tagging (inexpensive, innovative, valuable,user-friendly) Round 2: TEAM FORMATION: “Vote with your choice” – Team formation -> Individual Preference Computational Team Assignment (algorithm) -> Individual Profile Info in a stats model (real-time)

Functional breakdown:

• Account (Identities & Authorization/consent) management of their own data
• Event
• Project (public display then becomes a gallery)
• Team
• Schedule
• Workspace (kickoff Hangouts)
• Decision Rounds
• session
• plenary session (beginning and ending general info)
• teamwork
• project deadlines (session duration)
• review
• Decision Making/ratings
• Tutorials
• Interview(narrative)/highlights

Goals:

• Trans-Event Project Gallery/links to it (allows tracking back, attribution and where it goes)
• 10,000 person meeting/project (collaborative filtering, real-time analytics)
• Results with #Deployed #Creative #New Value in tinytime (free, no time, massive participations vs. costly, long time, small group)
• Team Rich Collab
• real time analytics
• integrated personally
• Data-Rich
• PEOPEL/TEAMS
• PROJECTS

Information and Capabilities Contained in a Workspace:

• title/caption
• hangout button
• projectAssets (link)
• Team
• Schedule
• Issue/To do list

Template Example Tailored for Context (from zero to distributed)

e.g. video

• Treatment
• Tagging: rating on sev. criteria
• Clustering
• scale of the project
• scattered or focused
• team formation
• Project BluePrint
• feeback on several criteria
• Initial Production
• shoots - rated
• trailer - rated
• budget - rated
• Production (modula)
• assembly cut
• Final Product
• final cut
• trailer
• Distribution

Differentiations between OnlineHackathon and a Conventional Hackathon Generalized from Example Above

• Modular
• Preferences/Ratings Recommendation System(feedback + evaluation)
• Narrow template/guiderail results in new value

Notion of individual Identities (aka users)

• own identity they bring with them and the ability to managing of their own data data from taking advantage from the open data online: (Data Driven)

• integrate the data across different platforms , cocoon of individual media data, implement google material design “CARDS” guidelines to guide the consistency and cohesion of design (input of title/caption are capped to fit in cards design)

• using Hangouts for meeting
• using Twitters for voting
• using Github for Repo

Time-based Experience

users only experience in the concept of time (Github Global Public Timeline)

Big Things To Tackle:

Timeline Work Space Collaboration Data from Team (Team Behavior) Individuality as Identity and Authorization