Saturday, March 16, 2013 @ 1:00 PM. Cafe Racer (5828 Roosevelt Way NE, Seattle, WA 98105) Meetup page
Notes from the meetup
localwiki_client ruby gem
Pushed version 0.2.0 of localwiki_client
june 1 hack day
what are the problems that people are having that can be worked on?
city robots
drones - patrolling data, where will the drones be deployed?
robot deployment data, where, how often, why
occupy protests
- where were arrests made
- past protest arrests data
bus route change notifier
- alerts when there are proposals, changes, and meetings where you can voice your concerns / questions / ideas
- weather, other route change alerts
city services directory
- what things aren’t online yet?
seattle parking api - where is it?
civic data hub:
subscribe to city events / info on a block by block basis:
http://www.seattle.gov/html/citizen/services.htm
notify me when this is relevant to me:
- abandoned automobiles
- lost pets
- alert when ballot is processed
- digest of crime / fire activity
- building proposals
- event permits
- road work
- seattlewiki updates
- yelp / urbanspoon updates
push notifications when they are relevant.
cards with relevant info.
show trends of crime / fire data by neighborhood
implementation:
linux / ubuntu / heroku
postgresql
rabbitmq
sinatra
plugins dir. submit plugin via pull request.
getting started:
mockup pages
talk about it with city of seattle, and other folks
develop crude prototype with one adapter, guide for creating new adapters
optional:
city of seattle neighborhood grant: http://www.seattle.gov/grants/
Technology Resources:
RabbitMQ: http://www.rabbitmq.com/
community calendars project: https://github.com/judell/elmcity
simple/old sample of sinatra and rabbitmq together.
data.seattle.gov
request a dataset - no responses
code for seattle:
what happened with the 2011 code for america year in seattle?
pursuing non profit status
approaches for working with city of seattle
- bidding on projects
- being completely autonomous
- ?
Meeting preparation
Meetup agenda!:
Totally flexible, but nice to have it all organized so we don't forget anything.
- Networking - 15 min
- Introductions - 5 min
- Presentation (prepared or ad-hoc) - 30 min
- Hack! - 60 min
-
Business items - 15 min
- Review and Improve Code for Seattle Projects
- Discuss Code for Seattle governance, etc
- Decide next meetup / meetup schedule
General news.
Updates on related work.
Events notification
Starting to plan the June 1 hack day. Notes here.
Project updates
Leads on projects to give status updates, lay our needs and support wanted, next steps and launch plans/dates.
-
4 UW continuing Ed students have been adding CRUD and history methods to the ruby gem localwiki_client
- That project wraps up several hours before the meetup, so contributions by anyone interested are encouraged.
- Step one could be to merge everything useful from the uwproject branch into master and release a new version of the gem.
New Project Consideration/Exploration:
- June 1 hack day
- Parks outreach – edit the wiki in a park day.
Management:
Matters pertaining to our operation, funding, decisions, directions, meeting structure.
Other Agenda Items:
Feel free to add any other matters here for discussion
Talk about what need to happen to create the business entity Code for Seattle, LLC.
Discuss what the requirements are for becoming a non-profit.
Cost for becoming non-profit.
Creating an advisory board.
Meeting location.