Maintenance: move RFCs to Discussions

[dreamorosi]

Summary

Currently we handle RFCs as issues - this works, especially thanks to issue forms/templates.

RFCs however are, by design, intended to have frequent back and forth between different threads. The current design of Issues in GitHub is an essentially append-only thread of messages. This comes with the assumption that the conversation is linear, which is not always the case for RFCs.

Why is this needed?

By moving RFCs to GitHub Discussions we might be able to have a more productive discussion because: 1/ it's possible to reply to a message right under it without having to quote it in a new one, 2/ it's possible to make the discussion progress on different areas/threads without creating noise for other threads.

Which area does this relate to?

Governance

Solution

Move the template from the .github/ISSUE_TEMPLATE directory to the .github/DISCUSSION_TEMPLATE one, and make slight changes to accommodate the syntax required for discussion forms.

Acknowledgment

• This request meets Powertools for AWS Lambda (TypeScript) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Python, Java, and .NET

Future readers

Please react with 👍 and your use case to help us understand customer demand.

[github-actions]

⚠️ COMMENT VISIBILITY WARNING ⚠️

This issue is now closed. Please be mindful that future comments are hard for our team to see.

If you need more assistance, please either tag a team member or open a new issue that references this one.

If you wish to keep having a conversation with other community members under this issue feel free to do so.

[github-actions]

This is now released under v2.12.0 version!