django-commons / django-commons/controls
Review security practices with team and reach out to projects
Open
Nobody has claimed this yet.
documentation
security
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- Avg merge
- 18m
- Merged PRs (30d)
- 1
Description
- Review security team responsibilities with the security team (Matthias and Carlton, need to check the list)
- Define the "default" security.yml file for project in best-practices repo
- Reach out to projects and offer support with security issues if they adopt the security.yml file and pattern
Contributor guide
No contributing guide indexed for this repository
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 by reviewing the security team responsibilities with Matthias and Carlton, including the list that still needs checking. Then define the default security.yml pattern in the best-practices repository and document the outreach needed for projects adopting it; done means the responsibilities, default pattern, and support process are agreed and recorded.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100