mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-12-11 12:03:27 +01:00
5b4d25bd03
Refs: https://codeberg.org/forgejo/forgejo/issues/8 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/153 Refs: https://codeberg.org/forgejo/forgejo/issues/123 Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/299 (cherry picked from commit08dcef0c8c) [DOCS] CONTRIBUTING/RELEASE: https://forgejo.org/docs/admin Because the version is not displayed on the landing page of Forgejo, there cannot be a link to a versionned documentation. There must exist a link that points to the latest version on the website for the forgejo instance to display. Better but more complicated approaches could be to: * Embed the documentation in Forgejo * Allow the admin to not display the help * Allow the admin to display a versionned help or not (cherry picked from commit83cc389239) (cherry picked from commit5df52b8a4f) (cherry picked from commit9a66b3d70b) [DOCS] CONTRIBUTING/RELEASE: reminder to update FORGEJO_VERSION (cherry picked from commit2a4d0bd164) (cherry picked from commitd68576ba67) [DOCS] CONTRIBUTING: updates * Remove obsolete description of the well being & moderation team and replace them with a link to the moderation email. * Remove description of the governance process and replace with a link to the governance readme that did not exist at the time. * Add links to the Forgejo documentation (cherry picked from commitdf749da272) (cherry picked from commit4da39128c5) (cherry picked from commitf442ca6f40) (cherry picked from commit031928c447) (cherry picked from commit1e6ba47216) (cherry picked from commit8916a1f8c6) (cherry picked from commit663e28c412) (cherry picked from commitd56b130baa) [DOCS] CONTRIBUTING (squash) (cherry picked from commit0dc4b6e5c9) (cherry picked from commit52f2163807) (cherry picked from commit47d0ae3e10) (cherry picked from commit7757a5c34c)
23 lines
1.2 KiB
Markdown
23 lines
1.2 KiB
Markdown
# Forgejo Contributor Guide
|
|
|
|
The Forgejo project is run by a community of people who are expected to follow this guide when cooperating on a simple bug fix as well as when changing the governance. For more information about the project, take a look at [the documentation explaining what Forgejo provides](README.md).
|
|
|
|
Sensitive security-related issues should be reported to [security@forgejo.org](mailto:security@forgejo.org) using [encryption](https://keyoxide.org/security@forgejo.org).
|
|
|
|
## For everyone involved
|
|
|
|
- [Documentation](https://forgejo.org/docs/next/)
|
|
- [Code of Conduct](https://forgejo.org/docs/next/developer/COC/)
|
|
- [Bugs, features, security and others discussions](https://forgejo.org/docs/next/developer/DISCUSSIONS/)
|
|
- [Governance](https://forgejo.org/docs/next/developer/GOVERNANCE/)
|
|
- [Sustainability and funding](https://codeberg.org/forgejo/sustainability/src/branch/master/README.md)
|
|
|
|
## For contributors
|
|
|
|
- [Developer Certificate of Origin (DCO)](https://forgejo.org/docs/next/developer/DCO/)
|
|
- [Development workflow](https://forgejo.org/docs/next/developer/WORKFLOW/)
|
|
|
|
## For maintainers
|
|
|
|
- [Release management](https://forgejo.org/docs/next/developer/RELEASE/)
|
|
- [Secrets](https://forgejo.org/docs/next/developer/SECRETS/)
|