What about an official server/group/channel of Codeberg?
Codeberg Discord/Telegram? #351
There is a channel found at #codeberg.org:matrix.org on matrix currently.
There is a channel found at #codeberg:matrix.org on matrix currently.
I think it's #codeberg.org:matrix.org
Yup, you are right. I've edited my comment as to not confuse anyone.
Yup, you are right. I've edited my comment as to not confuse anyone.
I will make the same with the title of this issue
I've made yesterday night a Telegram channel for Codeberg, it's @Codeberg_org
I think this issue is a dublicate of #38
and I think federated solutions are prefered ...
@lucas you of course can create codeberg chatrooms as you like, but I dont think they will be "official" one ...
ping @hw @ashimokawa
Ye, I put there is not official, I don't know if that chatroom is going to be active too much time. I prefer being on official ones.
I think I'll consider closing that chatroom.
Somebody knows how to close a issue?
as issue creater you also should be able to close it ...
@lucas you of course can create codeberg chatrooms as you like, but I dont think they will be "official" one ...
ping @hw @ashimokawa
there is an "inofficial" matrix room too (a few of us hang out there too), until #38 is implemented.
Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
Something is not working the way it should. Does not concern outages.
Errors evidently caused by infrastructure malfunctions or outages
This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
Please join the discussion and consider contributing a PR!
No bug, but an improvement to the docs or UI description will help
This issue or pull request already exists
New feature
Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
An issue directly involving legal compliance
involving questions about the ToS, especially licencing compliance
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.
Things related to Codeberg's external communication
More information is needed
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.
Related to Forgejo. Please also check Forgejo's issue tracker.
Migration related issues in Forgejo
Issues related to the Codeberg Pages feature
Issue is related to the Weblate instance at https://translate.codeberg.org
Woodpecker CI related issue
involves improvements to the sites security
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
Codeberg's current set of contributors are not planning to spend time on delegating this issue.
No due date set.
No dependencies set.
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?