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.
Working groups: Yeah, we'd need to work on that. And it might be somewhat different for each group. We'd want one or two people in each group to be coordinators that help define those things.
Smaller hack days: I'm imagining these would be small groups of people focused on a specific project or working group. Like when Working Washington proposed the minimum wage calculator project, maybe we would have kicked that off at a Saturday hack day that runs 1 to 5 p.m. instead of a Thursday meetup. So open seattle's support would be working with stakeholders, procuring space, promotion, at least light snacks/drinks but maybe not a meal. Wait this is basically like how seanetmap development started?
discuss/github: That's my concern, too.