The goal: create a more diverse membership. We'll still be able to stay a Code for America brigade.
That will be a much stronger relationship for supporting our local projects & events, and we'll still be able to receive support from Code for America.
The goal: distribute responsibilities so they're not just on a couple people.
The goal: give people a more meaningful way to get involved.
Possible working groups:
- diversity & digital equity
- government technology
- community outreach
- education & documentation
- design & user experience
- transportation & urban planning
- news & community media
- neighborhoods (maybe even a working group for each neighborhood? maybe based on demand)
The goals: avoid burnout, reduce costs, plan around other Thursday events.
Small, focused work sessions rather than weekly general interest meetups. This can include events for specific working groups.
Nobody uses it.
It was effective for io.js and works well for nodeschool.
Rename to Open Seattle Will this still be a Code for America brigade?
Switch to 2 Thursday meetups per month I like this idea, at least for the summer since attendance will likely be down. It would be nice to open up our Thursday evenings for other meetups, and the weekly general meetings are usually unproductive because there are too many projects at once.
Smaller hack days: I like the current calendar, like DiscoTech and Electric Sky. But how would this work for ongoing projects? Would something like "Hey Duwamish Hack Day at South Park Library" be an event?
discuss/github How will the "non-development" community provide input? Forcing Github on them doesn't seem unreasonable. I like the hackpad idea too.
We should also talk about holding an outdoor meetup or hack day. Maybe we can get funding for a hotspot router/modem?