Meeting recording 2025年07月29日 #66

fnetX commented 2025年07月29日 23:50:56 +02:00

No description provided.

earl-warren commented 2025年07月30日 10:58:35 +02:00

I enjoyed listening to the recording. It paints a picture of the state of the user research in Forgejo that match how I perceive it. And I also learned a few things that I did not (e.g where @mfenniak is at regarding the review process, or how @fnetx had so many interviews). It is also a good inventory of the many challenges it faces (privacy challenges of survey and the need to share them publicly, the perception of how user research is currently in a fuzzy state, the disconnect there currently is between the user research effort and the development effort).

Random notes.

• Recurring user research meetings is an idea to explore
• Encouraging developers to reach out to user research with unfinished implementations, prototypes, to get a sense of how likely it is to be received, perceived as valuable. Maybe reach out to valuable code pull request authors. A number of them have features with no tests but are fit for manual testing. Maybe they would be willing to set up a demo for the user research to experiment with it and give them feedback?
• Instead of having feature requests or bug, start with a one first stop: explain the problem. Then it can move on to be a bug fix or to be a feature request.
• Having a general and global view of the issues in all Forgejo is something @fnetx has in his head. That makes him a valuable asset (@0ko words). He conveys that by assigning labels to group issues. But it is also something that is not easy to convey to potential or even existing contributors.
• Questioning the workflow established in a project rarely happens. Recently there has been a change in the Forgejo runner. There is a familiar and well understood mental model when someone engages in an issue tracker: "bugs and features". I wonder how the UX would be if none of those were immediately visible when filing a new issue.
• The idea of hiding the issue count made me laugh (in a good way). I do like to keep numbers in check so I would miss that. But maybe it is a good idea.

I enjoyed listening to the recording. It paints a picture of the state of the user research in Forgejo that match how I perceive it. And I also learned a few things that I did not (e.g where @mfenniak is at regarding the review process, or how @fnetx had so many interviews). It is also a good inventory of the many challenges it faces (privacy challenges of survey and the need to share them publicly, the perception of how user research is currently in a fuzzy state, the disconnect there currently is between the user research effort and the development effort). Random notes. - Recurring user research meetings is an idea to explore - Encouraging developers to reach out to user research with unfinished implementations, prototypes, to get a sense of how likely it is to be received, perceived as valuable. Maybe reach out to [valuable code pull request authors](https://codeberg.org/forgejo/forgejo/pulls?q=&type=all&sort=&state=closed&labels=217340&milestone=0&project=0&assignee=0&poster=0&archived=false). A number of them have features with no tests but are fit for manual testing. Maybe they would be willing to set up a demo for the user research to experiment with it and give them feedback? - Instead of having feature requests or bug, start with a one first stop: explain the problem. Then it can move on to be a bug fix or to be a feature request. - Having a general and global view of the issues in all Forgejo is something @fnetx has in his head. That makes him a valuable asset (@0ko words). He conveys that by assigning labels to group issues. But it is also something that is not easy to convey to potential or even existing contributors. - Questioning the workflow established in a project rarely happens. Recently there has been [a change in the Forgejo runner](https://codeberg.org/forgejo/discussions/issues/369). There is a familiar and well understood mental model when someone engages in an issue tracker: "bugs and features". I wonder how the UX would be if none of those were immediately visible when filing a new issue. - The idea of hiding the issue count made me laugh (in a good way). I do like to keep numbers in check so I would miss that. But maybe it is a good idea.

0ko commented 2025年07月30日 17:29:19 +02:00

@earl-warren wrote in #66 (comment):

a valuable asset (@0ko words)

Shouldn't be taken literally or seriously 🙃

@earl-warren wrote in https://codeberg.org/forgejo/user-research/pulls/66#issuecomment-6047401: > a valuable asset (@0ko words) Shouldn't be taken literally or seriously 🙃