search

srobo / dev-team-proposal

Proposal for the Dev Team
0 stars 0 forks source link

Account for smaller fixes and already-specced things #15

Open PeterJCLaw opened 5 years ago

PeterJCLaw commented 5 years ago

The current proposal makes no mention of how things like bug reports or existing recorded issues are handled. I'm mostly thinking of small things though I imagine we could end up with some medium-sized projects which have already been specced out and are essentially waiting someone doing them.

For this sort of thing, where a bug report on GitHub could be solved by a quick fix and a PR, the current process feels highly likely to inject unnecessary overheads into what could be quite a simple flow.

This possibly interacts with #3 as the flow I'd hope that the above described things would have is something like:

  1. bug report appears, possibly via the forums or otherwise
  2. (optionally) brief discussion in slack/wherever happens to find someone interested in fixing it
  3. volunteer self-assigns github issue
  4. volunteer hacks on stuff
  5. volunteer submits PR
  6. PR is tested & code reviewed by another volunteer (perhaps the maintainer of the tech area, maybe not)
  7. PR is merged
  8. deployment happens (ideally automatically where that is viable)
PeterJCLaw commented 5 years ago

If this sort of thing is below the scope of the Dev Team, that's fine, but if so we should probably say somewhere that the Dev Team is scoped to larger projects only.