Skip to content

Instantly share code, notes, and snippets.

@bencates
Last active February 16, 2017 20:03
Show Gist options
  • Save bencates/a7e4a49424b517329ae19b73c6dea9c6 to your computer and use it in GitHub Desktop.
Save bencates/a7e4a49424b517329ae19b73c6dea9c6 to your computer and use it in GitHub Desktop.

Indivisible Tech Committee Meeting - Feb. 16, 2016

Objectives

  1. Commit to our first deliverable(s).
  2. Bulleten Board / Forum
  3. Calendar / Scheduling Solution
  4. Public Website
  5. Hosting (aka Security part 1)
  6. How, and with whom, should we host?
  7. Who has deploy permissions, and what's our policy on amending that list?
  8. Budget?
  9. Data Collection and Retention Policy (aka Security part 2)
  10. What data are we comfortable collecting in the first place?
  11. Who, if anyone, needs secure communication and file storage?
  12. How do we communicate to the org at large what is and is not safe to publish?
  13. Commit to our tooling
  14. Decide what we're writing ourself and what we're using existing solutions for.
  15. Decide on language, framework, etc. for all development projects.
  16. Agree on project management tools (github, trello, slack, etc.)
  17. Project-Level Ownership and Membership
  18. Each project should have a single owner, and ideally no one should own two.
  19. Owners should feel empowered by the end of the meeting to manage their projects.
  20. Members should understand which projects they are qualified to contribute to and how to do so.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment