`Server` security advisories link/section should link to/reference `nextcloud/security-advisories` repo rather than appearing empty
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Problem
The security advisories link/section located at https://github.com/nextcloud/server/security is misleading because it is empty.
Cause
All advisories are actually located in their own repository https://github.com/nextcloud/security-advisories/security/advisories so there should be a link to that instead.
Possible Solution(s)
I'm not sure if the security advisories link/section can be changed to point at another repository (AFAIK it cannot), but perhaps a placeholder advisory can be created in the server one that contains something like:
Note: Our advisories are centrally maintained and available at https://github.com/nextcloud/security-advisories/security/advisories.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the server repository's GitHub Security page and compare it with the linked nextcloud/security-advisories security-advisories page. Check whether GitHub supports directing the section to another repository; if not, assess the placeholder-advisory option. Done means the server security page clearly directs users to the centrally maintained advisories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100