PowerDNS
Consider creating a `.github` repository with a `SECURITY.md` file on the default branch
- Program: Other
- Issue type: Feature request
Short description
This repository has a security policy which is visible on https://github.com/PowerDNS/pdns/security. For any repository that's created in this org (either by forking another org, or just as a source) unless someone has created a SECURITY.md file, the /security route will show:
https://github.com/PowerDNS/pdns-builder/security
...And hopefully:
Usecase
In the case of a fork, it's helpful to say "this is a fork from somewhere else, you should really contact them instead of us". In the case of a home grown repo, it's helpful to point people somewhere -- and given that this org does have capacity to handle Security advisories, it makes sense to have a thing.
Description
Have a file SECURITY.md in a repo called .github.
It could probably be derived from https://github.com/PowerDNS/pdns/blob/master/SECURITY.md with some changes to remove references to PowerDNS and DNSdist and to add some notes about forks.
