Codeberg/Documentation
42
199
Fork
You've already forked Documentation
161

Notification management #153

Closed
opened 2021年07月01日 00:04:40 +02:00 by fnetX · 7 comments
Owner
Copy link

Currently, users repeatedly complain about receiving too many emails from Codeberg, they somehow don't get how to unsubscribe. Since there is currently no way to easily unsubscribe from emails with a link, we should at least provide some article covering information about

  • how to set the general settings (all emails vs on-mentions vs none)
  • managing notifications for
    • watched repos
    • your organizations
    • issues you commented on
    • etc
  • etc
Currently, users repeatedly complain about receiving too many emails from Codeberg, they somehow don't get how to unsubscribe. Since there is currently no way to easily unsubscribe from emails with a link, we should at least provide some article covering information about - how to set the general settings (all emails vs on-mentions vs none) - managing notifications for - watched repos - your organizations - issues you commented on - etc - etc
Author
Owner
Copy link

The global settings configure how you receive notifications: Everything per mail, only mentions per mail, nothing per mail.

But this doesn't affect what notifications you get after all (also in Codeberg within the notification area which is accessible via the navbar). You have the options to subscribe / unsubscribe from issues, watch full repos etc ...

Also, it's good to mention that commenting in an issue automagically subscribes you to the thread. We had people complain about receiving too many emails from us, after they commented in an issue. We thought this was obvious, but it would still be nice to give people a hint they can simply unsubscribe from the issue and are done.

Mentioning this in an article would be nice, also to refer people complaining about too many emails to the explanation, so they can either change their email settings to not receive everything via email, or unsubscribe from the irrelevant threads.

The global settings configure how you receive notifications: Everything per mail, only mentions per mail, nothing per mail. But this doesn't affect what notifications you get after all (also in Codeberg within the notification area which is accessible via the navbar). You have the options to subscribe / unsubscribe from issues, watch full repos etc ... Also, it's good to mention that commenting in an issue automagically subscribes you to the thread. We had people complain about receiving too many emails from us, after they commented in an issue. We thought this was obvious, but it would still be nice to give people a hint they can simply unsubscribe from the issue and are done. Mentioning this in an article would be nice, also to refer people complaining about too many emails to the explanation, so they can either change their email settings to not receive everything via email, or unsubscribe from the irrelevant threads.
Contributor
Copy link

I had the problem, too: Codeberg/Community#507

I see there is now a small documentation, but I'm not happy with the title.
What about "Email settings" instead?

I had the problem, too: https://codeberg.org/Codeberg/Community/issues/507 I see there is now a small [documentation](https://docs.codeberg.org/getting-started/communication-from-codeberg/), but I'm not happy with the title. What about "Email settings" instead?
Contributor
Copy link

I see there is now a small documentation, but I'm not happy with the title.
What about "Email settings" instead?

I agree. Communication from Codeberg makes it seem as if communication is about Codeberg itself.

> I see there is now a small [documentation](https://docs.codeberg.org/getting-started/communication-from-codeberg/), but I'm not happy with the title. > What about "Email settings" instead? I agree. `Communication from Codeberg` makes it seem as if communication is about Codeberg itself.
Contributor
Copy link

The global settings configure how you receive notifications: Everything per mail, only mentions per mail, nothing per mail.

But this doesn't affect what notifications you get after all (also in Codeberg within the notification area which is accessible via the navbar). You have the options to subscribe / unsubscribe from issues, watch full repos etc ...

Also, it's good to mention that commenting in an issue automagically subscribes you to the thread. We had people complain about receiving too many emails from us, after they commented in an issue. We thought this was obvious, but it would still be nice to give people a hint they can simply unsubscribe from the issue and are done.

Mentioning this in an article would be nice, also to refer people complaining about too many emails to the explanation, so they can either change their email settings to not receive everything via email, or unsubscribe from the irrelevant threads.

Is somebody already working on this topic? I see that the task has no assignee yet.
@fnetX Can I use the information you provided here to write an article about the subject?

> The global settings configure how you receive notifications: Everything per mail, only mentions per mail, nothing per mail. > > But this doesn't affect what notifications you get after all (also in Codeberg within the notification area which is accessible via the navbar). You have the options to subscribe / unsubscribe from issues, watch full repos etc ... > > Also, it's good to mention that commenting in an issue automagically subscribes you to the thread. We had people complain about receiving too many emails from us, after they commented in an issue. We thought this was obvious, but it would still be nice to give people a hint they can simply unsubscribe from the issue and are done. > > Mentioning this in an article would be nice, also to refer people complaining about too many emails to the explanation, so they can either change their email settings to not receive everything via email, or unsubscribe from the irrelevant threads. Is somebody already working on this topic? I see that the task has no assignee yet. @fnetX Can I use the information you provided here to write an article about the subject?
Author
Owner
Copy link

sure, maybe check the changelog for the upcoming deployment of Gitea 1.16 (already released) to see if there are potential changes. If not, go ahead :)

sure, maybe check the changelog for the upcoming deployment of Gitea 1.16 (already released) to see if there are potential changes. If not, go ahead :)
Contributor
Copy link

As I had time yesterday evening, I came up with a quick writeup in #213.

Please feel free to change or completely replace the write up. I think that is is a common nuissance and we can address it by this short write up in the meantime.

As I had time yesterday evening, I came up with a quick writeup in #213. Please feel free to change or completely replace the write up. I think that is is a common nuissance and we can address it by this short write up in the meantime.
Contributor
Copy link

@jklippel: Thank you for the contribution. I'm going to start a draft and try to include your content within the next days.

@jklippel: Thank you for the contribution. I'm going to start a draft and try to include your content within the next days.
Sign in to join this conversation.
No Branch/Tag specified
main
renovate/major-cspell-monorepo
renovate/mstruebing-editorconfig-checker-3.x
renovate/lycheeverse-lychee-0.x
renovate/font-awesome
renovate/prettier-3.x
renovate/markdownlint-cli2-0.x
renovate/markdown-it-14.x
renovate/davidanson-markdownlint-cli2-0.x
renovate/pipelinecomponents-yamllint-0.x
renovate/11ty-eleventy-3.x
renovate/node-lts-slim
renovate/npm-pnpm-vulnerability
ci_pr_close_no_preview
pr-554
pr/554
gitea-icons-shortcode
No results found.
Labels
Clear labels
Codeberg Pages
Issues affecting Codeberg Pages
Documentation Usability
Issues related to using and reading docs.codeberg.org
Forgejo
Good First Issue! 👋
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Kind: Security
Licensing
Part: Generator
This is related to the generation of the documentation, not to the content itself
Priority: High
The priority is high
Priority: Low
The priority is low
Priority: Medium
The priority is medium
Reviewed: Confirmed
Something has been confirmed
Reviewed: Duplicate
Something exists already
Reviewed: Invalid
Something was marked as invalid
Reviewed: Wontfix
Something won't be fixed
Status: Blocked
Status: Help wanted
Contributions are welcome!
Status: In progress
Work is in progress
Status: Needs feedback
Feedback is needed
Status: Ready for Review
Work is completed
Status: Review
Review is in progress / Reviewers wanted
Status: Stale
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 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/Documentation#153
Reference in a new issue
Codeberg/Documentation
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?