mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-14 18:24:14 +01:00
d5b78a53fe
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 commit6577fad1c9
)
1.3 KiB
1.3 KiB
Bugs, features and discussions
The Forgejo issue tracker is where bugs should be reported and features requested.
Dedicated repositories in the Forgejo organization cover areas such as:
- the website
- the Code of Conduct
- the sustainability and funding.
Other discussions regarding all non technical aspects of Forgejo, such as the governance, happen in the meta issue tracker and in the matrix chatroom.
Security
The security team takes care of security vulnerabilities. It handles sensitive security-related issues reported to security@forgejo.org using encryption.
The security team also keeps the content of the security.txt file up to date.
The private GPG key for security@forgejo.org
is shared among all members of the security team and not stored online.