Update lab manual: meetings, values and openness

[sbfnk]

Summary

• Restructure group meetings to 3×20 min presentation format (~90 min total) with written feedback
• Add feedback norms (curiosity not criticism, silent written feedback, commitments)
• Add journal club, coffee walks and other meeting types
• Add openness principle to group values: share work early, public GitHub repos
• Add expectations around sharing work openly and responding to help requests
• Add PI expectation to model group values
• Simplify communication, journal choice, presence and intro sections
• Add onboarding section

[seabbs]

Looks good. Some minor points - perhaps better addressed as their own issues/discussion items.

[seabbs]

Do we want to add something around expectations with code review in the group. Not so much if it happens but when it is being done expectations around it. i.e be nice, constructive, don't ask people to review LLM generated code you haven't reviewed etc etc

Could be its own issue

[seabbs]

Maybe this is an issue but there is a statement in the aims that we are value and aim to develop software.

There is then nothing in the output about valuing software alongside traditional academic goods (i.e there is just a publications section). I also couldn't see anything about code for a paper being as much a product of the paper as the manuscript and expectations around that. Also nothing about trying to expand/adapt existing software when doing new work vs rolling new models from scratch that I can see.

[seabbs]

On a related point there is nothing about contributing to lab software and how that works/expectations etc.

[seabbs]

And a related related point nothing about maintaince of those tools, ownership, decision making etc.

[sbfnk]

Re code review expectations: added "Review your own code before asking others to review it" to the Code section. See b444b92.

[sbfnk]

Re software valued alongside publications: now in Group principles — "We value software and tools as research outputs alongside papers". See 9f5c070.

[sbfnk]

Re contributing to lab software: covered in new Projects section — "build on each other's work... extend existing tools rather than starting from scratch". See 49da324.

[sbfnk]

Re maintenance, ownership and decision making: "Group packages have a named maintainer who is responsible for technical decisions about design, API and releases." See 49da324.

[seabbs]

Nice this looks good to me.