Skip to content

Latest commit

 

History

History
198 lines (130 loc) · 10.3 KB

File metadata and controls

198 lines (130 loc) · 10.3 KB
layout default
local-chapter-name Code for Kansas City
location Kansas City
title Welcome/Resources
excerpt Resources to get started with Code for Kansas City
desc Indoc for new members to Code for Kansas City, a Code for America Brigade
author Paul Barham, Jason Harper, and more
web-page-title New Attendee Resources for Code for Kansas City
meetup-location Sprint Accelerator
communication Meetup, Facebook, Google Plus, Google Group, & Google Hangouts
schedule weekly from 6:00-9:00 pm on Wednesdays
homepage-url http://codeforkc.org
google-group-url https://groups.google.com/a/codeforamerica.org/forum/#!forum/c4hrva
meetup-url http://www.meetup.com/KCBrigade/
slack-invite-url http://slackinvite.me/to/codeforkc
slack-url https://codeforkc.slack.com
twitter-hashtag
captain1 Paul Barham
captain2 Jason Haper
captain3 Jennifer Funk
captain4 Jon Kohrs
email-contact pbarham@codeforamerica.org
contact-name Paul Barham
repo-issues-url https://github.com/codeforkansascity/codeforkansascity.github.io/issues

Welcome to {{page.local-chapter-name}}
A Code for America Brigade!

Serve Your Community Through Civic Tech

We are {{page.local-chapter-name}}, the local chapter of Code for America Brigade supporting civic hacking in {{page.location}}.

Code for America Brigade brings together developers, designers, data geeks, civic leaders, organizers, and idea-makers from communities to help local government and civic organizations adopt open web technologies. Code for America Brigade is the volunteer arm of the larger, national organization Code for America.

What is Civic Hacking, this video will help explain it.

Who This is For

Anyone with a desire and a passion for applying their technology skills to improve our community, open government, and open civic data.

What to Expect

You can apply your skills and expertise to work on an existing problem or project you care about like:

  • Improving park access
  • Helping the fire department locate fire hydrants
  • Launching a web app to find your city bus
  • Creating an app to help residents find information about your city
  • Helping residents get up-to-date information on the status of blighted properties in their community
  • Creating an app that allows parents to track their child’s bus in real time
  • Create apps. Design websites. Organize events. Write copy. And more!
  • Hang out with other civic hackers, eat pizza and drink beverages.

What Not to Expect

  • You can pick up expert advice, tips and tricks about new technologies but we are not a tech meetup or user group, and are usually working sessions not presentation format.
  • You can meet a lot of new and interesting people and make useful connections but we are not a networking group. We are volunteers working to make our community better through technology.
  • You can learn a lot of things about coding and design by participating in Brigade but we are not a code or design school.

Who’s in Charge

  • Captain: Paul Barham
  • Brigade Evangelist: THEA RASINS
  • Delivery Lead/Data Co-Wrangler: DAVID LaCRONE
  • Developer Evangelist/Data Co-Wrangler: RON HOUSE
  • Developer Evangelist: JON KOHRS
  • Documentarian/Storyteller: JASON HARPER
  • Policy Evangelist: LESLIE SCOTT
  • User Experience Architect: OLEH KOVALCHUKE

How it Works

We meet weekly, usually on Monday nights at the Sprint Accelerator, to either Hack (work on projects), Yack (socialize) or Learn (hear from a speaker). We use Meetup for organizing our events, so be sure to visit meetup.com/kcbrigade for the latest information.

The format for Hack Nights:

  • 6:00 - Social / Introductions
  • 6:10 - New Member Orientation
  • 6:20 - Project Pitches
  • 6:30 - Work on projects
  • 7:00 - Pizza arrives
  • 7:45 - Wrap up - get project updates

Required Tools

Bring your laptop/tablet as it's typically a working group with the occasional presentation. Free wifi is provided.

How Decisions Are Made

We use the Lazy Consensus model, meaning that if you think it's right for the group you have a green light, so don't wait around for approval. Concerns can be asked, but if you don't get much feedback that's a good thing and you can rock on.

How Projects Are Chosen

We choose projects based on:

  • Needs we identify through listening sessions with local gov and community organizations. We want to make things people will actually use.

  • Things happening in other cities that we want to bring here.

  • Things we like.

Current Projects

Our projects are usually centered around software at some point. Those are all listed in our GitHub Organization. There are also non-programming tasks in our "task list" at http://codeforkc.org/tasks/

Get Connected

Get Inspired

Get Smart

Get Started

Often you can start getting involved before the first meeting.

Code of Conduct

Our Code of Conduct

Contact Us

This sites creator was {{page.contact-name}}, but many others help to keep it awesome. You can file a issue/request in our [bug tracker]({{page.repo-issues-url}}), join our email group and discuss there, find us on twitter using [@codeforkc](https://twitter.com/codeforkc), or just email [{{page.email-contact}}](mailto:{{page.email-contact}})