2014-05-13 Meeting Notes
Date
May 13, 2014
Attendees
Rebuen Binns
Dazza Greenwood
Mary Hodder
@Mark Lizar (Unlicensed)
Goals & Discussion
Consent Receipt - Draft Specifications
organise the GIT Hub with Ruben
moved consent receipt button into Open Notice Repository
Linked spec from Kantara website into the Open Notice Registry
Go Through Licensing
TBD - Defining the specification and Lexicon
Mary Discussion on Hackathon
Competition and prizes, should there
have a competition, with different categories: Data Control, Data Transparency, Civic Action
Talk with Dazza about summer schedule
Recognition
MIT Name Brand and SEO
Put it on a Learning Platform
Spotlight Portfolio page - MIT HUB
Requirement being that it is a real project, not abandoned, has merit on its own
Hackathon: Best way to use the data privacy,
Open the Tickets on June 12th, with an Online convening and start rounds of participation.
invite the other projects (from past hackathon) to participate in the next hackathon ..
Action: Email around the judging competition and criteria, include best of show format - startinging from rules on hackerleauge page already (for 1 week)
Action: Requirements on MIT HUB promoting finished projects (1 week)
Action: Overarching - End of October finish event.
Action: Sponsorship for the winners,
Action: Hacker Event Series High Level Strategy Email
Git Hub Licensing
Highlight each project and the people
choice is to move it forward, but the Open Notice GitHub can use this for Open Notice
Actions: arrange a meeting via email, to start the road map docuement, and the licsencing and the github org. with a draft high level of the hacker series
Forking GITHUB Policy - (TBR)
July - Winners get opportunity to get time with MIT Media Hub to develop project (with Mark & Mary) Project Makeover
October- Overall Winners from all competition get opportunity for winning a Mooc (Massive, Open Online Course) in October, sp
To be addressed:
- github sponsor
Winner pacakge to include: ? VC- Investors, Startup
Github accounts to projects as method of providing open independence for projects.