Proposals for prioritizing devops work

Approach-1.md

• Intention
  • Three net votes on an idea moves it to 'intended' (from Ideas)
  • 1 or less net votes on an intended card moves it back to ideas (2 week grace period for cards in intended now)
  • Negative 2 net votes on an idea for at least a week gets it archived after a week
  • Cards that are part of an ongoing project (epic) can be 'intended'
    • by getting 2 agreements in devops-int (which can also prioritize it, if those people agree it is urgent)
    • by making a PR and getting the two reviewers on the PR to comment that it should be done, like :+1:, we need this. (this is called 'delsmanning' :-P)
• Prioritization
  • Current Projects (Epics) are automatically prioritized - any card that is 'intended' and is part of that project can be taken for work immediately. Try not to expand the scope of MVP projects here - if it's not obvious that a given card belongs to some phase of a project, err on the side of deferring (until we can decide as a group in roundup or slack)
  • Other cards can be prioritized by dropping them into the 'pending' column
    • At any time, on say-so from Paul/Mark/etc (preferably they'd comment such in the card)
    • During roundups, by concensus
    • At any time via discussion in the devops-int channel (propose + 2 agrees)
    • Keep in mind that 'prioritizing' means "we should do this ASAP", not "we should do this eventually"
    • At any time if any two devops members agree that it's necessary to avoid a production threat
  • Cards that are currently prioritized can be de-prioritized by all the same methods
  • There can only be 6 prioritized cards on the devops board (the Pending column)
    • This means that cards being worked on (which should be on team boards) don't count
    • It also means that if we wind up at wip-limit, nobody can get a new card prioritized without first getting another card done or de-prioritized.
• All rules matter less than production stability. Break them if you need to!