Skip to content

docs(governance): allow community to suggest feature content #1593

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
56 changes: 56 additions & 0 deletions .github/ISSUE_TEMPLATE/share_your_work.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,56 @@
name: I Made This (showcase your work)
description: Share what you did with Powertools 💞💞. Blog post, workshops, presentation, sample apps, etc.
title: "[I Made This]: <TITLE>"
labels: ["community-content"]
body:
- type: markdown
attributes:
value: Thank you for helping spread the word out on Powertools, truly!
- type: input
id: content
attributes:
label: Link to your material
description: |
Please share the original link to your material.

*Note: Short links will be expanded when added to Powertools documentation*
validations:
required: true
- type: textarea
id: description
attributes:
label: Description
description: Describe in one paragraph what's in it for them (readers)
validations:
required: true
- type: input
id: author
attributes:
label: Preferred contact
description: What's your preferred contact? We'll list it next to this content
validations:
required: true
- type: input
id: author-social
attributes:
label: (Optional) Social Network
description: If different from preferred contact, what's your preferred contact for social interactions?
validations:
required: false
- type: textarea
id: notes
attributes:
label: (Optional) Additional notes
description: |
Any notes you might want to share with us related to this material.

*Note: These notes are explicitly to Powertools maintainers. It will not be added to the community resources page.*
validations:
required: false
- type: checkboxes
id: acknowledgment
attributes:
label: Acknowledgment
options:
- label: I understand this content may be removed from Powertools documentation if it doesn't conform with the [Code of Conduct](https://aws.github.io/code-of-conduct)
required: true
2 changes: 1 addition & 1 deletion .github/ISSUE_TEMPLATE/support_powertools.yml
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
name: Support Lambda Powertools (become a reference)
description: Add your organization's name or logo to the Lambda Powertools documentation
title: "[Support Lambda Powertools]: <your organization name>"
labels: ["customer_reference"]
labels: ["customer-reference"]
body:
- type: markdown
attributes:
2 changes: 2 additions & 0 deletions MAINTAINERS.md
Original file line number Diff line number Diff line change
@@ -94,6 +94,8 @@ These are the most common labels used by maintainers to triage issues, pull requ
| github-actions | Changes in GitHub workflows | PR automation |
| github-templates | Changes in GitHub issue/PR templates | PR automation |
| internal | Changes in governance, tech debt and chores (linting setup, baseline, etc.) | PR automation |
| customer-reference | Authorization to use company name in our documentation | Public Relations |
| community-content | Suggested content to feature in our documentation | Public Relations |

## Maintainer Responsibilities