nextcloud / nextcloud/nextcloudpi
E-mail for security issue
Open
Nobody has claimed this yet.
good first issue
has-updates
- Dominant language
- Shell
- Stars
- 2.9k
- Forks
- 318
- PR merge metrics
- No merged PRs in 30d
Description
The github issue categories recommend to contact nacho in case of security issues by mail.
Does it make sense to change that mail to a more general one or even to one of @theCalcaholic
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
No file or test is named. Start by locating the GitHub issue-category configuration containing the security-contact email, then confirm which general address maintainers want to use. Done means the category points to the agreed security contact and the rendered issue guidance is accurate.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100