chore: add maintainers handbook #62
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
svozza
reviewed
Jun 4, 2025
Co-authored-by: Stefano Vozza <[email protected]>
svozza
approved these changes
Jun 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Changes
This PR adds a maintainer handbook document at the root of the project that can be used as reference by maintainers and contributors to understand how we want to operate in this project.
Specifically, there are mentions on how we triage and categorize issues, their lifecycle, and their labels as well as the behaviors we're expected to uphold as maintainers.
Some of the high level content has been lifted from other maintainers docs in the TS & Python Powertools for AWS repositories, but things like labels and issues have been customized to fit this smaller and more agile project.
One section related to releases has been left as placeholder and will be filled as part of #57.
Issue number: closes #60
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.