@WinFan3672 It is a human resources issue. There are enough people to keep the site running in the sense that we have admins who log in to the server and fix things as soon as possible.
But there are not enough people who help improving the state of things so that long-term stability is improved.
@lil5#Weblate keeps permanent records of the Git repositories (their own copy of it). There are different options to integrate with it: You could pull the content from Weblate manually, you can have it push to your repo (separate branch or directly), or make it create a PR for you.
Weblate is Git-first, it is the source of truth. Modified translations are basically written to the repo and committed with a configurable delay.
Hi everyone, we are doing user research for #Forgejo, the software that powers #Codeberg.
If you have 30 minutes in the next week, consider participating in the interviews to help us get insights in how you interact with Codeberg and how we can improve the experience for you.
Thank you for your numerous participation. We're now particularly interested in input from underrepresented groups (i.e. people with disabilities of any kind and people who are not cis-male 😉)
To people looking for an archive of the XZ code, you might want to check out https://tukaani.org/xz-backdoor/ which links to https://git.tukaani.org/. GitHub is not the only source of truth, although meta information about the Pull Requests is locked in to this silo.
@waldi We don't have a precedence case yet. The easiest option would be to require users to sign in to Codeberg, so they are forced to see a warning and prevent distribution via automation like CI.
However, it requires everyone to create an account to investigate the code, so we are working on a better solution.
How come all text in @Codeberg is italics in my browser? Happens with more than one browser, with no extensions, in any of the available themes in the account preferences page, and both logged in and without logging in.
@josejfernandez Are you familiar with your local browser's debug tools? You could right-click a text element and check the CSS rules for the source of fonts; or use the "Computed" field to see which font is selected.
It is not intended, and we are not able to trace the behaviour to our CSS rules.
@Codeberg given the xz-backdoor incident, maybe a good idea to consider what your position would be if this happened on your platform, in particular: will you also start disabling accounts from users who may or may not have any involvement?
Github disabled the account of, among others, the original developer, who had nothing to do with the backdoor. He subsequently helped track down more suspicious activity, so it seems this must have been an unnecessary obstacle/annoyance for him.
In light of the current state of things, it would be awesome if there was a possibility @Codeberg could be a Trusted Publisher on @pypi, not sure if that is on the roadmap yet (and I am aware it requires some work on both ends)
Hey @Codeberg thanks for establishing the new service! I noticed some small inconveniences after confirming registration with a password. Maybe it would be worth looking at. All the best from me, and wish you luck in your future journey! 🙌
Are you waiting for #codesearch on Codeberg? Some free cycles and motivation to help?
Some team members are currently working on the goal, and they made progress. Consider helping to debug some issues, or even becoming a long-term maintainer of this service.
Are you a #python / #django or #webdeveloper? We are looking for contributions for #Weblate and potentially helping us implement some additional features or fixing bugs.
Huh, apparently #Gitea switched to an open core model a while back, and the good people at CodeBerg e.V. made a fork called #Forgejo . Maybe I should switch?
