How to conduct a proper UX Process on Github?

[tomashei (Tomasz Czarnecki)]

Hello There,
I am starting this post after research, and unfortunately, I did not find an answer to my question on our forum.

I familiarised myself with the following topic, but it did not provide answers I am looking for:

Difficulties of design in open source

I see four large topics here: infrastructure and separation, autochecks and scratching own itches Infrastructure Most infrastructure in open source has code as its core “type” of thing. This is not surprising given that most code is text and given the status of text media in western culture. Everything else is modeled after or around text: Communication media, storage of content, collaboration systems. Thus, doing non-text things in the existing infrastructure is hard. Separation of parts Des…

I want to ask:
Do any of you know any examples of Proper UX Process conducted on GitHub?

I understand that UX Designers could simply start to code and apply their findings using any language, but it is not always possible. How to share findings? I did not find any project on Github where UX Process was published and organized in any form. I imagine it in some way that UX Designer creates a pull request with proposed changes based on data, then chances are accepted or rejected by the community. But I could not find any examples.

I shall highly appreciate any help! Thank you in advance

[jdittrich (Jdittrich (he|they))]

Do any of you know any examples of Proper UX Process conducted on GitHub?

GitLab does a lot of research and seems to document it on their platform.

However, they might not edit as you propose, by creating pull requests and them being accepted or not by a community. One reason for not seeing a lot of processes done in this way might be because such a process is not practical from the perspective of the people/roles involved.

For example, git is not necessarily the ideal tool to share research findings or ideas, since it is very text/code focused. It also might not be very practical to suggest each edit then rejecting or accepting it (which works great for code) since it leads to high costs, much like doing everything inside a company as if on a “free market” is costly.

This being said, if there are designers who also have programming and git experience, a git-based-workflow might be right for them.

[Erioldoesdesign (Eriol Fox)]

When I was at Ushahidi I heavily documented the design process we went through as a remote dispersed team here: https://docs.ushahidi.com/platform-developer-documentation/design/design-process

well…as much as I could get away with and that was funded to do via grants…

I would not suggest it’s in any way a ’ Proper UX Process’ but it’s certainly a UX process that was done and maintained by a team.

Please note Ushahidi did not have at the time any OSS design contributors in the community so we couldn’t test it with contributors.

We did try to then evolve a process through the work we did in our project we called ‘Open Design’ (please don’t judge me for the name we had to pick something) https://github.com/ushahidi/opendesign

maybe some of those things will be interesting?

[tomashei (Tomasz Czarnecki)]

@jdittrich @Erioldoesdesign
Thank you guys for your answers. You are awesome!

There are a lot of materials and it will take me sometime to digest them.

[itsamemario (Mario)]

hi all! thank you for starting this conversation and sharing your experience. There are some great resources in here. I’m a designer currently collaborating with the Open Food Network, and trying to help them set up a design contribution workflow.
It’s a hard job I’ll keep you posted and share my lessons as well.

Thanks a lot,

Mario

[Erioldoesdesign (Eriol Fox)]

Hey @itsamemario (love this username btw!) I’d love to hear more about what you do and Open Food Network. You can officially introduce yourself over on the Introductions pinned topic: Introductions (come in, say hi)