Archived
15
23
Fork
You've already forked meta
6

Talking to humans instead of about users #190

Open
opened 2023年03月03日 21:26:01 +01:00 by Ryuno-Ki · 3 comments
Contributor
Copy link

I believe @aral made a lastening impression on me.

I'd like to get away from user as a term whenever possible.
Currently I'm walking through https://forgejo.org/docs/v1.19/user/first-repository/ and review it as part of the next release of Forgejo.

While I understand that there is some merit in calling it user documentation (because it is meant for people who use this software) I'm not okay with the term in

visiting another user’s repository

Because here it is about a person.

Similar to #171 I want to get opinions from the Forgejo community whether we can pledge to do better than the sources we derive our documentation from 🧡

I believe @aral made a lastening impression on me. I'd like to get away from _user_ as a term whenever possible. Currently I'm walking through https://forgejo.org/docs/v1.19/user/first-repository/ and review it as part of the next release of Forgejo. While I understand that there is some merit in calling it _user_ documentation (because it is meant for people who use this software) I'm not okay with the term in > visiting another user’s repository Because here it is about a person. Similar to #171 I want to get opinions from the Forgejo community whether we can pledge to do better than the sources we derive our documentation from 🧡
Member
Copy link

Personally, I find this ridiculous.

I am a user who uses software created by developers and I am a developer who creates software to be used by users.

That's it.

Personally, I find this ridiculous. I am a user who uses software created by developers and I am a developer who creates software to be used by users. That's it.

I think the answer is, it depends.

Looking at the link provided I see places where it should and probably shouldn't be used.

For example I think the following is fine:

when visiting another user’s repository

or

Issues is a very important communication tool between the author, their users and their contributors.

But I feel this feels somewhat alien and odd:

"Star" to show the user your appreciation (and to help other users find interesting projects more quickly)

Which I think would be better served by simply removing the word like:

"Star" to show them your appreciation (and to help others find interesting projects more quickly)

I think the answer is, it depends. Looking at the link provided I see places where it should and probably shouldn't be used. For example I think the following is fine: > when visiting another user’s repository or > Issues is a very important communication tool between the author, their users and their contributors. But I feel this feels somewhat alien and odd: > "Star" to show the user your appreciation (and to help other users find interesting projects more quickly) Which I think would be better served by simply removing the word like: > "Star" to show them your appreciation (and to help others find interesting projects more quickly)

In my opinion, the only problem with the term "user" is that it's ambiguous. Everyone who interacts with our software is using it. I prefer the term "end-user" because it disambiguates the people logging into the web interface and casually interacting with an instance from those who are managing the software.

In my opinion, the only problem with the term "user" is that it's ambiguous. Everyone who interacts with our software is using it. I prefer the term "end-user" because it disambiguates the people logging into the web interface and casually interacting with an instance from those who are managing the software.
Commenting is not possible because the repository is archived.
No Branch/Tag specified
readme
No results found.
Labels
Clear labels
[Decision] Building proposal(s)
We're in a decision-making process, buiding one or more proposals to address the shared aim based on the criteria
[Decision] Gathering criteria
We're in a decision-making process, gathering criteria, considerations and needs
[Decision] Integrating concerns
We're in a decision-making process, working with a proposal, trying to integrate concerns and create modifications/support such that the proposal works for everyone
Accessibility
Relates to Accessibility (a11y) of product, project and process.
Agreement proposal
Forgejo agreement proposal, following a discussion
Communication
Relates to all channels, social media, website, blog posts.
Election
Process of appointing a person into a role or team (if choosing people just for a specific one-time task, use the Entrustment label)
Entrustment
Process of choosing/approving specific people to do a critical/high-impact one-time task (if choosing people for an ongoing role/team, use the Election label)
Governance
Relates to processes, procedures and decision-making.
Meeting
An upcoming team meeting
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
4 participants Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/meta#190
Reference in a new issue
forgejo/meta
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?