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
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?
Addition to answer Julia’s question about this meeting’s goals: in my perception the meeting’s goal so far is to get and stay in contact with other open source design interested people, to exchange news and help or to just chat. To give it some more structure, I created a meeting agenda template in 2024.
I don’t know if I can participate in todays meeting, so here is whats on my mind
I made no progress on the website compared to last month (state then was: I ran jekyll, which still seems to be maintained and is supported by github, still). Suggestion for next steps: Text writing for front page, learning and participating in OSD. (Maybe in a live online co-working session?)
I finally watched the Audacity Redesign Video is is very good indeed. I also isolated some clips as examples for important UX concepts].
Spoke a little bit about the penpot talks and the vibes of the conf re. dev + designer collab and onboarding people as penpot users. Eriol spoke about how she spoke to many people about the history and practicalities of contributing to OSS as a designer.
How to contribute in open source in designer = i am totally confuse → Ritish on the call asked how to get started in contributing to OSS as a designer. Folks offered insight and advice.
A student asked us about how to find projects
Uphill battle but try to find projects that ask for design
Pick something you care about, use for your job, or care about, find a motivation
Same format as 2025, 3 talks (please suggest speakers), then suggesting discussion sessions, need more volunteers based in Berlin to help please! (email erioldoesdesign@gmail.com for details!)
They may ask OSD for funding for the venue costs again and they are also looking for a few more sponsors of between 1000 Euros and 3000 Euros - if you have funding or sponsorship money please consider sponsoring!
any other OS conferences (other than FOSDEM) that should be on our radar?
FOSSY USA 2026
All things open 2026
Come in, say hello: Who is here, some background information about ourselves (country/culture, profession, open source involvement - in what role?), wishes for this meeting and for our community (15 min)
We said hello and met Ritish the new person on the call.
How we are doing: (30 min.)
Things we are working on.
Forgjeo good news! more user research is happening
Positive things: What are some of the great things that have happened recently?
Money! website! FOSDEM!
The not-so-great stuff: What problems are we struggling with? What help do we need? What ideas do you have for solutions? How can we work together to make this happen?
Knowing how to get involved in OSS
About this meeting: (10 min.)
What went well for this meeting?
Well attended, good topics and chat!
What could we improve for the next meeting? What goes into the minutes and what doesn’t?
Having ‘new to OSS as a designer?’ links and text prepared!
Chit-chat - open end
OSD Jobs board feedback - need just 1 way for people to contact e.g. just email or just issues. It was hard to consolidate all comms methods.
Running jekyll, so one can try to create ones own prototype (or play with our current website)
Comments:
It would be potentially useful to have a search (@jdittrich agrees, it is probably difficult with a static site, except when using an external service)
Current website has multiple calls of action; its good that the box in Lisas prototype serves as a call for action: Here is things to learn about… here…
The website should have a “who we are”, to make sure it is not just seen as a "general explanation of design in FOSS). The current text on our site is not bad.
The homepage should fulfil two needs: 1) Knowing what is this? (i.e. what OSD is) And 2) “go here to…” (learn, participate)
Process being very slow, we should be more proactive. The worst thing would be rolling back a change
FOSSDEM
Talk reviews in progress
Canonical at FOSDEM
Reminders: Review last month for FOSDEM needs (volunteers!) and other Conferences: FOSS Backstage, FOSSY, All things open
Hi all I don’t usually join the calls but following passively with interest.
On this one: over at AntennaPod we also use Jekyll and we do have a documentation search. It’s basically JavaScript in combination with a json-based index (generated by Jekyll):
I don’t usually join the calls but following passively with interest.