dallasgroot/Documentation
1
0
Fork 0
mirror of https://codeberg.org/Codeberg/Documentation.git synced 2026-06-16 05:13:54 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions
Documentation/content/improving-codeberg/contributing-code.md

52 lines
3.2 KiB
Markdown
Raw Normal View History

Some instructions for improving the platform
2021-02-27 01:27:50 -08:00
---
eleventyNavigation:
key: ContributingCode
title: Contributing Code
parent: ImprovingCodeberg
---
Refresh Contact, Getting Started, Contributing Pages (#394) 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>
2024-02-17 14:04:10 -08:00
Hey there, thank you for heading here and your interest in improving Codeberg. This page is intended to give you a quick start on how and where to contribute code to the platform of Codeberg itself.
The various projects move at their own pace,
so if you already know where you are going to contribute to,
check out their own contributing guides or get in touch with the maintainers.
Updated the Code contribution documentation Applied some small textual improvements and fixed typo. Signed-off-by: Lenz Grimmer <lenzgr@noreply.codeberg.org>
2021-05-13 04:49:19 -07:00
Refresh Contact, Getting Started, Contributing Pages (#394) 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>
2024-02-17 14:04:10 -08:00
The following projects always need a helping hand:
Some instructions for improving the platform
2021-02-27 01:27:50 -08:00
Refresh Contact, Getting Started, Contributing Pages (#394) 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>
2024-02-17 14:04:10 -08:00
- [Forgejo](https://forgejo.org/), the software that powers Codeberg.org and all the Git features
- [Weblate](https://weblate.org), the localization platform available at [translate.codeberg.org](https://translate.codeberg.org)
- [Woodpecker CI](https://woodpecker-ci.org), our hosted CI/CD solution.
- [Codeberg Pages](https://codeberg.org/Codeberg/pages-server/), a service that allows you to serve static websites from Git repositories, see [codeberg.page](https://codeberg.page)
Diverse changes (#189) 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>
2022-01-21 02:36:38 -08:00
Refresh Contact, Getting Started, Contributing Pages (#394) 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>
2024-02-17 14:04:10 -08:00
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.
Improve 'Contributing Code' guide (#326) * Improve references to Forgejo and Gitea * Point reader to potentially good first issues * Be more specific as to what kinds of patches can be submitted to the `Codeberg/forgejo` repository * Explain how easy Go can be for beginners better * Include some advice as to what a prospective contributor can work on based on personal experiences Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/326
2023-08-22 06:17:52 -07:00
Refresh Contact, Getting Started, Contributing Pages (#394) 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>
2024-02-17 14:04:10 -08:00
## Getting Started
Improve 'Contributing Code' guide (#326) * Improve references to Forgejo and Gitea * Point reader to potentially good first issues * Be more specific as to what kinds of patches can be submitted to the `Codeberg/forgejo` repository * Explain how easy Go can be for beginners better * Include some advice as to what a prospective contributor can work on based on personal experiences Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/326
2023-08-22 06:17:52 -07:00
Refresh Contact, Getting Started, Contributing Pages (#394) 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>
2024-02-17 14:04:10 -08:00
Having a lot of options to choose from is hard.
We maintain a place for [all contributions to Codeberg](https://codeberg.org/Codeberg/Contributing) and you should read there.
If you don't know where to start, go ahead and introduce yourself there.
We'll try to match you with relevant and interesting tasks.
Improve 'Contributing Code' guide (#326) * Improve references to Forgejo and Gitea * Point reader to potentially good first issues * Be more specific as to what kinds of patches can be submitted to the `Codeberg/forgejo` repository * Explain how easy Go can be for beginners better * Include some advice as to what a prospective contributor can work on based on personal experiences Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/326
2023-08-22 06:17:52 -07:00
Refresh Contact, Getting Started, Contributing Pages (#394) 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>
2024-02-17 14:04:10 -08:00
## Finding issues to work on
Improve 'Contributing Code' guide (#326) * Improve references to Forgejo and Gitea * Point reader to potentially good first issues * Be more specific as to what kinds of patches can be submitted to the `Codeberg/forgejo` repository * Explain how easy Go can be for beginners better * Include some advice as to what a prospective contributor can work on based on personal experiences Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/326
2023-08-22 06:17:52 -07:00
The following issue trackers may contain a few ideas for things that could be worked on:
- [Codeberg Community Tracker](https://codeberg.org/Codeberg/Community/issues?&state=open&labels=338)
- [Forgejo Issue Tracker](https://codeberg.org/forgejo/forgejo/issues)
We also recommend working on changes that *personally* bother you first. Something in the direction of simple UI changes changes would probably make the most sense, as they are the easiest to get started with and will help you get more acquainted with the codebase (which could help you solve more complicated problems later) in the process.
Solving easy problems helps a lot too! It makes Codeberg's underlying software look much more polished; it also lets other contributors use more of their limited time to solve very sophisticated or unexpected problems.
In the *Codeberg Community Tracker*, there are some issues that are marked using the [`contribution welcome`](https://codeberg.org/Codeberg/Community/issues?&state=open&labels=105) tag. This tag is meant to show that we would really appreciate your help here. They also act as a good starting point if you are looking for something to work on.
Some instructions for improving the platform
2021-02-27 01:27:50 -08:00
improve the wording in the contribute page (#253) * `build-deploy-gitea` is not legacy in the sense that it still is in use * replace "it" with `build-deploy-gitea` for clarity. Signed-off-by: Loïc Dachary <loic@dachary.org> Co-authored-by: Loïc Dachary <loic@dachary.org> Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/253 Co-authored-by: Loïc Dachary <dachary@noreply.codeberg.org> Co-committed-by: Loïc Dachary <dachary@noreply.codeberg.org>
2022-08-05 13:20:27 -07:00
## More questions?
Some instructions for improving the platform
2021-02-27 01:27:50 -08:00
Improve 'Contributing Code' guide (#326) * Improve references to Forgejo and Gitea * Point reader to potentially good first issues * Be more specific as to what kinds of patches can be submitted to the `Codeberg/forgejo` repository * Explain how easy Go can be for beginners better * Include some advice as to what a prospective contributor can work on based on personal experiences Reviewed-on: https://codeberg.org/Codeberg/Documentation/pulls/326
2023-08-22 06:17:52 -07:00
If you need help or feel stuck, need inspiration or advice, you can always reach out to us in our [Contributing to Codeberg Matrix Channel](https://matrix.to/#/#contributing-to-codeberg:kle.li).
A more comprehensive list of our chatrooms can be found in the [Codeberg Matrix Space](https://matrix.to/#/#codeberg-space:matrix.org).
Some instructions for improving the platform
2021-02-27 01:27:50 -08:00
Thank you very much for your interest in improving Codeberg.
Reference in a new issue Copy permalink