working materials are made available online for anyone to fork, modify, discuss, and contribute to. ηЄϤЀϊЄφ΄߽;΅ ᔰ͢ηЀ϶αЀͽل樄ͫͼ͚Ά̵ 抑ͽΘᔰΨπϡЄ̵䄜ๅ̵πϬϲϘξЄτϴЀΨͭ͢Ο̵ 揙ሠڊΡوݶ֢䮣΄ᘍ͞ොͽ͘Ρ
disaster response and recovery 傑ਸ਼Ύ΄䌏䖕ɾ䕸岉΄͵Ηڥአ ‣ Developed by NGA (US GSI) ίϮϷθࢵਹࣈቖᑮ樌ఘ䁭ੴ͢樄咲 ‣ Contributed to by 18F (“startup” within US GSA) (昧ᮏ抠晄ੴٖ΄̿φόЄϕίϐϤ̀)͢揙ሠ ‣ Used by FEMA (federal) and Huntsville, AL (local)/FEMA (ίϮϷθݳ悡ࢵ昧ᮏ姴Ԫ䙪ᓕቘ䓆);ί϶ϝϫɾϜЀϑϠϸ૱͢ၚአ
‣ Uses data from Digital Analytics Program (government-wide shared analytics platform built on Google Analytics) ϔυόϸړຉϤϺν϶ϭ(Google AnalyticsӤ֢౮ͫͼ͚Ρق֛ͽوํͫͼ ͚ΡίϗϷϓΰμφϤ϶ϐϕϢζЄϭ)΄ϔЄόΨڥአ ‣ Shows real-time data of government website usage, bulk download available for developers 樛昧γδϣςαϕ΄ڥአᇫ丆ϔЄόΨϷίϸόαϭͽᤒᐏ̵樄咲ᘏݻͧӞೡύ γЀϺЄϖΘ׀ ‣ Grounded IT investment discussions in data-driven decision-making ϔЄόΨزͭ͵ITಭ揾΄䷥ਧΨݢᚆͭ͵ ‣ Used by the city of Philadelphia with minimal IT investment ๋ੜ΄ITಭ揾΄ΕͽϢΰ϶ϔϸϢΰί૱͢ڥአ
research lab) ίϮϷθࢵᒈٚኞݢᚆεϚϸλЄᎸᑪಅ͢樄咲 ‣ Sits in front of new and legacy systems to provide API keys, caching, rate limiting, and analytics ෛ憒;ϹιτЄτφϓϭ΄οЄϕγδα;ͭͼ̵APIκЄ̵κϰϐτϲ̵ί μψφګக;ίϗϷϓΰμφ;׀ ‣ Provided as a free, shared service by api.data.gov api.data.govΞͼϢϷЄͽوํͫ͵ςЄϠφ;ͭͼ׀ͫͼ͚Ρ ‣ Allows agencies to more easily execute the encasement strategy ݱ䓆岍ΞΡencasement strategy΄䋚ᤈΨΞΠ㲖ჶᤈ͞ΡΞͭ͜ͼ͚Ρ
entirely in the open 樄咲΅قͼηЄϤЀͽᤈΥ͵ ‣ Users commented on mock ups and initial code ӞᛱϳЄσЄ΅ϯϐμίϐϤ;ز΄πЄϖ䌏ͭͼΘπϮЀϕͭ͵ ‣ Launched with 150+ open issues 150զӤ΄๚ᥴ䷥ατϲЄ͘͢͵ᇫ䙪ͽ晁አ樄ত ‣ More development post-launch than pre-launch 晁አ樄ত΄ො͢樄咲͢ᤈΥͼ͚Ρ
ϼτЀϕЀDC΄ဩ΅ګᴴ͢ग़͚϶αψЀφΨֵͼϦЀύЄ΄γδϣςαϕͽل樄 ͫͼ͚͵ ‣ Civic hackers encouraged district government to release machine-readable version of the laws τϠϐμϜϐθЄ͢ϼτЀϕЀDC΄ဩΨπЀϡϲЄό͢㳌ቘڊΡ୵ୗͽل 樄ͯΡΞ͜㰕ͣͧ͡͵ ‣ Civic hackers created multiple open-source interfaces τϠϐμϜϐθЄ΅愢හ΄ηЄϤЀϊЄφ΄αЀόЄϢδαφΨ樄咲ͭ͵ ‣ Code is now searchable, accessible, mobile-friendly, and linkable 匍ࣁπЄϖ΅䭥ᔱ͢ͽ̵ͣಋ΄ͥ;ͩΣ͘Π̵ϯϝαϸ䌏䖕Θͭͼ͚ͼ̵ϷЀμΘ ͫͼ͚Ρ
shots ϧЀτϸϝϘίϢΰ϶ϔϸϢΰί૱΅αЀϢϸεЀσ΄Ԩᴠള圵Ψݑͧ ΟΡ䁰ಅΨل樄ͭ͵͡͵ ‣ Realized the problem was not specific to Pennsylvania ϧЀτϸϝϘίզक़ͽΘݶͮ抓氂͢ਂࣁͯΡͩ;䶲՞͚͵ ‣ Created an open standard to publish flu shot information αЀϢϸεЀσԨᴠള圵΄ఘ䁭ل樄΄͵Η΄ηЄϤЀφόЀύЄϖΨ樄咲 ‣ Chicago and San Francisco adopted the same standard τθρ૱;ςЀϢ϶Ѐτφπ૱͢ݶͮφόЀύЄϖΨ䟖አ ‣ Entrepreneurs can build against the standard, new cities can join ᩸䮣ਹ΅ͩ΄φόЀύЄϖΨڥአͽͣΡ̵ͭͿ΄᮷૱ͽΘ݇ے͢ڊΡ
reports, etc.) ဩΚϹϪЄϕΨތΖقͼ΄ίϮϷθ΄ڊᇇᇔ͢ڊᇇͫΡොဩ ‣ US GPO placed no code in the repository ݳ悡ࢵܦڬੴ΅ӞڔϊϢϕγδίπЄϖΨϹϪυϕϷͽᓕቘͭͼ̶͚͚ ‣ Publishing technical documentation where developers already are 樄咲ᘏ͢෬ᵞΔͼ͚Ρ䁰ಅದ悬ጱ揾ාΨل樄ͭ͵̶ ‣ Forum for developers to provide feedback, discuss issues 樄咲ᘏ͢ϢΰЄϖϝϐμΨ׀ͭ͵Π̵抓氂Ψ捍抷ͯΡ͵Η΄䁰ಅ ͼ͚Ρ̶ ‣ Established a community around the website γδϣςαϕΨӾஞπϬϲϘϓΰΨ戔ᒈͭ͵̶
Created by ~15 private sector vendors for use by cities ᛔလ֛͢ڥአڊΡΞ͜ʙ15΄࿆樌ψμόЄ΄ϦЀύЄ֢͢౮ ‣ Implemented within the software cities use to manage permits — no change to civil servants workflow or tools ෬ᛔလ֛͢战ݢ戣ΨᓕቘͯΡ͵Η΄ϊϢϕγδί䌏䖕ͯΡΞ͜樄咲ͫ͵-ᛔလ֛΄实㹓 ΅ϼЄμϢϺЄΚϑЄϸΨ䄜ๅͯΡᥝ΅僻͡͵ ‣ Shared standard is seen as a feature that prevents vendor lock-in وํͫ͵憒໒΅ϦЀύЄΞΡϺϐμαЀΨᴥྊڊΔͯ ‣ Civic entrepreneurs can more easily build apps to consume the data across multiple cities τϠϐμ᩸䮣ਹ΅愢හ΄ᛔလ֛ΨΔ͵͢ΡϔЄόΨၚአͯΡίϤϷΨΞΠ墋㶨樄咲ڊΡ
36 inspectors τθρ૱΅15,000զӤ΄汯ᷣମ͘͢Ρ̵͢䭥䪨ਥ΅36ՈͶͧ ‣ Created model using predictors of critical violations (crime, property value, etc.) ᯿य़晅ݍ΄Ԩ介ϯϔϸ(ᇨᗜ̵ࣈ㭅ᒵΨၚአͭͼ)Ψ֢౮ ‣ Made data available to the public, open source the model ϔЄόΨӞᛱل樄̵ϯϔϸΨηЄϤЀϊЄφ۸ ‣ ~15% increase in likelihood to find critical violations, found violations 1 week earlier on average ᯿य़晅ݍΨ咲憎ͯΡݢᚆ͢~15%ݻӤ̵ଘ࣐ͭͼՔΔͽΞΠ1昱樌ͥ晅ݍΨ咲憎 ‣ https://chicago.github.io/food-inspections-evaluation/
White House drafted guidance for agencies to implement the policy ϨϼαϕϜγφ΅ݱ䓆岍͢ϪϷτЄΨ䋚ෞͯΡ͵Η΄ιαϖ϶αЀ΄កໜ Ψ֢౮ ‣ Living, collaborative document; anyone in the world can contribute ӮኴӾ΄抑ͽΘ揙ሠ͢ڊΡϖκϲϮЀϕ ‣ US Congressman submitted pull request, White House accepted ίϮϷθ΄ӥᴺ捍㹓͢ϤϸϷμεφϕҁץྋໜ҂Ψໜ̵ϨϼαϕϜγ φ͢ݑͧف͵ ‣ Feedback was finalized and policy was signed into law ϢΰЄϖϝϐμ΅ݍฉͫͼ̵ͩ΄ϪϷτЄ΅ဩ۸ͫ͵
question: “what features would you love to see?” ‣ Flesh out documentation, note where documentation is lacking ‣ Community evangelism, speak, teach, and spread your love for the project ‣ Submit new questions to the project’s Q&A forums, or take a stab at an answer ‣ Host a genius bar at the next local meetup ‣ Translate the project into a different language ‣ Give feedback on proposed bug fixes and features, propose new ones ‣ Recruit new developers Opportunities to contribute
feedback or discuss features; minimize and memorialize meatspace discussions)ҁατϲЄϕ϶ϐθЄΨӞ۸̵ϢΰЄϖϝϐμΚϢΰЄώϰЄ΄ϔΰ φθϐτϴЀͯΡොဩΨӞ۸̵ηϢ϶αЀ΄տ扖Ψ๋ੜ۸ͭͺͺͰϺνΨݐΡ҂ ‣ Day-to-day(෭̸) (The project’s status, how to submit an issue/feature request or contribute a fix/enhancement) (ϤϺ υδμϕ΄昲䞨ᇫ丆̵ατϲЄɾϢΰЄώϰЄϷμεφϕ΄ڊොဩ̵ද࠺ɾ䱛ᚆ䝭䔴Ψ׀ ͯΡොဩ) ‣ Long-term(槱๗ጱ) (Project mission statement, philosophy, and goal, features and requirements list, project roadmap)(ϤϺ υδμϕ΄ϬϐτϴЀɾφϓЄϕϮЀϕ̵ϢΰϺϊϢΰЄ̵ፓ䰤̵䱛ᚆϷφϕ̵ϤϺυδμϕ ΄懯ኮ)
the easy part 2. Start small, go through the motions 3. Minimize information imbalance 4. Embrace the constraints of open source 5. Open source problems, not solutions 6. Expand your definition of stakeholders 7. Be the hub, encourage spokes 8. Minimize friction 9. Decentralize governance 10. Encourage contributors Internal collaboration External engagement
benbalter
fujiwara3
chiroito
a1a
rrreeeyyy
furuhashilab
nari_ex
mmochi23
tomoyakitaura
tcnksm
uhyo
chack411
oracle4engineer
marcduiker
trallard
aarron
hatefulcrawdad
morganepeng
vanstee
ufuk
kneath
mclloyd
jacobian
caitiem20
paulrobertlloyd
