hackathon!

[jeremymanning]

in preparation for a (lab-wide? department-wide?) hackathon, let's:

• create a project board
• create a set of well-defined issues and to-do items, tagged with difficulty level (e.g. good first issue, no coding, beginner task, intermediate, experts only, etc.) and priority (bugfix, critical, nice-to-have, wish-list, etc.)
• create documentation describing how to contribute:
  • introduce leadership team and say how to ask questions
  • set up local environment
  • join slack channel or gitter room
  • look over issues list and select an issue (or discuss with project leadership)
  • move issue to "in progress" column while you're working on it, and add any coding partners to "assignees" list. when done working:
    • document changes-- what's done, what's left to do, any implementation notes, things that are broken, recommended next steps, etc. as appropriate
    • move issue back to appropriate column (backlog, blocked, done, etc.)
• create templates for pull requests and issues
• set up some sort of test job or script