Codeberg/Community
54
325
Fork
You've already forked Community
12

a way to give/accept compliments (as opposed to Issues) #1852

Open
opened 2025年04月17日 06:26:50 +02:00 by soas · 1 comment

Comment

This is something of a fanciful request. For discussions.

Background & Problem

All hosted git repos, here and elsewhere, come with "Issues" (unless disabled by the dev). To report problems, bugs, suggestions etc.

I have often heard that devs can get burnt out by users whining and complaining. Even if they appreciate constructive feedback, the convention of facilitating only "negative" comments can get people down.

Sometimes I just want to drop a compliment on some project. But it's considered rude in Issues.

Existing solution = Email

  • not everyone supplies an email address to send to
  • these days a lot of people are not habitual email users
  • would be nice to have an public place to post, same as issues
  • Privacy concerns with sending and receiving email

Existing solution = "Stars" as on github, or other follow/like mechanism

  • Not specific enough; lazy clicking
  • Can be gamed/purchased
  • Sometimes I want to compliment something but not follow it or even use the software (e.g. it's wrong for my use case but has some really cool feature or thoughtful design)

Existing solution = tip jar / "buy me a coffee"

  • Even poor people should be able to leave a kind word
  • All kinds of barriers

Proposed solution

Therefor I suggest codeberg pave an innovative path by providing some sort of "positive" feedback forum for those devs who wish to enable it.

I don't have any mechanic details worked out. I don't know if threads would be allowed or just one-off comments. I can forsee some social issues. This might not be to right tool but it's something I've wished existed for years.

### Comment This is something of a fanciful request. For discussions. **Background & Problem** All hosted git repos, here and elsewhere, come with "Issues" (unless disabled by the dev). To report problems, bugs, suggestions etc. I have often heard that devs can get burnt out by users whining and complaining. Even if they appreciate constructive feedback, the convention of facilitating *only* "negative" comments can get people down. Sometimes I just want to drop a compliment on some project. But it's considered rude in Issues. Existing solution = Email - not everyone supplies an email address to send to - these days a lot of people are not habitual email users - would be nice to have an public place to post, same as issues - Privacy concerns with sending and receiving email Existing solution = "Stars" as on github, or other follow/like mechanism - Not specific enough; lazy clicking - Can be gamed/purchased - Sometimes I want to compliment something but not follow it or even use the software (e.g. it's wrong for my use case but has some really cool feature or thoughtful design) Existing solution = tip jar / "buy me a coffee" - Even poor people should be able to leave a kind word - All kinds of barriers **Proposed solution** Therefor I suggest codeberg pave an innovative path by providing some sort of "positive" feedback forum for those devs who wish to enable it. I don't have any mechanic details worked out. I don't know if threads would be allowed or just one-off comments. I can forsee some social issues. This might not be to right tool but it's something I've wished existed for years.

@soas wrote in #1852 (comment):

by providing some sort of "positive" feedback forum for those devs who wish to enable it.

Sounds like https://www.hezmatt.org/~mpalmer/blog/2024/05/30/githubs-missing-tab.html 🙃

How about: open an issue titled "General feedback" and pin it?

@soas wrote in https://codeberg.org/Codeberg/Community/issues/1852#issue-1307147: > by providing some sort of "positive" feedback forum for those devs who wish to enable it. Sounds like https://www.hezmatt.org/~mpalmer/blog/2024/05/30/githubs-missing-tab.html 🙃 How about: open an issue titled "General feedback" and pin it?
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
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
Codeberg/Community#1852
Reference in a new issue
Codeberg/Community
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?