You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Tom McCarthy |[cakepietoast](https://github.com/cakepietoast)| MongoDB |
55
-
| Nicolas Moutschen |[nmoutschen](https://github.com/nmoutschen)|Amazon|
55
+
| Nicolas Moutschen |[nmoutschen](https://github.com/nmoutschen)|Apollo|
56
56
57
57
## Labels
58
58
@@ -100,7 +100,9 @@ Be aware of recurring ambiguous situations and [document them](#common-scenarios
100
100
101
101
### Uphold Code of Conduct
102
102
103
-
Model the behavior set forward by the [Code of Conduct](CODE_OF_CONDUCT.md) and raise any violations to other maintainers and admins. There could be unusual circumstances where inappropriate behavior does not immediately fall within the [Code of Conduct](CODE_OF_CONDUCT.md). These might be nuanced and should be handled with extra care - when in doubt, do not engage and reach out to other maintainers and admins.
103
+
Model the behavior set forward by the [Code of Conduct](CODE_OF_CONDUCT.md) and raise any violations to other maintainers and admins. There could be unusual circumstances where inappropriate behavior does not immediately fall within the [Code of Conduct](CODE_OF_CONDUCT.md).
104
+
105
+
These might be nuanced and should be handled with extra care - when in doubt, do not engage and reach out to other maintainers and admins.
104
106
105
107
### Prioritize Security
106
108
@@ -152,14 +154,14 @@ RFC is a collaborative process to help us get to the most optimal solution given
152
154
153
155
Make sure you ask these questions in mind when reviewing:
154
156
155
-
* Does it use our [RFC template](https://github.com/awslabs/aws-lambda-powertools-python/issues/new?assignees=&labels=RFC%2Ctriage&template=rfc.yml&title=RFC%3A+TITLE)?
156
-
* Does the match our [Tenets](https://awslabs.github.io/aws-lambda-powertools-python/latest/#tenets)?
157
-
* Does the proposal address the use case? If so, is the recommended usage explicit?
158
-
* Does it focus on the mechanics to solve the use case over fine-grained implementation details?
159
-
* Can anyone familiar with the code base implement it?
160
-
* If approved, are they interested in contributing? Do they need any guidance?
161
-
* Does this significantly increase the overall project maintenance? Do we have the skills to maintain it?
162
-
* If we can't take this use case, are there alternative projects we could recommend? Or does it call for a new project altogether?
157
+
- Does it use our [RFC template](https://github.com/awslabs/aws-lambda-powertools-python/issues/new?assignees=&labels=RFC%2Ctriage&template=rfc.yml&title=RFC%3A+TITLE)?
158
+
- Does the match our [Tenets](https://awslabs.github.io/aws-lambda-powertools-python/latest/#tenets)?
159
+
- Does the proposal address the use case? If so, is the recommended usage explicit?
160
+
- Does it focus on the mechanics to solve the use case over fine-grained implementation details?
161
+
- Can anyone familiar with the code base implement it?
162
+
- If approved, are they interested in contributing? Do they need any guidance?
163
+
- Does this significantly increase the overall project maintenance? Do we have the skills to maintain it?
164
+
- If we can't take this use case, are there alternative projects we could recommend? Or does it call for a new project altogether?
163
165
164
166
When necessary, be upfront that the time to review, approve, and implement a RFC can vary - see [Contribution is stuck](#contribution-is-stuck). Some RFCs may be further updated after implementation, as certain areas become clearer.
165
167
@@ -199,11 +201,11 @@ Edit the respective PR title and update their [labels](#labels). Then run the [R
199
201
200
202
The best part comes now. Replace the placeholder `[Human readable summary of changes]` with what you'd like to communicate to customers what this release is all about. Always put yourself in the customers shoes. For that, these are some questions to keep in mind when drafting your first or future release notes:
201
203
202
-
* Can customers understand at a high level what changed in this release?
203
-
* Is there a link to the documentation where they can read more about each main change?
204
-
* Are there any graphics or code snippets that can enhance readability?
205
-
* Are we calling out any key contributor(s) to this release?
206
-
- All contributors are automatically credited, use this as an exceptional case to feature them
204
+
- Can customers understand at a high level what changed in this release?
205
+
- Is there a link to the documentation where they can read more about each main change?
206
+
- Are there any graphics or code snippets that can enhance readability?
207
+
- Are we calling out any key contributor(s) to this release?
208
+
- All contributors are automatically credited, use this as an exceptional case to feature them
207
209
208
210
Once you're happy, hit `Publish release`. This will kick off the [Publishing workflow](https://github.com/awslabs/aws-lambda-powertools-python/actions/workflows/publish.yml) and within a few minutes you should see the latest version in PyPi, and all issues labeled as `pending-release` will be notified.
209
211
@@ -240,6 +242,7 @@ Actions that negatively impact the project will be handled by the admins, in coo
240
242
In 2023, we will revisit this. We need to improve our understanding of how other projects are doing, their mechanisms to promote key contributors, and how they interact daily.
241
243
242
244
We suspect this process might look similar to the [OpenSearch project](https://github.com/opensearch-project/.github/blob/main/MAINTAINERS.md#becoming-a-maintainer).
245
+
243
246
## Common scenarios
244
247
245
248
These are recurring ambiguous situations that new and existing maintainers may encounter. They serve as guidance. It is up to each maintainer to follow, adjust, or handle in a different manner as long as [our conduct is consistent](#uphold-code-of-conduct)
0 commit comments