Create SECURITY.rst

[vanillajonathan]

This file is used by GitHub in the security tab.
https://github.com/python/cpython/security/policy

[the-knights-who-say-ni]

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on bugs.python.org (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for your contribution, we look forward to reviewing it!

[asvetlov]

The PR duplicates #13526 I guess

[asvetlov]

Thank you for your contribution.
Sorry, #13526 has merged.
Closing this PR as duplicated.

[webknjaz]

@vanillajonathan FTR, a lot of projects maintain their own pages with docs so the best thing to do is to redirect people there instead of forcing maintainers to watch out for multiple places to update...

btw, are you sure that RST works for this specific file? I wasn't able to locate this in docs

[vanillajonathan]

Yes, reStructuredText works for the security file on GitHub.
Example: https://github.com/apache/airflow/security/policy

[asvetlov]

Actually, it is a shared part of both Markdown and ReST syntax.
The link to devguide page is preferred anyway for sake of keeping Python versions status information in the single place.

[webknjaz]

Andrew, I think it's a good idea to keep all files with one extension for the sake of consistency

[asvetlov]

I don't care.
Ok with committed code.