Update contact page Prefer references to Forgejo, more relevant to users Updates to Getting Started Pages / FAQ - a lot of content was outdated and generally rewritten or rephrased - implement procedure for size limits as determined by annual assembly 2023, see Codeberg-e.V./Discussion#92 - people are sometimes confused wheter you need to be a paying member in Codeberg e.V. in order to use the platform Update improving Codeberg guides - reduce redundancy in code contribution guide and reference the Contributing Issue Tracker instead - separate (and ideally more appealing) donation page (deserves even more love IMHO) - shorten and strip outdated information Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/394 Reviewed-by: Panagiotis "Ivory" Vasilopoulos <git@n0toose.net> Co-authored-by: Otto Richter <git@otto.splvs.net> Co-committed-by: Otto Richter <git@otto.splvs.net>
3.3 KiB
eleventyNavigation | ||||||||
---|---|---|---|---|---|---|---|---|
|
Stay up to date
We recommend to follow us on Mastodon. You can also check out our blog. Also check out the Matrix Channels mentioned below!
Questions and Issues
Codeberg relies on community support and helping each other. You should try asking a question in public first. There are most likely people around to help you out, and your question will help users who experience similar problems in the future.
The most important place to ask for help and report any issues with Codeberg is the Codeberg/Community issue tracker. It's never wrong to open a ticket there.
If you need help quickly, or just want to join our community for exchange, discussions and news, you should consider to:
- join the community on Matrix! General discussions take place in the Codeberg room.
- join the unofficial (community-maintained)
#codeberg
IRC channel on libera.chat (much less activity than on Matrix)
If you need to get in touch with the people behind the non-profit Codeberg e.V. (e.g. for managing your membership etc), and only in this case, write to codeberg@codeberg.org.
Please only send us an email if your problem cannot be handled via public community support. Our user support is maintained by very few people in their spare time, and reading the FAQ first is always a good idea! If you believe that users should get kind responses to their emails, consider helping us out.!
If you still need to contact us, please email
help@codeberg.org.
Response times will be very long. If you do not receive a reply,
double-check if your question can be found in the FAQ
or asked via the public channels above.
Abuse
The preferred way to report content on Codeberg is an email to abuse@codeberg.org. When sending an email, please describe briefly why the reported material should be removed. Providing context helps us act faster.
Another faster method is tagging @moderation in an issue comment, which we highly recommend for automated spam bots.
When reporting people, we recommend making a private report, so as to protect yourself and others from retaliation in extreme cases.
Please keep in mind that we are only responsible for content hosted under the following domains:
codeberg.org
codeberg.page
(including custom domains using Codeberg Pages)codeberg-test.org
codeberg.eu
After submitting your report, please do not expect a written response. All reports will be investigated and acted upon accordingly, but due to constrained human resources and the possibility of duplicated reports, we do not typically find the time to keep you updated about the status of your reports.
Legal inquiries
For legal inquiries, please refer to the Imprint.