I joined Code for San Francisco Brigade- Civic Hack Night today. Since it was the first Civic Hack Night for 2014, the agenda was much structured than the regular hack nights :)
== Agenda ==
6:30 pm -- Intro to the SF Brigade, 2013 accomplishments, 2014 opportunities
6:45 pm -- Jay Nath, Mayor’s Chief Innovation Officer, San Francisco
7:15 pm -- Intro to Deep Dives
7:30 pm -- Deep Dives into topics such as leadership opportunities in the SF Brigade, project strategy, policy brainstorm, data discussion
8:30 pm -- Report out and next steps
9:00 pm -- Wrap
== Intro to the SF Brigade, 2013 accomplishments, 2014 opportunities ==
Hannah Young kicked off the meeting with her presentations explaining what the brigade program is, what they did in 2013, etc. I especially liked the fact that for each project, they need to have not just developers but also government person involved, so that we can make sure we are making the right thing. You can see the slides here:
== Jay Nath, Mayor’s Chief Innovation Officer, San Francisco ==
Jay explained about the work that his team does around open data etc.
James, Krista and Jake - who works for the city government as fellow or full-time - explained about their projects:
-Standardization of data
-ImproveSF which is a crowdsourcing platform
-Living Innovation Zone project on Market street
-Incorporating design thinking, design process to government / civic design camp
-SF local government is huge, and there are 28,000 employees in 60 departments
-Raise awareness of brigades
-There is no list of social services- need to create a yellow page for social services.
-Child care public services work with 200 nonprofits, more so with healthcare services.
-"Healthy San Francisco" project. How to make ACA and local healthcare useful to the SF citizens- creating a site as navigator, translator and calculator for Affordable Care Act.
-San Francisco Decoded By making San Francisco City laws, rules and regulations available on this website, there was a feedback from a citizen and this issue actually led to fixing the legislation.
-Visualizing metadata around law - SF Ordinances
== Deep Dives in breakout teams ==
The participants split to the following 3 teams, to discuss what we want to accomplish in Q1. I joined the data & policy team.
-Data & Policy
-Project strategy
-Outreach
== Data & Policy Team ==
1) We discussed what Open data means, examples, why we got interested in data/policy, what problems we want to resolve.
-Several people were interested in utilization of data to be prepared for natural disasters, others were interested in education, and some on politics.
-Economic value of data - "data is currency"
-Importance of making standards
-Opening government data and incorporating them to websites ex) Restaurant Health Scores used in Yelp, residential data used in Trulia
-Example from Japan: Fukushima nuclear power plant data
-Example from Nairobi: bus service data
-Example from Hawaii: Ohana API
2) We took a look at data.sfgov.org to check what data is available, what apps are already created in the Apps Showcase, and compared with what other cities have implemented.
-Case data for 311
-Apps Showcase
-There's only 1 app in politics showcase...
Maybe we should replicate what the Chicago team did with Chicago Lobbyists?
-DotMap - demographic data from 2010 census
== Outreach / community team ==
-Increase the diversity of participants
-Education
-Tell stories
-Run hackathon on effective topics such as safety, childcare
-Reach out to tech communities and nonprofits
-"Friends of brigade" "Bring your brigade friend day"
-Learn from other brigades, NY, Oakland are doing well
-Survey our group, talents, etc
== Project team ==
1) Existing projects
- Projects that San Francisco office is doing, brigades in the past did
2) Emerging projects
- Topics we don't know yet
- Housing is hot issue in San Francisco
- Communicate success stories
- Pets that need to be adopted
- Social services, food stamps
3) Redeployment and improvement of existing projects
==What should we fix?==
We need to do a better job making a system to know who's who within Code for San Francisco Brigade team.
- Learn from what code for philly is doing? They have website that gives visibility on what skills they have, what project they are working on, etc.
Code for Philly - A collaborative space for Philadelphia's civic developers -
Users' URL http://codeforphilly.org/
Developers' URL http://codeforphilly.org/develop
Apps for Philly - A living catalog of apps built for Philadelphians -
Users' URL http://appsforphilly.org/
Developers' URL http://appsforphilly.org/develop
==Pizza and Code for America Brigade cake==
==What's next?==
In case you are interested: the next Code for San Francisco Brigade- Civic Hack Night is going to be held on 1/22 (Wed)- sadly I can't join due to a business trip, but I'm sure it will be great.
Meetup: Weekly Civic Hack Night
==FYI on Brigades==
Brigade 101: How to Hack Night
Lessons from Brigade, Year One: Do This!
Brigade Spotlight: CHICAGO
How to Hack Night - Hangout
Disclaimer: The opinions expressed here are my own, and do not reflect those of my employer. -Fumi Yamazaki
== Agenda ==
6:30 pm -- Intro to the SF Brigade, 2013 accomplishments, 2014 opportunities
6:45 pm -- Jay Nath, Mayor’s Chief Innovation Officer, San Francisco
7:15 pm -- Intro to Deep Dives
7:30 pm -- Deep Dives into topics such as leadership opportunities in the SF Brigade, project strategy, policy brainstorm, data discussion
8:30 pm -- Report out and next steps
9:00 pm -- Wrap
== Intro to the SF Brigade, 2013 accomplishments, 2014 opportunities ==
Hannah Young kicked off the meeting with her presentations explaining what the brigade program is, what they did in 2013, etc. I especially liked the fact that for each project, they need to have not just developers but also government person involved, so that we can make sure we are making the right thing. You can see the slides here:
== Jay Nath, Mayor’s Chief Innovation Officer, San Francisco ==
Jay explained about the work that his team does around open data etc.
James, Krista and Jake - who works for the city government as fellow or full-time - explained about their projects:
-Standardization of data
-ImproveSF which is a crowdsourcing platform
-Living Innovation Zone project on Market street
-Incorporating design thinking, design process to government / civic design camp
-SF local government is huge, and there are 28,000 employees in 60 departments
-Raise awareness of brigades
-There is no list of social services- need to create a yellow page for social services.
-Child care public services work with 200 nonprofits, more so with healthcare services.
-"Healthy San Francisco" project. How to make ACA and local healthcare useful to the SF citizens- creating a site as navigator, translator and calculator for Affordable Care Act.
-San Francisco Decoded By making San Francisco City laws, rules and regulations available on this website, there was a feedback from a citizen and this issue actually led to fixing the legislation.
-Visualizing metadata around law - SF Ordinances
== Deep Dives in breakout teams ==
The participants split to the following 3 teams, to discuss what we want to accomplish in Q1. I joined the data & policy team.
-Data & Policy
-Project strategy
-Outreach
== Data & Policy Team ==
1) We discussed what Open data means, examples, why we got interested in data/policy, what problems we want to resolve.
-Several people were interested in utilization of data to be prepared for natural disasters, others were interested in education, and some on politics.
-Economic value of data - "data is currency"
-Importance of making standards
-Opening government data and incorporating them to websites ex) Restaurant Health Scores used in Yelp, residential data used in Trulia
-Example from Japan: Fukushima nuclear power plant data
-Example from Nairobi: bus service data
-Example from Hawaii: Ohana API
2) We took a look at data.sfgov.org to check what data is available, what apps are already created in the Apps Showcase, and compared with what other cities have implemented.
-Case data for 311
-Apps Showcase
-There's only 1 app in politics showcase...
Maybe we should replicate what the Chicago team did with Chicago Lobbyists?
-DotMap - demographic data from 2010 census
== Outreach / community team ==
-Increase the diversity of participants
-Education
-Tell stories
-Run hackathon on effective topics such as safety, childcare
-Reach out to tech communities and nonprofits
-"Friends of brigade" "Bring your brigade friend day"
-Learn from other brigades, NY, Oakland are doing well
-Survey our group, talents, etc
== Project team ==
1) Existing projects
- Projects that San Francisco office is doing, brigades in the past did
2) Emerging projects
- Topics we don't know yet
- Housing is hot issue in San Francisco
- Communicate success stories
- Pets that need to be adopted
- Social services, food stamps
3) Redeployment and improvement of existing projects
==What should we fix?==
We need to do a better job making a system to know who's who within Code for San Francisco Brigade team.
- Learn from what code for philly is doing? They have website that gives visibility on what skills they have, what project they are working on, etc.
Code for Philly - A collaborative space for Philadelphia's civic developers -
Users' URL http://codeforphilly.org/
Developers' URL http://codeforphilly.org/develop
Apps for Philly - A living catalog of apps built for Philadelphians -
Users' URL http://appsforphilly.org/
Developers' URL http://appsforphilly.org/develop
==Pizza and Code for America Brigade cake==
==What's next?==
In case you are interested: the next Code for San Francisco Brigade- Civic Hack Night is going to be held on 1/22 (Wed)- sadly I can't join due to a business trip, but I'm sure it will be great.
Meetup: Weekly Civic Hack Night
==FYI on Brigades==
Brigade 101: How to Hack Night
Lessons from Brigade, Year One: Do This!
Brigade Spotlight: CHICAGO
How to Hack Night - Hangout
Disclaimer: The opinions expressed here are my own, and do not reflect those of my employer. -Fumi Yamazaki
0 件のコメント:
コメントを投稿