write blogpost on discussions/analysis at Berlin Meetup

[jdittrich]

Reasons: Share knowledge/Ideas, let others participate Task: Write a blog post summarizing our discussions/analysis at Berlin Meetup, as noted on the etherpads at What needs to be done: Structuring topics, supplementing information, possibly collect quotes/statement, possible split subsections to people (like jan D. writes about earning trust, Jan M. a paragraph on the problems of getting changes done…)

https://etherpad.wikimedia.org/p/opensourcedesign170416 and https://etherpad.wikimedia.org/p/opensourcedesign170420

I remember the following topics:

• how can we build community for usability/design people to support each other?
• Beginning
  • Earning trust as a designer
  • Onboarding process
• it doesn't work so well to integrate design & usability ideas into traditional (code-centric) open source projects
  • Lack of open source software tools designed for designers or designer/dev collaboration
  • how can we create a more neutral field for non-code contributors to take part?
• project maturity: How serious is a project about actually making changes?
• Adding functions but never removing them? Design can hurt… Who takes such hard decisions, in particular if one relies on volunteers?
• Problems Openusability had to reach its goals
  • time intensive
  • changes were not done

@HeikoTietze @Incabell @janushead @cameralibre @jancborchardt (…and some more, please @ mention if you remember more)

[jancborchardt]

@jdittrich were some posts written? :) Or how come the issue is closed?

This seems still a topic to be tackled. So I would say we should keep this open, no? cc @simonv3 @victoria-bondarchuk @evalica

[evalica]

Well this issue seems to be about the Berlin meetups so not sure how I can help.

[jdittrich]

– sorry, I thought it was resolved already.

[jancborchardt]

To prevent confusion, when closing an issue there should always be a comment with how it was resolved. ;)