h759bkyo4/Documentation
1
0
Fork 0
Code Issues Pull requests Actions Packages Projects Releases Wiki Activity

Diverse changes (#189)

Browse source 
a bunch of (typo) fixes, additions, rewordings

Update references

- remove mentions of the master branch, as it's removed for many repos
and might change in the future for others (fixes some dead links)
- remove mentions of moved repos with our official examples
- some on-the-fly additions or rewordings

Close #186 foobar->examples

Co-authored-by: fnetx <git@fralix.ovh>
Co-authored-by: fnetX <git@fralix.ovh>
Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/189
Co-authored-by: Otto Richter <fnetx@noreply.codeberg.org>
Co-committed-by: Otto Richter <fnetx@noreply.codeberg.org>
This commit is contained in:
Otto Richter 2022-01-21 11:36:38 +01:00
parent f1552640e8
commit 2bda61e74d
16 changed files with 89 additions and 47 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
content/_includes/default_layout.njk
View file

@ -19,7 +19,7 @@
<link rel="preload" href="https://fonts.codeberg.org/dist/fontawesome5/css/solid.min.css" as="style">
<link rel="preload" href="https://fonts.codeberg.org/dist/fontawesome5/css/fontawesome.min.css" as="style">
<!-- Details and License: https://codeberg.org/Codeberg/Design/src/branch/master/design-kit -->
<!-- Details and License: https://codeberg.org/Codeberg/Design/src/design-kit -->
<link rel="stylesheet" href="https://design.codeberg.org/design-kit/codeberg.css"/>
<script defer src="https://design.codeberg.org/design-kit/codeberg.js"></script>

13
content/codeberg-pages/index.md
View file

@ -9,12 +9,12 @@ eleventyNavigation:
Codeberg Pages allows you to easily publish static websites with a human-friendly address (`{user-name}.codeberg.page`) via Git on Codeberg.org.
Follow the simple steps below to get started, or check out the advanced usage below.
1. Create a repository named 'pages' in your user account or organization.
1. Create a public repository named 'pages' in your user account or organization.
2. Create static content, HTML, style, fonts or images. Name the homepage file `index.html`
3. Push your content to the main branch of the new repository.
4. You should now be able to access your content using the domain `{user-name}.codeberg.page`.
See also [https://codeberg.page/](https://codeberg.page)
See also [https://codeberg.page/](https://codeberg.page) or the [Troubleshooting](troubleshooting) page.
## Advanced Usage: Canonical URLs
@ -45,4 +45,11 @@ If you can't use a CNAME record to configure the target (e.g. for a zone root),
## Having Questions, Feedback or found a bug?
The source code for Codeberg Pages is maintained over at the [Pages Server repository](https://codeberg.org/Codeberg/pages-server), feel free to head there and providing some feedback, suggestions, bug reports or even patches. We really appreciate your contribution.
The source code for Codeberg Pages is maintained over at the [Pages Server repository](https://codeberg.org/Codeberg/pages-server), feel free to head there and providing some feedback, suggestions, bug reports or even patches.
If you need general community support or have questions, [Codeberg/Community](https://codeberg.org/Codeberg/Community) is the better place, as more people will be watching there to help you out!
We really appreciate your contribution.
## Installing Pages for your own Gitea
Codeberg Pages works with any Gitea host out there. So if you are running your own Gitea, you can absolutely run it yourself and help with the development.
Check out the [Pages Server repository](https://codeberg.org/Codeberg/pages-server) for more.

6
content/codeberg-pages/troubleshooting.md
View file

@ -8,3 +8,9 @@ eleventyNavigation:
## My web browser displays a security warning when I try to access my Codeberg Pages.
If your user name contains a dot (e.g. `user.name`) your Codeberg Pages URL (https://user.name.codeberg.page) contains a sub-sub-domain which does not work with Let's Encrypt wildcard certificates. Use the alternative URL https://pages.codeberg.org/user.name/ as a workaround.
## My content is not updated
The new Codeberg Pages Server uses caching for files under a certain size (currently 1 MiB).
Please wait a few minutes until cache is invalidated.
This is to improve performance, reduce server load and cost as well as save energy.

4
content/collaborating/create-organization.md
View file

@ -7,7 +7,7 @@ eleventyNavigation:
---
## What is an organization?
An organization is a group of users that have access to a shared account. As such, they can all access the different projects (repositories) of the organization. An organization can be composed of several teams, each having a defined role in the project's development and also different access rights. This makes organzations an easy and powerful tool to collaborate on a project.
An organization is a group of users that have access to a shared account. As such, they can all access the different projects (repositories) of the organization. An organization can be composed of several teams, each having a defined role in the project's development and also different access rights. This makes organizations an easy and powerful tool to collaborate on a project.
Everyone can create organizations on Codeberg for free. The following sections will show you how to create and manage an organization.
@ -95,7 +95,7 @@ Click the green `+ New Team` to create a new team. Define its name, permissions
<img src="/assets/images/collaborating/create-organization/new-team.png" alt="new-team">
</picture>
You can choose whether members of the team can only access some repositories explicitly added to the team, or whether they can access all repositories of the organziation.
You can choose whether members of the team can only access some repositories explicitly added to the team, or whether they can access all repositories of the organization.
You can also allow members to be able to create new repositories for the organization.
If you have allowed repository administrators to grant or remove access for teams (see [Create an Organization](#create-an-organization) above), they can do so in `Settings > Collaborators` tab of the repository.
If you choose either `Read` or `Write` access, you can additionally define which sections of the repositories (code, issues, pull requests, releases and wiki) the members will have (read or write) access to. On the other hand, `Administrator` access automatically grants read and write access to all sections; this part of the form is therefore hidden in this case.

23
content/collaborating/pull-requests-and-git-flow.md
View file

@ -17,7 +17,7 @@ Although it is perfectly possible to use a Git project on Codeberg just as singl
### Cheat sheet
Let's say, you would like to contribute to project [Codeberg/build-deploy-gitea](https://codeberg.org/Codeberg/build-deploy-gitea).
Let's say, you would like to contribute to our "examples" project [knut/examples](https://codeberg.org/knut/examples).
First, fork the project you would like to work on, by clicking the `fork` button in the top-right corner of the project page:
@ -26,7 +26,7 @@ First, fork the project you would like to work on, by clicking the `fork` button
Then clone it onto your local machine. We assume that [you have set up your SSH keys](/security/ssh-key). This has to be done only once:
```shell
git clone git@codeberg.org:<YOURCODEBERGUSERNAME>/build-deploy-gitea.git
git clone git@codeberg.org:<YOURCODEBERGUSERNAME>/examples.git
```
Now, let's create a feature branch, do some changes, commit, push, edit, commit, push, ..., edit, commit, push:
@ -56,13 +56,16 @@ Sometimes the upstream project repository is evolving while we are working on a
In order to track the `upstream` repository, we add a second remote that is pointing to the original project. This has to be done only once:
```shell
git remote add upstream git@codeberg.org:Codeberg/build-deploy-gitea.git
git remote add upstream git@codeberg.org:knut/examples.git
```
Now, let's pull from `upstream`, and rebase our local branch against the latest `HEAD` of the upstream project repository:
You can also use the SSH variant here for public projects, if you want to be
able to pull without specifying your credentials.
Now, let's pull from `upstream`, and rebase our local branch against the latest `HEAD` of the upstream project repository (e.g. the `main` branch):
```shell
git pull --rebase upstream master
git pull --rebase upstream main
git pull
```
@ -70,4 +73,12 @@ That's it. You can now push your changes, and create the pull request as usual b
## A friendly note on owner rights, and forced push permissions
Please keep in mind that project owners can do *everything*, including editing and rewriting the history using `force-push`. In some cases this is a useful feature (for example to undo accidental commits that, say, leaked credentials), but in most cases a transparent history based on a pull-request based workflow is surely preferable.
Please keep in mind that project owners can do *everything*, including editing and rewriting the history using `force-push`. In some cases this is a useful feature
(for example to undo accidental commits or clean up PRs),
but in most cases a transparent history based on a pull-request based workflow is surely preferable,
especially for the default branches of your project where other people rely on intact history.
**Warning** If you accidentally leaked sensitive data, say, leaked credentials,
keep in mind that commits stay directly accessible, e.g. from the user
activity tab or a Pull Request feed, for a while.
Please contact us if you really need to remove such data from the public.

4
content/contact.md
View file

@ -19,12 +19,12 @@ If you need quicker help or want to freely discuss topics, or follow up on Codeb
For direct contact, you can write an email to [contact@codeberg.org](mailto:contact@codeberg.org).
## Legal inquiries
For legal inquiries, please refer to the [Imprint](https://codeberg.org/codeberg/org/src/branch/master/Imprint.md).
For legal inquiries, please refer to the [Imprint](https://codeberg.org/codeberg/org/src/Imprint.md).
### Abuse
If you notice some unwanted content on Codeberg.org, please immediately report this to us, describing briefly why you think this should be removed.
Please note that **Codeberg is a platform for software development**, and we are **only responsible for content on codeberg.org**, codeberg.page, codeberg-test.org and codeberg.eu.
Please note that **Codeberg is a platform for software development**, and we are **only responsible for content on Codeberg.org**, codeberg.page, codeberg-test.org and codeberg.eu.
If you visited Codeberg from another domain, this is likely because the software itself is developed at Codeberg.
Please reach out to the corresponding developer or to the operator of the platform directly.

2
content/getting-started/first-repository.md
View file

@ -38,7 +38,7 @@ Here's an explanation of the form's fields:
- **Template** Occasionally you may want to generate your repository from an existing template repository. In that case, you can specify that template here. Otherwise, simply leave this field empty.
- **Issue Labels** If you want to initialize your project's issue tracker with a set of labels that you can use to categorize issues, you can choose one here. You don't have to choose this right away though, as you can choose and modify issue labels at a later time too.
- **.gitignore** A [.gitignore](https://git-scm.com/docs/gitignore) file defines which files Git should not keep track of. This is for example useful to prevent project configuration files or binaries to be checked into version control. You can choose to add a pre-defined file matching the programming language you use now, or add one manually at a later time.
- **License** Here, you can choose from a list of FSF/OSI approved licenses. A `LICENSE` file will then be added to the repository. For some help on choosing the correct license, check for example the [GNU Operating System](https://www.gnu.org/licenses/license-list), the [Open Source Initiative](https://opensource.org/licenses) or the [choosealicense.com](https://choosealicense.com/) websites.
- **License** Here, you can choose from a list of FSF/OSI approved licenses. A `LICENSE` file will then be added to the repository. For some help on choosing the correct license, have a look at our [licensing article](licensing).
- **README** is the first file one should read when accessing a project. It also happens to be the first one displayed when accessing a repository, a bit like the "homepage" of your repository. On Codeberg, this is interpreted as a [Markdown](/markdown) file.
- **Initialize repository** To add the `LICENSE`, `README` and `.gitignore` files mentioned above to your new repository, make sure you tick this box.
- **Default branch** Using this field, you can choose how to name the default branch of your Git repository. We recommend you use the predefined default.

4
content/getting-started/first-steps.md
View file

@ -19,7 +19,7 @@ email account, you're done and good to go!
## Community
Codeberg is a non-profit volunteer effort. It relies on its friendly and dedicated community. We're happy that you're now a part of our community, too, and we hope you're feeling welcome!
We kindly ask you to be polite and civil when on Codeberg and to not excessively use the resources provided. Please see our [Terms of Use](https://codeberg.org/codeberg/org/src/branch/master/TermsOfUse.md) for details.
We kindly ask you to be polite and civil when on Codeberg and to not excessively use the resources provided. Please see our [Terms of Use](https://codeberg.org/codeberg/org/src/TermsOfUse.md) for details.
Please remember that everyone here is contributing on their free time, as volunteers.
@ -63,4 +63,4 @@ Now that you have an account on Codeberg.org, you can choose from a number of po
- [Create your first Repository](/getting-started/first-repository)
- [Report or Comment on an Issue](/getting-started/issue-tracking-basics)
- [Learn how to use Git](/git) and then [Contribute a Pull Request](/collaborating/pull-requests-and-git-flow)
- [Contribute to Codeberg](/improving-codeberg)
- [Contribute to Codeberg](/improving-codeberg)

8
content/getting-started/what-is-codeberg.md
View file

@ -6,7 +6,7 @@ eleventyNavigation:
order: 10
---
Codeberg is a community-driven, non-profit software development platform operated
Codeberg is a democratic community-driven, non-profit software development platform operated
by Codeberg e.V. and centered around Codeberg.org, a Gitea-based software forge.
On Codeberg you can develop your own [Free Software](https://simple.wikipedia.org/wiki/Free_software) projects, contribute to other
@ -32,12 +32,12 @@ The mission of the Codeberg e.V. is to build and maintain a free collaboration p
Dependencies on commercial, external, or proprietary services for the operation of the platform are thus decidedly avoided, in order to guarantee independence and reliability.
Read more at [Codeberg's intial announcement](https://blog.codeberg.org/codebergorg-launched.html) and the [Licensing article](/getting-started/licensing).
Read more at [Codeberg's initial announcement](https://blog.codeberg.org/codebergorg-launched.html) and the [Licensing article](/getting-started/licensing).
## Codeberg vs. Gitea
[Gitea](https://gitea.io) is a free software for Git-based software development that powers Codeberg. Compared to Codeberg, Gitea is not a hosted service, but the free software tool to build those. Everyone can install their own Gitea instance to host their own projects. There are also some Gitea instances next to Codeberg you can use, but please make sure you find a site that is actively maintained and updated, and that you trust the provider.
Beware: The official Gitea instance at [gitea.com](https://gitea.com) is only meant for development of Gitea and related products and not public use!
Beware: The official Gitea instance at [Gitea.com](https://gitea.com) is only meant for development of Gitea and related products and not public use!
People are often asking why they should use Codeberg over other Gitea instances. The most important points Codeberg adds are
- a vivid community to collaborate with and ask for help
@ -53,7 +53,7 @@ of the platform, but if you want you can [join Codeberg e.V.](https://join.codeb
support the project financially, be informed about Codeberg and, optionally, to actively
contribute to the association.
Codeberg members can also take part in the decisions of the platform as explained in the bylaws, and they elect the praesidium and board of the platform, thus Codeberg can be considered as community-owned.
Codeberg members can also take part in the decisions of the platform as explained in the bylaws, and they elect the presidium and board of the platform, thus Codeberg can be considered as community-owned.
---

6
content/git/clone-commit-via-cli.md
View file

@ -48,7 +48,7 @@ Unpacking objects: 100% (3/3), done.
Modify an existing file:
```shell
~$ cd foobar
~$ cd examples
~/examples$ nano README.md
```
@ -62,7 +62,7 @@ Command lines:
```shell
~/examples$ git commit -am 'test'
[master 10074d7] test
[main 10074d7] test
1 file changed, 2 insertions(+), 1 deletion(-)
```
@ -85,7 +85,7 @@ Compressing objects: 100% (2/2), done.
Writing objects: 100% (3/3), 266 bytes | 0 bytes/s, done.
Total 3 (delta 1), reused 0 (delta 0)
To https://codeberg.org/knut/examples.git
662e04e..10074d7 master -> master
662e04e..10074d7 main -> main
```
## Pull

16
content/git/squash-commits.md
View file

@ -12,17 +12,17 @@ Here is an example.
```bash
$ git log --graph --decorate --oneline
* cf634bb (HEAD -> master) english
* cf634bb (HEAD -> main) english
* 722a9c7 zwei
* e59e6d0 eins
* c6990ba a
* 6dfc50b (origin/master, origin/HEAD) ix
* 6dfc50b (origin/main, origin/HEAD) ix
* 10074d7 (tag: test) test
* 662e04e Initial commit
$ git status
On branch master
Your branch is ahead of 'origin/master' by 4 commits.
On branch main
Your branch is ahead of 'origin/main' by 4 commits.
(use "git push" to publish your local commits)
nothing to commit, working tree clean
@ -33,8 +33,8 @@ You want to merge the last 4 commits from `a` to `english`.
```bash
$ git reset --soft "HEAD~4"
$ git status
On branch master
Your branch is up to date with 'origin/master'.
On branch main
Your branch is up to date with 'origin/main'.
Changes to be committed:
(use "git reset HEAD <file>..." to unstage)
@ -42,13 +42,13 @@ Changes to be committed:
new file: a
$ git commit --amend
[master 24e0e06] English
[main 24e0e06] English
Date: Wed May 27 13:56:28 2020 +0200
2 files changed, 3 insertions(+), 1 deletion(-)
create mode 100644 a
$ git log --graph --decorate --oneline
* 24e0e06 (HEAD -> master) English
* 24e0e06 (HEAD -> main) English
* 10074d7 (tag: test) test
* 662e04e Initial commit
```

20
content/improving-codeberg/contributing-code.md
View file

@ -11,10 +11,12 @@ Since Codeberg uses [Gitea](https://gitea.io/) as a base, most features that go
Gitea itself is written in [Go](https://en.wikipedia.org/wiki/Go_(programming_language)), so it's best to make yourself familiar with this language first. It's focused on being a very easy and maintainable language, so it should not be a big issue if you haven't heard of it yet.
Also check out the [Codeberg](https://codeberg.org/Codeberg) and [Codeberg-Infrastructure](https://codeberg.org/Codeberg-Infrastructure) organizations, they contain numerous other software and setup projects that will appreciate your contributions.
## Where do patches go?
We currently sort patches on the following criteria:
- Changes in deployments and config goes to the [Codeberg/build-deploy-gitea](https://codeberg.org/Codeberg/build-deploy-gitea) repo. It holds the scripts used to set up the Codeberg instance and overrides other changes, so have a look at it in any case!
- Changes in deployments and config goes to the [Codeberg-Infrastructure/build-deploy-gitea](https://codeberg.org/Codeberg-Infrastructure/build-deploy-gitea) repo. It holds the scripts used to set up the Codeberg instance and overrides other changes, so have a look at it in any case!
- Changes that benefit the general Gitea user base should go into the [upstream repo](https://github.com/go-gitea/gitea). Contributions there also help improve Codeberg, so consider raising a merge request there to help all instances of Gitea
- A small set of patches are committed directly into the [Codeberg/gitea](https://codeberg.org/Codeberg/gitea) repo. These include:
- (Non-configurable) template changes or small tweaks that are not intended for upstream
@ -28,17 +30,21 @@ So let's put our hands-on and start hacking. If you don't already have an issue
### Working with the `build-deploy-gitea` repo
The deployment of Codeberg is handled via the [Codeberg/build-deploy-gitea](https://codeberg.org/Codeberg/build-deploy-gitea) repository which also contains the code of the Codeberg pages feature. While there's some work on different deployment approaches (more to that later), this is the way stuff is handled as of today.
This is a legacy deployment system for our infrastructure, it updates, builds, configures and deploys Gitea.
If you want to work on new features, please don't use it, but choose our [Gitea fork](https://codeberg.org/Codeberg/gitea) instead.
You shouldn't normally need to bother running it.
The deployment of Codeberg is handled via the [Codeberg/build-deploy-gitea](https://codeberg.org/Codeberg/build-deploy-gitea) repository. While there's some work on different deployment approaches (more to that later), this is the way stuff is handled as of today.
The deployment Makefile connects to a remote server via ssh, so we recommend configuring a virtual machine for this. You can use the provided script or perform the following tasks inside your favourite VM / container solution:
- Add a user and group git
- Provide SSH to root
- Set up a MySQL database `gitea` end enter the credentials into your app.ini
- Install at least `git make nodejs npm openssh-server librsvg2-bin` (example package names from Debian Buster)
- Run the makefile and see that Gitea is installed, you can override variables and run it like `make HOSTNAME_FQDN=localhost deployment`
- Run the Makefile and see that Gitea is installed, you can override variables and run it like `make HOSTNAME_FQDN=localhost deployment`
- After Gitea is installed, you might want to create an admin user for testing (should otherwise be first user by default), you can use `sudo -u git GITEA_WORK_DIR=/data/git GITEA_CUSTOM/etc/gitea /data/git/bin/gitea admin create-user --username you --admin --password yourpassword --email youremail@example.com`
Please see the deployment repo for the folder structure as well as the [upstream docs](https://docs.gitea.io/en-us/) on how to configure and hack on Gitea.
Also note that the Makefile compiles Codeberg's Gitea fork from the `codeberg-test` branch by default. You can override this behaviour by specifying `ORIGIN` and `GITEA_BRANCH` environment to the Makefile.
Also note that the Makefile might compile Codeberg's Gitea fork from the `codeberg-test` branch by default. You can override this behaviour by specifying `ORIGIN` and `GITEA_BRANCH` environment to the Makefile.
### Working with the Gitea codebase
@ -46,7 +52,7 @@ Please look at [the Gitea docs](https://docs.gitea.io/en-us/hacking-on-gitea/) o
### Raising an MR to our Gitea fork
If you fixed an issue specific to Codeberg that should not go into the upstream repo or was refused there, but fits the criteria for our own repo written above, you can file an MR to [our own fork of Gitea](https://codeberg.org/Codeberg/gitea). Make sure to point your MR to the codeberg branch and rebase to the latest commits there. Also explain why this should go into the Codeberg repo, if not obvious.
If you fixed an issue specific to Codeberg that should not go into the upstream repo or was refused there, but fits the criteria for our own repo written above, you can file an MR to [our own fork of Gitea](https://codeberg.org/Codeberg/gitea). Make sure to point your MR to the `codeberg` branch and rebase to the latest commits there. Also explain why this should go into the Codeberg repo, if not obvious.
> **Warning** Please note, that the branches may be force-pushed at
> certain times to make sure the Codeberg commits are well visible and
@ -62,7 +68,9 @@ If you fixed an issue specific to Codeberg that should not go into the upstream
### Working on better deployment methods
If you want to help us improve our deployment scripts, check out the [Codeberg-Infrastructure organization](https://codeberg.org/Codeberg-Infrastructure) (only visible when logged in) and check out eventual configuration. We'd really appreciate moving away from Makefile and shell scripts and ask you to join the discussion there. Please make sure to first understand what the `build-deploy-gitea` repo does to replicate its function. Also feel free to contact us (for example via Matrix) to ask where to help.
If you want to help us improve our deployment scripts, check out the [Codeberg-Infrastructure organization](https://codeberg.org/Codeberg-Infrastructure). We'd really appreciate moving away from Makefile and shell scripts and ask you to join the discussion there.
If you are interested in supporting this project, feel free to contact us. Some legacy resources or WIP might be still invisible to normal users (although we always try to work publicly when possible).
Please make sure to first understand what the `build-deploy-gitea` repo does to replicate its function. Also feel free to contact us (for example via Matrix) to ask where to help.
## Still questions?

4
content/improving-codeberg/docs-contributor-faq.md
View file

@ -53,7 +53,7 @@ After the header is in place, you can now start writing your article in Markdown
> Please do not repeat the article's title as a first-level heading in Markdown. It will added automatically when generating the final site.
### Can I preview my article?
Yes, but currently only if you're working with a local clone of the repository. In that case, simply follow the instructions in the [`README.md`](https://codeberg.org/codeberg/documentation/src/branch/master/README.md) file to set up and run a local preview.
Yes, but currently only if you're working with a local clone of the repository. In that case, simply follow the instructions in the [`README.md`](https://codeberg.org/codeberg/documentation/src/README.md) file to set up and run a local preview.
It is recommended to set this up, because it can help you a lot in spotting errors that would otherwise go unnoticed, especially aesthetic errors and broken links.
@ -64,7 +64,7 @@ Please adhere to [kebab-Case](https://en.wikipedia.org/wiki/Kebab_case) naming r
### When is my contribution being approved?
A Pull Request to Codeberg/Documentation will be reviewed by at least one other Codeberg Documentation collaborators and if your Pull Request is approved, they will merge it into master.
A Pull Request to Codeberg/Documentation will be reviewed by at least one other Codeberg Documentation collaborators and if your Pull Request is approved, they will merge it into the main branch.
There are a number of exceptions to the rule above:
- For bugfixes and other small and non-controversial changes, the process is much simplified - here it is enough for one collaborator to green-light and merge the changes. If you're already a collaborator yourself, feel free to merge right away (after sufficient testing, that is).

20
content/improving-codeberg/index.md
View file

@ -21,21 +21,31 @@ commercial software forges, such as GitHub, GitLab or Bitbucket.
By joining and using Codeberg, you're already helping our mission a lot - thank you!
And as always: Spread the word, tell your friends and invite them to collaborate on Codeberg with you :-)
### Contribute to Codeberg
Do you have ideas on improving Codeberg? Have you found a bug and would like to report (or even fix) it? You're welcome to contribute to Codeberg, for example by [creating or commenting an Issue](https://codeberg.org/Codeberg/Community/issues) or by [writing a
Do you have ideas on improving Codeberg? Have you found a bug and would like to report (or even fix) it? You're welcome to contribute to Codeberg, for example by [creating or commenting on an Issue](https://codeberg.org/Codeberg/Community/issues) or by [writing a
pull request](/collaborating/pull-requests-and-git-flow) to one of Codeberg's projects.
You can read more about the code contribution workflow in [this article](contributing-code)
If you are not fond of doing codework, feel free to step up for some maintenance roles like Community Support, Social Media and more. Just drop us an email, or consider [Joining Codeberg](#join-codeberg-e.v.) where you'll get easier access to internal teams and task forces. Also, you can always [work on the Codeberg Docs](docs-contributor-faq).
Codeberg explicitly welcomes newcomers or career changers to its repos, and we will gladly mentor you as resources permit.
If you have questions, always feel free to ask in the Issue Trackers or on the Matrix Channels mentioned on the [Contact page](/contact).
Even tiny patches or suggestions, even if you are not a skilled developer, will be considered and are part of the community-maintenance mission of Codeberg.
You can read more about the code contribution workflow in [this article](contributing-code).
Contributions are warmly welcome, everyone is invited!
### Donate to Codeberg
You can [donate to Codeberg e.V. using Liberapay](https://liberapay.com/codeberg/donate)
or [by SEPA wire transfer](https://codeberg.org/codeberg/org/src/branch/master/Imprint.md#user-content-sepa-iban-for-donations).
or [by SEPA wire transfer](https://codeberg.org/codeberg/org/src/Imprint.md#user-content-sepa-iban-for-donations).
Donations not only allow us to operate and scale the infrastructure behind Codeberg, but to develop the products that make Codeberg possible.
Codeberg is not an arbitrary Gitea instance, but commits itself into actively developing the software ecosystem around.
Codeberg e.V. is the non-profit organization behind Codeberg.org.
It's based in Berlin, Germany and [recognized as tax-exempt](https://codeberg.org/codeberg/org/src/branch/master/Imprint.md#user-content-gemeinn%C3%BCtzigkeit-recognition-of-status-as-non-profit-ngo-recognition-as-tax-excempt-entity) by the German authorities.
It's based in Berlin, Germany and [recognized as tax-exempt](https://codeberg.org/codeberg/org/src/Imprint.md#user-content-gemeinn%C3%BCtzigkeit-recognition-of-status-as-non-profit-ngo-recognition-as-tax-excempt-entity) by the German authorities.
### Join Codeberg e.V.
If you're interested in committing even more to Codeberg, consider [joining Codeberg e.V.](https://join.codeberg.org), the non-profit association behind Codeberg.org.

2
content/integrations/index.md
View file

@ -8,4 +8,4 @@ eleventyNavigation:
These documentation pages contain information on how you can use third-party software with Codeberg.
See also [awesome-gitea](https://gitea.com/gitea/awesome-gitea/src/branch/master/README.md) which lists projects that work with Gitea, the software which Codeberg is based on.
See also [awesome-gitea](https://gitea.com/gitea/awesome-gitea/src/README.md) which lists projects that work with Gitea, the software which Codeberg is based on.

2
content/security/ssh-fingerprint.md
View file

@ -31,7 +31,7 @@ SHA256:T9FYDEHELhVkulEKKwge5aVhVTbqCW0MIRwAfpARs/E codeberg.org (ECDSA)
SHA256:mIlxA9k46MmM6qdJOdMnAQpzGxF4WIVVL+fj+wZbw0g codeberg.org (ED25519)
```
These are the SHA256 versions of **[the fingerprints published in the Imprint](https://codeberg.org/codeberg/org/src/branch/master/Imprint.md#user-content-ssh-fingerprints)**,
These are the SHA256 versions of **[the fingerprints published in the Imprint](https://codeberg.org/codeberg/org/src/Imprint.md#user-content-ssh-fingerprints)**,
which are to be considered the authoritative fingerprints for Codeberg.
**If they match, you're good to go** and can safely use Codeberg via SSH.