Improvements and fixes for the 'Meet and Agree on Objectives' Step

[bielsnohr]

Revisiting this section in preparation for the workshop, I have noticed a few items that need attention. We can split these into separate issues if desired:

• [ ] At no point to we explicitly state that this should be a realtime meeting that happens before the code review. It is implied in this sentence (which is quite far down): "These expectations must be made clear during the startup meeting, before the review itself starts." and that paragraph starts with "During the startup meeting..." but we haven't really defined what this startup meeting is. Just feel it could be a bit more clear.
• [ ] #71
• [ ] I think there should be a rough schedule/agenda for what one of these startup meetings should include. In particular, there is no mention of explaining the broader scientific context of the code, which I would think would be the first item in this meeting (i.e. the code author is introducing what the code does).

[bielsnohr]

Further to my third point above, we do actually have an 'orphaned' recipe called Explain code structure to which we currently make no reference to anywhere else on the site!!! I'll raise a separate issue for this, but it should certainly be referenced from here.

[tlestang]

Thanks for looking back at this. The recipe is called "Meet and agree and objectives", I thought it's fairly clear that it's about a meeting? Agreed that a sentence motivating a meeting instead of e.g. an email conversation could help.

I'll complete the second example. thanks for pointing this out.

Re broader scientific context, this was a separate step in our original flowchart, coming before "Meet and agree on objectives". I'd say this part is really about "agree on objectives". Maybe we should have one "initial meeting" with two steps: explain scientific context and agree on objectives.