Replace IRC with Discord
Discord has more users. IRC traffic has ground to a halt.
Signed-off-by: Bruce Mitchell <bruce.mitchell@linux.vnet.ibm.com>
Change-Id: I3020f974de963bfdd74c2afbd64cd9e200a4be91
diff --git a/MAINTAINERS b/MAINTAINERS
index eea7400..1e4e918 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17,7 +17,7 @@
Section entries are structured according to the following scheme:
- X: NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>
+ X: NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>
X: ...
.
.
@@ -27,10 +27,10 @@
organization; FILE_PATH is a file path within the repository, possibly with
wildcards; X is a tag of one of the following types:
- M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
+ M: Denotes maintainer; has fields NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>;
if omitted from an entry, assume one of the maintainers from the
MAINTAINERS entry.
- R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <IRC_USERNAME!>;
+ R: Denotes reviewer; has fields NAME <EMAIL_USERNAME@DOMAIN> <DISCORD_USERNAME!>;
these people are to be added as reviewers for a change matching the repo
path.
F: Denotes forked from an external repository; has fields URL.
@@ -50,7 +50,7 @@
- Patches must not have an unresolved -1 vote by any maintainer.
- Patches should have all maintainers added for visibility.
- Patches should include unit tests where possible.
- - Feel free to ping on IRC about patches that look good but have not
+ - Feel free to ping on DISCORD about patches that look good but have not
received +2
Design approval rules: