2012 chicago fellowship presentation to code for japan

53
Rob Brackett 2012 Code for America Fellow, Chicago [ ブラケット・ロブ ]

Upload: mr0grog

Post on 26-Jun-2015

420 views

Category:

Internet


0 download

DESCRIPTION

Presented a summary of my 2012 Code for America fellowship experience at a Code for Japan meetup.

TRANSCRIPT

Page 1: 2012 Chicago Fellowship Presentation to Code for Japan

Rob Brackett

2012 Code for America Fellow, Chicago

[ブラケット・ロブ]

Page 2: 2012 Chicago Fellowship Presentation to Code for Japan
Page 3: 2012 Chicago Fellowship Presentation to Code for Japan
Page 4: 2012 Chicago Fellowship Presentation to Code for Japan
Page 5: 2012 Chicago Fellowship Presentation to Code for Japan
Page 6: 2012 Chicago Fellowship Presentation to Code for Japan
Page 7: 2012 Chicago Fellowship Presentation to Code for Japan
Page 8: 2012 Chicago Fellowship Presentation to Code for Japan
Page 9: 2012 Chicago Fellowship Presentation to Code for Japan
Page 10: 2012 Chicago Fellowship Presentation to Code for Japan

😱

Page 11: 2012 Chicago Fellowship Presentation to Code for Japan
Page 12: 2012 Chicago Fellowship Presentation to Code for Japan

😱

Page 13: 2012 Chicago Fellowship Presentation to Code for Japan
Page 14: 2012 Chicago Fellowship Presentation to Code for Japan
Page 15: 2012 Chicago Fellowship Presentation to Code for Japan

😱

Page 16: 2012 Chicago Fellowship Presentation to Code for Japan
Page 17: 2012 Chicago Fellowship Presentation to Code for Japan
Page 18: 2012 Chicago Fellowship Presentation to Code for Japan
Page 19: 2012 Chicago Fellowship Presentation to Code for Japan

The spec has problems.• Unclear what things are optional (in reality: everything)

• Lots of room for different cities/implementations to work differently

• Open311 is about customer service; the city is focused on operations

• Date problems — formatting, time zones

• No paging

• No searching

• No provision for how to show extra/custom data

• No way to show detailed progress

• No way to handle “follow-ons”

Page 20: 2012 Chicago Fellowship Presentation to Code for Japan

The spec has problems.• Unclear what things are optional (in reality: everything)

• Lots of room for different cities/implementations to work differently

• Open311 is about customer service; the city is focused on operations

• Date problems — formatting, time zones

• No paging

• No searching

• No provision for how to show extra/custom data

• No way to show detailed progress

• No way to handle “follow-ons”

Page 21: 2012 Chicago Fellowship Presentation to Code for Japan
Page 22: 2012 Chicago Fellowship Presentation to Code for Japan
Page 23: 2012 Chicago Fellowship Presentation to Code for Japan
Page 24: 2012 Chicago Fellowship Presentation to Code for Japan

Track your explorations.http://blog.apps.npr.org/2014/09/02/reusable-data-

processing.html

Page 25: 2012 Chicago Fellowship Presentation to Code for Japan
Page 26: 2012 Chicago Fellowship Presentation to Code for Japan
Page 27: 2012 Chicago Fellowship Presentation to Code for Japan
Page 28: 2012 Chicago Fellowship Presentation to Code for Japan

Have a use case.

Page 29: 2012 Chicago Fellowship Presentation to Code for Japan
Page 30: 2012 Chicago Fellowship Presentation to Code for Japan

Share your work.

Page 31: 2012 Chicago Fellowship Presentation to Code for Japan
Page 32: 2012 Chicago Fellowship Presentation to Code for Japan
Page 33: 2012 Chicago Fellowship Presentation to Code for Japan
Page 34: 2012 Chicago Fellowship Presentation to Code for Japan

Make it easy for others to participate.http://opensourcedesign.is/blogging_about/import-designers/

Page 35: 2012 Chicago Fellowship Presentation to Code for Japan
Page 36: 2012 Chicago Fellowship Presentation to Code for Japan
Page 37: 2012 Chicago Fellowship Presentation to Code for Japan
Page 38: 2012 Chicago Fellowship Presentation to Code for Japan

Good READMEs

• Quick and clear description

• A screenshot (seriously)

• Easy setup instructions

• Contribution instructions

• Recommended bugs to work on

Page 39: 2012 Chicago Fellowship Presentation to Code for Japan
Page 40: 2012 Chicago Fellowship Presentation to Code for Japan

Be nice.

• Respond to bugs and PRs quickly (even if just to say you can't get to it right away)

• Always use a friendly tone

• Be encouraging and constructive; don't say what's wrong, suggest how it could be better

• Say thank you!

Page 41: 2012 Chicago Fellowship Presentation to Code for Japan

Side Projects

Page 42: 2012 Chicago Fellowship Presentation to Code for Japan
Page 43: 2012 Chicago Fellowship Presentation to Code for Japan
Page 44: 2012 Chicago Fellowship Presentation to Code for Japan

Community Projects

Page 45: 2012 Chicago Fellowship Presentation to Code for Japan
Page 46: 2012 Chicago Fellowship Presentation to Code for Japan
Page 47: 2012 Chicago Fellowship Presentation to Code for Japan
Page 48: 2012 Chicago Fellowship Presentation to Code for Japan
Page 49: 2012 Chicago Fellowship Presentation to Code for Japan
Page 50: 2012 Chicago Fellowship Presentation to Code for Japan
Page 51: 2012 Chicago Fellowship Presentation to Code for Japan
Page 52: 2012 Chicago Fellowship Presentation to Code for Japan
Page 53: 2012 Chicago Fellowship Presentation to Code for Japan

ありがとうございます!Rob Brackett [email protected] @mr0grog GitHub.com/mr0grog flickr.com/mr0grog !

servicetracker.cityofchicago.org github.com/codeforamerica/srtracker http://dev.cityofchicago.org