Skip to content

Instantly share code, notes, and snippets.

@sethvincent
Last active August 29, 2015 14:22
Show Gist options
  • Save sethvincent/d87e5e4298590abcf39d to your computer and use it in GitHub Desktop.
Save sethvincent/d87e5e4298590abcf39d to your computer and use it in GitHub Desktop.
Ideas for next few months of Code for Seattle

Rename to Open Seattle.

The goal: create a more diverse membership. We'll still be able to stay a Code for America brigade.

Partner with a local non-profit that can act as fiscal sponsor for 501(c)3 status

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.

Recruit 2-3 more lead organizers.

The goal: distribute responsibilities so they're not just on a couple people.

Create working groups.

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)

Switch to 2 Thursday meetups per month.

The goals: avoid burnout, reduce costs, plan around other Thursday events.

Hold smaller hack days focused on specific projects & other more spontaneous events.

Small, focused work sessions rather than weekly general interest meetups. This can include events for specific working groups.

Take down discuss.codeforseattle.org.

Nobody uses it.

Adopt github repos/issues for discussion.

It was effective for io.js and works well for nodeschool.

@sethvincent
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment