WoofJS dev meeting 5 10 19

0. come up with label, project layout, milestone
1. relabel all issues, and collectively talk about new, cleaning house

Steve Prep

Maddy has 5 hours per week Steve has 3 hours per week Kate has X? hours per week

So 20 hours per weekpict

A couple things to discuss:

1. Urgent bugs that require my immediate attention
2. Paying down technical debt to make the project more long-term manageable
3. Reviewing all existing issues, as well as communicating to teachers how to add new ones
4. TODO how do we "accept" solutions? (agree on github issues and add label?)
5. For "accepted issues", potentially breaking up into sub issues (maybe grouped into a milestone), discussing implementation, prioritizing (TODO how to do this? project board, label, during a meeting?), assigning to a person
6. For "in-discussion issues", discussing on github issues
7. For pull requests, Steve reviews and we iterate

• useful to document everything for future people, including ourselves (context is crazy) so let's do on github issues or in meeting notes posted somewhere in the repo. So we can discuss implementation details on a call put someone should write them up and paste into issue for posterity.
• breaking things up as small as possible speeds everything up

Process

TODO put this in the repo README

1. Propose, ideas, debate, discuss things on issues
2. Prioritize together (combo of benefit, cost, technical debt vs other things)
3. divy up projects, and discuss implementation details (don't spend too much time where I can help)
4. Pull request to Steve, feedback, iterate, merge

Refactoring

• research into module / build system
• clean up open pull requests and issues
• automatic style / linting
• typescript?
• tests
• clean up dirty codemirror usage
• more immutable / functional approach to state

Open issues (115)

Open pull reqs (8)

• this one seems like it's on me to review: https://github.com/stevekrouse/WoofJS/pull/531

Big Projects

• Social Network