--- tags: Notes --- # Notes from Building Research Software Communities Jarno's notes * Targeted workshops drive more engagement than coffee meeting * I like this idea. * Informal coffee does not work? * But I enjoy the coffee meetings that do work... Why don't they work for us? * In Aalto we have a daily 1h garage that draws about 5 people each time * HY particle physics group has a meeting twice a day with 3-8 people each time * Lesson: it needs to be every day? # Challenges identified in our group - Organisational recognition of RSE as a brand - Define what is an RSE, different roles & career path (so it is easier to sell) - Finding the people who don’t know they’re an RSE group 5: - People drop in and out of the field due to job uncertainty and lack of career structure - What can we offer to RSEs, how do we get people engaged with the group? - RSEs might not self-identify as RSEs, either due to not wanting to be identified or not knowing about the concept of “RSE” - because there is pressure to put RSEs into central IT services ## Notes on Lou's talk - Need to have a shared purpose: should we clarify this (on Nordic-RSE website) and explain activities we have (RSE cirtual coffee, RSE association meeting) and why they are helpful to achieve these shared goals. - The CSCCE Community Participation Model – A framework to describe member engagement and information flow in STEM communities: https://zenodo.org/record/3997802#.YFHXd-0zZds - We should advertise our consume-level things more. RSH is great and we should mention it in member news letters. - We don't have easy ways for members to contribute. - Unconference meetups - More prods to share on the chat (what is your favourite python package?) - collect results somewhere? ### Day-2 - champion program: we should think about "formalizing" a champion program. See https://www.cscce.org/