Thank you, @jdittrich , for your notes! Here are some additions I wrote down:
- OSD on Mastodon ( Open Source Design (@opensourcedesign@mastodon.social) - Mastodon ) reports about news in the Open Source Design world (such as UX related news and design tools). If someone from us has interesting content, they can send it per DM to that account and Jan will post it.
- Sven: We need to get into action. For next steps see the strategy document : set concrete long/mid/short term goals, define tasks, execute tasks
- Next steps to get into action. They can be executed in parallel.
- clarify, who our users are (such as developers seeking for UX guidance like @fnetX ), find out their needs and take them into account: all
- create a website prototype from the Website’s goal thread: Lisa
- collect ideas and tasks for next actions (for instance in the Github issue tracker). In our next meeting, we create an action plan from them: all
- To get things forward, we don’t have to wait until the next call to discuss things, but can discuss them in our Discourse.
Next meeting:
- Juhan: present a 300 second introduction to Seldon, an AI based design tool (see their website)
- clarify the goal of the Monthly Design Calls (Julia’s question)
- create action plan from collected issues
- (Lisa: present website protoype)
I might have missed it in our next steps, but I find it noteworthy: @fnetX is seeking for practical design guidance. Otto: What next steps would be helpful from your point of view?