search

datasciencecampus / coding-in-the-open

A compendium of open-source guidance which aims to share the benefits, risks and a summarised strategy for open-source coding.
https://datasciencecampus.github.io/coding-in-the-open/
MIT License
8 stars 0 forks source link

Clarifying roles #44

Open NicciPotts opened 1 year ago

NicciPotts commented 1 year ago

Feedback from survey

Who signs off / is responsible for doing so? "project lead" is somewhat abiguous and likely open to interpretation. Is that deliberate?

and

Further guidance on who needs to sign off a repo publication is needed too.

My interpretation of this is that teams might be operating differently across the campus (for example, in International Development we all have a stated Project Lead in Project Agreements so this comments wouldn't apply in our team). Maybe broader conversation for SLT if there are projects operating where it's not clear whose leading the work?

r-leyshon commented 1 year ago

Comment from DS, ONS MDQ:

Looking at the "open at the start guidance", the one thing that's missing from what I can see is understanding roles and responsibilities, which is very important for things like quality assurance and disclosure control. I.e., does everyone on the team understand they have a personal responsibility not to put anything sensitive in an open repo? Do managers understand they are responsible for their team having the right skills and training to do this?

NicciPotts commented 1 year ago

Add in clarity on responsibilities across pages (i.e. everyone in team has a responsibility to keep repo in good condition)

NicciPotts commented 1 year ago

Roles - clearly defining responsibilities of dev team, project lead, fully documented through out

NicciPotts commented 1 year ago

Added in table on how different users can use this guide (overview) and reviewed text with clarifying roles in mind. Changes pushed on #68