4 ms·
To whomever downvoted this: I'd assume that you misunderstood this comment. How I understood this comment is that there's no easy or defined way to contribute U
by Dumbdo 6y ago
To whomever downvoted this: I'd assume that you misunderstood this comment. How I understood this comment is that there's no easy or defined way to contribute UI/UX improvements. For code improvements it's pretty clear, but the whole issue/PR workflow can't be applied 1:1 to the UI/UX process works from what I've seen. So I'd definitely agree with that sentiment.
- Vinnl 6y agoAn additional challenge is that, if I get a PR of which I don't like the specific way it's been done, I can patch it up myself. And if it's a feature I don't want added at all, I can already turn it down at the proposal stage, before any code is written. With UX, however, the contribution itself isn't the proof that the contributor actually knows what they're doing. I've been excited about getting a UX contributor in the past, but then with all due respect what they turned up with was even worse than what I could've done - and this was not just a matter of taste and expertise. But it's rough to turn it down after the work's been done.
- Closi 6y ago> But it's rough to turn it down after the work's been done. If the work suddenly turned up with zero iterations and input, this is UX work being done wrongly.
- Vinnl 6y agoSure, but just delivering the first iteration is already a significant step up from just reporting an issue describing your proposed approach, which is how it would work for writing software.