Platforms (How Will People Consume The Information?)

Important Features

Challenges [responsible group in brackets]

Code 

Current (super preliminary code for Shame Engine is located on github http://github.com/philnelson/shameengine/tree/master).

-----Meegs' Misc. Notes from Meeting - 27.01.09

-  ChangeCamp - ShamenApp Mtg
-  Get product to market very fast - develop ASAP
-  Go after social funds - evolution of HoHoTo idea - create software, dvlped by community w/ funding to solve any problem
-  Wiki notes - Still viable? Gut check
-  System to allow tag via coordinate - Associate message w/ pin in space - Questions/Problems/Announcements
-  Range around pin - Scope/Scale
-  Big idea - Government aggregate all data into dashboards - trending w/ tag#s logged - becomes tiered issues - instant straw poll
-  Socially built software for community - roll it out in any country/place in the world - says alot about TO design community
-  Not affecting structure change - Aggregating problems so officials can rank them
-  Can database drive, too? - Easier for drive/forward/easier to send
-  Pull out w/in coordinates - Can use RSS to drive problem list w/in Ward - use GPS coordinate
-  GoogleMaps can send photo - Can expand/slice
-  140 character space per pin - Can you take offline to message board/discussion?
-  BrightKite's tag wall - each location has a spot w/ communication - PIN could have comments
-  Build in the adopt a highway - Have a company click on & sponsor the problem -
-  Build 1st to solve problems - 2nd version add event - wait for requests
-  User adoption -create base product - modify - user voice account/get satisfaction
-  Community TOol - adds layer of announcement/question
-  Problem/Announcement/Questions - Tabbed browsing - Make it embeddable into politicians site
-  Site 1st - App later -
-  Colour code the content - Announcements/Problems
-  Audiences/Stakeholders
-  Design challenge - not a programming challenge in adding this 2/3rd layer
-  UI/UX Challenge? - Simple stuff - Most complicated is adding later on - Tag a non-geographic problem
-  Define vector & then a PIN in the middle -
-  Who do we want to use? Under what circumstances? Focus on what scenarios will occur
-  UX challenges
-  List - Infrastructure/Roads; BlockSafety; CommunityNotices; CommunicationToPoliticians
-  Communication w/ Politicians - ShameEngine - 'codeword' - Intent & design of the system
-  Vocal minority of people who contribute to politics - Engage everybody in the community
-  Engage politicians to address a need - Aggregate problems - Benefit politicians - Engage Constituency Staffers/Local level
-  311 services/Staffer work/Build a system let the government pull tickets out
-  Dashboard - Multi-Audience - Capacity to track things - for anybody to use - a filter on top of sea of data
-  Social COmmunity Bugtracker
-  Tiers of dashboards - tease'n'sieze - business model -
-  Citizen Access & Professional Access - Build API for politicians or interface different from regular users
-  Similar to Tweetspace w/ #ashtag tracker - gives you a big feed -
-  Collect info generally; Use dashboard to create anything; Versionize dashboard for only good events; 5% users customize homepage if it is
-  Social aspect - trend data - Aggregation - Join/TakeOwnership of the problem
-  Use heatmap model - don't show flags - vs. - having running tally
-  DIGG style/HeatMap model - encourage people to contribute
-  Twitter-like community & development community - Easy for anyone to use it - Pluggable - Apps Add on Functionality
-  Massive wrap up - prototype - 180 people trying it out - MomPal - Sponsorship - Geolocation-level problems
-  Deploy - LabsChangeCamp.ca -

Adam's Meeting Notes - 2009.01.27 (organization to come - or please garden!)

    ▪    Communication with politicians
    ▪    Dashboard ala Tweetdeck to track issues - bring up panels to track specific tags, etc.
    ▪    Objects - vote up, join, subscribe, enroll
    ▪    Collect all instances of an issue vs. collect all issues anonymously to generate a heatmap?

    ⁃    Anonymous issue reporting does not connect citizens together.

    ▪    Touch, smell, hear, see your problem? It's probably municipal.
    ▪    Multilingual support

    ⁃    Automatic translation supported by ScribbleLive

    ▪    What do you want this tool to do?

    ⁃    Lower the communication barrier between politicians and public
    ⁃    Voice problems, show result
    ⁃    Hyperlocal community interaction
    ⁃    Act as a visualization tool for citizens to record, view, monitor and react to community issues = government accountability
    ⁃    Turn my civic/community ideas, events and concepts into ACTION
    ⁃    Create the rural community interaction in suburban/urban areas between government and citizens
    ⁃    BUG TRACKER (and social connection)
    ⁃    Enable citizens to easily and effectively engage each other and politicians about issues they care about.
    ⁃    Usable interface from people to officials
    ⁃    Engage people in their community
    ⁃    Help me make my place better
    ⁃    To connect with other citizens around specific, solvable problems that our politicians can review and solve
    ⁃    Be useful
    ⁃    Get people talking with their community

    ▪    Meeg: "I don't want to do climate change."
    ▪    Building a prototype to tag issues geographically

    ▪    Steps:

    ⁃    1) Identify the problem

    ⁃    Awareness
    ⁃    To action
    ⁃    To solve

Adam's Rough Sketches from meeting (2009.01.27)

(Taken with iSight - sorry for the crappy quality and blueness)