Project Accessibility / Management Improvements [WIP]

[Noah-Silvera]

New developer experience isn't great

• Working with solidus dev support isn't great
  • The Dev support docs themselves don't describe a dummy app
  • We don't link to or describe the sandbox or dummy app, and how to use them. (Question: the heck are dummy apps supported by)
• Setting up env variables sucks (PR in progress Update readme local development instructions #104)
• Make a Contributing.md

Projects & Milestones

• There's no description, scope, root tickets, etc allowing someone to understand the project
• Projects should be related to milestones
• Milestones should lay out the scope of work at a high level and link to current projects
• Only have one or two projects going at a time, to keep backlog minimal and approachable and avoid interwoven blocking work, which is rough to manage on github

Public Roadmap?

• Could be helpful for public knowledge (and getting more companies on board with taxjar).

Project Management

• Ticket groomer/writing/ticket scoper - probably has to be a more dedicate role(s), people with lots of context on the wider project (currently this is defacto Nick and Noah)

Our labels are bad

• Potential labels?
• Good first issue
• More information needed

Size of backlog

• Try to keep focus to one or two projects at a time (e.g. go HAM on reporting)
• Always try to have "good first issues" and "bug fixes" that are fleshed out and grabbable
• Ensure tickets are actually linked to eachother, and have context - (less tacit knowledge)

Bug reporting Process

• Currently doesn't exist
• Issue reporting template

[Noah-Silvera]

TODO - split some of these out into different tickets