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.
Renaming: Yep, it can still be a brigade.
Smaller hack days: The Duwamish hack day you describe is exactly the kind of thing I have in mind. Or maybe a documentation sprint for civic tech projects, or a Seattle LocalWiki editing party, or a user-testing session for a project, etc.
Discuss/github: Yeah, I've been onboarding non-technical people to Github for the purpose of using issues as discussion forum & bug tracker, and that's been working out fairly well.
Outdoor hack day: So much yes.