Consider adding more resources on 'working in the open'

[clausmullie]

This issue summaries several notes about training resources that might be valuable for staff to have, that @Ainali and I found during our repository cleanup (#1081).

Notes included suggestions to provide or build training and resources around:

• Taking pride in collective work; particularly shifting away from identifying one's own success with one's own work, and taking more pride and satisfaction with supporting the work of others/the collective. This could include formal training as well as resources to share with other community members (eg in codebase communities)
• Shareable resources about best practice for open source maintainers
• Internal training/practising of writing good issues, good commit messages, and how to handle contributions - something which could be done with codebase communities as well
• General training and resources on how to work in the open, becoming and thinking like an open & community driven organization, with all the implications thereof (language use, taking more inclusive remote and asynchronous decisions, improving written and virtual communication...)

These resources and trainings would not only be useful for staff and codebase communities, but also civil servants interested in working towards/on public code in general.

List of resources

List of awesome maintainers

[clausmullie]

Old draft for a how we work session developed together with Jan - https://hackmd.io/4iO7eCq7TtmLkuhJktFd2g

[Ainali]

I found these week notes to be an inspiring example of explaining what a team has been working on: https://welsh-revenue-authority.github.io/weeknotes/property-data-poc/

[clausmullie]

Another nice example of week notes and working method in the open https://xbrp.notion.site/xbrp/XBRP-a18956aa0afb4eceb2e605764c70950a