Sort existing information #20

earl-warren commented 2023年10月25日 13:33:26 +02:00

• create labels
• tag issues in https://codeberg.org/forgejo/
• tag issues in https://codeberg.org/Codeberg/Community/issues
• tag issues in https://code.forgejo.org/forgejo/
• collect messages from the chatroom https://matrix.to/#/#forgejo-chat:matrix.org

- [x] [create labels](https://codeberg.org/forgejo/user-research/issues/20#issuecomment-1306650) - [x] tag issues in https://codeberg.org/forgejo/ - [ ] tag issues in https://codeberg.org/Codeberg/Community/issues - [x] tag issues in https://code.forgejo.org/forgejo/ - [ ] collect messages from the chatroom https://matrix.to/#/#forgejo-chat:matrix.org

earl-warren commented 2023年10月25日 13:46:02 +02:00

https://codeberg.org/org/forgejo/settings/labels

image

https://codeberg.org/org/forgejo/settings/labels 

Ghost commented 2023年10月27日 21:26:46 +02:00

https://code.forgejo.org/org/forgejo/settings/labels

image

https://code.forgejo.org/org/forgejo/settings/labels 

Ghost commented 2023年10月27日 22:52:20 +02:00

Each label was defined to represent an area of interest where at least one Forgejo contributor is active on a regular basis. Ocassional contributors are collectively refered to as "contributors".

• bug (1, 2)
• communication (1, 2)
• documentation (1, 2)
• feature (1, 2)
• federation (1, 2)
• governance (1, 2)
• release (1, 2)
• security (1, 2)
• testing (1, 2)
• UI (1, 2)
• UX (1, 2)

Each label was defined to represent an area of interest where at least one Forgejo contributor is active on a regular basis. Ocassional contributors are collectively refered to as "contributors". * bug ([1](https://codeberg.org/forgejo/issues?labels=158898), [2](https://code.forgejo.org/issues?labels=107)) * communication ([1](https://codeberg.org/forgejo/issues?labels=158903), [2](https://code.forgejo.org/issues?labels=108)) * documentation ([1](https://codeberg.org/forgejo/issues?labels=158900), [2](https://code.forgejo.org/issues?labels=110)) * feature ([1](https://codeberg.org/forgejo/issues?labels=158899), [2](https://code.forgejo.org/issues?labels=110)) * federation ([1](https://codeberg.org/forgejo/issues?labels=158907), [2](https://code.forgejo.org/issues?labels=111)) * governance ([1](https://codeberg.org/forgejo/issues?labels=158902), [2](https://code.forgejo.org/issues?labels=112)) * release ([1](https://codeberg.org/forgejo/issues?labels=158897), [2](https://code.forgejo.org/issues?labels=113)) * security ([1](https://codeberg.org/forgejo/issues?labels=158901), [2](https://code.forgejo.org/issues?labels=114)) * testing ([1](https://codeberg.org/forgejo/issues?labels=158906), [2](https://code.forgejo.org/issues?labels=115)) * UI ([1](https://codeberg.org/forgejo/issues?labels=158905), [2](https://code.forgejo.org/issues?labels=116)) * UX ([1](https://codeberg.org/forgejo/issues?labels=158904), [2](https://code.forgejo.org/issues?labels=117))

Ghost commented 2023年10月27日 22:55:34 +02:00

@ei8fdb all issues in all Forgejo repositories were labeled. There are many ways to further examine each category, do you have a suggestion?

@ei8fdb all issues in all Forgejo repositories were labeled. There are many ways to further examine each category, do you have a suggestion?

ei8fdb commented 2023年11月29日 20:07:49 +01:00

Thanks for doing this. It's a big piece of work. 🫡

@dachary I'm going to spend some days looking thru these, and try to work out if theres any other grouping that could come from it. I will let you know.

Thanks for doing this. It's a big piece of work. 🫡 @dachary I'm going to spend some days looking thru these, and try to work out if theres any other grouping that could come from it. I will let you know.

Ghost commented 2023年11月30日 15:38:57 +01:00

@ei8fdb great! I really look forward to working with you on this ❤️

@ei8fdb great! I really look forward to working with you on this ❤️

fnetX commented 2024年04月08日 01:21:27 +02:00

This work was done, but not really used :-(

This work was done, but not really used :-(

earl-warren commented 2024年04月08日 09:09:19 +02:00

Do you find the existing labels to be useful in your recent user research activity?

Do you find the existing labels to be useful in your recent user research activity?

fnetX commented 2024年04月08日 13:59:04 +02:00

I find the classification sometimes a little redundant, e.g. I don't see a point in labelling issues with both "bug" and "user-research: bug". I'm not sure how I can really make use of the labels.

We should at least try if there is something we can do with these, e.g. if there is one label that is not represented in the "normal" label structure and eventually rename it.

For me, the next thing would be to classify the results of my user research interviews and actually create or prioritize issues with this information. I would somehow need a label that gives issues more weight, i.e. have a distinction between "this is Otto's personal opinion" and "this is Otto's conslusion from User Support" issues.

I find the classification sometimes a little redundant, e.g. I don't see a point in labelling issues with both "bug" and "user-research: bug". I'm not sure how I can really make use of the labels. We should at least try if there is something we can do with these, e.g. if there is one label that is not represented in the "normal" label structure and eventually rename it. For me, the next thing would be to classify the results of my user research interviews and actually create or prioritize issues with this information. I would somehow need a label that gives issues more weight, i.e. have a distinction between "this is Otto's personal opinion" and "this is Otto's conslusion from User Support" issues.