mirror of
https://codeberg.org/forgejo/docs.git
synced 2024-11-24 18:09:26 -05:00
64fe34712f
Rename Developer to Contributor guide - I believe this sounds more inclusive and likely improves the diversity of contributors. Separate translation section clarify external resources Add links to UI/UX and user research repos Separate issue tracker and discussions - I imagine this is part of the confusion for people who report bugs to the discussion tracker. Add welcome section Reviewed-on: https://codeberg.org/forgejo/docs/pulls/821 Reviewed-by: Gusted <gusted@noreply.codeberg.org> Co-authored-by: Otto Richter <git@otto.splvs.net> Co-committed-by: Otto Richter <git@otto.splvs.net>
1.4 KiB
1.4 KiB
| title | license |
|---|---|
| Bugs, features and discussions | CC-BY-SA-4.0 |
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 governance
- the Code of Conduct
- the sustainability and funding.
Other discussions regarding all non technical aspects of Forgejo, happen in a dedicated 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.