team goal, end of 2016Q2:
- remove blockers to adoption of
npm@3 - try to get Node lts cut over to npm@3 exclusively
current problem:
- things are moving very slowly
takeaway:
- not a lot of the rest of the road map is going to happen in 2016
also necessary:
- npm, Inc. product work
- keeping the release train going
- support
- not so much with community management at this point
work balance:
- iarna: mixing redesigns and bug fixing seems unlikely to work; feature work + bug fixing works OK
- iarna: some of the project work brings with it redesign work, and that makes sense, but larger redesign work should be managed as projects
- othiym23: feels like CLI team is mostly working on product stuff _or_bug fixing, not really switching between the two
- othiym23: unsure how sequestering release work is affecting people not doing it – too soon to tell
- iarna: support affects different team members differently
- othiym23: is going to start tracking where he spends his time
- iarna: entering conference season
strategy:
- fix big bugs
- improve performance
solution:
- keep working on big bugs & product work
- iarna: fixing big bugs fixes blind spots in test coverage (which means I need to get back to improving CI robustness)
- pull out chunks of architecture to fix to support longer-term bug fixing & feature work
- pulling out dependency tree as a data structure and the set of operations that manipulate it
- remodularizing npm-registry-client
- removing god objects – injecting config rather than using global state, de-wiring the commands from calling each other
- cache rewrite
the team:
- kat:
- release work
- auth RFC (get to implementation)
- talk to me and Ben about unresolved issues with the RFC
- iarna:
- big bug PR(s)
- analytics project review of contributor work
- talk to Chris about blocking connections
- set up a meeting to plan for the intern
- othiym23:
- decide whether to fix or rebuild tarball packing to handle ignores and files properly
- CI work if any spare time left (ha ha ha