# Why not accept bug reports over email instead of just GitHub **URL:** \ **Category:** Uncategorized\ **Tags:** open-standards\ **Created:** [September 17, 2024, 4:04pm UTC](https://support.delta.chat/t/why-not-accept-bug-reports-over-email-instead-of-just-github/3263 "2024-09-17T16:04:49Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![WofWca](https://support.delta.chat/user_avatar/support.delta.chat/wofwca/32/1702_2.png) [@WofWca](https://support.delta.chat/u/WofWca)\ **Post date:** [September 17, 2024, 4:04pm UTC](https://support.delta.chat/t/why-not-accept-bug-reports-over-email-instead-of-just-github/3263/1 "2024-09-17T16:04:49Z")
This manifests it here: - [https://delta.chat/contribute](https://delta.chat/contribute) : “Translations and Bug Reports” doesn’t specify an email. - On Delta Chat desktop “Help → Report an issue” goes to GitHub It’s like it’s not practicing what it preaches. Requiring a GitHub account is a somewhat of a high barrier to normal people, whereas simply typing a message without even switching the app would be so easy and cozy. In case you want to say “it’s a spam issue”: an email is already specified on [https://delta.chat/imprint](https://delta.chat/imprint) and [SECURITY.md](https://github.com/deltachat/deltachat-desktop/blob/main/SECURITY.md), so IDK if it’s a fair point. In case we do want to add email as a feedback channel, let’s remember that there is Chatmail that doesn’t allow sending unencrypted email. In addition, let’s utilize the `?body=` parameter to include things such as Delta Chat version. ---
**Author:** ![Simon](https://support.delta.chat/user_avatar/support.delta.chat/simon/32/287_2.png) [@Simon](https://support.delta.chat/u/Simon)\ **Post date:** [September 17, 2024, 9:23pm UTC](https://support.delta.chat/t/why-not-accept-bug-reports-over-email-instead-of-just-github/3263/2 "2024-09-17T21:23:12Z")
We could do that if we connect it to some ticketing system. Like some support software like chatwoot. And then we would still need to have someone responsible for asking further questions if necessary and to assign reports to issue tracker issues. Maybe relevant: GitLab has a function to submit issues via email. ---
**Author:** ![Minim](https://support.delta.chat/letter_avatar_proxy/v4/letter/m/ccd318/32.png) [@Minim](https://support.delta.chat/u/Minim)\ **Post date:** [January 9, 2026, 5:11pm UTC](https://support.delta.chat/t/why-not-accept-bug-reports-over-email-instead-of-just-github/3263/3 "2026-01-09T17:11:00Z")
The [Sourcehut](https://sourcehut.org/) software also does an e-mail UI. See also this discussion on Codeberg: > **[Future of this project](https://codeberg.org/Codeberg-Infrastructure/email-service/issues/17)** > > This is a continuation of the discussion in #14. > > This project was first created to add e-mail support to Gitea. But soon after we started, Gitea integrated most of the functionality we planned for this service. > > One idea that is not integrated was a... A platform run by a democratic not-for-profit, like Codeberg or Framagit or Debian Salsa, would seem preferable to one run by Microsoft. ---
**Author:** ![trufae](https://support.delta.chat/user_avatar/support.delta.chat/trufae/32/2851_2.png) [@trufae](https://support.delta.chat/u/trufae)\ **Post date:** [August 17, 2026, 11:28am UTC](https://support.delta.chat/t/why-not-accept-bug-reports-over-email-instead-of-just-github/3263/4 "2026-08-17T11:28:22Z")
I would appreciate if the repo had a SECURITY.md file describing how the security vulns are suposed to be reported. I filled a ticket to discuss that but i guess this is a better place hxxps://github.com/deltachat/deltachat-ios/issues/3261 ---
**Author:** ![ploum](https://support.delta.chat/user_avatar/support.delta.chat/ploum/32/3655_2.png) [@ploum](https://support.delta.chat/u/ploum)\ **Post date:** [August 29, 2026, 9:09pm UTC](https://support.delta.chat/t/why-not-accept-bug-reports-over-email-instead-of-just-github/3263/5 "2026-08-29T21:09:26Z")
> [@Minim](#): > > The [Sourcehut](https://sourcehut.org/) software also does an e-mail UI. I find it awesome but it seems to be a too high barrier for some people. Maybe we can imagine a webxdc app designed to help people send a bug report to the potential delta-chat sourcehut. ---
**Author:** ![bleb](https://support.delta.chat/letter_avatar_proxy/v4/letter/b/c77e96/32.png) [@bleb](https://support.delta.chat/u/bleb)\ **Post date:** [September 11, 2026, 5:59pm UTC](https://support.delta.chat/t/why-not-accept-bug-reports-over-email-instead-of-just-github/3263/6 "2026-09-11T17:59:16Z")
Since we are already using Discourse, we could consider making a “bug” category like Discourse uses for their own bug reports: [https://meta.discourse.org/c/contribute/bug/1](https://meta.discourse.org/c/contribute/bug/1) Apparently this could also be configured to accept emails from users without accounts: [https://meta.discourse.org/t/posting-without-signup/299644/4](https://meta.discourse.org/t/posting-without-signup/299644/4) > [@](#): > > There is a way to configure categories so that people can send in e-mails to a category address which will create a new topic post from that e-mail, without them needing to create an account. The system will create a user I.D. from their e-mail automatically as a “staged user.” ---
**Author:** ![qpntw](https://support.delta.chat/letter_avatar_proxy/v4/letter/q/f05b48/32.png) [@qpntw](https://support.delta.chat/u/qpntw)\ **Post date:** [September 13, 2026, 4:28am UTC](https://support.delta.chat/t/why-not-accept-bug-reports-over-email-instead-of-just-github/3263/7 "2026-09-13T04:28:07Z")
I fully agree. Who wants to make or have a GitHub account these days? There should really be an easier way to contribute.