RFC-0002: Discord Community Channel Update #4
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,29 @@ | ||
| --- | ||
| title: An RFC | ||
| date: "YYYY-MM-DD" | ||
| author: An Author | ||
| type: <Organisation|Discord> | ||
| --- | ||
|
|
||
| # Summary | ||
|
|
||
| A short introduction to the intentions of the RFC | ||
|
|
||
| If someone only reads this far, what do you want them to know? | ||
|
|
||
| # Goal | ||
|
|
||
| What problems are you trying to solve? What problems are you not trying to solve? | ||
|
|
||
| # Background & Motivation | ||
|
|
||
| What is the current state or process? Why is this change being proposed? | ||
|
|
||
| # Resolution | ||
|
|
||
| Describe the proposed solution to the achieve the goal. | ||
|
|
||
| Where relevant this RFC should be submitted with the relevant changes to | ||
| supporting documentation or configuration, e.g. if the resolution is related to | ||
| Discord, then it's [configuration file](./discord/config.yml) should also be | ||
| updated. |
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,46 @@ | ||
| --- | ||
| title: An RFC Schema | ||
| date: "2022-08-05" | ||
| author: Alex Scotton | ||
| type: Organisation | ||
| --- | ||
|
|
||
| # Summary | ||
|
|
||
| Introduce a schema and process for handling RFCs within the community. | ||
|
|
||
| # Schema | ||
|
|
||
| This document represents the schema for a nor(DEV): RFC in some strange | ||
| self-propagating nature. | ||
|
|
||
| Updates to the schema will occur in subsequent RFCs if and when required. | ||
| An example of the current schema is [at the root of this repository](../RFC.md). | ||
| The document should then be referred to when proposing a new RFC. | ||
|
|
||
| [YAML front matter](https://assemble.io/docs/YAML-front-matter.html) should be | ||
| used to provide metadata for the RFC. The body of the RFC is currently open to | ||
| the author's discretion but should be used to explain the change desired. | ||
|
|
||
| ```yml | ||
| --- | ||
| title: An RFC | ||
| date: "2022-08-05" | ||
| author: An Author | ||
| type: <Organisation|Discord> | ||
| --- | ||
| ``` | ||
|
|
||
| If the RFC proposal includes updates to features already tracked within this | ||
| repository, then the [Pull Request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests) | ||
| should also include these changes when relevant or possible. | ||
|
|
||
| # Process | ||
|
|
||
| The process for accepting and implementing RFCs is: | ||
|
|
||
| 1. Create Pull Request (or remove the draft status from the PR) | ||
| 2. RFC is open for discussion | ||
| 3. The RFC is merged and applied given: | ||
| - All (upto a max of 5) colloborators have approved | ||
| 4. The RFC is applied by the admin team and "merged" |
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| --- | ||
| title: Discord Community Channel Update | ||
| date: "2022-09-03" | ||
| author: Will Corrigan, Alex Scotton | ||
| type: Discord | ||
| --- | ||
|
|
||
| # Summary | ||
|
|
||
| Ensuring Discord channels are fit-for-purpose, and ensuring seperation between | ||
| support & social conversation. | ||
|
|
||
| _This RFC is being submitted on behalf of Will by Alex, the changes described | ||
| are his_ | ||
|
|
||
| # Goal | ||
|
|
||
| Make dedicated spaces for conversation around Development & those is search of | ||
| help. | ||
|
|
||
| # Background & Motivation | ||
|
|
||
| The intention behind #development and similar channels is to seek help & advice. | ||
|
|
||
| It is currently used for both discussion and help. It's also quite opinion | ||
| driven. | ||
|
|
||
| # Resolution | ||
|
|
||
| The re-architecture and creation of appropriate channels to help in creating | ||
| this seperation. | ||
|
|
||
| Please see the [updated configuration](../discord/config.yml) contained within | ||
| to review these updates. |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably should be renamed to avoid channel conflict with Social/General. Maybe dev-general (but then that throws off some kind of naming convention, although not that fussy to care).