So the things I mentioned on the community call yesterday were:
Having a ‘design lead’ that does much of the interfacing with the OSS project/Linux. That allows for newer designers that haven’t ‘interfaced’ with OSS projects to be supported and deferr their contributions through a point of contact. That person/s can also offer general mentoring and support the designers to ‘stick around’ in a project.
I suggested that your planned activities which included ‘Sniffing out early design needs’ would make for great remote workshops/jams/hackathons and recommend the global design sprint methods to do that.
I mentioned about how in these OSS design cases you often have to do two way education so designers typically need the OSS education and OSS needs the design onboarding/education.
The last thing I mentioned was the more exposure OSS projects get to many designers the better they’ll know who,how,what and when to talk to them. It’s kind of like…exposure therapy…but for OSS orgs and designers are the tarantulas…
If you wanna drop your plan here @juhan I found that really useful.
I also mentioned Daniel Burka of https://docs.simple.org/design-1/design but many of us are familiar with this OSS design arm of that project.
From the call chat I’m copy pasting this from @jdittrich
What might be a good start: If you ask people who are with the Linux Foundation at this project for some time: What are their pains around design and what would they be open to change to do this?
Also to tease out stuff like: What are the goals? Who is the target group?… (That are questions that do not need to be solved if people self select for scratching their own itch)