|
2 | 2 |
|
3 | 3 | ## Introduction
|
4 | 4 |
|
5 |
| -First off, thank you for considering contributing to redis-py. We value |
6 |
| -community contributions! |
| 5 | +We appreciate your interest in considering contributing to redis-py. |
| 6 | +Community contributions mean a lot to us. |
7 | 7 |
|
8 |
| -## Contributions We Need |
| 8 | +## Contributions we need |
9 | 9 |
|
10 |
| -You may already know what you want to contribute \-- a fix for a bug you |
| 10 | +You may already know how you'd like to contribute, whether it's a fix for a bug you |
11 | 11 | encountered, or a new feature your team wants to use.
|
12 | 12 |
|
13 |
| -If you don't know what to contribute, keep an open mind! Improving |
| 13 | +If you don't know where to start, consider improving |
14 | 14 | documentation, bug triaging, and writing tutorials are all examples of
|
15 | 15 | helpful contributions that mean less work for you.
|
16 | 16 |
|
@@ -166,19 +166,19 @@ When filing an issue, make sure to answer these five questions:
|
166 | 166 | 4. What did you expect to see?
|
167 | 167 | 5. What did you see instead?
|
168 | 168 |
|
169 |
| -## How to Suggest a Feature or Enhancement |
| 169 | +## Suggest a feature or enhancement |
170 | 170 |
|
171 | 171 | If you'd like to contribute a new feature, make sure you check our
|
172 | 172 | issue list to see if someone has already proposed it. Work may already
|
173 |
| -be under way on the feature you want -- or we may have rejected a |
| 173 | +be underway on the feature you want or we may have rejected a |
174 | 174 | feature like it already.
|
175 | 175 |
|
176 | 176 | If you don't see anything, open a new issue that describes the feature
|
177 | 177 | you would like and how it should work.
|
178 | 178 |
|
179 |
| -## Code Review Process |
| 179 | +## Code review process |
180 | 180 |
|
181 |
| -The core team looks at Pull Requests on a regular basis. We will give |
182 |
| -feedback as as soon as possible. After feedback, we expect a response |
| 181 | +The core team regularly looks at pull requests. We will provide |
| 182 | +feedback as as soon as possible. After receiving our feedback, please respond |
183 | 183 | within two weeks. After that time, we may close your PR if it isn't
|
184 | 184 | showing any activity.
|
0 commit comments