benefits and practices of working open - rcm discussion points for wiki

[cassgvp]

Summary Sentence

Discssion in RCM co-working 20/09/23

RCMs are often on the front line of navigating our community members (and teams) concerns about developing and working open. We also are in a position to help our projects design effective use of the available infrastructure to work "open as possible, closed as necessary". It would be useful to capture some specific instances we have encountered and share the pathways and practices which were developed to navigate the complexity.

Not clear yet how much of this should go directly into TTW, but perhaps RCM wiki is a place to develop first then generalise.

Other points discussed:

• The technical infrastructure we have available to us makes things complicated - not just a separation of access levels, but also infrastructure.
• Distributed across platforms - what is where?
• When things are necessarily closed, how do we show that the information (e.g. metadata) is there, but that it is not available to everyone?

What needs to be done?

[Add details in bullet list]

Who can help?

[Add details]

---

Update after the issue was opened

[cassgvp]

Drafting in this hackmd as part of co-working session

Integrate the table on how we can operationalise working open in different project spaces, and associated policy. Integrate information from this table (also tagged in this existing issue #190 ). Use collapsable sections formatting as demo'd this Open WIN page