Developer manual: recommend a SECURITY.md in publishing.rst
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Domain
- documentation
Research direction
Edit developer_manual/app_publishing_maintenance/publishing.rst, starting with the app security-reporting guidance already described there. Add the recommendation for an app repository SECURITY.md and link the nextcloud/.github SECURITY.md as the example. Done means both checklist items are covered clearly in the rendered documentation.
Written by the indexing model from the issue text.
Description
The app guidelines ask authors to respond to security reports in good time, but developer_manual/app_publishing_maintenance/publishing.rst doesn't say how to tell people where to report.
- Recommend a
SECURITY.mdin the app repository, saying how security issues are reported to the app's developers. - Link the org's file as an example: https://github.com/nextcloud/.github/blob/master/SECURITY.md
- Dominant language
- JavaScript
- Stars
- 632
- Forks
- 2.5k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 96
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from nextcloud/documentation
-
0. needs triage enhancement manual: developer security
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/documentation#15693 ·
Maintainers usually reply within 1 day
-
0. needs triage bug developer experience manual: developer
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
nextcloud/documentation#15690 ·
Maintainers usually reply within 1 day
-
0. needs triage developer experience enhancement good first issue manual: developer
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
nextcloud/documentation#15687 ·
Maintainers usually reply within 1 day
-
0. needs triage enhancement good first issue manual: developer
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
nextcloud/documentation#15685 ·
Maintainers usually reply within 1 day
-
0. needs triage enhancement feature: emails good first issue manual: developer security
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
nextcloud/documentation#15683 ·
Maintainers usually reply within 1 day
All issues in nextcloud/documentation
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CopilotKit/aimock#491 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
keyxmakerx/Chronicle#967 ·
Maintainers usually reply within 1 day
-
good first issue hacktoberfest
Difficulty 1/5 Under an hour Newbie friendliness 92/100
RogueAlg0/taken#386 · 3 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
DietrichGebert/ponytail#978 ·
Maintainers usually reply within 2 days
-
bug component: bulk editor support
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Yoast/wordpress-seo#23669 ·
Maintainers usually reply within 3 days