caleb-brown/redict
1
0
Fork 0
mirror of https://codeberg.org/redict/redict.git synced 2025-01-22 08:08:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update top-level documentation

Browse Source 
Signed-off-by: Drew DeVault <sir@cmpwn.com>
This commit is contained in:
Drew DeVault 2024-03-22 13:41:07 +01:00
parent a032cb972a
commit 7e623bafcc
3 changed files with 5 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
CODE_OF_CONDUCT.md
View File

@ -49,7 +49,7 @@ representative at an online or offline event.
Enforcement Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at reported to the community leaders responsible for enforcement at
this email address: redis@redis.io. this email address: sir@cmpwn.com. (Note: this is a temporary measure)
All complaints will be reviewed and investigated promptly and fairly. All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the All community leaders are obligated to respect the privacy and security of the
reporter of any incident. reporter of any incident.

4
CONTRIBUTING.md
View File

@ -1,5 +1,7 @@
Contributors to Redict are asked to agree to the [Developer Certificate of Contributors to Redict are asked to agree to the [Developer Certificate of
Origin][0] when contributing code to the project: Origin][0] when contributing code to the project, reproduced below. To indicate
that you agree to the DCO, please use `git commit -s` to "sign-off" your
changes when contributing.
[0]: https://developercertificate.org/ [0]: https://developercertificate.org/

42
SECURITY.md
View File

@ -1,43 +1,3 @@
# Security Policy # Security Policy
## Supported Versions (To be updated following fork)
Redis is generally backwards compatible with very few exceptions, so we
recommend users to always use the latest version to experience stability,
performance and security.
We generally backport security issues to a single previous major version,
unless this is not possible or feasible with a reasonable effort.
| Version | Supported |
| ------- | ------------------ |
| 7.2.x | :white_check_mark: |
| 7.0.x | :white_check_mark: |
| 6.2.x | :white_check_mark: |
| < 6.2 | :x: |
## Reporting a Vulnerability
If you believe you've discovered a serious vulnerability, please contact the
Redis core team at redis@redis.io. We will evaluate your report and if
necessary issue a fix and an advisory. If the issue was previously undisclosed,
we'll also mention your name in the credits.
## Responsible Disclosure
In some cases, we may apply a responsible disclosure process to reported or
otherwise discovered vulnerabilities. We will usually do that for a critical
vulnerability, and only if we have a good reason to believe information about
it is not yet public.
This process involves providing an early notification about the vulnerability,
its impact and mitigations to a short list of vendors under a time-limited
embargo on public disclosure.
Vendors on the list are individuals or organizations that maintain Redis
distributions or provide Redis as a service, who have third party users who
will benefit from the vendor's ability to prepare for a new version or deploy a
fix early.
If you believe you should be on the list, please contact us and we will
consider your request based on the above criteria.