{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}

@ArneBab

More they get involved in what is being built, and contribute to making *that* usable.

After this...well it gets complicated on what happens next.

> To make it easy to contribute, the project must be structured in a way that UX people can make their changes themselves.

This means, realistically, that UX contributors need to contribute code themselves. And for the most part that is not feasible.

@humanetech @tyil @blacklight

1
Share
Share on Mastodon
Share on Twitter
Share on Facebook
Share on Linkedin
Bernard Tyers

@ArneBab

I prefer the following:
- spend time with the project (join the IRC/matrix/mailing list/whatever)
- identify what people want to work on (like you said), and why,
- make UX contributions to those pieces of work
- take part in discussions as to why a UX improvement is needed, or
- suggest a way for some software design to be done *before* it's done.

@humanetech @tyil @blacklight

1
2y
Replies