mirror of
https://codeberg.org/forgejo/forgejo
synced 2024-11-30 05:36:07 +01:00
19 lines
1.3 KiB
Markdown
19 lines
1.3 KiB
Markdown
|
# Bugs, features and discussions
|
||
|
|
|
||
|
|
The [Forgejo issue tracker](https://codeberg.org/forgejo/forgejo/issues) is where **bugs** should be reported and **features** requested.
|
||
|
|
|
||
|
|
Dedicated repositories in the [Forgejo organization](https://codeberg.org/forgejo) cover areas such as:
|
||
|
|
- the [website](https://codeberg.org/forgejo/website)
|
||
|
|
- the [Code of Conduct](https://codeberg.org/forgejo/code-of-conduct)
|
||
|
|
- the [sustainability and funding](https://codeberg.org/forgejo/sustainability).
|
||
|
|
|
||
|
|
Other discussions regarding all **non technical aspects** of Forgejo, such as the governance, happen in the [meta issue tracker](https://codeberg.org/forgejo/meta/issues) and in the [matrix chatroom](https://matrix.to/#/#forgejo-chat:matrix.org).
|
||
|
|
|
||
|
|
# Security
|
||
|
|
|
||
|
|
The [security team](https://codeberg.org/forgejo/meta/src/branch/readme/TEAMS.md#security) takes care of security vulnerabilities. It handles sensitive security-related issues reported to [security@forgejo.org](mailto:security@forgejo.org) using [encryption](https://keyoxide.org/security@forgejo.org).
|
||
|
|
|
||
|
|
The security team also keeps the content of the [security.txt](https://codeberg.org/forgejo/website/src/branch/main/public/.well-known/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.
|