Make modules more specific hands on for Research Supporters

[JaroCamphuijsen]

• More opinionated, more concrete
• More on the supporting side
• More hands-on, doing actual support
• "Here is what you need to do"
• They want to know what the current landscape is in the Netherlands (we also need to investigate this, and updated each year)
• More tools and weapons
• Also social tools, how to talk to researchers
• Chapter in every module with top 5 questions that you can ask researchers and resolve.
• Be explicit about that software includes code, scripts, everything. Use the right language.
• Frame the content from the point of view of the supporter: "it is important to tell researchers what that research software is something different than software used in research"
• Give arguments why things are important with everything they do

[LourensVeen]

For the licensing bit, I'd like to

• change tack to "I've been helping my colleagues with licensing questions for years"
• add the Cathedral and the Bazaar (should be in fairsoftware maybe?)
• shorten the copyright theory part and make things more practical.

[JaroCamphuijsen]

@LourensVeen i think these are good ideas. keep in mind though that the materials might also be used by other in the future, for which it might not be true that "they have been helping their colleagues with licensing questions for years"

[LourensVeen]

I'm not expecting there to be many people who have been helping their colleagues with licensing questions for years, so the target audience is (still) people who've never done that but will need to do it soon, and the story changes from "I know all about the Berne convention" to "Let me show you how I do this".

[JaroCamphuijsen]

Another thought from a meeting with Mateusz:

Be practical about policy, if your organization has no policy: these are good example of other policies. These are the things you can already do, but be aware that because there is no policy, you are in the wrong, but it’s the only thing you can do and you will not be sued. Be pragmatic, but also transparent. Doing nothing is not an option.

Also connect to @OleMussmann and @sjvrijn to discuss alignment with their Software Management Tool.